[Greasemonkey] Greasemonkey 0.6.6

[Aaron Boodman]

On 10/18/06, Henrik Nyh <henrik at nyh.se> wrote:
> Sure, but e.g.
>         javascript:alert("10" < "2")
> evaluates to true. ;)

Of course you'd want to parse it into a number first if you did this.

> I think the simplest and most useful thing would be to only consider
> values containing some numerical value (and parsing out that value,
> comparing it as a number). Other values are ignored, as though there was
> no value specified.

Right now I don't have any use in mind for the numerical information,
the version is just a label. Even if someday there is a script
autoupdating service, you only need numbers if you want to put into
place a policy like: autoupdate silently for minor version changes and
ask the user for major version changes. I don't see user scripts every
having this complex of a versioning scheme, but I could be wrong.

I like Henrik's point that if we ever want to do that, we could just
start doing parseVersion() on the string.

I really want to be able to call versions of my script "ducky". That
would the h0t.

On 10/18/06, Henrik Nyh <henrik at nyh.se> wrote:
> Monkey >
>         + Script one
>                 + Enabled
>                 --
>                 Some command
>                 Some other command
>           Script two
>                   Enabled
>         --
>         New User Script
>         Manage User Scripts...
>         --
>         + Enabled

The only thing is that if the script doesn't have any commands (most
scripts) then there will only be one option in the pull out --
enabled/disabled, which might look silly.

Hrm.

> Tools > Greasemonkey >
>        Install, manage etc
>        --
>        [Script one]
>        Command one
>        Command two
>        --
>        [Script two]
>        Command three
>
> where [] represents inactive/grayed out.

Would rather the above solution than this one. I always thought the
disabled menu items used as dividers was a pretty ugly hack.

- a