WazeBar v0.0.54 - Safari Extension for Waze Map Editor

[mike-bronner]

Haha , I'm in the US, so the day is just starting here. Probable not for another 6 hours at least, as I have other commitments this morning.

[AlanOfTheBerg]

I think I found a bug: enter "barview, or" for a search. Two results, looking identical will come up. Clicking on or selecting either will not result in the Waze map showing the location, but looks like the search is being re-executed.

(There are two Barview, OR cities separated by a few hundred miles.)

[mike-bronner]

I think I found a bug: enter "barview, or" for a search. Two results, looking identical will come up. Clicking on or selecting either will not result in the Waze map showing the location, but looks like the search is being re-executed.

(There are two Barview, OR cities separated by a few hundred miles.)

Good find! I'll look into that. Behavior is confirmed, I was able to replicate the issue.

[mike-bronner]

How hard will it be to port this to Chrome/Firefox?

I was thinking about this, but will need to do some more research. In theory, all the meat and potatoes is there, it would just need to be wrapped as a userscript.

Rename the .safariextz to .gz and see for yourself . Might just work as is (but I'm not that experienced extension coder, but you seem to be ).

That probably won't work, but you never know. I think the Framework that Safari Extensions are built upon is very different from other toolbars or userscripts like Greasemonkey.

I managed to unpack the .gzip safari extension.
At the Chrome Extensions Page, chrome://chrome/extensions, there is a "Pack extension"...
Help?

Looking into getting this working in Chrome, this requires actually quite a bit of coding, too much for the moment. I have plans for converting this into a UserScript for non-Safari browsers, but that's only once I have this code-base shored up and stable. Sorry for being the bearer of bad news (you could install Safari for Windows -- I know, there isn't any new development for it, but the latest version will support the extension).

[pvaladares]

Installed WazeBar on Safari for Windows and works fine.
Maybe I'll leave Chrome and just start using Safari now

I would suggest to add the shortcuts keys to the label of existing Add Elements:
- Road (I)
- Landmark (U)
- Landmark (O)

[mike-bronner]

Patch 0.0.17 is now out -- more in the initial post.

pvaladares, good point. I'll add that in.

[AlanOfTheBerg]

Patch 0.0.17 is now out -- more in the initial post.

Bug in code:
console.log("Wazebar: error handling was triggered, but error object is empty.";

Missing closing paren.

[pvaladares]

Maybe you could also include the UROverview script from Twister_UK (http://userscripts.org/scripts/show/145186)


Between, I have been reading about porting Safari to Chrome extensions and it seems to be easier to port from Chrome to Safari !

[mike-bronner]

Thanks for the link to that script. I will look into it.

Yes, I have found there is much more documentation on migrating from Chrome to Safari, than the other way around. I believe the reason is that Safari Extensions can be much more than just scripts, but can actually integrate into the browser functionality. Not sure how in-depth Chrome lets their users get with Extensions.

[pvaladares]

Patch 0.0.17 is now out -- more in the initial post.

Bug in code:
console.log("Wazebar: error handling was triggered, but error object is empty.";

Missing closing paren.

In this new version the WazeBar does not show up in the Safari version for Windows
Had to install the previous version (http://www.rocking-mm.com/WazeBar/WazeB ... safariextz)