Hi,
M. Fioretti wrote:
Nobody should use sxw files for deployment. We use *UNO packages*.
Sorry for not getting back on this earlier. Thanks for the detailed explanation, but I still have some doubts:
1) Are these UNO packages useable/recommended also for single macros, templates, clip-art? That is, not core, serious stuff, made by professionals?
For single macros, yes. The system is not intended for templates, but ultimately templates are just documents you need to put somewhere. Neither is the system intended for installing clipart into the gallery. But in this regard sxw documents don't appear to be suited either.
If you want to distribute some data (templates, clipart, whatever) together with a macro that needs to be run to further install this stuff, then you could use a UNO package for this.
2) Can they easily be used to create relocatable packages, that is stuff that can either be installed once, systemwide, or in the user home directory?
Yes. They can themselves be installed either systemwide or in the user home directory. You can wrap the 'systemwide installation' feature into a native system package.
3) Where is the "official" documentation/web page explaining all this to new, potential, one-time contributors? And *deprecating* the use of .sxw or .sxc files as installers?
The UNO package manager is documented in the UNO developers guide <http://api.openoffice.org/DevelopersGuide/DevelopersGuide.html>.
HTH, Joerg
-- Joerg Barfurth Sun Microsystems - Desktop - Hamburg >>>>>>>>>>>>>>>>>> using std::disclaimer <<<<<<<<<<<<<<<<<<<<<<< Software Engineer [EMAIL PROTECTED] OpenOffice.org Configuration http://util.openoffice.org
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
