Tickets :: Comment on [#2565] Firefox 3 bookmarks extension

* Your Email Address
* Spam protection	Enter the letters below: _ __ _______________ __ __ \| \|\ \ / /___ /__ __\| \/ \| \| \| \ \ / / / / \| \| \| \ / \| \| \| \ \/ / / / \| \| \| \|\/\| \| \| \|____ / / /__ \| \| \| \| \| \| \|______\/ /_____\| \|_\| \|_\| \|_\|
Comment	>> Finally, most important: where/how do we want to host and distribute > >> the XPI? I assume that we should have the uncompressed files checked > >> in to CVS as a TreanPlaces project or something (maybe we should have > >> a BrowserPlugins module to hold other stuff, too?); then I guess it'd > >> be great to put it up on the moz plugins site if we can get it > >> approved. Other thoughts here? Jan, any progress serving the XPI out > >> of Horde? > > > > Yes, but I started cleaning up the whole extension which is obviously > more work than just getting the XPI working. > > > > But the layout I use is the following: imp/extension.php is providing > the XPI and the XPI is built from files in imp/templates/extension/. > The layout in this directory is the same like in the XPI to ease > maintenance. But it doesn't have to. I attach an extensions.php the > simply takes the directory one-to-one, in real life we need some > processing, i.e. adding the correct URLs, etc. > > > > This is why I don't agree with your approach of having the > extension(s) in a separate module or even on the mozilla site. The > idea is to have one extension per (Horde) site. 1) because users > don't have to configure any site settings like URLs etc., 2) users > can have separate extensions for each Horde site, and 3) users can > get extension updates automatically from the Horde sites, depending > on the IMP/Trean version they run. With "Horde sites" I obviously > don't mean horde.org, but sites that have Horde installed.
Attachment
Watch this ticket