ModalX allows you to create set of 'generic' modal windows waiting in the wings ready for display.
Any specific modal that you want simply needs to derive from a generic modal class and you can then open it at will. See here for info and demo: http://www.visualclassworks.com/list/modalx-for-wicket/modalx All open source Wicket and it's part of WicketStuff https://github.com/wicketstuff/core/wiki/ModalX I'm not sure it's exactly what you're after when when you said you want to avoid having 20 invisible dialogs already rendered and opened on request that reminded me of the very reason we created ModalX in the first place. Regards, Chris >-----Original Message----- >From: Patrick Davids [mailto:[email protected]] >Sent: Friday, 5 July 2013 7:16 PM >To: [email protected] >Subject: conditional component / as singleton on page > >Hi all, >does anyone have a best practice putting a component on a page (as >singleton) independendly how many other components on that page "needs" it? > >e.g. a global dialog, which can be used from different components. >Not to have 20 invisible dialogs aleady rendered and opened on request. > >In out special to achieve this we do not want use page inheritence. >This component shouldn't be on page, if no other component needs it. > >thanx for help... >kind regards >Patrick >--------------------------------------------------------------------- >To unsubscribe, e-mail: [email protected] >For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
