On 30 Mar 2006, at 01:35, [EMAIL PROTECTED] wrote:
Here is a posting by Robert Zeigler from Decemeber that says it all (I
hope it's considered polite to quote at length). It's seems Tap3-
centric,
but probably applies to Tap4 as well.
Ah ha! (and thanks for bending the rules and 'quoting at length' ;)
Note the quote "static structure, dynamic behavior", which is why this
seems so hard/unnatural--you're looking for dynamic structure. Static
structure, dynamic behavior is Tapestry's motto--quite different
from some
other frameworks, which have dynamic structure at their core.
Yes, I had been getting that message from looking at the framework
code itself Mike (static structure, dynamic behavior). If I'm honest,
I can see that design principle weakening over time with frameworks
like Hivemind on the scene that positively encourage 'emergent'
behavior.
That said, and from my point of view this is the most important thing
-- I think that post helps me a lot -- it hadn't occurred to me that
it might be possible to 'extract' the component from another page.
I've already implemented infrastructure that automatically adds
libraries to the application specification based on hivemind
contributions, so it's a logical extension of this for the modules to
provide their 'plug-in' UI components embedded within blocks in the
page, and then render them into the page at runtime.
I'll give this a whirl, but I'd be interested to know if anyone else
has any appetite for dynamic component creation, or whether that's
just me!
Paul
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
