@Edo78
"at least for now I hope" - Why?
Gears built in and built on "components from... Firefox" (according to their blog), whatever that means. So I wouldn't right off extensions completely.
@anotherjesse: Uniqueness and dynamic IPs are tough but wouldn't an onclick tracker on the INSTALL button bypass any other problems (as auto-updates would be direct, not visiting the page and clicking)
Also.. in addition to this, it should show browser versions (as I'm sure there are javascript differences between FF3 and FF2, so we might soon see scripts that are incompatible with FF2)
Scanning for GM_* =bad idea-not all GM functions have this prefix(doGMMeenoo), some other things are incompatible w/Opera(XPConnect) & some things aren't needed in Opera(unsafeWindow, window.content)
Any automated way would be tricky. Adding an "Opera compatible" checkbox when scripts are submitted would be far more effective, & would educate scripters in the fact that Opera scripts are possible.
@Edo78
Ah, in that case I misunderstood you, sorry.
As for extensions for chrome, here's the first one: http://greasemetal.31tools.com/
0 Greasemonkey for Google Chrome! - 2 months ago
@Edo78
Ah, in that case I misunderstood you, sorry.
As for extensions for chrome, here's the first one: http://greasemetal.31tools.com/
0 Greasemonkey for Google Chrome! - 2 months ago
@alexrah
Please go leave a comment on Googles own feedback page http://www.google.com/support/chrome/bin/request.py?contact_type=feedback. USO has nothing to do with which browsers support scripts.
@Edo78
"at least for now I hope" - Why?
Gears built in and built on "components from... Firefox" (according to their blog), whatever that means. So I wouldn't right off extensions completely.
0 Greasemonkey for Google Chrome! - 2 months ago
Maybe have three options for each too. Like:
- Full support for:- blah blah blah
- Some support for:- blah blah blah
- No support for:- blah blah blah
For example a script might use @resource but still partially work in older Greasemonkeys etc.
3 Possibility to show in what browsers script works. - 3 months ago
@anotherjesse: Uniqueness and dynamic IPs are tough but wouldn't an onclick tracker on the INSTALL button bypass any other problems (as auto-updates would be direct, not visiting the page and clicking)
0 Amount of unique installs - 5 months ago
Also.. in addition to this, it should show browser versions (as I'm sure there are javascript differences between FF3 and FF2, so we might soon see scripts that are incompatible with FF2)
3 Possibility to show in what browsers script works. - 5 months ago
Scanning for GM_* =bad idea-not all GM functions have this prefix(doGMMeenoo), some other things are incompatible w/Opera(XPConnect) & some things aren't needed in Opera(unsafeWindow, window.content)
Any automated way would be tricky. Adding an "Opera compatible" checkbox when scripts are submitted would be far more effective, & would educate scripters in the fact that Opera scripts are possible.
3 Possibility to show in what browsers script works. - 5 months ago