I don't think JPanel is going to be a fair comparison for layout logic. Are you saying that you want to dynamically render a block of UI depending on certain conditions? If that is the case then I would use Block and RenderBlock components (check documentation) to do it. I use them myself with no problems. (For instance, providing a specific form input for a list of N objects of different types.)
If it's anything other than dynamically choosing a component/container to display I would have to ask why/what you are trying to do exactly that html doesn't already handle? On 1/18/06, John Coleman <[EMAIL PROTECTED]> wrote: > > but what I am looking for is a sort of component that is a flexible > container for other components that I allocate dynamically, just like in > Swing you have a JPanel that you can add components to > > Is there a way to do JPanel in Tapestry? > > John > > ----- Original Message ----- > From: "Raul Raja Martinez" <[EMAIL PROTECTED]> > To: <[email protected]> > Sent: Wednesday, January 18, 2006 4:15 PM > Subject: Re: dynamic allocation of components? > > > > You don't have to declare components in a config file (.page or .jwc) if > > you don't want to. > > Tapestry supports implicit components that can be declared directly in > > the html template. > > For example: > > > > <span jwcid="@Insert" value="ognl:new java.util.Date()">June 26 > 2005</span> > > > > You can now use any html editor and move around the span tag as it was > > an standalone component. > > > > best regards. > > > > Raul. > > > > > > John Coleman wrote: > > > I've been playing with mamboserver, and like how you allocate modules > to > a > > > slot on the template. > > > > > > Anyone know how this can be achieved in Tapestry? > > > > > > I might want to have a sort of parent component called "bannercell", > and > > > then identify some components to stick into bannercell, maybe a search > > > component and a login form component for example. Ideally, as per > mambo > I > > > need to have a UI to move the components around, rather than have them > coded > > > into a config file. > > > > > > TIA > > > John > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
