Aaron,
Thank-you so much for your reply. I was skimming through lots of the public
posts, and I've been trying to gather up as much information as possible, so
that this information can at least be posted as "bug reports", so at least
the developers can be "made aware" of the situation, and hopefully these
issues can be addressed.
I can honestly say, that Chromium kicks the pants off of Firefox, IE, and
just about everything out there in terms of speed.
Everyone is forced to use Firefox (with Greasemonkey) for the time being,
and others have posted things in the past about Greasemetal and native
Greasemonkey support in Chrome/Chromium, but from what I've read (and
understand) no one has been able to get it to work properly (and it seems
many of the functions are simply not implemented yet).
Would it be possible to add native support in Chromium for:
GM_registerMenuCommand
GM_getValue
GM_listValues
GM_deleteValue
GM_setValue
GM_xmlhttpRequest
There are over 16+ Million users that play many of Zynga's games, and we've
written a handful of scripts to support many of them, using Greasemonkey,
but we have over 2+ million users complaining that the scripts won't work in
Google Chrome.
I've tried testing this myself, and it doesn't seem that the functions are
working properly in Chrome/Chromium. Is there any solution at the moment to
run Greasemonkey from within Chrome/Chromium?
I've listened to everyone's gripes, and read hundreds of thousands of posts
(since September/October) about Greasemonkey working natively in
Chrome/Chromium but that was over 9+ months ago, and Chrome is just such a
much better (and faster) browser than Firefox, and when a window crashes in
Firefox, it takes down your whole browser.
A lot of people play at work, and have 40 or 50 windows open, and they
complain when a window crashes in Firefox, and everything goes down. I've
been telling them to just use Chrome, but now everyone is using Chrome (and
saying how fast and great it is) but complaining that there is no
Greasemonkey support, and that the scripts won't work in Chrome.
So now I'm stuck trying to tell them to use Firefox. :-)
Some users are running multiple players and they can only run one instance
in Firefox, and they would like to run another instance in Chrome. Any
ideas as to when these Greasemonkey functions could be implemented into
Chromium, and any ideas as to what the timeline would even be?
GM_registerMenuCommand
GM_getValue
GM_listValues
GM_deleteValue
GM_setValue
GM_xmlhttpRequest
Is there anything we can do in the meantime to get these functions to work
in Chromium?
Thank-you for all that you do,
Mark
On Thu, Jul 9, 2009 at 11:08 AM, Aaron Boodman <[email protected]> wrote:
> Thank you for your passionate plea.
>
> There are two features that we are working on along the lines of what
> you are asking about:
>
> - User scripts (similar to Greasemonkey scripts)
> - Extensions
>
> The user scripts feature has not made much progress because we have
> not been sure exactly how the two features should relate. We did not
> want to enable something that we would later have to disable.
>
> But FWIW, the current plan is:
>
> - User scripts will be enabled by default (no --enable-user-scripts
> needed).
> - But there won't be any Greasemonkey-style UI - they will always be a
> power user feature.
>
>
> On Thu, Jul 9, 2009 at 8:45 AM, Mark Malewski<[email protected]>
> wrote:
> > I can easily point you to 800,000+ postings just since December of users
> > asking the status of Greasemonkey support in Chromium.
>
> Seriously? Please do :)
>
> > There are probably at least 400+ postings just on Mashable alone. I've
> > skimmed through, and read everything I could.
> > There seems to be a small handful of people that have managed to somehow
> get
> > "Greasemonkey" to work in December, but from what I read none of the
> > functions have been implemented, and the whole project seems to just "not
> > exist". Everyone is posting comments, and nobody seems to have any
> answers
> > as to what on Earth is going on, and how we can get Greasemonkey for
> > Chromium working.
>
> The URL that you keep linking to
> (
> http://sites.google.com/a/chromium.org/dev/developers/design-documents/user-scripts
> )
> says explicitly: "Chromium does not support @exclude, @require,
> @resource, unsafeWindow, or any of the special GM_* APIs.". Isn't that
> the status information you're asking for?
>
> > I have looked at some of Adam Hirsch's posts, and some of the posts over
> at
> > GHack, and various other forums.
> > http://mashable.com/2008/12/15/google-chrome-greasemonkey-scripts/
> > It's been about 9+ months of posts from what I've been reading, but all I
> > hear is "great news" and then a flurry of posts saying "it doesn't work"
> and
> > "how do I get it to work"? Then towards the end, everyone just says "the
> > shit is broken, it doesn't work". That doesn't seem very helpful, and
> I've
> > read several hundred posts from others wanting to help, and move this
> > project forward, but nobody seems to have any information (other than
> some
> > "greasespot" page, and a personal blog of Aaron Boodman, but there is no
> > place where anyone can even post, or even take part in this project.
> > http://ajaxian.com/archives/greasemonkey-chrome-edition
> > Can we make this an OpenSource project...?
>
> Chromium is open source. You are welcome to get involved
> (http://dev.chromium.org/developers/).
>
> > Also so others can get some help, and at least see the status of the
> project
> > and various functions (and their current implementation status). 9+
> months
> > is a long time, and it seems that nothing has been done at all in the
> past
> > nine months (other than lots of people bitching and complaining about
> > nothing working). I'm one of those people that would like to see things
> get
> > fixed (and implemented), and would at least like to help move this
> project
> > forward if we can at least get some information as to what is going on,
> and
> > who is the lead developer, or who is even running this project, or what
> the
> > current status of each of the functions even is?
>
> The document you link to clearly states that the GM_* functions are
> unsupported (technically, that isn't true -- there is some minor
> support, but not worth digressing into here). This hasn't changed
> since we added basic support for user scripts because:
>
> a) We can't do it in a way that we're comfortable with, security-wise,
> without lots more code that needs to be built.
> b) We did not perceive it as a high priority (we haven't been deluged
> with feature requests for these functions).
> c) We did not understand exactly how it would related to Chromium
> extensions and we didn't want to enable something we'd have to later
> disable.
>
> > A Greasemonkey for Chromium WIKI page would be extremely useful, so users
> > can at least see what is going on, and other developers can at least get
> > involved.
>
> I agree, the current state with the Chromium-only editable pages
> stinks. I will fix this. I think that we can create user-editable
> wikis on code.google.com.
>
> - a
>
--~--~---------~--~----~------------~-------~--~----~
Chromium Discussion mailing list: [email protected]
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-discuss
-~----------~----~----~----~------~----~------~--~---
