Second attempt: Greasemonkey 0.6.6.20061015.0

Here goes. Quite a few changes from 0.6.6.20061008.0:

* Got rid of the little textbox for viewing script source.
Now, View
Script Source opens the script in a tab. The tab gets the
same yellow
install banner that it did before.

* Moved greasemonkey tools menu options into a single menu.

* Made "Install this user script" tools menu
option only visible when
actually viewing a script (I remember several new users were
always
confused by this).

* Made the "install user script" option in context
menu bold to
indicate that it is the default option.

* Added "view script source" to context menu when
right-clicking on a
user script link. This goes straight to the script source in
a tab,
instead of popping up the install dialog. Should be useful
for
advanced users and developers.

* Improved animation of "foobar.user.js installed
successfully..."
status messages. They no longer "bounce" right
before the expansion
starts. That was driving me crazy.

* Added a loading animation where the monkey icon is while a
user
script is loading.

* General cleanup of many global functions in browser.js (no
affect on
functionality)

* Finished internationalization of the entire UI, except the
manage
dialog (I'm not going to improve the manage dialog anymore
since I
plan to replace it in the next release (see forthcoming
roadmap)). I'd
love any patches to finish localization in the existing
languages, or
to localize to new languages.

* Some changes to access keys in tools menu now that they
are in their
own submenu. Hopefully nobody was too in love with the
previous ones.
I think these make more sense.


Let me know what you guys think. I'd like to post this to
addons.mozilla.org soonish, but not until after people have
had
sufficient time to find any bugs.

Thanks,

- a
_______________________________________________
Greasemonkey mailing list
Greasemonkeymozdev.org
http:
//mozdev.org/mailman/listinfo/greasemonkey

I just noticed the "manage user script" item in
the greasemonkey
status menu doesn't work. I'll fix this in the next build.

- a

On 10/16/06, Aaron Boodman <zboogsgmail.com> wrote:
> Here goes. Quite a few changes from 0.6.6.20061008.0:
>
> * Got rid of the little textbox for viewing script
source. Now, View
> Script Source opens the script in a tab. The tab gets
the same yellow
> install banner that it did before.
>
> * Moved greasemonkey tools menu options into a single
menu.
>
> * Made "Install this user script" tools menu
option only visible when
> actually viewing a script (I remember several new users
were always
> confused by this).
>
> * Made the "install user script" option in
context menu bold to
> indicate that it is the default option.
>
> * Added "view script source" to context menu
when right-clicking on a
> user script link. This goes straight to the script
source in a tab,
> instead of popping up the install dialog. Should be
useful for
> advanced users and developers.
>
> * Improved animation of "foobar.user.js installed
successfully..."
> status messages. They no longer "bounce"
right before the expansion
> starts. That was driving me crazy.
>
> * Added a loading animation where the monkey icon is
while a user
> script is loading.
>
> * General cleanup of many global functions in
browser.js (no affect on
> functionality)
>
> * Finished internationalization of the entire UI,
except the manage
> dialog (I'm not going to improve the manage dialog
anymore since I
> plan to replace it in the next release (see forthcoming
roadmap)). I'd
> love any patches to finish localization in the existing
languages, or
> to localize to new languages.
>
> * Some changes to access keys in tools menu now that
they are in their
> own submenu. Hopefully nobody was too in love with the
previous ones.
> I think these make more sense.
>
>
> Let me know what you guys think. I'd like to post this
to
> addons.mozilla.org soonish, but not until after people
have had
> sufficient time to find any bugs.
>
> Thanks,
>
> - a
>
>
>
_______________________________________________
Greasemonkey mailing list
Greasemonkeymozdev.org
http:
//mozdev.org/mailman/listinfo/greasemonkey

The Manage User Scripts item in the monkey icon menu no
longer works. I get
an error:
Error: manageMenuItemClicked is not defined
Source file: chrome://browser/content/browser.xul
Line: 1


On 10/16/06, Aaron Boodman <zboogsgmail.com> wrote:
>
> Here goes. Quite a few changes from 0.6.6.20061008.0:
>
> * Got rid of the little textbox for viewing script
source. Now, View
> Script Source opens the script in a tab. The tab gets
the same yellow
> install banner that it did before.


I like.

* Moved greasemonkey tools menu options into a single menu.


I like.

* Made "Install this user script" tools menu
option only visible when
> actually viewing a script (I remember several new users
were always
> confused by this).


I can only see it when right-clicking a link to a
userscript, not on the
user.js page itself. At first I thought "viewing a
script" meant viewing the
script source. That was a bit confusing but I found it.

* Added "view script source" to context menu when
right-clicking on a
> user script link. This goes straight to the script
source in a tab,
> instead of popping up the install dialog. Should be
useful for
> advanced users and developers.


I like.

