[CPS-devel] Re: CPSSkins skins in extension profiles

Jean-Marc Orliaguet jmo at ita.chalmers.se
Wed Jan 18 21:55:24 CET 2006


Florent Guillaume wrote:

> On 17 Jan 2006, at 22:53, Olivier Grisel wrote:
>
>> Olivier Grisel a écrit :
>>
>>> Could someone please explain me why they are such things as:
>>> '''
>>>   <skin-path name="CPSSkins">
>>>   <layer name="cps_subscriptions" insert-after="cps_default"/>
>>>   <layer name="cps_subscriptions_installer" insert- 
>>> after="cps_default"/>
>>>  </skin-path>
>>>  <skin-path name="CPSSkins-macroless">
>>>   <layer name="cps_subscriptions" insert-after="cps_default"/>
>>>   <layer name="cps_subscriptions_installer" insert- 
>>> after="cps_default"/>
>>>  </skin-path>
>>> '''
>>> in CPSSubscriptions/profiles/default/skins.xml and other extension  
>>> profiles?
>>
>
> What's the question exactly? The meaning of insert-after ? The fact  
> that it's after cps_default ?
>
> If it's why there's CPSSkins and CPSSkins-macroless, I don't know, I  
> just kept the preexisting configuration. Jean-Marc? Do we still need  
> both?
>
>
Yes, both are needed (CPSSkins and CPSSkins-macroless), because the 
macroless skin is used by the main content templet to render the content 
of the main ZPT macro slot using python code.

the skins overrides the default 'main_template.pt' with:

<metal:block define-slot="main" />

I don't know about the cps_subscriptions skin though.

/JM


More information about the cps-devel mailing list
More information about CPS: CPS project - CVS - API

Hosting: Nuxeo: Zope service provider


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