I'm not sure if that would be a good idea, the thing is that it would
add a set of dependencies that I don't think are desirable
(scriptaculous, prototype, overlib, etc), I don't see ajaxtags going too
far in the future if struts supports these simple ajax tags, because
most of its users are using struts anyway. If you guys decide to keep
the ajax tags I will work on them despite they are in ajaxtags already.
I think keeping thin wrappers over dojo's stuff is a good idea.
Don Brown wrote:
Ok, sounds reasonable. I'm all for offloading the maintaining of code
to other projects when possible :)
Hmm...I wonder...could your work be improved to allow your tags to be
called from velocity and freemarker as well? Currently, IMO, Struts
has only half-hearted support for Ajax widgets and while we've talked
about a compressive strategy to tackle the problem, it was never
enacted upon.
I wonder if there is any way to link our projects better so that we
can eliminate the overlap.... Some way of delegating the actual tags
to you, but perhaps provide some advanced features that could only be
developed when you have control over the server framework...I'm
thinking of DWR or JSON views of Struts actions here...
Don
Musachy Barroso wrote:
It doesn't provide anything on top of Dojo right now, it is just a
wrapper. Even when it is available using dojo, it is really nice
when you get isolated from the js and just have to use a couple of
tags on your page. That's what ajaxtags does, wrappers around other
widgets(scriptaculous and family) and people are using it a lot.
Considering that we are using dojo anyway, and that it is almost done
(with not too much effort), I think we should keep it.
musachy
Don Brown wrote:
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]
---------------------------------------------------------------------
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]
