Re: do you want to blow your mind?
Re: do you want to blow your mind?
- Subject: Re: do you want to blow your mind?
- From: Lachlan Deck <email@hidden>
- Date: Sun, 19 Oct 2008 13:47:35 +1100
On 19/10/2008, at 1:52 AM, Mike Schrag wrote:
particularly given that there will only be one instance of a
WOSwitchComponent on a given parsed page (meaning that if there's
a WOSwitchComponent for an element in your Main component, there
will only be ONE INSTANCE of WOSwitchComponent servicing that slot
on the page for all of your users).
I'm not convinced of that .. yet. i.e., It's not a stateless
component, but then again it's not a subclass of WOComponent but
WODynamicElement. So okay ... back to me first answer :-)
Yeah, exactly ... It's sort of nuts, right?
So the magic is WOComponentReference + WOComponentDefinition +
WOComponent. What happens is that when your template is parsed, it
gets parsed into a bunch of WOComponentReferences. If you
understand WOAssociation, WOComponentReference is like the
equivalent concept for components. That is, you have a handle that
says "I represent an AjaxInPlace with a set of bindings" but it's
not a stateful instance, it just describes how you're going to use it.
<...>
So anyway ... That's the long story that probably nobody else cares
about, but I think it's sort of a fascinating aspect of WO, because
it's this crazy and clever underpinning that makes the entire
framework function that I really had no idea about the inner
workings of.
Interesting... need more time to ponder this :-)
Looking forward to seeing what comes of your partial pages.
with regards,
--
Lachlan Deck
_______________________________________________
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