Hi
I'm actually thinking to the extensions project through the DicOOo
porting work.
The purpose is to provide DicOOo, or any future valuable extension, at
source level so that it can be delivered within OOo and share the
translation mechanisms
Generally, people who wrote an addon package, in any UNO supported
language, do not care about OOo sources internal organization and it
will be difficult to ask them to transforms deeply their code to
integrate OOo
A solution would be to provide them with best practices and common
framework (one of the extensions project purpose) and deploy as an
addon. The sources could be unpacked inside the cvs and built from
scratch. This would also allow to integrate the translation process
So the question
Is it possible to deploy addons at OOo installation level (so, running
unopkg) ? if yes, some pointers are welcommed
If no, what prevent this ?
IMHO, allowing Uno packages deployement at installation level will
lighten the integration process
Thanks in advance for your response
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]
