|
|
| (391 tussenliggende versies door 3 gebruikers niet weergegeven) |
| Regel 1: |
Regel 1: |
| The Waze community has created the following plugins/extensions/addons for use in the Waze web-based environments. (Client-side possible?)
| | {{TopLine}} |
| ==Developing==
| | <languages /> |
| ===JavaScript Development Best Practices for Waze Extensions and Scripts===
| | <translate> |
| ====Best Practices====
| | ==Wiki Vertaling== <!--T:6--> |
| All of the normal best practice guidelines apply, some references:
| |
| * [http://www.javascripttoolbox.com/bestpractices/ JavaScript Toolbox]
| |
| * [http://sarfraznawaz.wordpress.com/2012/02/19/842/ Sarfraz Ahmed's Blog]
| |
| To help with this, run your code through some useful analyzers to head off potential problems, like:
| |
| * [http://www.jshint.com JSHint]
| |
| * [http://www.jslint.com JSLint]
| |
| * [https://developers.google.com/closure/ JavaScript Closure Tools]
| |
| ====jQuery==== | |
| WME is built on jQuery. This makes it easy to manipulate, access properties, and directly reference the built-in Waze objects underlying WME. Using jQuery enables tighter integration into WME, reduces code, and builds on what is already there. As of now, WME is running jQuery 1.7 vanilla, which does not include any optional modules like jQuery UI.
| |
| ====Variable & Function Prefix====
| |
| To ensure that your code is safe from collision with other scripts and extensions, please prefix all variables and functions with a prefix of your choosing (this includes local variables and global variables, since your entire script is made public when it is loaded in WME). An example would be instead of naming a variable "version", name it "coolscript_version" instead, if your script is named "Cool Script".
| |
| ====Code Encapsulation====
| |
| While not technically code encapsulation in the object oriented sense, please encapsulate all code with a function, except requisite bootstrap code and initializer calls.
| |
| ====UserScript Bootstraping====
| |
| When creating user scripts for Greasemonkey, Chrome, or TamperMonkey, use the following bootstrap at the start of your script. timbones did extensive research on this to make sure it is completely cross-browser compatible. Not only will it work in GreaseMonkey, Chrome, and TamperMonkey, but can also be dropped into a Safari Extension without any recoding.
| |
| ---- | |
| <pre>
| |
| function coolscript_bootstrap()
| |
| {
| |
| var bGreasemonkeyServiceDefined = false;
| |
|
| |
|
| try
| | <!--T:7--> |
| {
| | ===Wiki Vertaal Extensie=== |
| if (typeof Components.interfaces.gmIGreasemonkeyService === "object")
| | De vertaling van onze [[Wiki]] pagina's gebeurt met behulp van de [https://www.mediawiki.org/wiki/Help:Extension:Translate Translate extension]. |
| {
| | <br /> |
| bGreasemonkeyServiceDefined = true;
| | * Onze [[Wiki]] pagina's die beginnen met de tag <i>"languages"</i> tonen in de taalselectiebalk de beschikbare taalversies. |
| }
| | * De basistekst van elke pagina, die vertaald moet worden, is ingesloten in <i>''translate''</i> tags. |
| }
| | * De extensie splitst de aangegeven basistekst op in eenheden van alineagrootte en creëert er een berichtengroep voor. Eén pagina zou één <i>berichtgroep</i> zijn, waarbij, in de eenvoudigste vorm, elke paragraaf één <i>bericht</i> in die groep zou zijn. |
| catch (err)
| | * Je kan links automatisch naar de voorkeurstaalversie van de gebruiker laten gaan (alleen) als deze bestaat, door links te gebruiken in de vorm van een paginalink met <i>Speciaal:MijnTaal/Paginanaam</i>. |
| {
| |
| //Ignore.
| |
| }
| |
| if ( typeof unsafeWindow === "undefined" || ! bGreasemonkeyServiceDefined)
| |
| {
| |
| unsafeWindow = ( function ()
| |
| {
| |
| var dummyElem = document.createElement('p');
| |
| dummyElem.setAttribute ('onclick', 'return window;');
| |
| return dummyElem.onclick ();
| |
| } ) ();
| |
| }
| |
| /* begin running the code! */
| |
| coolscript_init();
| |
| }
| |
|
| |
|
| function coolscript_init()
| |
| {
| |
| //run your code here
| |
| }
| |
|
| |
|
| // [...]
| | <!--T:8--> |
| // then at the end of your script, call the bootstrap to get things started
| | ===Vertaalproces=== |
| coolscript_bootstrap();
| | * Wanneer de tekst gereed is kan een pagina gemarkeerd worden voor vertaling. De Wiki-pagina [https://wazeopedia.waze.com/wiki/Netherlands/Special:PageTranslation Page translation] vermeldt de pagina's die moeten worden gemarkeerd voor vertaling en de pagina's die momenteel vertaald kunnen worden. |
| </pre> | | <br /> |
| ---- | | '''Een pagina vertalen''' |
| ==Editing== | | * Selecteer een pagina die is gemarkeerd voor vertaling om te vertalen. Op de pagina wordt bovenaan gecentreerd de tekst "Translate this page" weergegeven. Klik op deze tekst. |
| ===WME Add-Ons=== | | * Er wordt een venster weergegeven met "Berichtgroep Alles > plus de paginatitel. Selecteer de doeltaal via de vervolgkeuzelijst die beschikbaar is rechtsboven in het venster. |
| '''CAUTION!''' | | * Klik op elk berichtgroepvak en vertaal de tekst. Klik op '''Vertaling opslaan''' als u klaar bent. |
| Please do not use this tool unless you are a very experienced Waze editor and fully understand the ramifications of using this tool. Even experienced editors should learn how to use it only on very smaller areas at a time. Read the forum linked below to better learn how to use it and to understand the ramifications of its use!
| | * Doe dit voor alle berichtgroepvakken. |
| | * Nadat je je vertaling hebt opgeslagen, is de pagina beschikbaar in de doeltaal. |
| | * Klik op de knop '''Review''' via het potloodpictogram. Als u de cursor over de vertaalde tekst beweegt, kunt u nog steeds wijzigingen aanbrengen in de vertaalde tekst.<br /> |
|
| |
|
| This is a plugin/extension which displays a table of all the current view's country, state, city and street names. You can select all segments of a street using a custom button. This extension makes it very easy to find and fix incorrect cities and states (in the U.S.) and bad street names. The tool has many other capabilities as well.
| | <!--T:9--> |
| | | ===Links=== |
| Since this tool is often updated, please see the forum linked below for a full list of features, download links, installation instructions, and discussion.
| | * [https://www.mediawiki.org/wiki/Help:Extension:Translate/Page_translation_example Voorbeeld van paginavertaling] |
| | | * [https://wazeopedia.waze.com/wiki/Global/Help:How_to_use_the_Translation_tool Hoe de vertaaltool te gebruiken] |
| [http://www.waze.com/forum/viewtopic.php?p=334169 "(Script) WME Add-Ons"]
| | </translate> |
| | | {{Bottomline}} |
| ''There is a previous version of this tool called "WME Extended Tools". Due to changes to the Waze Map Editor, its functionality was broken, and the decision was made to re-write the tool from scratch. '''WME Extended Tools is no longer supported, should be uninstalled, and should no longer be used.'''
| |
| | |
| ===Street to River===
| |
| [[image:street-created-selected-and-named.png|thumb|Street created, selected and named]]
| |
| [[image:created-river-after-helper-street-deleted.png|thumb|River created and helper street deleted]]
| |
| | |
| The script is designed as a helper for creating river/railroad landmarks for the free waze navigation system. The script transforms the the geometry of a new unsaved street to a river or railroad landmark. You can predefine the width and the name for the new landmark in the form of a special street name.
| |
| | |
| Mini howto:
| |
| * install this script as greasemonkey script or chrome extension
| |
| * draw a new street but do not save the street
| |
| * add and apply a street name to define the rivers name and width. This step is optional.
| |
| : Example: ''20m Spree'' creates a 20 meters wide river named ''Spree''
| |
| * Select the helper street
| |
| * Click the '''Street to river''' or '''Street to railroad''' button
| |
| * Delete the helper street
| |
| * Edit the new landmark as you like. You can even set the landmark to another type. [http://world.waze.com/livemap/?zoom=9&lat=52.45873&lon=6.17407&layers=BTTTTT "Here"] it is used to mark a railroad (using landmark type 'other'.
| |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| Examples of rivers created by the script:
| |
| * Spree: https://world.waze.com/cartouche/?zoom=2&lat=52.29672&lon=14.25296&layers=BTFFFTTTTFTTTFTTTTT
| |
| * Nottekanal: https://world.waze.com/cartouche/?zoom=1&lat=52.22414&lon=13.48316&layers=BTFFFTTTTFTTTFTTTTT | |
| | |
| Download the script from: [http://userscripts.org/scripts/show/122049 userscripts.org]
| |
| (Firefox requires the [https://addons.mozilla.org/en-US/firefox/addon/greasemonkey/ Greasemonkey Addon].)
| |
| | |
| Discussion for the script can be found in the forum topic: [http://www.waze.com/forum/viewtopic.php?f=10&t=14550 "Greasemonkey script for easy river drawing"]
| |
| | |
| ===Highlights for Landmarks and Segments===
| |
| This script adds color highlighting to segments and landmarks according to their status and type. The highlighting of segments is likely to be most useful, for it shows locked and un-named roads.
| |
| | |
| > [http://userscripts.org/scripts/show/141050 WME Color Highlights] script at userscripts.org.
| |
| | |
| [[Image:Wme-highlights.png]]
| |
| | |
| ''Chrome users will need to download this to their PC, and then drag '141050.user.js' into the Extensions tab.''
| |
| ''Firefox requires the [https://addons.mozilla.org/en-US/firefox/addon/greasemonkey/ Greasemonkey Addon].''
| |
| | |
| Discussion of the script can be found in the forum: [http://www.waze.com/forum/viewtopic.php?f=10&t=25806 Script to add Highlights for Segments & Landmarks]
| |
| ===WazeBar===
| |
| WazeBar is an alternative menu bar for WME that also integrates other scripts, making them available on Safari. While this is (as of yet) mainly geared to bring extensions to Mac users, making WazeBar cross-browser is being evaluated for future implementation.
| |
| WazeBar provides the following features:
| |
| * Full-screen mode
| |
| * Alternative dark theme
| |
| * Integration of WME Color Highlights and UR Overview scripts.
| |
| More features and additional script integrations are being worked on. You can get in on the discussion here: [http://www.waze.com/forum/viewtopic.php?f=10&t=28031]. The Safari Extension can be downloaded here: [http://www.rocking-mm.com/WazeBar/].
| |
| | |
| ==LiveMap==
| |
| ===LiveMap Navigation List===
| |
| This plugin/extension works with the Waze LiveMap only. After installing, create a route in the LiveMap by clicking on the origin and destination. Once the LiveMap requests the route, the left side area will switch from the current events scrolling list, to a navigation list of the route. Multiple routes are displayed. Each turn is clickable and the map will zoom to that location.
| |
| | |
| [http://userscripts.org/scripts/show/118389 Download the LiveMap Navigation List] (Firefox requires the [https://addons.mozilla.org/en-US/firefox/addon/greasemonkey/ Greasemonkey Addon].)
| |
| | |
| ''Chrome users may need drag the file downloaded to their PC into the Chrome Extensions tab.''
| |
| | |
| [http://www.waze.com/forum/viewtopic.php?f=8&t=13511 Discussion and feedback for this addon] (Forum)
| |
