Dojo plugin update using 1.1.0 framework

[Al Sutton]

[I'm posing this via nabble because the apache mail servers are saying my last 3 attempts to send this via my normal mailbox are spam :(]

All,
 
I have a barely tested version of the dojo plug-in which uses Dojo 1.1 instead of 0.4.3.
 
The two main changes that were necessary were;
 
* baseRelativePath replaced by baseUrl to reflect changes in dojo API
* parseContent removed due to removal from dojo API.
 
By barely tested I mean it passes the inbuilt maven tests (after they've been modified due to the changes above), so I would appreciate anyone else's help in either checking this into subversion so can start to be official, or grab it, thrash it, and discuss problems here so we can get it into a state fit for S2.1
 
If you want to download the source with svn directories you can from http://www.alsutton.com/dojo_1_1_0_for_2_1_1.zip
 
Thanks,
 
Al.

[Pedro Herrera]

good job. I´ve started a new project and I´m going to test your plugin for now. I were waiting for this improve for a long time.

Thanks

Herrera

Al Sutton wrote:

[I'm posing this via nabble because the apache mail servers are saying my last 3 attempts to send this via my normal mailbox are spam :(]

All,
 
I have a barely tested version of the dojo plug-in which uses Dojo 1.1 instead of 0.4.3.
 
The two main changes that were necessary were;
 
* baseRelativePath replaced by baseUrl to reflect changes in dojo API
* parseContent removed due to removal from dojo API.
 
By barely tested I mean it passes the inbuilt maven tests (after they've been modified due to the changes above), so I would appreciate anyone else's help in either checking this into subversion so can start to be official, or grab it, thrash it, and discuss problems here so we can get it into a state fit for S2.1
 
If you want to download the source with svn directories you can from http://www.alsutton.com/dojo_1_1_0_for_2_1_1.zip
 
Thanks,
 
Al.

[Tsemach]

Thanks Al - We(& Others I know) are waiting for it quite a long time
since we believe that Struts 2 with Dojo 1.X
are very good choice from architecture prespective.
1 note -
We started working with Dojo 1.0 for few months with Struts 2  - (We had
minimal conversion of some of the tags we used)
From what we've learned in last months it was better for us to work on
dojo declarative mode rather than programmatic
since we wanted to use Dojo Struts Components inside Dialogs which
doesn't have executeScripts turned on.
It may be solved by using alternate theme with same FTLs but in
declarative mode ,or configuration in Plug-in level.

thx
        tsemach
Amdocs Ltd.,  MVCInfra A&M
mailto:Tsemach.Hadad@...

-----Original Message-----
From: Al Sutton [mailto:al.sutton@...]
Sent: Wednesday, April 02, 2008 9:18 AM
To: dev@...
Subject: Dojo plugin update using 1.1.0 framework


[I'm posing this via nabble because the apache mail servers are saying
my last 3 attempts to send this via my normal mailbox are spam :(]

All,
 
I have a barely tested version of the dojo plug-in which uses Dojo 1.1
instead of 0.4.3.
 
The two main changes that were necessary were;
 
* baseRelativePath replaced by baseUrl to reflect changes in dojo API
* parseContent removed due to removal from dojo API.
 
By barely tested I mean it passes the inbuilt maven tests (after they've
been modified due to the changes above), so I would appreciate anyone
else's help in either checking this into subversion so can start to be
official, or grab it, thrash it, and discuss problems here so we can get
it into a state fit for S2.1
 
If you want to download the source with svn directories you can from
http://www.alsutton.com/dojo_1_1_0_for_2_1_1.zip
 
Thanks,
 
Al.
--
View this message in context:
http://www.nabble.com/Dojo-plugin-update-using-1.1.0-framework-tp1644299
2p16442992.html
Sent from the Struts - Dev mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...


This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement,
you may review at http://www.amdocs.com/email_disclaimer.asp


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Pedro Herrera]

is the source correct (http://www.alsutton.com/dojo_1_1_0_for_2_1_1.zip);

I cant execute mvn package command.

---------
java.lang.RuntimeException: java.io.FileNotFoundException: C:\Temp\struts_dojo1.1\dojo\..\..\core\src\site\resources\tags\ajax\a.html
       


Herrera
 

Al Sutton wrote:

[I'm posing this via nabble because the apache mail servers are saying my last 3 attempts to send this via my normal mailbox are spam :(]

All,
 
I have a barely tested version of the dojo plug-in which uses Dojo 1.1 instead of 0.4.3.
 
The two main changes that were necessary were;
 
* baseRelativePath replaced by baseUrl to reflect changes in dojo API
* parseContent removed due to removal from dojo API.
 
By barely tested I mean it passes the inbuilt maven tests (after they've been modified due to the changes above), so I would appreciate anyone else's help in either checking this into subversion so can start to be official, or grab it, thrash it, and discuss problems here so we can get it into a state fit for S2.1
 
If you want to download the source with svn directories you can from http://www.alsutton.com/dojo_1_1_0_for_2_1_1.zip
 
Thanks,
 
Al.

[Al Sutton]

It's a download URL for a zip file, not a maven repository.

I don't want people to confuse it with the official S2.1 dojo plugin.

Al.

----- Original Message -----
From: "Pedro Herrera" <pedro_herrera@...>
To: <dev@...>
Sent: Friday, April 04, 2008 2:19 PM
Subject: Re: Dojo plugin update using 1.1.0 framework

>
> is the source correct (http://www.alsutton.com/dojo_1_1_0_for_2_1_1.zip);
>
> I cant execute mvn package command.
>
> ---------
> java.lang.RuntimeException: java.io.FileNotFoundException:
> C:\Temp\struts_dojo1.1\dojo\..\..\core\src\site\resources\tags\ajax\a.html
>
>
>
> Herrera
>
>
> Al Sutton wrote:
>>
>> [I'm posing this via nabble because the apache mail servers are saying my
>> last 3 attempts to send this via my normal mailbox are spam :(]
>>
>> All,
>>
>> I have a barely tested version of the dojo plug-in which uses Dojo 1.1
>> instead of 0.4.3.
>>
>> The two main changes that were necessary were;
>>
>> * baseRelativePath replaced by baseUrl to reflect changes in dojo API
>> * parseContent removed due to removal from dojo API.
>>
>> By barely tested I mean it passes the inbuilt maven tests (after they've
>> been modified due to the changes above), so I would appreciate anyone
>> else's help in either checking this into subversion so can start to be
>> official, or grab it, thrash it, and discuss problems here so we can get
>> it into a state fit for S2.1
>>
>> If you want to download the source with svn directories you can from
>> http://www.alsutton.com/dojo_1_1_0_for_2_1_1.zip
>>
>> Thanks,
>>
>> Al.
>>
>
> --
> View this message in context:
> http://www.nabble.com/Dojo-plugin-update-using-1.1.0-framework-tp16442992p16491430.html
> Sent from the Struts - Dev mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[dkarr]

Is it appropriate at this point to submit a bug for this, and provide a
patch for your changes?

> -----Original Message-----
> From: Al Sutton [mailto:al.sutton@...]
> Sent: Tuesday, April 01, 2008 11:18 PM
> To: dev@...
> Subject: Dojo plugin update using 1.1.0 framework
>
>
> [I'm posing this via nabble because the apache mail servers
> are saying my last 3 attempts to send this via my normal
> mailbox are spam :(]
>
> All,
>  
> I have a barely tested version of the dojo plug-in which uses
> Dojo 1.1 instead of 0.4.3.
>  
> The two main changes that were necessary were;
>  
> * baseRelativePath replaced by baseUrl to reflect changes in dojo API
> * parseContent removed due to removal from dojo API.
>  
> By barely tested I mean it passes the inbuilt maven tests
> (after they've been modified due to the changes above), so I
> would appreciate anyone else's help in either checking this
> into subversion so can start to be official, or grab it,
> thrash it, and discuss problems here so we can get it into a
> state fit for S2.1
>  
> If you want to download the source with svn directories you
> can from http://www.alsutton.com/dojo_1_1_0_for_2_1_1.zip
>  
> Thanks,
>  
> Al.
> --
> View this message in context:
> http://www.nabble.com/Dojo-plugin-update-using-1.1.0-framework

-tp16442992p16442992.html
> Sent from the Struts - Dev mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[newton.dave]

How deep are the client-side tests for the Dojo components? My impression was
that a fair amount had changed moving from Dojo 0.4mumble -> 1.0.

I don't know the nature of all the changes that were made, but it makes me
nervous. Musachy might have a better handle on this.

Dave

--- "Karr, David" <david.karr@...> wrote:

> Is it appropriate at this point to submit a bug for this, and provide a
> patch for your changes?
>
> > -----Original Message-----
> > From: Al Sutton [mailto:al.sutton@...]
> > Sent: Tuesday, April 01, 2008 11:18 PM
> > To: dev@...
> > Subject: Dojo plugin update using 1.1.0 framework
> >
> >
> > [I'm posing this via nabble because the apache mail servers
> > are saying my last 3 attempts to send this via my normal
> > mailbox are spam :(]
> >
> > All,
> >  
> > I have a barely tested version of the dojo plug-in which uses
> > Dojo 1.1 instead of 0.4.3.
> >  
> > The two main changes that were necessary were;
> >  
> > * baseRelativePath replaced by baseUrl to reflect changes in dojo API
> > * parseContent removed due to removal from dojo API.
> >  
> > By barely tested I mean it passes the inbuilt maven tests
> > (after they've been modified due to the changes above), so I
> > would appreciate anyone else's help in either checking this
> > into subversion so can start to be official, or grab it,
> > thrash it, and discuss problems here so we can get it into a
> > state fit for S2.1
> >  
> > If you want to download the source with svn directories you
> > can from http://www.alsutton.com/dojo_1_1_0_for_2_1_1.zip
> >  
> > Thanks,
> >  
> > Al.
> > --
> > View this message in context:
> > http://www.nabble.com/Dojo-plugin-update-using-1.1.0-framework
> -tp16442992p16442992.html
> > Sent from the Struts - Dev mailing list archive at Nabble.com.
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@...
> > For additional commands, e-mail: dev-help@...
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Pedro Herrera]

This point is clear to me,but ,why don´t you leave a only the jar available instead the all structure (.pom, src, etc)  because is not working with mvn.

thanks

Herrera

Al Sutton wrote:

It's a download URL for a zip file, not a maven repository.

I don't want people to confuse it with the official S2.1 dojo plugin.

Al.

----- Original Message -----
From: "Pedro Herrera" <[e-mail]>
To: <[e-mail]>
Sent: Friday, April 04, 2008 2:19 PM
Subject: Re: Dojo plugin update using 1.1.0 framework


>
> is the source correct (http://www.alsutton.com/dojo_1_1_0_for_2_1_1.zip);
>
> I cant execute mvn package command.
>
> ---------
> java.lang.RuntimeException: java.io.FileNotFoundException:
> C:\Temp\struts_dojo1.1\dojo\..\..\core\src\site\resources\tags\ajax\a.html
>
>
>
> Herrera
>
>
> Al Sutton wrote:
>>
>> [I'm posing this via nabble because the apache mail servers are saying my
>> last 3 attempts to send this via my normal mailbox are spam :(]
>>
>> All,
>>
>> I have a barely tested version of the dojo plug-in which uses Dojo 1.1
>> instead of 0.4.3.
>>
>> The two main changes that were necessary were;
>>
>> * baseRelativePath replaced by baseUrl to reflect changes in dojo API
>> * parseContent removed due to removal from dojo API.
>>
>> By barely tested I mean it passes the inbuilt maven tests (after they've
>> been modified due to the changes above), so I would appreciate anyone
>> else's help in either checking this into subversion so can start to be
>> official, or grab it, thrash it, and discuss problems here so we can get
>> it into a state fit for S2.1
>>
>> If you want to download the source with svn directories you can from
>> http://www.alsutton.com/dojo_1_1_0_for_2_1_1.zip
>>
>> Thanks,
>>
>> Al.
>>
>
> --
> View this message in context:
> http://www.nabble.com/Dojo-plugin-update-using-1.1.0-framework-tp16442992p16491430.html
> Sent from the Struts - Dev mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [e-mail]
> For additional commands, e-mail: [e-mail]
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [e-mail]
For additional commands, e-mail: [e-mail]

[Musachy Barroso]

> How deep are the client-side tests for the Dojo components? My impression was
>  that a fair amount had changed moving from Dojo 0.4mumble -> 1.0.
>

Pretty much the whole thing changed, as far as I know.

musachy

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Al Sutton]

You can do, I'm keeping it on my system atm, so I'm happy to co-ordinate
changes.

Al.

----- Original Message -----
From: "Karr, David" <david.karr@...>
To: "Struts Developers List" <dev@...>
Sent: Friday, April 04, 2008 11:32 PM
Subject: RE: Dojo plugin update using 1.1.0 framework


Is it appropriate at this point to submit a bug for this, and provide a
patch for your changes?

> -----Original Message-----
> From: Al Sutton [mailto:al.sutton@...]
> Sent: Tuesday, April 01, 2008 11:18 PM
> To: dev@...
> Subject: Dojo plugin update using 1.1.0 framework
>
>
> [I'm posing this via nabble because the apache mail servers
> are saying my last 3 attempts to send this via my normal
> mailbox are spam :(]
>
> All,
>
> I have a barely tested version of the dojo plug-in which uses
> Dojo 1.1 instead of 0.4.3.
>
> The two main changes that were necessary were;
>
> * baseRelativePath replaced by baseUrl to reflect changes in dojo API
> * parseContent removed due to removal from dojo API.
>
> By barely tested I mean it passes the inbuilt maven tests
> (after they've been modified due to the changes above), so I
> would appreciate anyone else's help in either checking this
> into subversion so can start to be official, or grab it,
> thrash it, and discuss problems here so we can get it into a
> state fit for S2.1
>
> If you want to download the source with svn directories you
> can from http://www.alsutton.com/dojo_1_1_0_for_2_1_1.zip
>
> Thanks,
>
> Al.
> --
> View this message in context:
> http://www.nabble.com/Dojo-plugin-update-using-1.1.0-framework

-tp16442992p16442992.html
> Sent from the Struts - Dev mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Al Sutton]

I'm not sure how deep the tests are, but only two needed changing, and those
two were the header tests which needed an update to reflect a removed config
parameter and a pair of parameters that were combined and renamed.

It's working for my needs at the moment, but I'm pretty more bugs will be
discovered as people thrash it.

Al.

----- Original Message -----
From: "Dave Newton" <newton.dave@...>
To: "Struts Developers List" <dev@...>
Sent: Saturday, April 05, 2008 1:03 AM
Subject: RE: Dojo plugin update using 1.1.0 framework

> How deep are the client-side tests for the Dojo components? My impression
> was
> that a fair amount had changed moving from Dojo 0.4mumble -> 1.0.
>
> I don't know the nature of all the changes that were made, but it makes me
> nervous. Musachy might have a better handle on this.
>
> Dave
>
> --- "Karr, David" <david.karr@...> wrote:
>
>> Is it appropriate at this point to submit a bug for this, and provide a
>> patch for your changes?
>>
>> > -----Original Message-----
>> > From: Al Sutton [mailto:al.sutton@...]
>> > Sent: Tuesday, April 01, 2008 11:18 PM
>> > To: dev@...
>> > Subject: Dojo plugin update using 1.1.0 framework
>> >
>> >
>> > [I'm posing this via nabble because the apache mail servers
>> > are saying my last 3 attempts to send this via my normal
>> > mailbox are spam :(]
>> >
>> > All,
>> >
>> > I have a barely tested version of the dojo plug-in which uses
>> > Dojo 1.1 instead of 0.4.3.
>> >
>> > The two main changes that were necessary were;
>> >
>> > * baseRelativePath replaced by baseUrl to reflect changes in dojo API
>> > * parseContent removed due to removal from dojo API.
>> >
>> > By barely tested I mean it passes the inbuilt maven tests
>> > (after they've been modified due to the changes above), so I
>> > would appreciate anyone else's help in either checking this
>> > into subversion so can start to be official, or grab it,
>> > thrash it, and discuss problems here so we can get it into a
>> > state fit for S2.1
>> >
>> > If you want to download the source with svn directories you
>> > can from http://www.alsutton.com/dojo_1_1_0_for_2_1_1.zip
>> >
>> > Thanks,
>> >
>> > Al.
>> > --
>> > View this message in context:
>> > http://www.nabble.com/Dojo-plugin-update-using-1.1.0-framework
>> -tp16442992p16442992.html
>> > Sent from the Struts - Dev mailing list archive at Nabble.com.
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: dev-unsubscribe@...
>> > For additional commands, e-mail: dev-help@...
>> >
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@...
>> For additional commands, e-mail: dev-help@...
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Al Sutton]

All of the bits are left in place so that the source can be re-integrated as
easily as possible when appropriate.

At the moment it's a drop in replacement in the struts2 tree, further down
the line the svn directories will provide the ability to merge the changes
in as smoothly as possible.

I've deliberately avoided publishing a jar to avoid people going "Hey,
theres a jar, let me dump it in my app, wait a minute it doesn't work, thats
just cr**", and moving on. If people want to use the code they'll need to
understand it's a work in progress.

Al.

----- Original Message -----
From: "Pedro Herrera" <pedro_herrera@...>
To: <dev@...>
Sent: Saturday, April 05, 2008 1:47 AM
Subject: Re: Dojo plugin update using 1.1.0 framework



This point is clear to me,but ,why don´t you leave a only the jar available
instead the all structure (.pom, src, etc)  because is not working with mvn.

thanks

Herrera



Al Sutton wrote:

>
> It's a download URL for a zip file, not a maven repository.
>
> I don't want people to confuse it with the official S2.1 dojo plugin.
>
> Al.
>
> ----- Original Message -----
> From: "Pedro Herrera" <pedro_herrera@...>
> To: <dev@...>
> Sent: Friday, April 04, 2008 2:19 PM
> Subject: Re: Dojo plugin update using 1.1.0 framework
>
>
>>
>> is the source correct (http://www.alsutton.com/dojo_1_1_0_for_2_1_1.zip);
>>
>> I cant execute mvn package command.
>>
>> ---------
>> java.lang.RuntimeException: java.io.FileNotFoundException:
>> C:\Temp\struts_dojo1.1\dojo\..\..\core\src\site\resources\tags\ajax\a.html
>>
>>
>>
>> Herrera
>>
>>
>> Al Sutton wrote:
>>>
>>> [I'm posing this via nabble because the apache mail servers are saying
>>> my
>>> last 3 attempts to send this via my normal mailbox are spam :(]
>>>
>>> All,
>>>
>>> I have a barely tested version of the dojo plug-in which uses Dojo 1.1
>>> instead of 0.4.3.
>>>
>>> The two main changes that were necessary were;
>>>
>>> * baseRelativePath replaced by baseUrl to reflect changes in dojo API
>>> * parseContent removed due to removal from dojo API.
>>>
>>> By barely tested I mean it passes the inbuilt maven tests (after they've
>>> been modified due to the changes above), so I would appreciate anyone
>>> else's help in either checking this into subversion so can start to be
>>> official, or grab it, thrash it, and discuss problems here so we can get
>>> it into a state fit for S2.1
>>>
>>> If you want to download the source with svn directories you can from
>>> http://www.alsutton.com/dojo_1_1_0_for_2_1_1.zip
>>>
>>> Thanks,
>>>
>>> Al.
>>>
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Dojo-plugin-update-using-1.1.0-framework-tp16442992p16491430.html
>> Sent from the Struts - Dev mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@...
>> For additional commands, e-mail: dev-help@...
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>
>
>

--
View this message in context:
http://www.nabble.com/Dojo-plugin-update-using-1.1.0-framework-tp16442992p16508212.html
Sent from the Struts - Dev mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Al Sutton]

I think there's been a lot of back end changes, but they have a couple of
API change docs at

http://dojotoolkit.org/book/dojo-porting-guide-0-4-x-0-9

and

http://dojotoolkit.org/book/dojo-porting-guide-0-9-x-1-0

My stuff is definitely a work in progress, so I'm sure people will hit bugs,
but at least we now starting the move :).

Al.

----- Original Message -----
From: "Musachy Barroso" <musachy@...>
To: "Struts Developers List" <dev@...>
Sent: Saturday, April 05, 2008 3:18 AM
Subject: Re: Dojo plugin update using 1.1.0 framework

>> How deep are the client-side tests for the Dojo components? My impression
>> was
>>  that a fair amount had changed moving from Dojo 0.4mumble -> 1.0.
>>
>
> Pretty much the whole thing changed, as far as I know.
>
> musachy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[dkarr]

> -----Original Message-----
> From: Al Sutton [mailto:al.sutton@...]
> Sent: Saturday, April 05, 2008 12:44 AM
> To: Struts Developers List
> Subject: Re: Dojo plugin update using 1.1.0 framework
>
> All of the bits are left in place so that the source can be
> re-integrated as easily as possible when appropriate.
>
> At the moment it's a drop in replacement in the struts2 tree,
> further down the line the svn directories will provide the
> ability to merge the changes in as smoothly as possible.
>
> I've deliberately avoided publishing a jar to avoid people
> going "Hey, theres a jar, let me dump it in my app, wait a
> minute it doesn't work, thats just cr**", and moving on. If
> people want to use the code they'll need to understand it's a
> work in progress.

That's great, but you're effectively limiting the audience of people who can test this.  I don't know how to build it.  I tried, but I couldn't.  I'm sure it's obvious to people familiar with the structure of Struts2, or using Maven2.  I don't have enough of either yet.

> ----- Original Message -----
> From: "Pedro Herrera" <pedro_herrera@...>
> To: <dev@...>
> Sent: Saturday, April 05, 2008 1:47 AM
> Subject: Re: Dojo plugin update using 1.1.0 framework
>
>
>
> This point is clear to me,but ,why don´t you leave a only the
> jar available
> instead the all structure (.pom, src, etc)  because is not
> working with mvn.
>
> thanks
>
> Herrera
>
>
>
> Al Sutton wrote:
> >
> > It's a download URL for a zip file, not a maven repository.
> >
> > I don't want people to confuse it with the official S2.1
> dojo plugin.
> >
> > Al.
> >
> > ----- Original Message -----
> > From: "Pedro Herrera" <pedro_herrera@...>
> > To: <dev@...>
> > Sent: Friday, April 04, 2008 2:19 PM
> > Subject: Re: Dojo plugin update using 1.1.0 framework
> >
> >
> >>
> >> is the source correct
> (http://www.alsutton.com/dojo_1_1_0_for_2_1_1.zip);
> >>
> >> I cant execute mvn package command.
> >>
> >> ---------
> >> java.lang.RuntimeException: java.io.FileNotFoundException:
> >>
> C:\Temp\struts_dojo1.1\dojo\..\..\core\src\site\resources\tags
> \ajax\a.html
> >>
> >>
> >>
> >> Herrera
> >>
> >>
> >> Al Sutton wrote:
> >>>
> >>> [I'm posing this via nabble because the apache mail
> servers are saying
> >>> my
> >>> last 3 attempts to send this via my normal mailbox are spam :(]
> >>>
> >>> All,
> >>>
> >>> I have a barely tested version of the dojo plug-in which
> uses Dojo 1.1
> >>> instead of 0.4.3.
> >>>
> >>> The two main changes that were necessary were;
> >>>
> >>> * baseRelativePath replaced by baseUrl to reflect changes
> in dojo API
> >>> * parseContent removed due to removal from dojo API.
> >>>
> >>> By barely tested I mean it passes the inbuilt maven tests
> (after they've
> >>> been modified due to the changes above), so I would
> appreciate anyone
> >>> else's help in either checking this into subversion so
> can start to be
> >>> official, or grab it, thrash it, and discuss problems
> here so we can get
> >>> it into a state fit for S2.1
> >>>
> >>> If you want to download the source with svn directories
> you can from
> >>> http://www.alsutton.com/dojo_1_1_0_for_2_1_1.zip
> >>>
> >>> Thanks,
> >>>
> >>> Al.
> >>>
> >>
> >> --
> >> View this message in context:
> >>
> http://www.nabble.com/Dojo-plugin-update-using-1.1.0-framework

-tp16442992p16491430.html

> >> Sent from the Struts - Dev mailing list archive at Nabble.com.
> >>
> >>
> >>
> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@...
> >> For additional commands, e-mail: dev-help@...
> >>
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@...
> > For additional commands, e-mail: dev-help@...
> >
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Dojo-plugin-update-using-1.1.0-framework

-tp16442992p16508212.html

> Sent from the Struts - Dev mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Aixcept]

Hi,

I'd propose to get out 2.1.1 test build asap and integrate the latest dojo
stuff into 2.1.2-dev as well as the other updated plugins.
I'd volunteer for this unless Musachy has time to do so.

So we can test all other features and enhancements we integrated in the
past months and can continue with the development of S2.1.x.

What do you think?

cheers,
Rainer

>> -----Original Message-----
>> From: Al Sutton [mailto:al.sutton@...]
>> Sent: Saturday, April 05, 2008 12:44 AM
>> To: Struts Developers List
>> Subject: Re: Dojo plugin update using 1.1.0 framework
>>
>> All of the bits are left in place so that the source can be
>> re-integrated as easily as possible when appropriate.
>>
>> At the moment it's a drop in replacement in the struts2 tree,
>> further down the line the svn directories will provide the
>> ability to merge the changes in as smoothly as possible.
>>
>> I've deliberately avoided publishing a jar to avoid people
>> going "Hey, theres a jar, let me dump it in my app, wait a
>> minute it doesn't work, thats just cr**", and moving on. If
>> people want to use the code they'll need to understand it's a
>> work in progress.
>
> That's great, but you're effectively limiting the audience of people who
> can test this.  I don't know how to build it.  I tried, but I couldn't.
> I'm sure it's obvious to people familiar with the structure of Struts2, or
> using Maven2.  I don't have enough of either yet.
>
>> ----- Original Message -----
>> From: "Pedro Herrera" <pedro_herrera@...>
>> To: <dev@...>
>> Sent: Saturday, April 05, 2008 1:47 AM
>> Subject: Re: Dojo plugin update using 1.1.0 framework
>>
>>
>>
>> This point is clear to me,but ,why don´t you leave a only the
>> jar available
>> instead the all structure (.pom, src, etc)  because is not
>> working with mvn.
>>
>> thanks
>>
>> Herrera
>>
>>
>>
>> Al Sutton wrote:
>> >
>> > It's a download URL for a zip file, not a maven repository.
>> >
>> > I don't want people to confuse it with the official S2.1
>> dojo plugin.
>> >
>> > Al.
>> >
>> > ----- Original Message -----
>> > From: "Pedro Herrera" <pedro_herrera@...>
>> > To: <dev@...>
>> > Sent: Friday, April 04, 2008 2:19 PM
>> > Subject: Re: Dojo plugin update using 1.1.0 framework
>> >
>> >
>> >>
>> >> is the source correct
>> (http://www.alsutton.com/dojo_1_1_0_for_2_1_1.zip);
>> >>
>> >> I cant execute mvn package command.
>> >>
>> >> ---------
>> >> java.lang.RuntimeException: java.io.FileNotFoundException:
>> >>
>> C:\Temp\struts_dojo1.1\dojo\..\..\core\src\site\resources\tags
>> \ajax\a.html
>> >>
>> >>
>> >>
>> >> Herrera
>> >>
>> >>
>> >> Al Sutton wrote:
>> >>>
>> >>> [I'm posing this via nabble because the apache mail
>> servers are saying
>> >>> my
>> >>> last 3 attempts to send this via my normal mailbox are spam :(]
>> >>>
>> >>> All,
>> >>>
>> >>> I have a barely tested version of the dojo plug-in which
>> uses Dojo 1.1
>> >>> instead of 0.4.3.
>> >>>
>> >>> The two main changes that were necessary were;
>> >>>
>> >>> * baseRelativePath replaced by baseUrl to reflect changes
>> in dojo API
>> >>> * parseContent removed due to removal from dojo API.
>> >>>
>> >>> By barely tested I mean it passes the inbuilt maven tests
>> (after they've
>> >>> been modified due to the changes above), so I would
>> appreciate anyone
>> >>> else's help in either checking this into subversion so
>> can start to be
>> >>> official, or grab it, thrash it, and discuss problems
>> here so we can get
>> >>> it into a state fit for S2.1
>> >>>
>> >>> If you want to download the source with svn directories
>> you can from
>> >>> http://www.alsutton.com/dojo_1_1_0_for_2_1_1.zip
>> >>>
>> >>> Thanks,
>> >>>
>> >>> Al.
>> >>>
>> >>
>> >> --
>> >> View this message in context:
>> >>
>> http://www.nabble.com/Dojo-plugin-update-using-1.1.0-framework
> -tp16442992p16491430.html
>> >> Sent from the Struts - Dev mailing list archive at Nabble.com.
>> >>
>> >>
>> >>
>> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: dev-unsubscribe@...
>> >> For additional commands, e-mail: dev-help@...
>> >>
>> >
>> >
>> >
>> ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: dev-unsubscribe@...
>> > For additional commands, e-mail: dev-help@...
>> >
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Dojo-plugin-update-using-1.1.0-framework
> -tp16442992p16508212.html
>> Sent from the Struts - Dev mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@...
>> For additional commands, e-mail: dev-help@...
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@...
>> For additional commands, e-mail: dev-help@...
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>
>

--
Rainer Hermanns
aixcept
Mariahilfstrasse 9
52062 Aachen - Germany
w: http://aixcept.de/
t: [phone]
m: [phone]

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Al Sutton]

David,

No problem, the easiest was to compile is to download Struts2 head
(instructions at http://struts.apache.org/dev/builds.html), locate the
plugins\dojo directory, delete it, and replace with the directory from the
zip file.

As for the compiling, follow the build instructions for struts after you've
done the replacement.

Al.

----- Original Message -----
From: "Karr, David" <david.karr@...>
To: "Struts Developers List" <dev@...>
Sent: Saturday, April 05, 2008 4:09 PM
Subject: RE: Dojo plugin update using 1.1.0 framework

> -----Original Message-----
> From: Al Sutton [mailto:al.sutton@...]
> Sent: Saturday, April 05, 2008 12:44 AM
> To: Struts Developers List
> Subject: Re: Dojo plugin update using 1.1.0 framework
>
> All of the bits are left in place so that the source can be
> re-integrated as easily as possible when appropriate.
>
> At the moment it's a drop in replacement in the struts2 tree,
> further down the line the svn directories will provide the
> ability to merge the changes in as smoothly as possible.
>
> I've deliberately avoided publishing a jar to avoid people
> going "Hey, theres a jar, let me dump it in my app, wait a
> minute it doesn't work, thats just cr**", and moving on. If
> people want to use the code they'll need to understand it's a
> work in progress.

That's great, but you're effectively limiting the audience of people who can
test this.  I don't know how to build it.  I tried, but I couldn't.  I'm
sure it's obvious to people familiar with the structure of Struts2, or using
Maven2.  I don't have enough of either yet.

> ----- Original Message -----
> From: "Pedro Herrera" <pedro_herrera@...>
> To: <dev@...>
> Sent: Saturday, April 05, 2008 1:47 AM
> Subject: Re: Dojo plugin update using 1.1.0 framework
>
>
>
> This point is clear to me,but ,why don´t you leave a only the
> jar available
> instead the all structure (.pom, src, etc)  because is not
> working with mvn.
>
> thanks
>
> Herrera
>
>
>
> Al Sutton wrote:
> >
> > It's a download URL for a zip file, not a maven repository.
> >
> > I don't want people to confuse it with the official S2.1
> dojo plugin.
> >
> > Al.
> >
> > ----- Original Message -----
> > From: "Pedro Herrera" <pedro_herrera@...>
> > To: <dev@...>
> > Sent: Friday, April 04, 2008 2:19 PM
> > Subject: Re: Dojo plugin update using 1.1.0 framework
> >
> >
> >>
> >> is the source correct
> (http://www.alsutton.com/dojo_1_1_0_for_2_1_1.zip);
> >>
> >> I cant execute mvn package command.
> >>
> >> ---------
> >> java.lang.RuntimeException: java.io.FileNotFoundException:
> >>
> C:\Temp\struts_dojo1.1\dojo\..\..\core\src\site\resources\tags
> \ajax\a.html
> >>
> >>
> >>
> >> Herrera
> >>
> >>
> >> Al Sutton wrote:
> >>>
> >>> [I'm posing this via nabble because the apache mail
> servers are saying
> >>> my
> >>> last 3 attempts to send this via my normal mailbox are spam :(]
> >>>
> >>> All,
> >>>
> >>> I have a barely tested version of the dojo plug-in which
> uses Dojo 1.1
> >>> instead of 0.4.3.
> >>>
> >>> The two main changes that were necessary were;
> >>>
> >>> * baseRelativePath replaced by baseUrl to reflect changes
> in dojo API
> >>> * parseContent removed due to removal from dojo API.
> >>>
> >>> By barely tested I mean it passes the inbuilt maven tests
> (after they've
> >>> been modified due to the changes above), so I would
> appreciate anyone
> >>> else's help in either checking this into subversion so
> can start to be
> >>> official, or grab it, thrash it, and discuss problems
> here so we can get
> >>> it into a state fit for S2.1
> >>>
> >>> If you want to download the source with svn directories
> you can from
> >>> http://www.alsutton.com/dojo_1_1_0_for_2_1_1.zip
> >>>
> >>> Thanks,
> >>>
> >>> Al.
> >>>
> >>
> >> --
> >> View this message in context:
> >>
> http://www.nabble.com/Dojo-plugin-update-using-1.1.0-framework

-tp16442992p16491430.html

> >> Sent from the Struts - Dev mailing list archive at Nabble.com.
> >>
> >>
> >>
> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@...
> >> For additional commands, e-mail: dev-help@...
> >>
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@...
> > For additional commands, e-mail: dev-help@...
> >
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Dojo-plugin-update-using-1.1.0-framework

-tp16442992p16508212.html

> Sent from the Struts - Dev mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Al Sutton]

I'm split on this.

Whilst I can see that there is an advantage to getting a 2.1 release out, my
question would be do we want it to go out with a (very) old version of dojo
as the demonstration of it's modern ajax capabilities?, and do we want to
put developers through getting used to 0.4 as the bundled version and then
jump to a much newer version as a minor version release?

Al.

----- Original Message -----
From: "Rainer Hermanns" <hermanns@...>
To: "Struts Developers List" <dev@...>
Sent: Saturday, April 05, 2008 4:22 PM
Subject: RE: Dojo plugin update using 1.1.0 framework

> Hi,
>
> I'd propose to get out 2.1.1 test build asap and integrate the latest dojo
> stuff into 2.1.2-dev as well as the other updated plugins.
> I'd volunteer for this unless Musachy has time to do so.
>
> So we can test all other features and enhancements we integrated in the
> past months and can continue with the development of S2.1.x.
>
> What do you think?
>
> cheers,
> Rainer
>
>>> -----Original Message-----
>>> From: Al Sutton [mailto:al.sutton@...]
>>> Sent: Saturday, April 05, 2008 12:44 AM
>>> To: Struts Developers List
>>> Subject: Re: Dojo plugin update using 1.1.0 framework
>>>
>>> All of the bits are left in place so that the source can be
>>> re-integrated as easily as possible when appropriate.
>>>
>>> At the moment it's a drop in replacement in the struts2 tree,
>>> further down the line the svn directories will provide the
>>> ability to merge the changes in as smoothly as possible.
>>>
>>> I've deliberately avoided publishing a jar to avoid people
>>> going "Hey, theres a jar, let me dump it in my app, wait a
>>> minute it doesn't work, thats just cr**", and moving on. If
>>> people want to use the code they'll need to understand it's a
>>> work in progress.
>>
>> That's great, but you're effectively limiting the audience of people who
>> can test this.  I don't know how to build it.  I tried, but I couldn't.
>> I'm sure it's obvious to people familiar with the structure of Struts2,
>> or
>> using Maven2.  I don't have enough of either yet.
>>
>>> ----- Original Message -----
>>> From: "Pedro Herrera" <pedro_herrera@...>
>>> To: <dev@...>
>>> Sent: Saturday, April 05, 2008 1:47 AM
>>> Subject: Re: Dojo plugin update using 1.1.0 framework
>>>
>>>
>>>
>>> This point is clear to me,but ,why don´t you leave a only the
>>> jar available
>>> instead the all structure (.pom, src, etc)  because is not
>>> working with mvn.
>>>
>>> thanks
>>>
>>> Herrera
>>>
>>>
>>>
>>> Al Sutton wrote:
>>> >
>>> > It's a download URL for a zip file, not a maven repository.
>>> >
>>> > I don't want people to confuse it with the official S2.1
>>> dojo plugin.
>>> >
>>> > Al.
>>> >
>>> > ----- Original Message -----
>>> > From: "Pedro Herrera" <pedro_herrera@...>
>>> > To: <dev@...>
>>> > Sent: Friday, April 04, 2008 2:19 PM
>>> > Subject: Re: Dojo plugin update using 1.1.0 framework
>>> >
>>> >
>>> >>
>>> >> is the source correct
>>> (http://www.alsutton.com/dojo_1_1_0_for_2_1_1.zip);
>>> >>
>>> >> I cant execute mvn package command.
>>> >>
>>> >> ---------
>>> >> java.lang.RuntimeException: java.io.FileNotFoundException:
>>> >>
>>> C:\Temp\struts_dojo1.1\dojo\..\..\core\src\site\resources\tags
>>> \ajax\a.html
>>> >>
>>> >>
>>> >>
>>> >> Herrera
>>> >>
>>> >>
>>> >> Al Sutton wrote:
>>> >>>
>>> >>> [I'm posing this via nabble because the apache mail
>>> servers are saying
>>> >>> my
>>> >>> last 3 attempts to send this via my normal mailbox are spam :(]
>>> >>>
>>> >>> All,
>>> >>>
>>> >>> I have a barely tested version of the dojo plug-in which
>>> uses Dojo 1.1
>>> >>> instead of 0.4.3.
>>> >>>
>>> >>> The two main changes that were necessary were;
>>> >>>
>>> >>> * baseRelativePath replaced by baseUrl to reflect changes
>>> in dojo API
>>> >>> * parseContent removed due to removal from dojo API.
>>> >>>
>>> >>> By barely tested I mean it passes the inbuilt maven tests
>>> (after they've
>>> >>> been modified due to the changes above), so I would
>>> appreciate anyone
>>> >>> else's help in either checking this into subversion so
>>> can start to be
>>> >>> official, or grab it, thrash it, and discuss problems
>>> here so we can get
>>> >>> it into a state fit for S2.1
>>> >>>
>>> >>> If you want to download the source with svn directories
>>> you can from
>>> >>> http://www.alsutton.com/dojo_1_1_0_for_2_1_1.zip
>>> >>>
>>> >>> Thanks,
>>> >>>
>>> >>> Al.
>>> >>>
>>> >>
>>> >> --
>>> >> View this message in context:
>>> >>
>>> http://www.nabble.com/Dojo-plugin-update-using-1.1.0-framework
>> -tp16442992p16491430.html
>>> >> Sent from the Struts - Dev mailing list archive at Nabble.com.
>>> >>
>>> >>
>>> >>
>>> ---------------------------------------------------------------------
>>> >> To unsubscribe, e-mail: dev-unsubscribe@...
>>> >> For additional commands, e-mail: dev-help@...
>>> >>
>>> >
>>> >
>>> >
>>> ---------------------------------------------------------------------
>>> > To unsubscribe, e-mail: dev-unsubscribe@...
>>> > For additional commands, e-mail: dev-help@...
>>> >
>>> >
>>> >
>>>
>>> --
>>> View this message in context:
>>> http://www.nabble.com/Dojo-plugin-update-using-1.1.0-framework
>> -tp16442992p16508212.html
>>> Sent from the Struts - Dev mailing list archive at Nabble.com.
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@...
>>> For additional commands, e-mail: dev-help@...
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@...
>>> For additional commands, e-mail: dev-help@...
>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@...
>> For additional commands, e-mail: dev-help@...
>>
>>
>
>
> --
> Rainer Hermanns
> aixcept
> Mariahilfstrasse 9
> 52062 Aachen - Germany
> w: http://aixcept.de/
> t: [phone]
> m: [phone]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[newton.dave]

--- Al Sutton <al.sutton@...> wrote:
> Whilst I can see that there is an advantage to getting a 2.1 release out,
> my question would be do we want it to go out with a (very) old version
> of dojo as the demonstration of it's modern ajax capabilities?, and do
> we want to put developers through getting used to 0.4 as the bundled
> version and then jump to a much newer version as a minor version release?

So the questions are how well tested are the new Dojo tags, and if they're
not tested well enough how long would it take to test them? Lastly, how much
rework, if any, is required to match the functionality of the 0.4x plugin?

My impression is still that Dojo 1.0 is pretty different from Dojo 0.4x, and
that this is a non-trivial project--but that's a guess made from ignorance.
Is there any evidence to the contrary? Have the tags been tested (even
manually) on the client side to bulk-verify behavior?

Due to some immediate responsibilities, my availability for working on a Dojo
1.0 plugin is limited and conditional:

-- I have some time I can dedicate to *testing* new Dojo tags.
-- I don't have the time to learn Dojo 1.0 well and implement much changed
and/or new functionality if both the cost and risk are high.
-- The window within that time is available is short, and dwindling.
-- The more people working on it the more likely I am to make the time
because of a perceived lower risk.

Nutshell: what's anybody's take on the effort this would require, and who's
available to make that effort?

Dave


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Musachy Barroso]

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 googlecode or somewhere else and we can all
contribute/test and eventually bring it on (or just keep it there and
get rid of our current plugin).

my 2 centavos :)

musachy

On Sat, Apr 5, 2008 at 6:19 PM, Dave Newton <newton.dave@...> wrote:

> --- Al Sutton <al.sutton@...> wrote:
>  > Whilst I can see that there is an advantage to getting a 2.1 release out,
>  > my question would be do we want it to go out with a (very) old version
>  > of dojo as the demonstration of it's modern ajax capabilities?, and do
>  > we want to put developers through getting used to 0.4 as the bundled
>  > version and then jump to a much newer version as a minor version release?
>
>  So the questions are how well tested are the new Dojo tags, and if they're
>  not tested well enough how long would it take to test them? Lastly, how much
>  rework, if any, is required to match the functionality of the 0.4x plugin?
>
>  My impression is still that Dojo 1.0 is pretty different from Dojo 0.4x, and
>  that this is a non-trivial project--but that's a guess made from ignorance.
>  Is there any evidence to the contrary? Have the tags been tested (even
>  manually) on the client side to bulk-verify behavior?
>
>  Due to some immediate responsibilities, my availability for working on a Dojo
>  1.0 plugin is limited and conditional:
>
>  -- I have some time I can dedicate to *testing* new Dojo tags.
>  -- I don't have the time to learn Dojo 1.0 well and implement much changed
>  and/or new functionality if both the cost and risk are high.
>  -- The window within that time is available is short, and dwindling.
>  -- The more people working on it the more likely I am to make the time
>  because of a perceived lower risk.
>
>  Nutshell: what's anybody's take on the effort this would require, and who's
>  available to make that effort?
>
>  Dave
>
>
>
>
>  ---------------------------------------------------------------------
>  To unsubscribe, e-mail: dev-unsubscribe@...
>  For additional commands, e-mail: dev-help@...
>
>

--
"Hey you! Would you help me to carry the stone?" Pink Floyd

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Jeromy Evans - Blue Sky Minds]

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 googlecode project for it
until it reaches a certain level of maturity.  The benefit of googlecode
over the sandpit is the low barrier to contribute and informal releases.

Musachy Barroso wrote:

> 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 googlecode or somewhere else and we can all
> contribute/test and eventually bring it on (or just keep it there and
> get rid of our current plugin).
>
> my 2 centavos :)
>
> musachy
>
> On Sat, Apr 5, 2008 at 6:19 PM, Dave Newton <newton.dave@...> wrote:
>  
>> --- Al Sutton <al.sutton@...> wrote:
>>  > Whilst I can see that there is an advantage to getting a 2.1 release out,
>>  > my question would be do we want it to go out with a (very) old version
>>  > of dojo as the demonstration of it's modern ajax capabilities?, and do
>>  > we want to put developers through getting used to 0.4 as the bundled
>>  > version and then jump to a much newer version as a minor version release?
>>
>>  So the questions are how well tested are the new Dojo tags, and if they're
>>  not tested well enough how long would it take to test them? Lastly, how much
>>  rework, if any, is required to match the functionality of the 0.4x plugin?
>>
>>  My impression is still that Dojo 1.0 is pretty different from Dojo 0.4x, and
>>  that this is a non-trivial project--but that's a guess made from ignorance.
>>  Is there any evidence to the contrary? Have the tags been tested (even
>>  manually) on the client side to bulk-verify behavior?
>>
>>  Due to some immediate responsibilities, my availability for working on a Dojo
>>  1.0 plugin is limited and conditional:
>>
>>  -- I have some time I can dedicate to *testing* new Dojo tags.
>>  -- I don't have the time to learn Dojo 1.0 well and implement much changed
>>  and/or new functionality if both the cost and risk are high.
>>  -- The window within that time is available is short, and dwindling.
>>  -- The more people working on it the more likely I am to make the time
>>  because of a perceived lower risk.
>>
>>  Nutshell: what's anybody's take on the effort this would require, and who's
>>  available to make that effort?
>>
>>  Dave
>>
>>
>>
>>
>>  ---------------------------------------------------------------------
>>  To unsubscribe, e-mail: dev-unsubscribe@...
>>  For additional commands, e-mail: dev-help@...
>>
>>
>>    
>
>
>
>  

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...