@Slicer - On s'en sert des deux mais - d'apres tous que j'ai compris - on voulait garder l'ancien PLUS disponibles au bebes, et l'autre un peu cache... comme ca, il faut chercher un peu.

@Everyone else,
Google translate really does a good job just as long as you choose your words carefully! I can serve as the go-between and translator, but am not super connected right now, nor will I be doing much Waze editing in the next few days/weeks (Sidebar: happy to report that the LA freeways and ramps actually look pretty good!).

Things move fast here on the forum, but if someone would be willing to compile a succinct list of questions, observations, statements, etc I'd be able to pull that over to the French forum by end of day today.

WRT the different versions, it seemed to a few of us that it would be valuable to have both the original, less powerful version as well as the newer one available. The broad brush ability to mass change segments concerns me, particularly in the hands of new editors... but any of us have a greatly increased power to really mess up the maps. Thoughts?
Jenni

I've updated the wiki, but with for the advanced version, the links point directly to

waze-papyrus-extended-tools.googlecode.com/svn/trunk/

Not sure what the diff is between pointing there versus

http://code.google.com/p/waze-papyrus-e ... loads/list

although I am sure there is something with "official release" versioning? The problem is that this second source doesn't differentiate between the firefox or chrome versions.

J'ni

GizmoGuy411 wrote:Noticed tonight that the select when using a landmark did not select everything correctly within the landmark.

Jenn, would you be so kind to pass these issues along?

Sent from my Galaxy Nexus using Tapatalk

Gizmo, are you still having this problem? Note that it only selects if the segment is completely enclosed within the landmark...

Not sure if/how you can do it in Chrome, but in ff you can add *.waze.com/editor/* as user setting for the script

New version and new link to Chrome extension.
http://www.waze.com/forum/viewtopic.php ... 06#p141006
No time to update the wiki; can someone else do so?

AlanOfTheBerg wrote:It does some badish things in Chrome now. Previous version worked better, though I don't use it much. After using a landmark to select lots of streets and change city name, the toolbox properties never would change from being associated with the landmark I'd already deleted. Selecting segments, etc. never changed the toolbox until I hit the permalink to refresh.

I've not tried it yet, but will do so and report back to the author with issues.

gettingthere wrote:These tools need to be used with extreme caution.

Agreed. This has been my concern from the start and why I and a few others were trying/hoping to keep the direct link to the code somewhat "buried" in the wiki.

Any suggestions? I can certainly cross-post anything you'd like me to translate - of course, google translate probably works better...

The beast is unleashed, so no chance putting it back in the cage. For those who have also expressed (or just thought about) concern over the ability to do damage with the tools, any thoughts on how to limit?

I know programmers hate to remove functionality, but what if landmark were required? Seems it wouldn't restrict functionality too much but might slow people down a touch.

Again, I am more than happy to try and convey any suggestions over to the developer, or Slicer can probably do so as well...

What zoom level are you at when you select? I've noticed it gets flaky when you are zoomed out.

We don't want to restrict all the tools, just the nuclear ones.

I've used extended tools very little. Almost solely to add city names where none existed. Since the advent of the highlighter tool and the new editor, I haven't touched it.

Unfortunately, it promotes low quality editing even in the hands of responsible users, because they don't get "intimate" with each segment and spy the real problems that cause bad routing. I've spent all week cleaning up after an editor who was apparently using it. From 10,000 feet, the map looks great, but when you get up close, it is a disaster, barely route-able and full of mistakes of names, cities and turns.

If I may make an analogy, in real life we don't give little children high-powered electric tools until they have demonstrated the maturity, wisdom and experience to handle them.