# New script: User Request Overview

**URL:** https://www.waze.com/discuss/t/new-script-user-request-overview/109872
**Category:** United Kingdom
**Created:** [September 8, 2012, 6:19pm UTC](https://www.waze.com/discuss/t/new-script-user-request-overview/109872 "2012-09-08T18:19:48Z")
**Posts on this page:** 20
**Page:** 1

<div class="post-metadata">

### Author: ![Twister-UK](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/t/1BAB50/32.png) [@Twister-UK](https://www.waze.com/discuss/u/Twister-UK)
#### Post date: [September 8, 2012, 6:19pm UTC](https://www.waze.com/discuss/t/new-script-user-request-overview/109872/1 "2012-09-08T18:19:48Z")

</div>

Just a quick hack to implement something I’ve been trying to find the time to work on for ages… And surprisingly, given my track record for script development, it doesn’t have anything to do with the Ordnance Survey :mrgreen:

In a nutshell, it simply adds a single status line to the bottom of the WME window, which will then display the type and (where available) any additional text added by the user, for the UR marker currently under the mouse pointer. This provides a quick way to check URs to see if if they’re ones that sound as if they do or don’t need urgent attention, or if they’ve been marked as for the attention of someone else and need to be left well alone for now, without all the hassle of having to click on the marker, wait for WME to relocate the map view, read the type/description there, and then try and find where you were on the map prior to clicking the UR…

Tested with FF and Chrome on the public version of WME

[http://userscripts.org/scripts/show/145186](http://userscripts.org/scripts/show/145186)

---

<div class="post-metadata">

### Author: ![dknight212](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/d/0099FF/32.png) [@dknight212](https://www.waze.com/discuss/u/dknight212)
#### Post date: [September 10, 2012, 6:39am UTC](https://www.waze.com/discuss/t/new-script-user-request-overview/109872/2 "2012-09-10T06:39:28Z")

</div>

Thanks. I can’t get it to work on chromium for some reason but I’ll continue playing with it.

Just as an aside, is it possible to do something similar for speed cameras?

---

<div class="post-metadata">

### Author: ![dknight212](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/d/0099FF/32.png) [@dknight212](https://www.waze.com/discuss/u/dknight212)
#### Post date: [September 10, 2012, 6:40am UTC](https://www.waze.com/discuss/t/new-script-user-request-overview/109872/3 "2012-09-10T06:40:19Z")

</div>

and yes, I’m using latest public WME.

---

<div class="post-metadata">

### Author: ![dknight212](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/d/0099FF/32.png) [@dknight212](https://www.waze.com/discuss/u/dknight212)
#### Post date: [September 10, 2012, 6:45am UTC](https://www.waze.com/discuss/t/new-script-user-request-overview/109872/4 "2012-09-10T06:45:40Z")

</div>

Very odd. I disabled all other WME scripts then re-enabled them one by one hoping to see if there was a clash. And now, your script works, with all the others too!

thanks

---

<div class="post-metadata">

### Author: ![loadbang](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/l/FD804B/32.png) [@loadbang](https://www.waze.com/discuss/u/loadbang)
#### Post date: [September 10, 2012, 12:17pm UTC](https://www.waze.com/discuss/t/new-script-user-request-overview/109872/5 "2012-09-10T12:17:27Z")

</div>

> [@dknight212](#):
>
> Thanks. I can’t get it to work on chromium for some reason but I’ll continue playing with it.

User scripts can no longer be installed in Chrome/Chromium from third party web sites or local files, they have to be installed from the Chrome Web Store. The Chrome Web Store does not allow for JS scripts a the moment so Twister cannot upload them, unless he makes them in to a Chrome addon.

Firefox is your only solution at the moment, or revert to an older version of Chrome/Chromium.

EDIT: [http://www.chromium.org/administrators/policy-list-3#ExtensionInstallSources](http://www.chromium.org/administrators/policy-list-3#ExtensionInstallSources)

---

<div class="post-metadata">

### Author: ![dknight212](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/d/0099FF/32.png) [@dknight212](https://www.waze.com/discuss/u/dknight212)
#### Post date: [September 10, 2012, 12:24pm UTC](https://www.waze.com/discuss/t/new-script-user-request-overview/109872/6 "2012-09-10T12:24:06Z")

</div>

Simon

Thanks, did you read my last post? For the record, I have had no problem installing scripts direct from [userscripts.org](http://userscripts.org). I’m sure chromium will change this at some future point.

David using Tapatalk

---

<div class="post-metadata">

### Author: ![Twister-UK](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/t/1BAB50/32.png) [@Twister-UK](https://www.waze.com/discuss/u/Twister-UK)
#### Post date: [September 10, 2012, 2:48pm UTC](https://www.waze.com/discuss/t/new-script-user-request-overview/109872/7 "2012-09-10T14:48:26Z")

</div>

> [@dknight212](#):
>
> Just as an aside, is it possible to do something similar for speed cameras?

Possibly, I haven’t looked at the visible data structures provided for cameras, but I guess the necessary data would be available to a third-party script in the same way as for URs. What bits of data would you be interested in seeing just by hovering over the camera icon?

Can I ask why you’re interested in having camera data shown as well? WME doesn’t do the whole annoying pan-zoom-disorientate the user thing when you click on a camera icon, so as far as I can see from a quick reminder of how the camera layer works (until today, I can’t recall the last time I used it…) the only thing to be gained by adding camera support to the script is removing the need to click.

Please note that I’m not saying this as a way of trying to get out of doing the work, I’m simply genuinely interested in understanding how other people use my code and, given my love for programming (especially when there’s no project managers breathing down my neck wondering where the next release is!), I’m quite happy to spend the time hacking out code for any suggestions that come my way if I think there’s any chance they might be feasible.

---

<div class="post-metadata">

### Author: ![Twister-UK](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/t/1BAB50/32.png) [@Twister-UK](https://www.waze.com/discuss/u/Twister-UK)
#### Post date: [September 10, 2012, 3:00pm UTC](https://www.waze.com/discuss/t/new-script-user-request-overview/109872/8 "2012-09-10T15:00:59Z")

</div>

> [@simonhowes](#):
>
> User scripts can no longer be installed in Chrome/Chromium from third party web sites or local files, they have to be installed from the Chrome Web Store.

Chrome 22.0.1229.39 still allows user scripts to be installed via Tools…Extensions.

---

<div class="post-metadata">

### Author: ![Timbones](https://www.waze.com/discuss/user_avatar/www.waze.com/timbones/32/12290_2.png) [@Timbones](https://www.waze.com/discuss/u/Timbones)
#### Post date: [September 10, 2012, 3:25pm UTC](https://www.waze.com/discuss/t/new-script-user-request-overview/109872/9 "2012-09-10T15:25:15Z")

</div>

> [@Twister\_UK](#):
>
> Chrome 22.0.1229.39 still allows user scripts to be installed via Tools…Extensions.

Yup, just need to drag and drop the script into the Extensions window: chrome://chrome/extensions/ 🙂

---

<div class="post-metadata">

### Author: ![dknight212](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/d/0099FF/32.png) [@dknight212](https://www.waze.com/discuss/u/dknight212)
#### Post date: [September 10, 2012, 3:28pm UTC](https://www.waze.com/discuss/t/new-script-user-request-overview/109872/10 "2012-09-10T15:28:54Z")

</div>

> [@Twister\_UK](#):
>
> > [@dknight212](#):
> >
> > Just as an aside, is it possible to do something similar for speed cameras?
> 
> Possibly, I haven’t looked at the visible data structures provided for cameras, but I guess the necessary data would be available to a third-party script in the same way as for URs. What bits of data would you be interested in seeing just by hovering over the camera icon?
> 
> Can I ask why you’re interested in having camera data shown as well? WME doesn’t do the whole annoying pan-zoom-disorientate the user thing when you click on a camera icon, so as far as I can see from a quick reminder of how the camera layer works (until today, I can’t recall the last time I used it…) the only thing to be gained by adding camera support to the script is removing the need to click.
> 
> Please note that I’m not saying this as a way of trying to get out of doing the work, I’m simply genuinely interested in understanding how other people use my code and, given my love for programming (especially when there’s no project managers breathing down my neck wondering where the next release is!), I’m quite happy to spend the time hacking out code for any suggestions that come my way if I think there’s any chance they might be feasible.

I’m just trying to slow you down on the points front! No, seriously I would love something like the set mph (!) speed to pop up as a tool tip on rollover. It would save a few microseconds when filtering cameras (not something I like to do very often). Maybe also the creator/approver as I know a few problem ones. But this is all very much in the nice to have territory.

---

<div class="post-metadata">

### Author: ![Twister-UK](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/t/1BAB50/32.png) [@Twister-UK](https://www.waze.com/discuss/u/Twister-UK)
#### Post date: [September 10, 2012, 3:54pm UTC](https://www.waze.com/discuss/t/new-script-user-request-overview/109872/11 "2012-09-10T15:54:27Z")

</div>

> [@dknight212](#):
>
> I’m just trying to slow you down on the points front!

No worries there, my daughter is doing a perfectly good job of sabotaging my slog up to the 100K edit mark… I used to be able to get in some useful editing sessions whilst rocking her off to sleep each night, but now that she’s turned 2 she’s a bit more demanding 😑

> [@dknight212](#):
>
> No, seriously I would love something like the set mph (!) speed to pop up as a tool tip on rollover. It would save a few microseconds when filtering cameras (not something I like to do very often). Maybe also the creator/approver as I know a few problem ones.

Ok, that makes sense. The speed popup could also point out where it thinks the speed has been entered in mph rather than kph - now that I’ve started looking at the camera layer, I notice several of the cameras local to me have been set to the numerical mph value rather than the converted kph equivalent…

---

<div class="post-metadata">

### Author: ![dknight212](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/d/0099FF/32.png) [@dknight212](https://www.waze.com/discuss/u/dknight212)
#### Post date: [September 10, 2012, 3:58pm UTC](https://www.waze.com/discuss/t/new-script-user-request-overview/109872/12 "2012-09-10T15:58:04Z")

</div>

Kids huh! My youngest goes to nursery next week which means 3 extra hours a day. Except the wife expects the house to be clean!

---

<div class="post-metadata">

### Author: ![Twister-UK](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/t/1BAB50/32.png) [@Twister-UK](https://www.waze.com/discuss/u/Twister-UK)
#### Post date: [September 10, 2012, 11:30pm UTC](https://www.waze.com/discuss/t/new-script-user-request-overview/109872/13 "2012-09-10T23:30:52Z")

</div>

The camera-aware 0.3 is now available… [http://userscripts.org/scripts/show/145186](http://userscripts.org/scripts/show/145186)

---

<div class="post-metadata">

### Author: ![dknight212](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/d/0099FF/32.png) [@dknight212](https://www.waze.com/discuss/u/dknight212)
#### Post date: [September 11, 2012, 5:42am UTC](https://www.waze.com/discuss/t/new-script-user-request-overview/109872/14 "2012-09-11T05:42:22Z")

</div>

Can’t wait to try!

David using Tapatalk

---

<div class="post-metadata">

### Author: ![dknight212](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/d/0099FF/32.png) [@dknight212](https://www.waze.com/discuss/u/dknight212)
#### Post date: [September 11, 2012, 6:06am UTC](https://www.waze.com/discuss/t/new-script-user-request-overview/109872/15 "2012-09-11T06:06:29Z")

</div>

Very good indeed, just what I wanted!

---

<div class="post-metadata">

### Author: ![Twister-UK](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/t/1BAB50/32.png) [@Twister-UK](https://www.waze.com/discuss/u/Twister-UK)
#### Post date: [September 11, 2012, 10:19pm UTC](https://www.waze.com/discuss/t/new-script-user-request-overview/109872/16 "2012-09-11T22:19:46Z")

</div>

0.4 is now available - [http://userscripts.org/scripts/show/145186](http://userscripts.org/scripts/show/145186)

The UR/camera overview details are now shown in a floating box next to the UR/camera icon rather than in the status bar at the bottom of the WME window. Also, if the UR contains a URL for Timbones’ petrol station checker site, it will be turned into a clickable link with the checker site opening in a new tab.

---

<div class="post-metadata">

### Author: ![Superfraggle](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/s/0099FF/32.png) [@Superfraggle](https://www.waze.com/discuss/u/Superfraggle)
#### Post date: [September 11, 2012, 11:35pm UTC](https://www.waze.com/discuss/t/new-script-user-request-overview/109872/17 "2012-09-11T23:35:44Z")

</div>

Probably not possible without assistance from Waze, but I would love a list of all UR’s in my editable area, so I don’t have to scroll half over England to see if there is anything I can help with.

---

<div class="post-metadata">

### Author: ![dknight212](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/d/0099FF/32.png) [@dknight212](https://www.waze.com/discuss/u/dknight212)
#### Post date: [September 12, 2012, 6:45am UTC](https://www.waze.com/discuss/t/new-script-user-request-overview/109872/18 "2012-09-12T06:45:52Z")

</div>

Love the new version, much easier to see.

---

<div class="post-metadata">

### Author: ![Timbones](https://www.waze.com/discuss/user_avatar/www.waze.com/timbones/32/12290_2.png) [@Timbones](https://www.waze.com/discuss/u/Timbones)
#### Post date: [September 12, 2012, 9:02am UTC](https://www.waze.com/discuss/t/new-script-user-request-overview/109872/19 "2012-09-12T09:02:34Z")

</div>

Nice work, Twister.

Something I was trying months ago was to highlight URs that were off the screen, either in a list, or by adding icons around the edge of the screen to indicate where they might be. I didn’t have much luck then, maybe you can try?

---

<div class="post-metadata">

### Author: ![ncc1701v](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/n/90959C/32.png) [@ncc1701v](https://www.waze.com/discuss/u/ncc1701v)
#### Post date: [September 12, 2012, 8:52pm UTC](https://www.waze.com/discuss/t/new-script-user-request-overview/109872/20 "2012-09-12T20:52:20Z")

</div>

> [@Twister\_UK](#):
>
> 0.4 is now available

Is there a way to get notified of updates besides this forum? RSS feed perhaps? Thanks.

[Next page](https://www.waze.com/discuss/t/new-script-user-request-overview/109872.md?page=2)
