On 20-May-09, at 6:58 PM, Peter Kasting wrote: > Similar-sounding goals to Chrome extensions: web-tech-based, no > restart needed, backwards-compatible, etc.
... API-based for well-understood common developer tasks (user notifications, bookmark integration, UI additions, etc), lower barrier to entry, more web-like and web-centric development model, quick iterative in-browser development environment. The goals for the project are outlined on our wiki here: https://wiki.mozilla.org/Labs/Jetpack (You can also join the conversation in Google Groups http://groups.google.com/group/mozilla-labs-jetpack or on irc.mozilla.org#jetpack) > Not sure how much overlap there is between the two. Any Mozillians > who read this (hi beltzner!) feel free to chime in. It would be > very cool if these would run in Chrome and Chrome extensions in > Firefox. I'm actually not sure at all. In terms of the scripts themselves, both are based in JS, though the APIs at this point are very different looking. Might be worth investigating standardizing common browser UI actions (notification, opening a tab, adding a bookmark, etc) and even seeing if we can dovetail with any of the w3c-webapps work? Hard to tell what the right way is to go about these things. I do agree, though, that we don't want to get into a fragmented story where when you go to a website you see a kajillion buttons to download a script for site X for each browser. Though link-rel and such might make that easier. cheers, mike --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
