2011/4/26 Jason Pyeron :
>> -Original Message-
>> From: Lukasz Lenart [mailto:lukasz.len...@googlemail.com]
>> Sent: Tuesday, April 26, 2011 14:26
>> To: Struts Developers List
>> Subject: Re: Moving Dojo plugin to archive
>>
>> 2011/4/26 Jason Pye
On Tue, Apr 26, 2011 at 2:49 PM, Dave Newton wrote:
> Potentially. IMO non-trivial-enough to be worth it [...]
I meant "not worth it".
d.
-
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mai
uesday, April 26, 2011 14:26
>> To: Struts Developers List
>> Subject: Re: Moving Dojo plugin to archive
>>
>> 2011/4/26 Jason Pyeron :
>> > What are the reasons for moving it?
>>
>> It's support the old version of Dojo - 0.4 as I can reca
> -Original Message-
> From: Lukasz Lenart [mailto:lukasz.len...@googlemail.com]
> Sent: Tuesday, April 26, 2011 14:26
> To: Struts Developers List
> Subject: Re: Moving Dojo plugin to archive
>
> 2011/4/26 Jason Pyeron :
> > What are the reasons for moving it
2011/4/26 Jason Pyeron :
> What are the reasons for moving it?
It's support the old version of Dojo - 0.4 as I can recall
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
Warszawa JUG conference - Confitura http://confitura.pl/
--
What are the reasons for moving it?
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
- -
- Jason Pyeron PD Inc. http://www.pdinc.us -
- Principal Consultant 10 West 24th Street #100
2010/8/24 Martin Cooper :
> If there's a good reason for not having the code in the main trunk,
> even when it's not part of the distribution, then I suppose it could
> be moved back to the sandbox, or even to the archive.
Basically not, it can stay where it is right now. There is a minor
problem
On Sat, Aug 21, 2010 at 8:51 AM, Dave Newton wrote:
> Should the Dojo plugin be removed from the distro now?
>
> WW-3484 was just entered against it--if it's not going to be supported, I
> guess I'd vote for stripping it out and putting the code elsewhere like on
> Googl
I would think so, but that's just me.
(I would like to see it live on Google Code, though, so if anybody *wants*
to support it, they could.)
On Sat, Aug 21, 2010 at 12:00 PM, Dale Newfield wrote:
> On 8/21/10 11:51 AM, Dave Newton wrote:
>
>> Should the Dojo plugin be remove
On 8/21/10 11:51 AM, Dave Newton wrote:
Should the Dojo plugin be removed from the distro now?
Wasn't it deprecated in 2.1? Doesn't that mean we can just kill it in 2.2?
-Dale
-
To unsubscribe, e-mail: de
Should the Dojo plugin be removed from the distro now?
WW-3484 was just entered against it--if it's not going to be supported, I
guess I'd vote for stripping it out and putting the code elsewhere like on
Google or something.
Thoughts?
Dave
To include others in out talk ;-)
-- Forwarded message --
From: Lukasz Lenart
Date: 2010/3/24
Subject: Re: Discussion - drop Dojo plugin
To: Wes Wannemacher
Ups... I sent it only to you instead to the group ;-)
2010/3/24 Wes Wannemacher :
> My main thought is this - Le
I see this type of behavior when there is a dependency, side effect,
between tests.
An example of this is STATIC variables and I have seen this same type of
effect many times when running JUnits with IntelliJ v.s maven
IntelliJ reinstates the JUnit Runner class for each test method, and
therefor
I feel a disturbance in the force ;)
musachy
On Wed, Aug 26, 2009 at 7:30 AM, Lukasz
Lenart wrote:
> Hi,
>
> I discovered another strange thing. When I just launch the test from
> IDEA with -Duser.country=US -Duser.language=en, then it pass. But when
> I use maven with the same settings, only two
Hi,
I discovered another strange thing. When I just launch the test from
IDEA with -Duser.country=US -Duser.language=en, then it pass. But when
I use maven with the same settings, only two test fail :P
testSimple(org.apache.struts2.dojo.views.jsp.ui.DateTimePickerTagTest)
testSimpleDisabled(org.a
On Tuesday 25 August 2009 02:59:47 pm Lukasz Lenart wrote:
> 2009/8/25 Musachy Barroso :
> > something changed in the way the dates are formatted I guess.
> >
> > 2008-03-03 vs 2008-03-03T00:00:00
>
> Yeah, I noticed that but I've been thinking it's related to Locale but
> I've tried different comb
2009/8/25 Musachy Barroso :
> something changed in the way the dates are formatted I guess.
>
> 2008-03-03 vs 2008-03-03T00:00:00
Yeah, I noticed that but I've been thinking it's related to Locale but
I've tried different combinations.
> I thought it was using the second one already. Maybe you ju
trying to build and install struts2-dojo-plugin
> from source but each time I'm getting errors in test. I've tried with
> different locales but no luck: mvn install -Duser.country=US
> -Duser.language=en
>
> What to do? Please help!
>
>
> testSimple(org.apache.str
Hi,
I'm desperate ;-( I'm trying to build and install struts2-dojo-plugin
from source but each time I'm getting errors in test. I've tried with
different locales but no luck: mvn install -Duser.country=US
-Duser.language=en
What to do? Please help!
testSimpl
Just to be clear, I'm not complaining about the Dojo plugin being deprecated (
I understand the reasons for deprecation ). I was just trying to determine the
future of the Struts Ajax mailto:mfncoo...@gmail.com]on Behalf Of Martin Cooper
Sent: Thursday, 15 January 2009 7:36 p.m.
To: S
Rene Gielen wrote:
Hmm, that is not what I am experiencing - I know a lot of people using the
dojo tags for exactly what it is capable right now, basically doing some
asynchronous page updates and form validation.
I said this once a long time ago; I'll throw it out again now.
I think a core (
In fact the tags are a lot better in 2.1 than they were in 2.0. The
problem is that for a long time we (as in struts 2 committers) have
stopped trying to catch up with Dojo versions and updating the tags
accordingly. This deprecation is the official announcement of my
previous sentence. If they nev
Frank W. Zammetti wrote:
I don't know, I think Andreas' point has at least some validity... the
page he linked to does in fact state:
"*First-class AJAX support* - Add interactivity and flexibility with
AJAX tags that look and feel just like standard Struts tags."
Seems like if that's no lon
ooper
>
>
> On Wed, Jan 14, 2009 at 10:19 PM, Andreas Joseph Krogh
> > wrote:
>
>> On Wednesday 14 January 2009 23:42:18 Gustave Pheiffers wrote:
>> > Thanks for the info.
>> >
>> > It would be a shame if the > easy to use especially the ">
+1 for removing the First-Class AJAX support line.
Al.
Frank W. Zammetti wrote:
I don't know, I think Andreas' point has at least some validity... the
page he linked to does in fact state:
"*First-class AJAX support* - Add interactivity and flexibility with
AJAX tags that look and feel just
14, 2009 at 10:19 PM, Andreas Joseph Krogh
wrote:
On Wednesday 14 January 2009 23:42:18 Gustave Pheiffers wrote:
Thanks for the info.
It would be a shame if the
easy to use especially the "http://struts.apache.org/2.1.6/index.html). Built-in AJAX-support
(first-cla
gs Struts2 announces as a
main-feature, and with the dojo-plugin going away this isn't true any more.
This means Struts-2.1 no longer has any decent ui-tags?
--
Andreas Joseph Krogh
Senior Software Developer / CEO
+-+
d, Jan 14, 2009 at 10:19 PM, Andreas Joseph Krogh wrote:
> On Wednesday 14 January 2009 23:42:18 Gustave Pheiffers wrote:
> > Thanks for the info.
> >
> > It would be a shame if the easy to use especially the " validation. But I suppose its alot of work to upgrade/main
On Wednesday 14 January 2009 23:42:18 Gustave Pheiffers wrote:
> Thanks for the info.
>
> It would be a shame if the to use especially the " But I suppose its alot of work to upgrade/maintain the DOJO plugin.
I think there should be a warning-sign about this on
Thanks for the info.
It would be a shame if the mailto:musa...@gmail.com]
Sent: Thursday, 15 January 2009 11:05 a.m.
To: Struts Developers List
Subject: Re: Dojo plugin deprecated
It means they will eventually be removed or not updated, unless
someone comes up with the code to upgrade them to
ng is the Dojo plugin is deprecated on Struts 2.1.x Does this
> mean the ajax tags " will a replacement for Dojo be put in place so we can continue to use the
> ajax
> Thanks
> Gus
>
--
"Hey you! Would you help
Hi there,
My understanding is the Dojo plugin is deprecated on Struts 2.1.x Does this
mean the ajax tags "
A few people have tried, but this was some time ago. I can't remember
the problems right now, other than it was non-trivial.
I agree with Martin that we shouldn't just dump the code expecting that
someone else looks after it. Although, other than Musachy, I'm not
aware of any of the committers wo
--- On Sat, 12/20/08, Matt Raible wrote:
> Do we have a plugins area we can check it into? I'd be interested
> in helping update this project to the latest version of Dojo.
It's already in the "plugins" directory. The (potential) issue with leaving it
there is the implied support. Maybe we coul
t, Dec 20, 2008 at 11:38 AM, Dave Newton
>> wrote:
>>
>> > --- On Sat, 12/20/08, Musachy Barroso wrote:
>> > > We have talked about this Ad nauseam, and it is obvious that
>> > > we don't have anyone willing to fix all the current bugs,
>> > >
> On Sat, Dec 20, 2008 at 11:38 AM, Dave Newton
> wrote:
>
> > --- On Sat, 12/20/08, Musachy Barroso wrote:
> > > We have talked about this Ad nauseam, and it is obvious that
> > > we don't have anyone willing to fix all the current bugs,
> > > upgrade t
roso wrote:
We have talked about this Ad nauseam, and it is obvious that
we don't have anyone willing to fix all the current bugs,
upgrade the Dojo plugin, or write a replacement. 2.1 is
around the corner and I think we should let users know
that the Dojo plugin won't be maintained anymor
ious that
> > we don't have anyone willing to fix all the current bugs,
> > upgrade the Dojo plugin, or write a replacement. 2.1 is
> > around the corner and I think we should let users know
> > that the Dojo plugin won't be maintained anymore.
> > So my
--- On Sat, 12/20/08, Musachy Barroso wrote:
> We have talked about this Ad nauseam, and it is obvious that
> we don't have anyone willing to fix all the current bugs,
> upgrade the Dojo plugin, or write a replacement. 2.1 is
> around the corner and I think we should let users
We have talked about this Ad nauseam, and it is obvious that we don't
have anyone willing to fix all the current bugs, upgrade the Dojo
plugin, or write a replacement. 2.1 is around the corner and I think
we should let users know that the Dojo plugin won't be maintained
anymore. So my p
;>
>>> I'd suggest that we put a replacement together before pulling the Dojo
>>> plugin out of the distribution (I can help). We could at least
>>> deprecate Dojo in the meantime.
>>>
>>> -T.
>>>
>>
>> I can help too but
ed Husted wrote:
>>
>> I'd suggest that we put a replacement together before pulling the Dojo
>> plugin out of the distribution (I can help). We could at least
>> deprecate Dojo in the meantime.
>>
>> -T.
>>
>
> I can help too but I'm moving h
It's interesting to see the list of dojo sponsors and supporters
(http://dojotoolkit.org/foundation) on the one side, and the slow and
always API breaking development on the other. If they had a 1.0 out a
year ago, along with a stable API, it might have had a chance to become
something like a stand
- Original Message
From: Dave Newton <[EMAIL PROTECTED]>
To: Struts Developers List
Sent: Friday, July 25, 2008 9:38:37 AM
Subject: Re: [PROPOSAL] Deprecate or remove Dojo plugin
I was thinking about all this last night.
One thing that might be useful is to provide enough information to i
.
- Original Message
From: Dave Newton <[EMAIL PROTECTED]>
To: Struts Developers List
Sent: Friday, July 25, 2008 9:38:37 AM
Subject: Re: [PROPOSAL] Deprecate or remove Dojo plugin
I was thinking about all this last night.
One thing that might be useful is to provide
ation guide.
Dave
--- On Thu, 7/24/08, Ted Husted <[EMAIL PROTECTED]> wrote:
> From: Ted Husted <[EMAIL PROTECTED]>
> Subject: Re: [PROPOSAL] Deprecate or remove Dojo plugin
> To: "Struts Developers List"
> Date: Thursday, July 24, 2008, 3:48 PM
> I'd su
Ted Husted wrote:
I'd suggest that we put a replacement together before pulling the Dojo
plugin out of the distribution (I can help). We could at least
deprecate Dojo in the meantime.
-T.
I can help too but I'm moving house today so may be offline for a while
(it takes weeks to
yeah, that's what I had in mind.
musachy
On Thu, Jul 24, 2008 at 3:48 PM, Ted Husted <[EMAIL PROTECTED]> wrote:
> I'd suggest that we put a replacement together before pulling the Dojo
> plugin out of the distribution (I can help). We could at least
> deprecate Doj
I'd suggest that we put a replacement together before pulling the Dojo
plugin out of the distribution (I can help). We could at least
deprecate Dojo in the meantime.
-T.
On Thu, Jul 24, 2008 at 3:44 PM, Musachy Barroso <[EMAIL PROTECTED]> wrote:
> So is the consensus so far that we
So is the consensus so far that we should have a few, very simple
tags, based on another framework, and take the dojo plugin out of
struts?
musachy
On Thu, Jul 24, 2008 at 7:20 AM, Dave Newton <[EMAIL PROTECTED]> wrote:
> One solution would be to provide the backing components for s
updates is easier, and (in
theory) it makes it easier to understand how users can extend or create
additional tags to suit their needs.
So I vote +1 for removing the existing Dojo plugin (+0 for deprecating) and +1
for creating the simplistic components and example integrations.
Dave
--- On Tue
Frank W. Zammetti wrote:
Think about all you're taking for granted when you write
$("#content).load(url);
It largely boils down to differences between how developers think the
dom/language works and how it really works.
The time it takes to have your developers watch Crockford's three
lectu
I think that ignores the underlying complexity of developing complex
RIAs today. I would take any of the apps I've developed on the job over
the past 5+ years and put them up against any out there in terms of
complexity... when I talk to other developers about what they're doing
it's nearly al
Having a simple taglib-based approach to do some of the more common
AJAX-y things, maybe some widgets here and there too, means that Java
developers can leverage their existing skills without having to take the
plunge into heavy client-side development, which I can say from the
experience of
If this is the case, I would not recommend we create an "ajax" plugin, but
call it the "ajax-yui" plugin or a "ajax-whatever" plugin so that people can
use different ajax implementations.
Paul
On Wed, Jul 23, 2008 at 1:40 AM, Jeromy Evans <
[EMAIL PROTECTED]> wrote:
> Paul Benedict wrote:
>
>> D
Paul Benedict wrote:
Dojo 0.4.3 is old :-) I didn't know that. No one wants to move it to 1.x or
wherever they are now?
Paul
Many have tried. In general, the effort doesn't justify the result.
ie. you put a lot of effort writing new templates and tags that
predominately wrap and constra
ExtJS is a big no-no in my book. To use it in a commercial project you
need to buy a license, which would put off a lot of commercial customers.
Personally I use YUI for two reasons;
1) It's easy to separate out and include only the parts I need in my
webapp so I don't end up with war bloat.
e ajax tag at all, unless they are
>>> doing something extremely simple. the beginners: they will use the
>>> ajax tags out of the box. When the beginners need to do something that
>>> is not provided by th
of the box, they start hacking away,
and end up dumping the tags. So our target is the beginners, and they
don't want customization, they just want to drop a few tags on their
jsps and get it working. Based on that, I think we should either:
don't provide any ajax tags at all, or just
On Tue, Jul 22, 2008 at 8:19 PM, Dave Newton <[EMAIL PROTECTED]> wrote:
> --- On Tue, 7/22/08, Bob Tiernay <[EMAIL PROTECTED]> wrote:
>> I really don't see why even a taglib is even on the table.
>
> I think the issue was a "let's make some of this cool stuff really easy for
> the people that don'
--- On Tue, 7/22/08, Bob Tiernay <[EMAIL PROTECTED]> wrote:
> I really don't see why even a taglib is even on the table.
I think the issue was a "let's make some of this cool stuff really easy for the
people that don't know JavaScript."
To steal the phrase: now you have two problems.
I'm not su
> From: "Martin Cooper" <[EMAIL PROTECTED]>
> Sent: Tuesday, July 22, 2008 7:36 PM
> To: "Struts Developers List"
> Cc: <[EMAIL PROTECTED]>
> Subject: Re: [PROPOSAL] Deprecate or remove Dojo plugin
>
>
> On Tue, Jul 22, 2008 at 3:57 PM, Te
> Has anyone had good or bad experiences with tag-based libraries like these?
>
I used to maintain Ajax Tags, but I thought there were too many
frameworks already and gave it away :). I haven't used any of the
other ones.
musachy
--
ns logging.
--
From: "Martin Cooper" <[EMAIL PROTECTED]>
Sent: Tuesday, July 22, 2008 7:36 PM
To: "Struts Developers List"
Cc: <[EMAIL PROTECTED]>
Subject: Re: [PROPOSAL] Deprecate or remove Dojo plugin
On Tue, Jul 22, 2008 at 3:5
> What does anyone think about donating the dojo plugin to codehaus? I think
> it's a better idea than letting the code go stale. You could even try
> donating to the dojotoolkit project.
I am not sure what you mean by donating it to codehaus. If someone wants to
support the plugi
That would be totally fine, but I doubt anyone would be interested in
Dojo 0.4.3 at this point.
musachy
On Tue, Jul 22, 2008 at 7:29 PM, Paul Benedict <[EMAIL PROTECTED]> wrote:
> What does anyone think about donating the dojo plugin to codehaus? I think
> it's a better idea
On Tue, Jul 22, 2008 at 3:57 PM, Ted Husted <[EMAIL PROTECTED]> wrote:
> Dojo seems to get the most lip service, but I've seen persistence
> reports that YUI has broader acceptance.
The thing is, it depends a whole lot on what you are doing with it.
For example, the people I know who are develo
What does anyone think about donating the dojo plugin to codehaus? I think
it's a better idea than letting the code go stale. You could even try
donating to the dojotoolkit project.
Paul
On Tue, Jul 22, 2008 at 6:18 PM, Ted Husted <[EMAIL PROTECTED]> wrote:
> +1 for Musachy
provide any ajax tags at all, or just provide a very limited set
> of tags (like what Jeromy listed) with very little functionality to
> cover simple use cases, and use a reliable and simple framework for
> the implementation.
>
> Disregarding what path we take, I think it is fairly
Dojo seems to get the most lip service, but I've seen persistence
reports that YUI has broader acceptance.
-Ted.
On Tue, Jul 22, 2008 at 4:48 PM, Dave Newton <[EMAIL PROTECTED]> wrote:
> --- On Tue, 7/22/08, Paul Benedict <[EMAIL PROTECTED]> wrote:
>> Isn't Dojo the defacto ajax standard on the w
Tapestry is using Dojo too [1].
I'm not developing any AJAX application so my comments could be
somewhat biased, but either the dojo toolkit is used or not in
upcoming S2 versions, I think it is still worthwhile providing easy to
use, good looking javascript/dhtml widgets to quickly solve form inp
--- On Tue, 7/22/08, Paul Benedict <[EMAIL PROTECTED]> wrote:
> Isn't Dojo the defacto ajax standard on the web?
In terms of deployments I'd put money on Prototype and/or jQuery. Not that it's
a large sample size, but I don't know *anybody* using Dojo outside of S2.
Dave
-
Isn't Dojo the defacto ajax standard on the web? I know there is no such
"certification" :-) but why deprecate something so popular? If anything, I
would spin off the project into Codehaus and let the world continue writing
it.
Paul
On Tue, Jul 22, 2008 at 10:18 AM, Dave Newton <[EMAIL PROTECTED]
--- On Tue, 7/22/08, Musachy Barroso <[EMAIL PROTECTED]> wrote:
> I think Dave also had a JQuery plugin somewhere, isn't that right?
I can neither confirm nor deny the existence of said project.
I started to convert the Dojo tags to jQuery and stopped again pretty quickly;
I only had with a sin
> You would have to start the tags from scratch.
Very optimistic ;-) Maybe than, the jQuery is a better option to start
from scratch..
Regards
--
Lukasz
http://www.lenart.org.pl/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
You would have to start the tags from scratch.
musachy
On Tue, Jul 22, 2008 at 1:56 AM, Lukasz Lenart
<[EMAIL PROTECTED]> wrote:
> Hi,
>
>> Disregarding what path we take, I think it is fairly obvious that the
>> Dojo plugin will end up unmaintained, that's why we sh
flipside is as you add functionality, maintainability becomes an issue.
>
> btw. If anybody is interested in some JQuery tags I could start a plugin..?
> --
> View this message in context:
> http://www.nabble.com/-PROPOSAL--Deprecate-or-remove-Dojo-plugin-tp18573704p18587222.
-or-remove-Dojo-plugin-tp18573704p18587222.html
Sent from the Struts - Dev mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi,
> Disregarding what path we take, I think it is fairly obvious that the
> Dojo plugin will end up unmaintained, that's why we should users know
> that we do not plan on upgrading from 0.4.3.
I'm just wondering, what have to be done to migrate to the latest
version of Do
we take, I think it is fairly obvious that the
Dojo plugin will end up unmaintained, that's why we should users know
that we do not plan on upgrading from 0.4.3.
musachy
On Mon, Jul 21, 2008 at 10:24 PM, Jeromy Evans
<[EMAIL PROTECTED]> wrote:
> Musachy Barroso wrote:
>>
>>
Musachy Barroso wrote:
With all the problems/questions and time that the ajax tags have
caused, and not having any takers on porting to the latest Dojo
release. I would propose to deprecate, or even remove the Dojo plugin,
or at least let users know that we will not be upgrading to a newer
Dojo
> -Original Message-
> From: Musachy Barroso [mailto:[EMAIL PROTECTED]
> Sent: Monday, July 21, 2008 10:36 AM
> To: Struts Developers List
> Subject: [PROPOSAL] Deprecate or remove Dojo plugin
>
> With all the problems/questions and time that the ajax tags
> hav
I have some code using jquery that submits a form using jquery and
fits the returned result in a target div, and a A tag that does the
same. Both codes don't have topics or any other sofistication. In
fact, using jquery is a breeze (and i feel dojo an *extremely*
complicated thing). Making the jque
time that the ajax tags have
> caused, and not having any takers on porting to the latest Dojo
> release. I would propose to deprecate, or even remove the Dojo plugin,
> or at least let users know that we will not be upgrading to a newer
> Dojo version anytime soon. I still like the i
With all the problems/questions and time that the ajax tags have
caused, and not having any takers on porting to the latest Dojo
release. I would propose to deprecate, or even remove the Dojo plugin,
or at least let users know that we will not be upgrading to a newer
Dojo version anytime soon. I
gt; there are a few people who use screen readers and that puts me personally on
> spot for using framework's ajax tags.
>
> - Original Message
> From: Dave Newton <[EMAIL PROTECTED]>
> To: Struts Developers List
> Sent: Thursday, July 10, 2008 1:19:47 PM
>
Dave Newton <[EMAIL PROTECTED]>
To: Struts Developers List
Sent: Thursday, July 10, 2008 1:19:47 PM
Subject: Re: dojo plugin
My take on it is that a limited amount of functionality is valuable--make the
simplest use-cases extremely simple. Anything beyond that it's better to just
u
PROTECTED]>
> Subject: Re: dojo plugin
> To: "Struts Developers List"
> Date: Thursday, July 10, 2008, 1:11 PM
> Well, I have started 3 times so far, and quit each time. In
> my very
> own humble opinion I don't think it is worth all the
> effort. Our
> j
rrent implementation.
musachy
On Thu, Jul 10, 2008 at 12:20 PM, Miguel <[EMAIL PROTECTED]> wrote:
> Hello All,
> Is there anyone that is trying to port the struts2-dojo-plugin from
> dojo 2.4.x to 1.1.1?
> I've downloaded de source, and will be trying to figure which struts
&g
Hello All,
Is there anyone that is trying to port the struts2-dojo-plugin from
dojo 2.4.x to 1.1.1?
I've downloaded de source, and will be trying to figure which struts
widgets don't play well with the new dojo, but to be honest, i'm feel
a bit lost in all that code, specially
I've seen a number of posts on this list about the different ajax frameworks
and how much value there is in a Struts 2 taglib that wraps the ajax library
(vs using the libraries directly). As a long time user of Struts (1 & 2) and
ajaxtags.sourceforge.net for the past year I can say there most
s of supporting, matured code with a smaller footprint in
a short period of time.
Al.
- Original Message -
From: "Dave Newton" <[EMAIL PROTECTED]>
To: "Struts Developers List"
Sent: Sunday, April 06, 2008 3:18 PM
Subject: Re: Dojo plugin update using 1.1.0 fra
nformation as to the potential cost of making
Dojo 1.0 work and nobody answered my question regarding what level of
functionality currently exists in the Dojo 1.0 plugin, so I'm pretty much
unable to come to any cogent conclusion.
If it came to a vote I'd probably say (a) leave the curren
line. I'd say that path will
be a whole lot less hassle - unless, that is, you expect the Dojo 1.x plugin
to be a major project that requires additional committers and spans an
extended period of time to get into shape equivalent to that of today's Dojo
plugin.
--
Martin Cooper
ED]>
To: "Struts Developers List"
Sent: Sunday, April 06, 2008 3:16 AM
Subject: Re: Dojo plugin update using 1.1.0 framework
On Sat, Apr 5, 2008 at 5:35 PM, Jeromy Evans <
[EMAIL PROTECTED]> wrote:
Agreed. The Dojo 0.43 plugin in Struts2.1.1 contains significant
improv
> -Original Message-
> From: Jeromy Evans [mailto:[EMAIL PROTECTED]
> Sent: Saturday, April 05, 2008 5:56 PM
> To: Struts Developers List
> Subject: Re: Dojo plugin update using 1.1.0 framework
>
>
> I've concluded that tag libraries for rich client fram
is, you expect the Dojo 1.x plugin
to be a major project that requires additional committers and spans an
extended period of time to get into shape equivalent to that of today's Dojo
plugin.
--
Martin Cooper
>
> Musachy Barroso wrote:
>
> > I don't think we should wait at all
Dave Newton wrote:
Nutshell: what's anybody's take on the effort this would require, and who's
available to make that effort?
I share similar sentiment and at most will just be able to convert my
existing 2.1.1 test applications over to use the Dojo 1.x plugin to
investigate the conseque
Agreed. The Dojo 0.43 plugin in Struts2.1.1 contains significant
improvements over the Dojo 0.40 tags bundled in 2.0.x. It's worth
releasing as-is and I'd give it a +1 today.
It sounds like there's enough people interested to complete a Dojo 1.x
plugin. I also think it's worth creating a go
I don't think we should wait at all. Refactoring dojo out of core was
one of the main things for 2.1 and it's been there for a year already.
Unless Dojo 1.0 is a lot, way, way better than the older versions, I
would say you will find lots of surprises. IMO you should set it up as
a project on googl
1 - 100 of 142 matches
Mail list logo
