I'm probably not the best person for describing what he might be thinking,
but here are some thoughts. .

mixins - http://en.wikipedia.org/wiki/Mixins

More or less allows you to dynamically add methods/implementation of things
to classes at runtime. Howard's already been doing this in a way with the
render enhancement workers, but I'm guessing this is a more direct approach
based on annotations. So, if you define a listener method in your class that
you want to be invoked when the "PropertySelection" component value has
changed on the client you might in theory be able to do something like:

@EventListener(component="myPropertySelect", event="onChange",
validateForm="false")
public void selectSomethingBasedOnProperty(Object foo) {
....
}

It can probably get a ~lot~ more dynamic and graceful than that, but the
basic premise I think is that he'd be going in and automagically connecting
all of these things for you..Instead of having to manually specify a lot of
logic all over the place. The same would hold true for a lot of other things
as well I'm guessing.

rendering queue - Again, no idea what's actually in his head, but my
layman's notion of it was that this would more or less be addressing the
issue of not knowing about something until you get to it, and then more or
less it being too late to do something smarter by the time you've gotten
there..

This would enable css to be globally contributed into the Shell for example.
So, we know how the Form does the rewind cycles...It passes in a null writer
that basically still does the entire render, it just doesn't output
anything..I think in this scenerio he would completely break out the logic
of rendering from the logic that sort of "moves the cycle forward". ..Making
it very very efficient to do the form rewind sort of logic if the actual
rendering is made into a seperate thing.

This would also make about 10 billion other things much better. Like direct
component renders, etc....

That's a layman's view on it though. I'm sure there is more too it but I
think that is the overall ~reason~ for the queue, even if not what the
actual details would contain.

On 2/27/06, Geoff Longman <[EMAIL PROTECTED]> wrote:
>
> Howard,
>
> You described a rendering queue and mixins recently.
>
> Frankly I don't understand what you are getting at.
>
> Care to elaborate? Thanks.
>
> Geoff
>
> --
> The Spindle guy.          http://spindle.sf.net
> Get help with Spindle:
> http://lists.sourceforge.net/mailman/listinfo/spindle-user
> Blog:                     http://jroller.com/page/glongman
> Feature Updates:          http://spindle.sf.net/updates
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Reply via email to