[CPS-devel] Re: CPSDefault profiles??

Olivier Grisel ogrisel at nuxeo.com
Thu Jul 20 13:39:49 CEST 2006


Alpha Dia a écrit :
> Thanks a lot, MyProject is very interesting even though i do not
> understand everything inside yet :(
> Correct me if i am wrong:
> 1. when i want to create a product that use the features of CPS, it's
> better to create an extension, rather than writing codes directly in
> CPSDefault?

Yes. The point is to make it easier to install new versions of CPSDefault 
without breaking your extension by keeping its file out of the CPS source tree.

> 2. But to create such an extension, i can use an instance of CPS Default
> site to build easily new document type, then export the xml files into
> my new product?

Yes.

> 3. other question : what are python files getCustomDocumentXXX.py in
> CPSDocument/skins/cps_document for? can they be used to create new
> document types for a new product? if yes do you recommend it?

The getCustomXXX.py files are deprecated. They were used to customise CPS site 
before we had XML profile. It's better to use to the method you described at 
point #2.

-- 
Olivier




More information about the cps-devel mailing list

This list archive provided by Nuxeo, the leaders of open source ECM. Check out the Nuxeo 5 open source, standards-based ECM project.