How's it just going to work? I can break component independence with
as simple a line of code as:
protected void renderComponent(IMarkupWriter writer, IRequestCycle cycle)
{
IForm currentForm = getForm(cycle);
String currentComponentId = currentForm.getElementId();
}
That's the way all the OOB form components generate their component
IDs, and it's guaranteed not to work in a partial render (in the special
case of a form with no dynamic elements, it might be determinable by
introspecting the component tree, but that's a lot of work for a special
case solution).
Or did some sort of major overhaul of the compoment naming scheme
take place in 4.0? Even then, I can still write a component which calls
getPage().doSomething() in which case my component is lost without the
page...
--- Pat
> -----Original Message-----
> From: Jesse Kuhnert [mailto:[EMAIL PROTECTED]
> Sent: Thursday, December 01, 2005 1:05 PM
> To: Tapestry users
> Subject: Re: daydreaming of tapetry and ajax
>
> It's all because of Tapestry's/hivemind wonderful binding parameter
> infrastructure. You really can do this, and the components ~don't~ need to
> be completely self contained. It just works :)
>
> I think the interfaces/IRequestCycle/base classes all provide more than
> enough for this functionality to also "just work". There are more ideal
> new
> concepts that I'd like to introduce, but overall the framework really does
> support these things as is. It just needs an ever so slight change here or
> there to make it possbile. I promise, it really is possible. You will see
> :)
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