* Improved animation of "foobar.user.js installed
successfully..."
> status messages. They no longer "bounce"
right before the expansion
> starts. That was driving me crazy.


I never noticed that problem, but whatever it was I guess
its fixed.

* Finished internationalization of the entire UI, except the
manage
> dialog (I'm not going to improve the manage dialog
anymore since I
> plan to replace it in the next release (see forthcoming
roadmap)). I'd
> love any patches to finish localization in the existing
languages, or
> to localize to new languages.


Good. Things tended to move around a lot when clicking a
script in there.

Let me know what you guys think. I'd like to post this to
> addons.mozilla.org soonish, but not until after people
have had
> sufficient time to find any bugs.
>
> Thanks,
>
> - a
>
>
> _______________________________________________
> Greasemonkey mailing list
> Greasemonkeymozdev.org
> http:
//mozdev.org/mailman/listinfo/greasemonkey
>
>
>
>
_______________________________________________
Greasemonkey mailing list
Greasemonkeymozdev.org
http:
//mozdev.org/mailman/listinfo/greasemonkey

Aaron Boodman wrote:
> Here goes. Quite a few changes from 0.6.6.20061008.0:
> 
> * Got rid of the little textbox for viewing script
source. Now, View
> Script Source opens the script in a tab. The tab gets
the same yellow
> install banner that it did before.
> * Moved greasemonkey tools menu options into a single
menu.

I would strongly suggest moving the User Script Commands out
into the 
same level as Install/Manage/New. I felt they were almost
too deep into 
the menu hierarchy before, and this is definitely too deep
for me to 
want to use them. So my suggestion would be to have e.g.
this under 
Tools > Greasemonkey:

Install User Script...
Manage User Scripts...
New User Script
---
Name of Command #1
Name of Command #2

If there are no commands, there would be nothing under
"New User 
Script", or perhaps some inactive text like "No
commands are available."

Oh, and does anyone use "New User Script"? Also,
what with the 
installation banner and dialog, perhaps the "Install
User Script..." 
menu item is not necessary. If these are both removed, I
don't think 
it'd be very cluttery to put stuff into the Tools top level
again, so:

Extensions
Themes
---
Some other tools
---
Manage User Scripts...
---
Name of Command #1
Name of Command #2

> * Made "Install this user script" tools menu
option only visible when
> actually viewing a script (I remember several new users
were always
> confused by this).

Not so for me. Firefox 1.5.0.7/Mac. Tools > GM >
Install is visible and 
active (not grayed out) for non-scripts (but clicking it in
that case 
does nothing).

> * Made the "install user script" option in
context menu bold to
> indicate that it is the default option.
> 
> * Added "view script source" to context menu
when right-clicking on a
> user script link. This goes straight to the script
source in a tab,
> instead of popping up the install dialog. Should be
useful for
> advanced users and developers.

Right-clicking and selecting "Open link in new
tab" (I realize this != 
View Script Source), or Cmd+clicking for the same effect (on
the Mac) 
will open the install dialog but also a blank tab.

I still miss the previous "ease-of-source", but
since the advanced users 
that care can script around it by adding a dummy hash or
query string, I 
suppose it doesn't really matter. Perhaps userscripts.org
can be 
convinced to offer both installation links and
"source" links.

> <snip>
> 
> Thanks,
> 
> - a

-- 
Henrik Nyh
http://henrik.nyh.se

_______________________________________________
Greasemonkey mailing list
Greasemonkeymozdev.org
http:
//mozdev.org/mailman/listinfo/greasemonkey

On 10/16/06, Henrik Nyh <henriknyh.se> wrote:

> Oh, and does anyone use "New User Script"?


I use it. It provides a template of the GM metadata, which
is easily changed
to your own data. I would not want that removed.
_______________________________________________
Greasemonkey mailing list
Greasemonkeymozdev.org
http:
//mozdev.org/mailman/listinfo/greasemonkey

2006/10/16, Henrik Nyh <henriknyh.se>:
> I would strongly suggest moving the User Script
Commands out into the
> same level as Install/Manage/New. I felt they were
almost too deep into
> the menu hierarchy before, and this is definitely too
deep for me to
> want to use them.

True, I also feel that script commands lie too deep in the
menu hierarchy.
Some time ago I thought about writing a patch (for personal
use) to
allow scripts commands to appear as buttons within a bar (in
page
content, not in chrome); this bar would be dynamically
displayed
whenever at least one user command was relevant to the
displayed page.
 To rule out commands available for all pages, it should be
