Frank Schönheit - Sun Microsystems Germany escribió:
Hi Ariel,
my somewhat unsorted thoughts on this in the late evening, I might
detail this tomorrow.
In general, we need to establish a codex for extensions - the layer
structure you cited is open for extensions, and will continue to be, so
they will be able to add own content to the
DataAccess.xcu/RegisteredNames node. Which means we need to care for
this, anyway.
(By definition, OOo cannot distinguish from which layer a certain config
setting originates: The transparent layering is a (strong, IMO)
configuration feature. So, a codex becomes a necessity.)
That said, I don't see what the codex shouldn't be: If you register a
database, make sure the registration is read-only. Of course this implies
- declaring config nodes as read-only must work at all
- The registration UI must respect read-only-ness, and not allow the
user to change read-only registrations, neither in location nor in
name
I am tempted to consider the approaches taken in the areas you cited a
... time-pressed solution:
- I bet that programmatically, I am still able to change the template
paths, even the ones installed by extensions. This is implied by the
fact that the "user" layer overrules the "user/uno_packages" layer,
and config write access goes to the user layer.
- the auto-text example shows that in some places, a "Don't do
it"-documentation was the only solution :)
... and your sharp eye sure noticed that I didn't mention the Gallery
advice:
http://wiki.services.openoffice.org/wiki/Non-code_extensions#Gallery_Extensions
"Everything told about templates extensions *also* applies to extensions
for gallery items. The Paths.xcu of course now doesn't contain a value
for the "Template" path but for the "Gallery" path. Again here is an
*example* that can be filled with gallery themes you have created by
yourself. As this is a little bit *tricky* and the gallery code
currently is *prone* to *name* *clashes* of the theme files it is *not*
*recommended* to use gallery extensions until the issue about these
problems is fixed."
what's the point of an example for something not recommended? other than
"here is an example of what you shouldn't do at all because it is
prone to errors"...
Regards,
Ariel.
--
Ariel Constenla-Haile
La Plata, Argentina
[EMAIL PROTECTED]
[EMAIL PROTECTED]
http://www.arielconstenlahaile.com.ar/ooo/
"Aus der Kriegsschule des Lebens
- Was mich nicht umbringt,
macht mich härter."
Nietzsche Götzendämmerung, Sprüche und Pfeile, 8.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
