Yes, you'll find it in wicket-extensions and an example in wicket-examples
Juergen
On 11/1/05, David Liebeherr [EMAIL PROTECTED] wrote:
I guess i will find this all in the CVS versions, do i?
Thank you very much,
Dave
Igor Vaynberg wrote:
Just checked in my first pass at implementation.
I guess i will find this all in the CVS versions, do i?
Thank you very much,
Dave
Igor Vaynberg wrote:
Just checked in my first pass at implementation. Its in
wicket-extensions wicket.extensions.markup.html.tabs.TabbedPanel.
There is also an example in the component reference that shows four
Not core, but a support project is nice. Please take a look at
wicket-stuff and look (in CVS) at the wicket-contrib-navmenu project.
There's an example for it in wicket-stuff-examples.
I need more people to participate/ contribute to this too, so please help.
Eelco
On 10/30/05, Andrew Berman
In my Ui design experience i found WicketStack very usefull, i my
current wicket app i design my own wicket stackt that was very simple
using standar wicket components i extend panel and adding only this
tow methods and a java Map that permit me to map panelName to a
component
void addPanel(Panel
I use the idea of a
public interface Tab {
IModel getTitle();
Panel getPanel(String panelId);
}
My tabbedpane component takes in a list of Tab object, this allows me to create the panels dynamically - only when they are accessed by the user. I think this is a better approach then creating all
Can you share your Component with us?
that would be nice
Thanks,
Dave
Igor Vaynberg wrote:
I use the idea of a
public interface Tab {
IModel getTitle();
Panel getPanel(String panelId);
}
My tabbedpane component takes in a list of Tab object, this allows me
to create the panels
Tabs like that could work too. Maybe easier than navmenu. The idea
behind navmenu was that navigation inherently is a tree structure -
possibly just one level - but in such a way that you wnat to access
each level seperately (so that you can render each level
independently). Having a tree makes it
Just checked in my first pass at implementation. Its in wicket-extensions wicket.extensions.markup.html.tabs.TabbedPanel. There is also an example in the component reference that shows four different css styles. Check it out and let me know what you think and how we can make it better.
-Igor
On
why is it a core component?
It is mostly a design issue if you ask me.
Because under neath it are just links that are setting a panel (or switching visibility)
How would such a component look like?
On 10/30/05, Stefan Lindner [EMAIL PROTECTED] wrote:
Dear Dave, dear wicket developers,I had the
I agree with Johan. Tabs are by no means a core component.
In fact, you can accomplish tabs easily using a ListView and some CSS,
so it's definitely a design issue as Johan mentioned.
See these for the CSS to create tabs:
http://www.alistapart.com/articles/slidingdoors/
10 matches
Mail list logo
