IMO, this is not about one dynamic component. If you open the door to introduce the dynamically created component, you introduce a chain of things. People will ask for everything equivalent to Swing, you will need layout components, ..., etc. It will make everything complicated. In the hype of ajax, I think that it's not a good idea to spend a lot of time to develop a server side "Swing". Anyway, I think that Tapestry has a good infrastructure, if you really like dynamic components, maybe you can create a subproject to create a DynamicPage service.
just my two cents. On 1/27/06, Norbert Sándor <[EMAIL PROTECTED]> wrote: > > > rock on... is PROPERLY FACTORED in capitols because you are shouting it? > > lol > Maybe he only wanted you to pay more attention to those words.... > > Why is it so hard to instantiate a component when needed? Tapestry's > infrastructure could do it because it is a suboperation of instantiating a > page, only a public API is needed for this. Or are there any theoretical > difficulties I haven't recognised? > (I know that it is an expensive operation, but if so many developers want > to > do it, Tapestry should support it. Maybe these dynamically constructed > component instances could be pooled as well!) > > Regards, > Norbi > > ----- Original Message ----- > From: "gaz jones" <[EMAIL PROTECTED]> > To: "Tapestry users" <tapestry-user@jakarta.apache.org> > Sent: Friday, January 27, 2006 5:57 PM > Subject: Re: tapestry not really component based? > > > >No, what it means is that Tapestry is PROPERLY FACTORED, such that > >generating links is not the concern of the components that render > >those links, > > rock on... is PROPERLY FACTORED in capitols because you are shouting it? > lol > > >making it easy to get the same or similar behavior of a > >component, such as PageLink, without using a template. If you want to > >use a PageLink, extend from BaseComponent and use a template. > > but i want to use a pagelink in my code :( ... bah, but fine if thats the > way tapestry works... > > >If you want to write your components in code, make use of the Engine > Services > >to generate your links, just like the built-in components do. > > this is exactly what i did after looking at the source for the PageLink > component when i first had the problem. my irritation is that there is > already a component existing that does this and i cant re-use it in code. > instead i have to repeat the effort of the PageLink author. i dont like to > repeat myself. repeating myself is not something i like to do. > > aaaanyway, this was only a side-note to the original post which was about > a > problem with accessing looped components inside complex forms... > > > On 1/27/06, Howard Lewis Ship <[EMAIL PROTECTED]> wrote: > > > > > imo that is a major disadvantage, as it prevents you from dynamically > > > creating components that are made up of _other_ components when you > > inherit > > > from AbstractComponet - that is a REAL pain. and something you can do > > easily > > > in other component based frameworks. > > > > > > > No, what it means is that Tapestry is PROPERLY FACTORED, such that > > generating links is not the concern of the components that render > > those links, making it easy to get the same or similar behavior of a > > component, such as PageLink, without using a template. If you want to > > use a PageLink, extend from BaseComponent and use a template. If you > > want to write your components in code, make use of the Engine Services > > to generate your links, just like the built-in components do. > > > > The scalability that Tapestry gets because of its rigid page and > > component structure is one of its clear differentiators; something > > I've heard that the JSF Expert Group is envious about. The structure > > is rigid, the behavior is highly dynamic. That's good enough for > > almost everyone. > > > > What I expect to do in a later release of Tapestry is change and > > simplify the APIs so that it doesn't even look like something you can > > or should do. > > -- > > Howard M. Lewis Ship > > Independent J2EE / Open-Source Java Consultant > > Creator, Jakarta Tapestry > > Creator, Jakarta HiveMind > > > > Professional Tapestry training, mentoring, support > > and project work. http://howardlewisship.com > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > -------------------------------------------------------------------------------- > > > No virus found in this incoming message. > Checked by AVG Free Edition. > Version: 7.1.375 / Virus Database: 267.14.22/239 - Release Date: 2006. 01. > 24. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
