Re: [T5] instantiate a component on the fly

2007-08-21 Thread David Avenante
On 8/20/07, Howard Lewis Ship <[EMAIL PROTECTED]> wrote: > > That's close to my opinion. > > I appreciate how people would like to create a new component on the > fly, and I understand the use cases involving that. > > However, it goes against the grain of Tapestry. I've finally > documented this,

Re: [T5] instantiate a component on the fly

2007-08-20 Thread Massimo Lusetti
On 8/21/07, Howard Lewis Ship <[EMAIL PROTECTED]> wrote: > However, it goes against the grain of Tapestry. I've finally > documented this, the concept of static structure and dynamic behavior. This seems to answer (or comment if you prefer) on other thread "Recursion of components", nice! -- M

Re: [T5] instantiate a component on the fly

2007-08-20 Thread Howard Lewis Ship
> > > > -Original Message- > From: David Avenante [mailto:[EMAIL PROTECTED] > Sent: Fri 8/17/2007 10:29 AM > To: Tapestry users > Subject: Re: [T5] instantiate a component on the fly > > Hum I not sure. > > My component is not define in class and is

Re: [T5] instantiate a component on the fly

2007-08-20 Thread David Avenante
Humm alway in my way So I try to enhance T5 to support some Ajax Features. 1 - I've Aliased the ComponentActionRequestHandler to use my own. 2 - Now if my ComponentAction is and ajax action ex : http://mySite/myPage.myComponent:ajax/99 I want try to instanciate my targeted component. So I

Re: [T5] instantiate a component on the fly

2007-08-17 Thread David Avenante
Yes but in an Ajax point of view I think you can't use this approach in my humble point of view. In an Ajax way for me the good approach is to have a component call like ComponentSubstitution who encapsulate and permit to generate an Ajax return whit html node substitution. With T5 it's very easy

RE: [T5] instantiate a component on the fly

2007-08-17 Thread Mark Stang
k J. Stang Software Engineer office: +1 303.468.2900 Ping Identity -Original Message- From: David Avenante [mailto:[EMAIL PROTECTED] Sent: Fri 8/17/2007 10:29 AM To: Tapestry users Subject: Re: [T5] instantiate a component on the fly Hum I not sure. My component is not define in class

Re: [T5] instantiate a component on the fly

2007-08-17 Thread David Avenante
Hum I not sure. My component is not define in class and is not define in the template => It's a really a NEW component. So as I can see there is a possibility with PageElementFactory.newComponentElement() that I can inject in my page. But there is too many parameters. I hope Tapestry give me

Re: [T5] instantiate a component on the fly

2007-08-17 Thread Robert Zeigler
Best bet here is probably to put your component into a block, then render the block (or else grab the component from the block and render the component). Check out the "delegate" component, for example. Robert On Aug 17, 2007, at 8/179:26 AM , David Avenante wrote: Hi, I'm very disappoint

[T5] instantiate a component on the fly

2007-08-17 Thread David Avenante
Hi, I'm very disappointed. After some investigation it seem it's not possible to instantiate a component in a page on the fly in T5. I have a page and his template, my component is not defined on the template but on a specific event, I want to create and instantiate this component. I need someth