Sure, the wiki is open for contributions. musachy
On 5/3/07, Felipe Rodrigues <[EMAIL PROTECTED]> wrote:
Sounds good. I'm using the workaround display: none and its working as expected. I'm learning lots of workaround looking at templates. Each time I got any issue, I report it, after ask here and get a proff it is really an issue. But I think we really need a doc telling about these little things about Ajax theme. I can help you to do that if you want to. Just let me know. Thanks, Felipe Musachy Barroso wrote: > > The first tab is the default one, but you can change that using the > "selectedTab" in the tabbedPanel tag. Dynamic tabs load their content > automatically, this was mentioned on another thread and was fixed in > WW-1860, adding a "preload" (defaults to true) attribute to the div tag. > Bear in mind the ajax theme is experimental, so feel free to log jira > tickets for any problem you find and we'll try to fix them for 2.1 (big > ajax > overhaul). Thanks for flying with struts ajax theme :) > > regards > musachy > > On 5/3/07, Felipe Rodrigues <[EMAIL PROTECTED]> wrote: >> >> >> Hi Guys, >> >> I'm really trying to use TabbedPannel, but it seems to have lots of >> problems >> when you try to use in a real world WebApp. >> >> For example, I have a TabbedPannel with 6 tabs. Each one is a remote one. >> The problem here is, when the user change the tab, I need to update a >> session attribute. But TabbedPannel don't have the events support (yet, >> because there is an open issue for that), so I changed to refreshOnShow >> and >> executeScripts = true. >> Then I got new problems. The default tab is the first one, but struts >> render >> all of them and obviously, execute all its scripts, including the one >> wich >> changes the session attribute. The result is a mess, because the >> rendering >> depends on this attribute value, wich is there only to provide a way to >> app >> recognize what tab is selected. >> >> Another problem is that the first tab is executed once, when everyone is >> being redered, and execute again to show its content, since is the one >> which >> will be shown to user. This approach generate lots of Widget ID colision >> in >> the debug output. >> >> Sometimes I wonder if these things happens only in my case, because I >> can't >> find others threads about that in the mail-list. >> I'm waitting some answers to make a decision about keep tabbedPannel or >> exclude this forever (at least until this stuff be fixed). >> >> Thanks in advance guys, >> >> Felipe >> -- >> View this message in context: >> http://www.nabble.com/TabbedPannel%3A-So-many-problems.-tf3686055.html#a10303545 >> Sent from the Struts - User mailing list archive at Nabble.com. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > > -- > "Hey you! Would you help me to carry the stone?" Pink Floyd > > -- View this message in context: http://www.nabble.com/TabbedPannel%3A-So-many-problems.-tf3686055.html#a10305512 Sent from the Struts - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- "Hey you! Would you help me to carry the stone?" Pink Floyd
