jerrybrown5
23 Feb 2008, 6:08 PM
Components such as TabPanel are incredibly powerful but equally strict in terms of what options must be turned on with which child items. The failure to adhere to these rules causes headaches and lost productivity time to experienced web programmers and can turn newbies completely off of this library--not to mention the added support time on your side.
Example of hidden handshakes on just the TabPanel component:
deferredRender:true,
layoutOnTabChange: true,
layoutConfig : { renderHidden : true },
defaults:{hideMode:'offsets'},
I recommend that when items that cause special requirements get added to a container it should bubble the requirement up the container chain to set these particular rules...eg adding a child border layout inside a particular tab needs to set the hideMode:'offsets' of the tab container. This is just one example but I believe a rules engine like this would help more developers utilize the full power of this great layout/component engine.
Regards,
Jerry Brown
Example of hidden handshakes on just the TabPanel component:
deferredRender:true,
layoutOnTabChange: true,
layoutConfig : { renderHidden : true },
defaults:{hideMode:'offsets'},
I recommend that when items that cause special requirements get added to a container it should bubble the requirement up the container chain to set these particular rules...eg adding a child border layout inside a particular tab needs to set the hideMode:'offsets' of the tab container. This is just one example but I believe a rules engine like this would help more developers utilize the full power of this great layout/component engine.
Regards,
Jerry Brown