Hi,
Usually, I use WOSwitchComponent for an editor component used for an entity with subclasses. The switch is based on the object real entity to select the right editor component.
With WOSwitchComponent, there are 2 things to ensure:
1- Binding required for the used components are common to all of them.
2- Make sure the the component used by the WOSwitchComponent does not change between two responses, breaking this rule is easy and produce very nasty results. i.e. it should change only during appendToResponse. (Same rule for WORepetition list...)
For surrounding contents commun to multiple pages, a PageWrapper using the WOComponentContent is a better pattern, I often even stack them. A main page wrapper for the application and a specialized one for admin sections or visitor pages that will include the main one.
WOComponentContent indicate to place the content between the parent <WEBOBJECT> and </WEBOBJECT> tags. It is a reverse inclusion to add content around us !
Samuel
Le 2015-06-02 à 07:43, HOUNKPONOU Ronald < email@hidden> a écrit :
Hi everyone, Actually, i think all my pages (managed by woswitch) will have the same binding. I am now implementing the woswitching and it seems to work fine for the moment. The one thing i am having problem with is the menu on which user will click to trigger the component switch.
Trying to use AjaxUpdateLink for the first time.
Thank you all for your contributions.
Ronald.
|