It sure would be nice if Chromium could use the Greasemonkey API natively as
the basis for a user-JS standard to be adopted by all browsers.
There is such a large database of Greasemonkey scripts (millions of them
over at userscripts.org) and it sure would be nice if the Greasemonkey API
could be added (natively) to Chromium, so that these scrips would work
natively in Chromium.
I wish someone could post a full list of all the functions of the current
Greasemonkey API, and then post them to a WIKI page so that we could begin
work on implementing the Greasemonkey API into Chromium.
At this point, there doesn't seem to be any information available, no point
of contact, and no one seems to know anything about who is leading this
project.
Could I at least just get some more information from whoever is involved in
this, and maybe I can help create a WIKI page, and help organize an effort
to help move this project forward. At this point it doesn't seem like any
progress is being made, or that the project hasn't moved forward at all in
the past 9+ months, so I would like to at least get a few of the developers
that want to help involved, so we can start making native Greasemonkey
support in Chromium a reality.
Thank-you,
Mark
2009/7/9 Mark Malewski <[email protected]>
> I can easily point you to 800,000+ postings just since December of users
> asking the status of Greasemonkey support in Chromium.
> 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.
>
> 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://mashable.com/2008/12/15/google-chrome-greasemonkey-scripts/>
> http://ajaxian.com/archives/greasemonkey-chrome-edition
> <http://ajaxian.com/archives/greasemonkey-chrome-edition>
> Can we make this an OpenSource project, and create a WIKI page for
> Greasemonkey support for Chromium, so that others can get involved in this
> project, and help move this project forward?
>
> 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?
>
> 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.
>
>
> On Thu, Jul 9, 2009 at 10:23 AM, PhistucK <[email protected]> wrote:
>
>> I guess the names will grow identical some day, what I mentioned before
>> (the regular XMLHttpRequest) is part of the Extensions system (and maybe
>> also part of the User Scripts, but I have not verified that). It is not
>> considered as part of the Greasemonkey support. So, officially (and not
>> officially, since you have to add a command line switch to make User Scripts
>> work in the first place), there is no support for native Greasemonkey API.
>>
>> I am not sure an official support is planned anyhow and I am really not
>> sure the API will be persistent.
>>
>> ☆PhistucK
>>
>>
>>
>> On Thu, Jul 9, 2009 at 18:18, Mark Malewski <[email protected]>wrote:
>>
>>> Phistuck,
>>> Thanks for the reply, I had just sent out a post about 2 seconds before I
>>> received your reply.
>>>
>>> Is there any reason why they are using different command names (that are
>>> incompatible with the Firefox/Greasemonkey command names)?
>>>
>>> It would seem to make sense to keep the commands identical, so that
>>> Greasemonkey scripts (for Firefox) can just be downloaded and executed in
>>> Chromium (without having to modify the scripts).
>>>
>>>
>>>
>>>
>>> On Thu, Jul 9, 2009 at 10:12 AM, PhistucK <[email protected]> wrote:
>>>
>>>> The syntax is different and it is only a temporary state, but
>>>> GM_xmlhttpRequest (as you stated) is kind of implemented.Try using a
>>>> XMLHttpRequest from an extension - it will allow cross origin requests (if
>>>> that is the purpose of this function).
>>>>
>>>> ☆PhistucK
>>>>
>>>>
>>>>
>>>> On Thu, Jul 9, 2009 at 16:59, Mark Malewski <[email protected]>wrote:
>>>>
>>>>>
>>>>> I've tried installing the latest Google Chrome (2.0.172.33) and I've
>>>>> also installed the latest Chromium 3.0.193.0 (20244) build as of July
>>>>> 8, 2009, hoping to use Greasemonkey in Chrome or Chromium.
>>>>>
>>>>> I've been reading thousands of posts on various websites, about
>>>>> Greasemonkey support in Google Chrome/Chromium, but none of the
>>>>> scripts we've tried using function properly.
>>>>>
>>>>> What is the status of Greasemonkey support in Chrome/Chromium, what
>>>>> functions have already been implemented, and what is the status of
>>>>> support for the following Greasemonkey functions:
>>>>>
>>>>> Add support for:
>>>>>
>>>>> GM_registerMenuCommand
>>>>> GM_getValue
>>>>> GM_listValues
>>>>> GM_deleteValue
>>>>> GM_setValue
>>>>> GM_xmlhttpRequest
>>>>>
>>>>> These six GM_ functions are the only functions that we really need at
>>>>> the moment that don't seem to be currently supported, is there any way
>>>>> that these functions could possibly be added to Chromium, so that we
>>>>> can begin using Greasemonkey in Chromium?
>>>>>
>>>>> Thank-you for all that you do,
>>>>>
>>>>> Mark
>>>>>
>>>>> >>>>>
>>>>>
>>>>
>>>
>>
>
--~--~---------~--~----~------------~-------~--~----~
Chromium Discussion mailing list: [email protected]
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-discuss
-~----------~----~----~----~------~----~------~--~---
