Re: WOComponent children
Re: WOComponent children
- Subject: Re: WOComponent children
- From: Mike Schrag <email@hidden>
- Date: Mon, 7 Jan 2008 13:52:52 -0500
Awake is just not going to give you what you want. I think the only
thing that will do that is some major changes to WO. It would
probably be best to do something like record the needed resources in
the .api file and when the .wo template is parsed, this information
gets propagated up to the page. I think this would be more
successful and trying to handle this as part of the RR loop.
Conceptually, this seems more associated with interpreting the
template than with a specific request. And when you are parsing the
WOD file, it is easy to see what is used, regardless of later
WOConditional states. That said, WOSwitchComponent is still going
to break that.
Except that .api files are never used at runtime ... I think Lachlan's
suggestion of lazily loading js/css is probably the best bet for
success without chopping up the core frameworks and potentially
introducing some really strange behaviors. I suspect with a little
bit of js trickery you could make this pretty smooth to not reload
files it has already loaded. This could also be solved in Ajax
framework only without monkeying with the core frameworks.
ms
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden