Thursday, July 27, 2006

Greasemonkey 0.6.5 - 2.0 support and localization

I'm happy to announce Greasemonkey 0.6.5, which includes support for Firefox 2.0 beta 1 and basic localization in Czech, Dutch, and German. I've also fixed up the problems in the CVS main branch for people where were trying to use source directly.

Thanks to Chris Feldmann for internalization code, esquifit for a 2.0 compatibility patch, and all those who helped test.

20 comments:

didaio said...

How I can help you with translation to Ukrainian?

Jeremy Dunck said...

Translate the files in:
<profile directory>\
\extensions\{e4a8a97b-f2ed-450b-b12d-ee082ba24781}\\
chrome\chromeFiles\locale\en-US to your language, then post them to the mailing list.

pupil said...

i don't know if this is the correct place to ask for this, but couldn;t find an appropriate greaemonkey forum anywhere. I got a feature request that would make me very happy. Would it be possible to have the userscripts you have installed dragable and reorderable in the preferences window? Imagine like you can bookmarks in the bookmarks drop down menu in firefox. This would help me alot as I like to have some active and some inactive and toggle the inactive ones on only when I need them, so prefer these at the botom of the list (and laos having site specific ones next to each other in the list) I'm a anal like that :)

thanks

Anonymous said...

what, no bug fixes, new features?

LouCypher said...

Bug 13002 hasn't been fixed.

Anonymous said...

Could I use GM_xmlhttpRequest without async mode?

Anonymous said...

Please add support for beta 2!

Anonymous said...

Beta 2? How about support for minefield aka Firefox 3.0a1?
Now -that- would be kick ass. Is there a nightly out there working with 3.0a1 yet?

Sergio Abreu said...

I am running it in Firefox 2.0b2 indeed.

I have modified some things to make it even better:

1- Wrote the pt-BR locales and completed what was lacking in order to the locales work perfectly.
2- Put all menus inside a unique Tools -> Greaesemonkey menu
3- Put the User Script Commands both in the Tools -> Greasemonkey menu as in the context menu of the status bar
4- Added a code to prevent User Commands doubling.
5- Changed the alert confirmation by status text effect:it means "one click less".
6- Made the Manage User Scripts from the Status bar static (so, easier and faster to access it), by putting it BELOW the scripts list instead of in the top... It got much easier, as it is always JUST above the enabled button.

I have a better Greasemonkey now. I tried to contact the author to send my suggestions, but it was a bit difficult...

Install Web site in Portuguese:
http://sitesbr.net/br_greasemonkey.asp

The xpi: here

Regards

Sergio Abreu

Sergio Abreu said...

Anti-User Script Command duplication code:

GM_MenuCommander.prototype.registerMenuCommand =
function(commandName, commandFunc, accelKey, accelModifiers, accessKey) {

// Protection against item duplication by Sergio Abreu

for( i = 0; i < this.menuItems.length; i++){
if(this.menuItems[i]._commandFunc == commandFunc) return;
}

... here the code continues normally

Jeremy Dunck said...

"
I have a better Greasemonkey now. I tried to contact the author to send my suggestions, but it was a bit difficult...
"

Did you try the developer mailing list?

"
xpi here...
"

While I am happy to see contributions, please don't distribute forked GM XPIs.

We're not hiding. Mailing lists are a common convention in open source development.

:)

Sergio Abreu said...

Mailing list:
I have posted to this mailing list, as anonymous, and GOT NO ANSWER AT ALL. I believe you get thousands of e-mails and it might be impossible to care of all...

The xpi link:
I put that xpi link in order that the author could check the improvements I made, by himself.

I just think that all my suggestions make sense and all people who use Gresaemonkey would approve if you implement them.

If you release one version containing my suggestions, of course I can stop hosting a different xpi, because it would be nonsense.

However, as long as it has the problems I appointed, I will not use the official xpi.

I want to help, but need to have a faster response (and see things changing).

Sergio Abreu said...

What I said but it was a bit difficult... was exactly...

to get an answer from this mailing list.

I sent a message to greasemonkey@mozdev.org in 15/09/2006 at 01:19h and up to now (19/09/2006 14:13h), no reply.

Is the "open source development" always this slow concerning to communication or is it a particular case ?

Jeremy Dunck said...

"
Is the "open source development" always this slow concerning to communication or is it a particular case ?
"

Just this case, apparently.

Please send the email again to jdunck@gmail.com. I think anonymous mails to the list are bounced due to spam problems.

Sergio Abreu said...

Thank you!

Now I will be able to give you all the details.

Anonymous said...

Any chance on adding Seamonkey compatibility? 0.6.5 won't install as is.

BG said...

We really need a firefox 2.0 version!

Anonymous said...

b2 how about rc2

Anonymous said...

What prevents GM from working in mozilla suite?

JLD said...
This post has been removed by a blog administrator.