Hi all
Thanks for this dicussion that feeds me for the IRC conf. (huuuh, am i late ?!!! - one week left ;))
In my experience, (1) coding the extension was easy, but (2) the documentatin was inpenetrable and (3) I couldn't figure out how to deploy them. There just wasn't a simple system for that.
(2) and (3) are a problem
but it is sometine a matter finding the right person that has the answer. When i started, i didn't even know there were a [EMAIL PROTECTED] ML
After, i couldn't trust people were so kind to help me, poor scripter
I have high hopes that Ian Laurenson and Laurent will aleviate this. Ian is working on a wiki to help people learn the API, and both have talked about ways to simplify deployment.
Some tools already exists. Xray (and pyXray) should be included in OOo by default. Same for addon manager
Bernard Marcelly (Xray and addon manager author) did a great job there
But in any event, based on my experience, documentation and deployment are the biggest obstacles. It'd be wonderful if, for example, OOo had a dialog for extensions, like Thunderbird. It could download the extensions from some central server, like OOoMacros.
This is the way and not so hard to implement as it is the basis of DicOOo and FontOOo
Templates would have helped me inmsensely. Could you donate those templates to Ian's Wiki? That would be a good step forward.
I wanted to propose a pre-build wizard
with all the navigation already coded, the translation engine (that is very important to address international community)
beginners (and why not, other) could use it to focus on the purpose of there addon.
And it should uniformize the look
What are the chances of a near-future OOo version having an extension installer, like Thunderbird?
well, the time to code it .... could be a macro
but an extension installer, needs a repository with all the management tools : updated lists, classification by features, certification aso
quite a project (an incubator already exists ?) with real people inside
Regarding license, as these addons are separated tools, they can be under whatever free licence the author wants. Some policies to build though
Enhancing OOo can be done by people who don't even know what cvs is
if the addon they developp becomes so popular that it has to be integrated in OOo, well, it can be done by more advanced coders and they can be driven (as i'm actually)
Thank's all for this discussion
Laurent
-- Laurent Godard <[EMAIL PROTECTED]> - Ing�nierie OpenOffice.org Indesko >> http://www.indesko.com Nuxeo CPS >> http://www.nuxeo.com - http://www.cps-project.org Livre "Programmation OpenOffice.org", Eyrolles 2004
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
