[sugar] [Sugar] Browse extension/plugin structure

[David Van Assche]

Hi,
   Me and Tomeu were discussing the way browse should handle
extensions/plugins and we came to the conclusion that really, it
should do this the same way firefox does it, thereby making it far
easier to make future extensions/plugins... Right now, xulrunner
already has a way of doing this directly, even with an installer that
injects the .xpi where it should go... the question is, does it work
that way with browse already? In which case, maybe someone (Marco?)
can shed some light onto where all the unzipped .xpi stuff should
go...

Here is the recommended mozilla structure for .xpis and the way
Firefox 3 is doing it:

helloworld.xpi/
 chrome.manifest
 install.rdf
 components/
 defaults/
   preferences/
     mydefaults.js
 chrome/
   helloworld.jar
     content/
       overlay.js
       overlay.xul
     locale/
       en-US/
         overlay.dtd
     skin/
       overlay.css

Kind Regards,
David Van Assche