RE: [flexcoders] Cairngorm and deferred instantiation

[Steven Webster]

Michael,   Looking at this a little differently ... can you give us an idea as to why the ViewHelper not being instantiated until the view is instantiated, is causing you a problem ?   Since the view helper exists to help you manipulate a view, then if the view doesn't exist *arguably) the view helper needn't exist yet.   If you could provide a use-case as to why the viewhelper should exist before the view, perhaps we can identify whether what you're trying to achieve, might be achieved more elegantly with a different strategy ?   Cairngorm is a lightweight framework, and it seemsto me that your application use-case (having an application that is composed of multiple applications that may or may not require to be created or used at all by the user) may merit some additional architecture and infrastructure to manage the application-specific problems that you are uncovering.   Best,   Steven   -- Steven Webster Technical Director iteration::two   This e-mail and any associated attachments transmitted with it may contain confidential information and must not be copied, or disclosed, or used by anyone other than the intended recipient(s). If you are not the intended recipient(s) please destroy this e-mail, and any copies ofit, immediately.   Please also note that while software systems havebeen used to try to ensure that this e-mail has been swept for viruses, iteration::two do not accept responsibility for any damage or loss caused in respect of any viruses transmitted by the e-mail. Please ensure your own checks are carried out before any attachments are opened.   From: Michael Herron [mailto:[EMAIL PROTECTED] Sent: 17 February 2005 17:14 To: flexcoders@yahoogroups.com Subject: RE: [flexcoders] Cairngorm and deferred instantiation That’s certainly a workable strategy, but from a design point of view the separate “tabs” (in reality a view stack but works on same principles) are really applications within their own right and I would like to be able include them just by passing their root mxml name. Also, children will be added at run time tothe view stack using the create child method so I don’t want to have todefine all the required view helpers for applications that may not be loaded.   Looks like I will have to use the view locator 3 separate times in the execute, onResult and onFault methods…