> I installed it, it worked :). Awesome!
> Let us know what you found lacking. It's hard for us to see the docs > clearly since we all know how the system works. > > - a Maybe some more samples/templates for people to experiment with? Looks like you can do a toolstrip, or change the content in a page- can you add things to toolbars? Change context menus? 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? 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? 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? I've seen some people in this group reference mozilla docs. How similar are the components? 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. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
