+kathyw, our documentation author On Fri, Sep 11, 2009 at 7:38 AM, ehamiter <[email protected]> wrote: > Maybe some more samples/templates for people to experiment with?
You are right about that. Samples are a good way to learn, we do need more of them. > Looks > like you can do a toolstrip, or change the content in a page- can you > add things to toolbars? Change context menus? The complete list of features is here: http://code.google.com/chrome/extensions/devguide.html Right now, you can't add toolbars. We are experimenting with putting toolstrips in the main toolbar (instead of the bottom bar), but that may not pan out. You also can't change the context menus, but that is another interesting idea. In general, we've made a different set of tradeoffs than the Firefox system. The result should be that our system is overall, less flexible, but more polished and easier to use. > Is there anyway to > "reverse-pack" a .crx extension to see what makes it tick? If it is > open source, then you should be able to-- right? The only real way to do this now is to install it, and then go find it in your user data directory. You're right that you should be able to more easily unpack extensions. We have a bug on this already: http://crbug.com/20134 > I also see that the > manifest.json file does not support some additional tags, like author, > or at least, it doesn't show up in the extensions page. Will that > change? We only put things in the manifest that are actually used by the browser. It isn't general metadata. Since author is not displayed anywhere in the browser, it isn't yet in the manifest. > I'm not a programmer by trade (as I suspect a lot of Firefox extension > authors are as well) so for me, there's a lot of trial and error and > copious amounts of help from experienced people to get an extension up > and running. That said, I think the biggest group of people who are > going to be interested in making Chrome extension are Firefox-converts > like myself. A sample tutorial on how to port a Firefox extension to > Chrome would be super useful. I am used to the mozilla DOM and using > XUL, so maybe a quick primer on key differences? You're right that this would be a very good thing for us to do. > I've seen some people > in this group reference mozilla docs. How similar are the components? Not similar at all. The only area of overlap is that both systems can use a lot of HTML5 APIs. I referred to mozilla docs a few times because they have pretty good HTML5 references. > So far, making the above extension is about a million times easier in > Chrome. I have the same extension for Firefox and it is much more > complex, as far as packaging and even the content is different. :). - a --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-extensions" 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-extensions?hl=en -~----------~----~----~----~------~----~------~--~---
