Hi,
Reply to Thibaut:
I'm thinking of implementing the association between view ids and themes
(a.k.a 'method themes' in CPSSkins).
There is already an 'applications' extension point where theme settings
are stored. An application is identified by its context root (e.g.
/nuxeo): the 'negotiation strategy' defines the order in which
parameters are read (cookie, url parameter, view id, ...)
It could be something like:
<extension target="org.nuxeo.theme.services.ThemeService"
point="applications">
<application root="/nuxeo">
<negotiationStrategy>default</negotiationStrategy>
<view id="/workspaces.xhtml">
<theme>default/workspaces</theme>
</view>
<view id="/relations.xhtml">
<theme>default/relations</theme>
</view>
</application>
</extension>
/JM
_______________________________________________
ECM mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm
