Joachim Schmitz a écrit :
I find xml-files highly unreadable and hard to edit.
They are not that a hard to read/edit compared to the python equivalents.
for me the opposite is true, even when using an xml-aware editor.
How do you "debug" those xml-files ?
What do you mean by debugging? They only host declarative configuration. Most of
the time you import a profile, change some parameters in the ZMI to fit your
need and rexport back the steps that we changed to put them back in your profile.
They are two kinds of profiles extension profiles that host only new
modifications against some existing setting and base profiles that host
everything. Most of the time you'll use extension profiles with small XML files.
A documentation on GenericSetup should be published soon with more details on that.
To convert an existing product, you can use your installer to setup your product
on a 3.4 instance, then go to the portal_setup and export the steps that were
changed by your installer. Then put the XML files in the profiles/default/
folder of your product and register that folder as an extension profile in the
__init__.py file. See CPSWiki/__init__.py for instance.
--
Olivier
_______________________________________________
cps-devel mailing list
http://lists.nuxeo.com/mailman/listinfo/cps-devel
