[Greasemonkey] Greasemonkey 0.6.6

[Vectorspace]

Good ideas - GM does use a lot of Tools menu space and moving the items 
into a submenu could help.

On a related note, subdividing the User Script Commands menu might be 
useful too - while I only have one script that makes use of it, I'd 
imagine it could get confusing if there were multiple entries from 
multiple scripts - could each script get a submenu for its commands, or 
maybe a banner name & divider between each scripts commands? The ability 
to write text to the right as well as the left for the command name 
might also be useful (the part where the keyboard shortcuts usually are).

For a more future version (as I imagine it would be a bigger job), some 
kind of version number support? So the version number can somehow be a 
part of the shown script name (both in GM and userscripts.org), without 
it having to have a different name and therefore be considered by GM to 
be a different script?
If that made sense :)

esquifit wrote:
> Hi
>
> first of all, many thanks for the update.
>
> Not sure whether this is the right time to ask for it, but given that
> you are making changes in the UI, I dare to give my opinion about one
> point that I've always perceived as annoying: GM demands too much real
> state from the "tools" menu.  In my view it should take no more than a
> single entry.  The current entries might be reallocated into a submenu
> or somehow integrated into the statusbar icon menu/s.
>
> I think the typical GM user is something of a hacker in miniature; it
> is highly probable that s/he would have a bunch of extensions
> installed, and all they (the extensions) tend to abuse the tools menu.
>  Although there are ways to take control over what is displayed on it,
> it would be better if extensions authors limited its use to the very
> essential.
>
> cheers
> e.
>
> 2006/10/9, Aaron Boodman <zboogs at gmail.com>:
>   
>> On 10/9/06, Henrik Nyh <henrik at nyh.se> wrote:
>>     
>>> Not sure I like the fact that you get the dialog rather than the script
>>> source when navigating to e.g.
>>> http://userscripts.org/scripts/source/1.user.js. I often want to look at
>>> a script's source source rather than install it, and though you can peek
>>> at the source in the dialog, that window is a bit small for extended
>>> reading (though resizable).
>>>       
>> Yeah, I went around and around on this a few times. I would have
>> preferred that clicking "show script source" opened it in the browser
>> with the yellow banner, same as before.
>>
>> But implementing this was a serious PITA and I eventually decided it
>> was better to get this out the door than keep puttering with it. I
>> didn't think about the hash link trick, that's a clever workaround.
>>
>> I need to do a FF 2.0 release really soon. Do people think it's worth
>> continuing to try and make the "show script source" feature open the
>> script in a tab, or should I do that for the next version?
>>
>> - a
>> _______________________________________________
>> Greasemonkey mailing list
>> Greasemonkey at mozdev.org
>> http://mozdev.org/mailman/listinfo/greasemonkey
>>
>>     
> _______________________________________________
> Greasemonkey mailing list
> Greasemonkey at mozdev.org
> http://mozdev.org/mailman/listinfo/greasemonkey
>
>