WazeBar v0.0.54 - Safari Extension for Waze Map Editor

[AlanOfTheBerg]

Oh, that's cool! Why didn't you include a screenshot of this badass extension?

First issue I found was that after entering a search in the box, I can't make the list of results go away without clicking on one of them.

Where is the permalink?

The bright yellow highlight (I can't remember what it is for) is on by default. I'd like to be able to have it not highlight neighboring segments all the time when a segment is selected.

Tooltips are needed onmouseover.

Clicking on your username could bring up points and editing rank info.

[AlanOfTheBerg]

1. Cool.
2. Ok. Two suggestions:
2a. Make it a chain-link type icon. I think that's perhaps more universal?
2b. One should be able to get the URL underlying it from the contextual menu "copy link" just like a regular hyperlink. I often have changes pending when I find something I want to permalink, and with the original Permalink, I can easily copy that link without having to save changes first.
2c. The original Permalink at the bottom of the map didn't really take up that much space...
3. Yeah, I figured as much.
4. Cool.
5. Yes, it is there, but I was kinda thinking something would be hiding behind there as there was with the "WazeBar" title. No biggee. Really not necessary, actually.

[AlanOfTheBerg]

This may not be behavior you can change, but when I have an editor window open and in use, and I install the extension, the native Waze elements disappear from the page, but the WazeBar doesn't appear until I reload the page. Usually, so I don't lose my location and because the permalink is gone, I just reload the /editor base URL and it's good.

This is some really solid work, Mike. I am very happy with this overall.

[AlanOfTheBerg]

On another note, I have contacted the developer of ExtTools and am hopeful that they give permission to integrate it.

There are some features which are heavily abused by people just looking for points. I would carefully consider which features to add.

[AlanOfTheBerg]

Superb. Again. Being redundant.

I'm just now looking at this on Win7 as well.

I would like to request the ability to not use the full editing window/full screen. Could you make that an option? Or is it already and I've missed the setting?

The extension fails to work at all on the editor beta (not your fault because you don't have access!) and, in fact, appears to disable the editor altogether.

Is there a line of debug output still enabled on window resize? I cannot resize the window, except for the maximize/restore button. If I try to drag the window larger, I get an alert on mousedown and on mouseup.

[AlanOfTheBerg]

I was going to add that option in the next update, I kind of figured that might be useful. Just to get an idea, what would your impetus be for using the original size instead of full-screen? (Just trying to figure out what the different use-cases are for that.)

Based on what we understand from Waze, the editing window maximum is set on purpose. This viewable area is directly related to server and network load in terms of preparing road images and sending them to the client. If everyone uses a 25% increased editor viewable area, that is potentially a 50% increase in server and/or network load. (There is a lot of caching going on, so 50% is approximate.) I personally have no issue with the smaller editing window and would, for the sake of overall editor/server-side performance, choose to use it as such.

[AlanOfTheBerg]

Here's images comparing

WME


WME Beta

[AlanOfTheBerg]

I'll bet that JavaScript is erroring out in beta, preventing it from continuing to load. What is the beta URL, so I can turn the extension off for beta.

Though it's password protected, I don't want to post. It is listed at the top of Timbones' highlighting userscript.

[AlanOfTheBerg]

Oh, also please post if you are experiencing issues while using the beta editor. (Theoretically the extension shouldn't even be running in the beta editor, but you never know.) If you do suspect an issue, please take a look at the error console output to see if there are any errors.

Why don't you enable it for the beta, too? It seems that your fix for the screen setup in the production editor has also fixed it in the beta. The only thing now is the Toolbar is half there: the Find box shows, but the buttons do not. Also, since it "isn't loading" for the beta, the WazeBar doesn't appear at all. With the number of users so small who can get into the beta editor, I think you should enable it so we can troubleshoot.

[AlanOfTheBerg]

PS: How do you get into the beta program? (Not that I need to be, but I'm always glad to help out and test -- and it would give me full access to the functionality just to ensure everything works right.)

I don't think there is any documentation on that. I've wondered myself at times...