Laurentiu Ceausescu wrote: > In order to better display quick help. quick links, etc., I want to make > a new component (say RightColumn) that can receive a list of components > and add them on page (in the right side).
So you basically want to render them in the <div /> that is styled as the 3rd column, right? Just as we render 'left navigation'? That would make solving problems such a overflowing tables much easier (although I have a patch from Carolyn that might just solve this problem once for all - she added an extra div to wrap all the tables with). > This component will be used to display components such as quick help, > download link, etc. > I have thought of a solution to pass those components from page to > RightColumn component. I was thinking of giving unique ids to components > that we want to display in the right side. > And inside the RightColumn component to check the list of all components > against the passed list and display the passed components. > > But I'm wondering if this works. > For example, if we have a custom component into a page which has a quick > help, I think that we want to pass just the id of the quick help because > we want to display just the quich help in the right side. > However, if that component is used twice, than we will not have unique ids. > Yup - the ID idea will not work: since the client IDs are calculated dynamically by Tapestry. Did you try using the component type as an indicator? Another option is to add a meta property [1] to such components - I never used them but it strikes me as a way to mark some components - as long as you can get to metas from your new RightColumn. BTW: please don't use 'Right' in the name of the component. How things are rendered should be defined by CSS. All you need is to gather some components into a special <div /> and leave rendering details to whoever writes CSS. Using names like "Left", "Right" or "Top" might be quite misleading. D. [1] http://tapestry.apache.org/tapestry4.1/usersguide/injection.html _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
