> 1. Is it OK to create multiple Fragment objects for the same markup fragment? yes, the relation is: 1 "markup fragment", 1 "fragment type", n "fragment objects"
> 2. Is it possible to nest Fragments so that I can support multiple > levels of tabs? yes, the Fragment extends from Component, and as an Component, it can to be placed where you want. On Mon, Jun 14, 2010 at 4:35 PM, Alec Swan <alecs...@gmail.com> wrote: > Hello Pedro, > > I am not sure what you mean by "wrapped panels", but I am planning to > have a l<ul/> list and single fragment with wicket:id="tabTemplate" > on my page. > > When the user accesses the page the first time, the Page code will > populate the list and display the first tab with the content pulled > from the database. The code will also keep a reference to that > fragment object. > > When the user selects a different tab, the code will create a new > fragment and will swap it with the one from the previous step. > > The two issues that I am concerned about are: > 1. Is it OK to create multiple Fragment objects for the same markup > fragment? > 2. Is it possible to nest Fragments so that I can support multiple > levels of tabs? > > Thanks, > > Alec > > On Mon, Jun 14, 2010 at 11:17 AM, Pedro Santos <pedros...@gmail.com> > wrote: > > wicket:container are meant to don't output invalid markup when using > > repeaters. You can use AjaxTabbedPanel to implement your tabbed panel, > and > > ITab for the complexity of swap your tabs contents... > > In my last mail I said that is preferably to have you logic that use > > database info to assemble your tabbed panel in an Wicket component, > rather > > than in javascript. > > > > About create an new component TabbedContents, I exaggerated. There is no > > good reason to create an new type and api for that. If the component > initial > > component design don't solve all user cases, we can always write > > customizations. Do you considered to use an wrapper panels for your > > fragments, your write panels for them? > > > > On Mon, Jun 14, 2010 at 1:39 PM, Alec Swan <alecs...@gmail.com> wrote: > > > >> Pedro, could you clarify your last message? > >> > >> I also came across wicket:container. I don't think it is possible to > >> swap container components at runtime because they don't have HTML ids > >> and hence cannot be reference via AJAX. Is that right? > >> > >> Thanks > >> > >> On Mon, Jun 14, 2010 at 10:11 AM, Pedro Santos <pedros...@gmail.com> > >> wrote: > >> > "I am working with a web designer who delivers a single HTML page > which > >> > should display a panel with tabs." > >> > Simply use javascript > >> > > >> > With "arbitrary number of", " loaded from the database at runtime" > >> > Is preferable to implement an component at server side with the tabs > >> > assemble and presentation rules. > >> > > >> > On Mon, Jun 14, 2010 at 12:16 PM, Igor Vaynberg < > igor.vaynb...@gmail.com > >> >wrote: > >> > > >> >> you can simply use javascript tabs. all js frameworks provide them. > >> >> > >> >> -igor > >> >> > >> >> On Sun, Jun 13, 2010 at 6:54 PM, Alec Swan <alecs...@gmail.com> > wrote: > >> >> > Hello, > >> >> > > >> >> > I am working with a web designer who delivers a single HTML page > which > >> >> > should display a panel with arbitrary number of tabs. In the HTML > the > >> >> > tabbed panel consists of a <ul> list of links and the content of > the > >> >> > first tab. The content for the remaining tabs is loaded from the > >> >> > database at runtime. > >> >> > > >> >> > I know how to implement tabbing using tab swapping or TabbedPanel. > >> >> > However, both of these approaches require a separate panel object > and > >> >> > markup for the tabs. Instead, I would like to be able to use the > HTML > >> >> > page I received from the designer unmodified. > >> >> > > >> >> > Is there a way to create a WebMarkupContainerWithAssociatedMarkup > >> >> > object which is mapped to a specific element on the page markup? If > >> >> > so, can I implement tabbing by swapping such objects when tabs are > >> >> > clicked? > >> >> > > >> >> > Any ideas would be appreciated. > >> >> > > >> >> > Thanks > >> >> > > >> >> > > --------------------------------------------------------------------- > >> >> > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > >> >> > For additional commands, e-mail: users-h...@wicket.apache.org > >> >> > > >> >> > > >> >> > >> >> --------------------------------------------------------------------- > >> >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > >> >> For additional commands, e-mail: users-h...@wicket.apache.org > >> >> > >> >> > >> > > >> > > >> > -- > >> > Pedro Henrique Oliveira dos Santos > >> > > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > >> For additional commands, e-mail: users-h...@wicket.apache.org > >> > >> > > > > > > -- > > Pedro Henrique Oliveira dos Santos > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- Pedro Henrique Oliveira dos Santos
