Hmmm... That is doubtful. At least my initial gut reaction didn't like it very much.
Whether or not a form(s) should be hidden can be easily specified using a single property on a page (if need be) . If you need to control this for your entire application then you could make it a property on a single base page. (or interface that your pages implement) On 1/3/07, karthik G <[EMAIL PROTECTED]> wrote:
On 1/3/07, Jesse Kuhnert <[EMAIL PROTECTED]> wrote: > > I almost added a central hivemind service to expose those page > listener methods as global listeners you can have a hivemind service > implement to generically listen to all page changes (for all pages) that will be great. I want to be able to hide/disable all formcomponents based on some condition globally. Can we bind the hidden/enabled attributes all Form components to some interface method globally? thanks, Karthik
-- Jesse Kuhnert Tapestry/Dojo team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
