On 16 Jan 2006, at 21:39, Olivier Grisel wrote:
Florent Guillaume a écrit :
A general note about writing extension profiles.
For all the files that are there only to *add* things to an
existing tool, you don't need to add the meta_type attribute for
the references to that tool. For example below, you only need to
write:
<object name="portal_actions">
or
<object name="portal_layouts">
The meta_type is only useful if these objects were about to be
created, which they're not in an extension profile.
About extension profiles, wouldn't it be possible to clearly label
which profiles are extension profiles and which are base profiles
in the portal setup UI so as to be able to guess whether
configuration made in the ZMI will be purged or not at next import
time?
The CPS setup tool lists the base profile first, the others are
extension profiles.
Probably all that UI could be done better.
Furthermore, the import/export tabs should display a reminder to
which profile is currently activated.
Yes. Actually just import, as export doesn't care and just uses the
listed export steps.
Patches welcome :)
Florent
--
Florent Guillaume, Nuxeo (Paris, France) Director of R&D
+33 1 40 33 71 59 http://nuxeo.com [EMAIL PROTECTED]
_______________________________________________
cps-devel mailing list
http://lists.nuxeo.com/mailman/listinfo/cps-devel
