Re: T5: Best practice for rendering a dynamic component

2008-12-09 Thread mad7777
- From: Howard Lewis Ship [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 23, 2007 1:41 PM To: Tapestry users Subject: Re: T5: Best practice for rendering a dynamic component The Delegate component is what you need: t:delegate to=fruit/ @Component private Apple apple

Re: T5: Best practice for rendering a dynamic component

2007-05-25 Thread Howard Lewis Ship
In fact, BeanEditForm and Grid suffer from the same problem, and a fix will be forthcoming. Basically, there will be a configuration point for contributing page names, and matching them up to (in BeanEditForm/Grid) various property types. The same pattern can hold; define new pages, contribute

RE: T5: Best practice for rendering a dynamic component

2007-05-24 Thread Joel Wiegman
; } return null; } -Original Message- From: Howard Lewis Ship [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 23, 2007 4:08 PM To: Tapestry users Subject: Re: T5: Best practice for rendering a dynamic component Absolutely. You can put it inside

Re: T5: Best practice for rendering a dynamic component

2007-05-24 Thread Howard Lewis Ship
, May 23, 2007 1:41 PM To: Tapestry users Subject: Re: T5: Best practice for rendering a dynamic component The Delegate component is what you need: t:delegate to=fruit/ @Component private Apple apple; @Component private Banana banana; public Object getFruit() { if ( ... ) return apple

Re: T5: Best practice for rendering a dynamic component

2007-05-23 Thread Howard Lewis Ship
The Delegate component is what you need: t:delegate to=fruit/ @Component private Apple _apple; @Component private Banana _banana; public Object getFruit() { if ( ... ) return _apple; return _banana; } With Tapestry, the construction of pages is static, fixed, unchanging, much like the

RE: T5: Best practice for rendering a dynamic component

2007-05-23 Thread Joel Wiegman
the rendering of it? -Original Message- From: Howard Lewis Ship [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 23, 2007 1:41 PM To: Tapestry users Subject: Re: T5: Best practice for rendering a dynamic component The Delegate component is what you need: t:delegate to=fruit/ @Component private

Re: T5: Best practice for rendering a dynamic component

2007-05-23 Thread Howard Lewis Ship
: Best practice for rendering a dynamic component The Delegate component is what you need: t:delegate to=fruit/ @Component private Apple apple; @Component private Banana banana; public Object getFruit() { if ( ... ) return apple; return banana; } With Tapestry, the construction of pages

Re: T5: Best practice for rendering a dynamic component

2007-05-23 Thread Daniel Tabuenca
PROTECTED] Sent: Wednesday, May 23, 2007 1:41 PM To: Tapestry users Subject: Re: T5: Best practice for rendering a dynamic component The Delegate component is what you need: t:delegate to=fruit/ @Component private Apple apple; @Component private Banana banana; public Object getFruit

Re: T5: Best practice for rendering a dynamic component

2007-05-23 Thread Howard Lewis Ship
: Howard Lewis Ship [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 23, 2007 1:41 PM To: Tapestry users Subject: Re: T5: Best practice for rendering a dynamic component The Delegate component is what you need: t:delegate to=fruit/ @Component private Apple apple; @Component