possible
to configure individually for each command whether it would
be
represented with a button in the command bar.  In short, a
dynamic
bookmarklets bar.  My laziness was stronger than my actual
needs. :(
Has anybody better ideas?


> Oh, and does anyone use "New User Script"?
Yes, I do it all the time.

> [...] perhaps the "Install User Script..."
> menu item is not necessary.

Agree.

> If these are both removed, I don't think
> it'd be very cluttery to put stuff into the Tools top
level again, so:
>
> Extensions
> Themes
> ---
> Some other tools
> ---
> Manage User Scripts...
> ---
> Name of Command #1
> Name of Command #2

I have nearly 70 extensions installed. Nearly all of them
take an
entry in the tools menu, some even more. Each new entry is
critical
space for me, and I bet I am not the only one.  I am
strongly against
having more than one entry under Tools for each extension,
nothing
specific to GM.


> > * Made the "install user script" option
in context menu bold to
> > indicate that it is the default option.

Is this a standard behaviour in FF (cannot test it right
now)?

>[...] Perhaps userscripts.org can be
> convinced to offer both installation links and
"source" links.

Yeah, that would be the proper thing to do, among other
reasons
because otherwise the popularity ranking of scripts gets
altered. As a
script author, I like to know whether my scripts get
actually
installed or just discarded upon inspection of the source
code.
_______________________________________________
Greasemonkey mailing list
Greasemonkeymozdev.org
http:
//mozdev.org/mailman/listinfo/greasemonkey

Gary Tyler wrote:
> On 10/16/06, Henrik Nyh <henriknyh.se> wrote:
> 
>> Oh, and does anyone use "New User
Script"?
> 
> 
> I use it. It provides a template of the GM metadata,
which is easily changed
> to your own data. I would not want that removed.
[snip]Second.

-- 
In Reach Technology:    http://www.inreachtech.ne
t/

Robert G. Werner
robertinreachtech.net

Tel: 559.304.5122

Your sister swims out to meet troop ships.
_______________________________________________
Greasemonkey mailing list
Greasemonkeymozdev.org
http:
//mozdev.org/mailman/listinfo/greasemonkey

Interesting points.

On 10/16/06, Henrik Nyh <henriknyh.se> wrote:
> Aaron Boodman wrote:
> > Here goes. Quite a few changes from
0.6.6.20061008.0:
> >
> > * Got rid of the little textbox for viewing script
source. Now, View
> > Script Source opens the script in a tab. The tab
gets the same yellow
> > install banner that it did before.
> > * Moved greasemonkey tools menu options into a
single menu.
>
> I would strongly suggest moving the User Script
Commands out into the
> same level as Install/Manage/New. I felt they were
almost too deep into
> the menu hierarchy before, and this is definitely too
deep for me to
> want to use them. So my suggestion would be to have
e.g. this under
> Tools > Greasemonkey:
>
> Install User Script...
> Manage User Scripts...
> New User Script
> ---
> Name of Command #1
> Name of Command #2

Good point, I would like to do this, but I'm not sure how
much work it
is. Previously GM commands impl. took advantage of the fact
that it
was the only thing in the menu. Commands aren't really
working well at
all right now (sometimes there are dupes) so I think most
people
aren't using them (are you?). Perhaps this can be fixed in a
future
release.

> > * Made "Install this user script" tools
menu option only visible when
> > actually viewing a script (I remember several new
users were always
> > confused by this).
>
> Not so for me. Firefox 1.5.0.7/Mac. Tools > GM >
Install is visible and
> active (not grayed out) for non-scripts (but clicking
it in that case
> does nothing).

So this is tools > Greasemonkey > install script that
we're talking
about, right? It works for me. Do you see any errors in your
js
console after viewing the menu?

> Right-clicking and selecting "Open link in new
tab" (I realize this !=
> View Script Source), or Cmd+clicking for the same
effect (on the Mac)
> will open the install dialog but also a blank tab.

That's true. Extensions have this behavior as well I
believe, right? I
think that's just something we'll have to live with for now.
If
someone's interested, they could look into hacking around
it.

> I still miss the previous "ease-of-source",
but since the advanced users
> that care can script around it by adding a dummy hash
or query string, I
> suppose it doesn't really matter. Perhaps
userscripts.org can be
> convinced to offer both installation links and
"source" links.

I tried to keep it easy to view source, as I love that
feature of GM
today. I think putting it in the context menu is a good
compromise
between people like us and the rest of the potential users
of GM who
don't know what to make of user script source.


- a
_______________________________________________
Greasemonkey mailing list
Greasemonkeymozdev.org
http:
//mozdev.org/mailman/listinfo/greasemonkey

On 10/16/06, esquifit <esquifitgooglemail.com> wrote:
> Is this a standard behaviour in FF (cannot test it
right now)?

No, I stole it from Windows. I think maybe OSX does it as
well.
Looking around a bit now, I see that the standard is to not
put the
default action in the context menu. Thus there is no need to
distinguish it. I could do that too -- just remove
"install user
script" completely from the context menu. Thoughts?

- a
_______________________________________________
Greasemonkey mailing list
Greasemonkeymozdev.org
http:
//mozdev.org/mailman/listinfo/greasemonkey