EDIT: since AP is used for UI testing, it may need to be slightly modified, for plugins run on a more deeper level than the UI (but still include the UI). However, there are those plugins that run solely on the user interface, such as AdBlock, which recognizes javascript ad scripts in which case it can be established just as greasemetal
On Sep 9, 11:13 pm, "Mark F." <[EMAIL PROTECTED]> wrote: > I believe it is extremely possible to use AutomationProxy as a > middleman/protocol for Chrome Plugins. Similarly to the way you have > GreaseMetal running through a webserver and the AP (AutomationProxy) > reading of the scripts found on the server, one can have a plugin > system running in the same fashion. > > BTW, great job with greasemetal. AP can be the first open door to > Chrome Plugins. > > On Sep 9, 10:58 pm, "Kazuho Oku" <[EMAIL PROTECTED]> wrote: > > > Hi, > > > While reading the source code of Google Chrome, I found out that it > > was possible to customize its behaviour through AutomationProxy (a > > named pipe used for automated UI testing), and have created a > > userscript runtime above it. > > > If you have any interest, please visithttp://greasemetal.31tools.com/ > > > -- > > Kazuho Oku --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~----------~----~----~----~------~----~------~--~---
