[Greasemonkey] Greasemonkey 0.6.6

[esquifit]

Hi haven't had the opportunity until now to test the last version.
Overall I find it really good!  However I've run into a couple of
minor problems:

The "Show script source" button is actually a toggle button; it would
be proper either to call it something like "toggle view source" or to
make it display alternate labels depending on whether source code or
script properties are being displayed.

The second remark regarding the UI redesign is relative to the context
menu of the statusbar icon (I had to admit that this is really subtle
and does not deserve much attention).  Assume the role of a new user:
1) Install GM on a fresh profile,
2) Check the context menu, it says "No scripts installed!", which is fine.
3) Go on and install any script *that doesn't apply to the current
page* (this is the normal situation; few, if any, scripts are offered
for download from the same site  the script is supposed to enhance).
4) Check the context menu again: the top item still says "No scripts
installed!", which is wrong, and can be misleading to new users.
5) Now go to the Manage user scripts dialog, and uninstall the script.
6) Check the context menu: the top entry has disappeared, although the
separator still remains.
7) restart FF and check the context menu: "No scripts installed!" is back.

The are variations of these steps that produce similar inconsistent
behaviours.  Again, nothing that deserves a day of struggling with xul
& Co. , except you are in one of those rare moments in which you feel
you will live four hundred years...


2006/10/10, esquifit <esquifit at googlemail.com>:
> 2006/10/9, Anthony Lieuallen <arantius at gmail.com>:
> > On 10/9/2006 6:33 AM, esquifit wrote:
> > > GM demands too much real state from the "tools" menu.
> >
> > Shameless plug: http://firefox-extensions.arantius.com/more+tools+menu
> >
> > Which doesn't really change that, but it does help a bit.
> >
>
> Oh, yes.  As I said before, there is a number of ways to work around this.
>
> 1) Anthony's extension :)
> 2) A direct modification in userChrome to hide unsued items or those
> that can be accessed in alternative ways (context menu, shortcuts,
> options dialog)
> 3) Same a above, but via Stylish
> 4) The userChrome.js extension
> 5) The Menu Editor extension
> 6) Write your own extension
>
>
> In essence, all of them amount to the same. Nevertheless, rather than
> having a problem and a bunch of more or less tricky solutions I'd
> still prefer not having the problem at all ;)
>