[Script] WME Add-Ons V0.45 ==> Features moved in WME Toolbox

[zannax]

Hi all,
I've granted edit/commit access to the google repository for some guys who recently provides me good patches. I hope they will provide you the next release very soon.

Hi all,
thank Gill

There's new version 0.45, changelog:

1) added new beta editor url
2) added link to other maps: Google, Google Beta, Bing, ViaMichelin
3) injectit.user.js now works under Chrome+TamperMonkey & FireFox+GreaseMonkey just click on link, in Chrome with TamperMonkey no more download with drag&drops, autoupdate, manual update of all script with 1 click

v0.45 for Chrome+TamperMonkey & FireFox+GreaseMonkey:
https://wme-addons.googlecode.com/svn/b ... it.user.js

v0.45 for Chrome CRX:
https://wme-addons.googlecode.com/svn/b ... addons.crx

PS:
I use TamperMonkey with all most popular WME extensions

Schermata 07-2456493 alle 11.38.58.png

(163.96 KiB) Downloaded 2518 times

[HandofMadness]

NVM, got it working. Had to delete and reinstall ALL extensions to get them working again.

[HandofMadness]

Odd, it was working for me yesterday. But today its not been working on either of my two computers.

[gdu1971]

Hi all,
I've granted edit/commit access to the google repository for some guys who recently provides me good patches. I hope they will provide you the next release very soon.
I'm not anymore able to work on this topic but I'm really glad to see how it is highly requested to be maintained (=> message to WME maintainers )
Do not hesitate to send me your requests to have access to the main repository, it's better than publishing your own code in your own side even if you're create branches.
Please remember that the plugin is published under the MIT licence => don't forget to add your signature when you're submitting patches.
I'm still there to answer and discuss about the features and the way to solve issues by mail for those who knows how to reach me .
Regards,
Gilles

[OyyoDams]

I haven't tested with tampermonkey. But the crx extension works directly in Chrome. I've name it 0.44 to avoid some errors, but basically it's the code of version 0.43.

[miole67]

I've updated this addon to work with the new beta editor (features remain exactly the same):

Firefox: http://www.wazeteam.com/firefox/injectit.user.js

Chrome: http://www.wazeteam.com/chrome/WME_Addons.crx

Thank you for your work.
I had installed WME addons. 0.44 in Chrome under tampermonkey taken from the first topic of this discussion that gave problems with the new address of the WME beta.
Now is the fixed version does not work with the 0.43 and tampermonkey, but only as an extension of Chrome.
It 'the same thing?

[OyyoDams]

I've updated this addon to work with the new beta editor (features remain exactly the same):

Firefox: http://www.wazeteam.com/firefox/injectit.user.js

Chrome: http://www.wazeteam.com/chrome/WME_Addons.crx

[gohamstergo]

How do you edit a .crx file? I thought the whole point of those is that you can't edit them.

edited the userscript, not the crx

[beffl]

Would you please add in the header of the scipt the new editor url:

Code: Select all

// @include             <new url>

THX, Stefan

Talking to me? Already did that, still doesn't load.

Sorry .... it was a little bid unclear from my side .... I ment gdu1971 and wanted him to change the header of the script so that all can suffer from it.

Stefan

[Mike-1323]

How do you edit a .crx file? I thought the whole point of those is that you can't edit them.

Dunno how to do it to a crx file, but when installed the .js files are at:
C:\Users\<user>\AppData\Local\Google\Chrome\User Data\<Default|user>\Extensions\
The folders match the ID's that show up on the extensions tab in Chrome when developer mode is enabled.

I've changed some of the extensions to @include the new beta url but that doesn't seem to be effective.