> I would guess that the best way would be to pack the jQuery source > into > the greasemonkey xpi and access it using the chrome URI interface > somehow. I have very limited experience with firefox extensions but > that > would seem to be the best way in terms of bandwidth and in terms of > usability (you wouldn't need to add a dynamic script load to every > page > load just to use jQuery in your user scripts)
This would be great if Greasemonkey developers include jQuery natively. I can't develop a fork, with jQuery included, and ask people wanting to use my scripts to also have a specific fork of Greasemonkey... That's why I think the most pragmatic solution would be to include the compact version of jQuery in my script, as it has been done before. My only problem is that I don't know what I need to change in the source to make it work. -Nicolas -- Nicolas "Brush" HOIZEY Clever Age : http://www.clever-age.com/ Gastero Prod : http://www.gasteroprod.com/ Photos : http://www.flickr.com/gp/[EMAIL PROTECTED]/M1c002 phpHeaven : http://www.phpheaven.net/ _______________________________________________ jQuery mailing list [email protected] http://jquery.com/discuss/
