Yes, I just want to get a handle on GXP first, to see if there's any
synergy between the two proposals. (Trying to get the tests to run
now.)
On Sun, Jul 27, 2008 at 11:55 AM, Musachy Barroso <[EMAIL PROTECTED]> wrote:
> My hand are full for the next couple of weeks (releases at work), but
> I can
My hand are full for the next couple of weeks (releases at work), but
I can jump in and help from time to time. Ted, do you want get started
on them? I would suggest we setup a project in the sandbox.
musachy
On Thu, Jul 24, 2008 at 5:40 PM, Jeromy Evans
<[EMAIL PROTECTED]> wrote:
> Ted Husted wr
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 get a new a
ate
>>> 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,
s.
>>
>> Dave
>>
>> --- On Tue, 7/22/08, Musachy Barroso <[EMAIL PROTECTED]> wrote:
>>
>>> From: Musachy Barroso <[EMAIL PROTECTED]>
>>> Subject: Re: [PROPOSAL] Deprecate or remove Dojo plugin
>>> To: "Struts Developers List"
7/22/08, Musachy Barroso <[EMAIL PROTECTED]> wrote:
>
>> From: Musachy Barroso <[EMAIL PROTECTED]>
>> Subject: Re: [PROPOSAL] Deprecate or remove Dojo plugin
>> To: "Struts Developers List"
>> Date: Tuesday, July 22, 2008, 9:34 AM
>> I think D
, 7/22/08, Musachy Barroso <[EMAIL PROTECTED]> wrote:
> From: Musachy Barroso <[EMAIL PROTECTED]>
> Subject: Re: [PROPOSAL] Deprecate or remove Dojo plugin
> To: "Struts Developers List"
> Date: Tuesday, July 22, 2008, 9:34 AM
> I think Dave also had a JQuery
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.
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
On Tue, Jul 22, 2008 at 10:29 PM, Frank W. Zammetti <[EMAIL PROTECTED]>
wrote:
> As you could probably guess, I've had a lot of success with AjaxParts
> Taglib ;) I've also had a lot of succe
As you could probably guess, I've had a lot of success with AjaxParts
Taglib ;) I've also had a lot of success with Dojo, ExtJS,
ActiveWidgets, dHTMLx and my personal favorite, DWR (I've found that
DWR, plus best-of-breed widgets is all the "framework" I need, which is
why I haven't posted her
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 plugin he may do so u
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 than letting the code
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's suggestion, and I'm
+1 for Musachy's suggestion, and I'm also at a point where I could
help with the implementation.
As to Ajax-enabling some of the tags, there are several tag-based Ajax
libraries out there that we could look at embedding or emulating. In
this case, we wouldn't be adopting a general-purpose Ajax lib
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 should users know
>> that we do
I think Dave also had a JQuery plugin somewhere, isn't that right?
musachy
On Tue, Jul 22, 2008 at 7:49 AM, alvins <[EMAIL PROTECTED]> wrote:
>
> +1 to remove.
>
> Valid points raised by all. I personally use JQuery in my daily life and
> have written my own tags to do these functions. I did prev
+1 to remove.
Valid points raised by all. I personally use JQuery in my daily life and
have written my own tags to do these functions. I did previously look at the
effort required to update the current tags to the latest dojo but it would
be very time consuming and far easier to start from scratc
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 Dojo toolkit? I'm not usi
I am not sure about that approach. On one hand it is very "strutsish",
in that is supports many ways of doing the same thing, and provides
ways to extend what is provided, on the other hand, I think we should
learn from other frameworks and just don't give users that many
options, for they can be c
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 v
> -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
> have caused, and not having a
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
+1.
I'd rather us not lose the AJAX tags, but rather implement with something
more lightweight like Prototype, jQuery, or similar that's much easier to
work with.
On Mon, Jul 21, 2008 at 1:35 PM, Musachy Barroso <[EMAIL PROTECTED]> wrote:
> With all the problems/questions and time that the ajax
43 matches
Mail list logo
