Ok, I guess my next question is does the tag provide anything
significant on top of Dojo? If we are a simple wrapper for Dojo, it
might not be worth continuing to support the tabbed pane tag. What do
you think?
Don
Musachy Barroso wrote:
Well, dojo's has some of nice things out of the box(they are just hard
to figure out given the amount of documentation), tabs can placed on
any of the sides, you can have close buttons on the tabs, (either on
the tab or on a corner, firefox-style), and they look a lot better by
default ;)
about WW-1371, I will have to check it out.
Don Brown wrote:
Cool! Any chance it fixes other tickets like WW-1371? Do you think
this should be a new tag or replace the existing? What are the
advantages of the new implementation?
Don
Musachy Barroso wrote:
I picked WW-205, (https://issues.apache.org/struts/browse/WW-205) to
start playing with and I have replaced the tabbedpanel
implementation with dojo's implementation, so far I have the static
and dynamic tabs working. I was having so much fun that I didn't
stop to ask if this is what you guys want, although it is suggested
by Ian Roughley in the bug's comments.
musachy
Don Brown wrote:
The help would be appreciated. Take a look at the tag
documentation -
http://cwiki.apache.org/confluence/display/WW/Tag+Developers+Guide
- and look at the templates themselves in
core/src/main/resources/templates
There are several ajax-related issues in our JIRA right now, so
that would be a very helpful place to start. :)
Don
Musachy Barroso wrote:
Hi all,
I was checking out struts 2 yesterday (I'm a 1.2.7 user) and I
found that some of the UI tags(tree, tab panel...) overlap with a
project that I'm currently maintaining (ajaxtags at
http://ajaxtags.sourceforge.net/). I'd like to contribute to the
UI ajax tags, so some pointers on where to start or whom to talk
to would be appreciated. Ajaxtags is distributed under an apache
2.0 license so we could lift some code if needed.
thanks
musachy
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
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]
