Hi Stephan,
> Feel free to come back here with any questions along your way,
Thank you very much for your kind offer!
Indeed, after studying your information there would be a couple of
questions:
* where would one find the full definition for "manifest.xml" and a
list of valid "mainfest:media-type"s; I looked in the developers
guide and tried the search function of the Wiki, but have not been
really able to locate it?
* also, where would one be able to find the full definition for the
"description.xml" file?
o ad version numbers: would something like "2.1.0.20070202" or
"210.20070202" be o.k. (according to the production rule it
should be possible) or would that pose any problems (the
date of the version is the trailing value, possibly
supplemented with the time of the day like "210.20070202162200")
* ad "application/vnd.sun.star.uno-component;type=native":
o This can be used to not only denote libraries, but also
executables and modules (or with other words: these files
will be put into a place that is accessible via the PATH
settings?)
o Is there a complete list somewhere of the operating system
dependent strings? The extension document mentions
"Windows", "Linux_x86", "Solaris_SPARC". So what about PPC
versions of Linux or Intel versions of Solaris or PPC and/or
Intel versions of MacOSX?
* is there a possibility to copy a set of scripts (in any available
scripting language) to the user and/or shared script repository?
If possible, what would be the appropriate "manifest:media-type"
entry?
o Of course this may pose a little problem when using the
update feature, as such scripts could have been edited in
the meantime by the users (but then one could resolve this
by moving the existing/edited extension scripts to an own
backup library)
TIA,
---rony
