Olivier Grisel wrote:
Jean-Marc Orliaguet a écrit :
Hi,
Reply to Thibaut:
I'm thinking of implementing the association between view ids and themes
(a.k.a 'method themes' in CPSSkins).
Yes that would be great and soon needed, indeed. What other negociation
strategies a part from the application root are already implemented?
a negotiation strategy is a series of steps:
- check a URL parameter
- check a cookie
- check the view id
- ...
executed in a given order to ultimately determine which theme / engine /
perspective to use in a given context.
there is no "better" obvious order, hence an application must specify
which negotiation strategy to use. The default strategy is defined in
NXThemesJsf:
<extension target="org.nuxeo.theme.services.ThemeService"
point="negotiations">
<negotiation object="engine" strategy="default">
<scheme>
org.nuxeo.theme.jsf.negotiation.objects.engine.RequestParameter
</scheme>
<scheme>
org.nuxeo.theme.jsf.negotiation.objects.engine.CookieValue
</scheme>
<scheme>
org.nuxeo.theme.jsf.negotiation.objects.common.DefaultEngine
</scheme>
</negotiation>
</extension>
...
Other question: what is the state of the perspective management? Does a
perspective include the id of the page to be displayed (ie does it affect the
layout) or just a mask for the theme fragments?
perspectives are implemented ( in the UI too). It's just that the nuxeo5
application defines only one perspective (default).
at the moment perspectives define the visibility of fragments (always
visible vs visible in a collection of perspectives)
/JM
_______________________________________________
ECM mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm
