I'd suggest we don't include the static DatePicker and TimerPicker for
2.0.2, these are not the dropdown ones. They were not in WW, and they
have some serious issues (Dojo code) which I would need more time to
work on. That would leave us with the DropDownDateTimePicker, which we
could split if
Ted Husted wrote:
Don mentioned a separate tag library, so that would indicate another
prefix, but there'd be no reason why the internal tag syntax would
change.
To keep the codebase manageable, I believe we do need to make this
change, and I'd rather make it now while we are in our first beta
On 12/27/06 2:38 PM, "cvu" <[EMAIL PROTECTED]> wrote:
>
> Hi,
> Anyone knows how to iterate over a collection of object each object has
> string property:
> public class Door {
> String color;
> public void setColor(String color){
> this.color=color;
> }
> public String getColor(){
Don mentioned a separate tag library, so that would indicate another
prefix, but there'd be no reason why the internal tag syntax would
change.
To keep the codebase manageable, I believe we do need to make this
change, and I'd rather make it now while we are in our first beta
series than after th
Ok, as long as we keep the tag prefixes and tag names once they are
abstracted from the plugin.
At one point we talked about having a simple version which is extended
by the dojo version and added additional (dojo-specific) featuers. It
seems like the current names would be more likely be use
A struts-dojo plugin shouldn't change the tag syntax. It should just
be a matter of adding the JAR, as we do for Spring, and JasperReports,
and Tiles, so forth.
On 12/27/06, David H. DeWolf <[EMAIL PROTECTED]> wrote:
Nope, that's the one I'm talking about. I got the impression we were
going to
Nope, that's the one I'm talking about. I got the impression we were
going to keep it as is and thus break backwards compatibility in 2.0.2
-- and then mess with it again it when we create the plugin. . .
David
Don Brown wrote:
The only currently broken tag, in terms of 2.0.1 compatibility, i
The only currently broken tag, in terms of 2.0.1 compatibility, is the
date picker tag. It has been reimplemented and renamed. Am I missing any?
Don
David H. DeWolf wrote:
Unless I'm missing something, that would mean we break backwards
compatibility between 2.0.1 and 2.0.2 and then force an
Done and Done.
Don
Ted Husted wrote:
Do you have any ideas about WW-1571 - the problem wth the
action-redirect prefix?
If we can resolve that, and figure out the problem with
OptionTransfersSelect, I could roll 2.0.2 on Saturday. Or Monday, if
we look close on this proposal.
-Ted.
On 12/27/0
Unless I'm missing something, that would mean we break backwards
compatibility between 2.0.1 and 2.0.2 and then force another break
between 2.0.2 and 2.0.3, right? I want to get 2.0.2 out as well, but
that doesn't sound like a good idea to me.
Why not roll back the tags to 2.0.1 compatibility
Do you have any ideas about WW-1571 - the problem wth the
action-redirect prefix?
If we can resolve that, and figure out the problem with
OptionTransfersSelect, I could roll 2.0.2 on Saturday. Or Monday, if
we look close on this proposal.
-Ted.
On 12/27/06, Don Brown <[EMAIL PROTECTED]> wrote:
If we are talking a day or two, sure, let's get 2.0.2 out there. If we
are talking two weeks, then I think we should move the dojo tags out.
How about this - I plan to work on this sometime this week/weekend, so
if you release 2.0.2 before I finish, then yes, let's release 2.0.2 first :)
Don
On 12/27/06, Don Brown <[EMAIL PROTECTED]> wrote:
I'd like to move on this quickly and have it completed within two weeks.
Thoughts?
Do we want to release Struts 2.0.2 with what we have already?
A Struts 2.0.3 is already a foregone conclusion since XWork 2 is at RC1.
-Ted.
-
Are we using any library for the client side validation? I haven't look
at it, but if we do, that would probably need to be in core.
musachy
Don Brown wrote:
Ok, let's put this into a formal proposal. I propose that we extract
any Dojo-related tags and behaviors into a new tag library. This
I'll be hitting the road in about 12 hours, but I'll be back on
Saturday, and I'd be happy to finish this up then, if no one beats me
to it.
Thanks for your help, Musachy .
-Ted.
On 12/27/06, Musachy Barroso <[EMAIL PROTECTED]> wrote:
I'm checking an issue reported on the user list, but overal
I'm checking an issue reported on the user list, but overall they should
be working. Everybody seems to agree with the plugin idea, and as long
as there is a brave soul willing to apply my patches :), I will continue
to work on them.
musachy
Ted Husted wrote:
I don't mind breaking backward c
I'm currently using the datepicker tag with the "simple" theme in 2.0.1 and
would hope that there is some client side date selection widget available with
this theme in 2.0.2.
- Original Message
From: Ted Husted <[EMAIL PROTECTED]>
To: Struts Developers List
Sent: Wednesday, December 2
Ok, let's put this into a formal proposal. I propose that we extract
any Dojo-related tags and behaviors into a new tag library. This new
library could extend the old tags for the purposes of adding
Dojo-related attributes, however, it should be its own logical tag
library. We should keep th
I don't mind breaking backward compatability for the date/time picker
tags, so long as we document the changes.
Along the lines of what Don mentioned, my own preference would be to
create a struts-dojo plugin that separated the AJAX code from the
core. I just don't know whether that would work, a
I didn't know about that. In that case, why bother with WW-1555 at all?
Why don we keep it the way they are now, and just document how to
migrate from the WW ones?
musachy
//what about the ajax plugin spin off??
Don Brown wrote:
The old WW date picker tags are very different than the Dojo one
Yes, the date/time picker. The main difference is that WW did the date
formatting, now we are just passing the value straight to Dojo, who uses
RFC 3339 (http://www.faqs.org/rfcs/rfc3339.html)
musachy
Ted Husted wrote:
Are we just talking about the Ajax date/time picker?
Ian, who did a lot o
The old WW date picker tags are very different than the Dojo ones. The
problem is that the old tags used an LGPL Javascript library, so they
had to be replaced. Therefore, it really isn't possible to keep
backwards compatibility here with the old WW tags. The situation is
similar with the ri
Are we just talking about the Ajax date/time picker?
Ian, who did a lot of the original WW coding, seemed to think that the
Ajax tags were not widely used yet. If we were going to break with the
WW Ajax tags, this would be a good time. The key question is whether
we can document the differences.
The problem with the datepicker is worst than I thought, Dojo's
DatePicker and TimePicker are way different that the ones that WW had.
In order too keep it backward compatible, the best thing we can do is
resurrect the "DatePicker.js" and "TimePicker.js" from WW, instead of
using Dojo directly,
I can give you a hand on that problem when I finish with the datepicker
stuff.
musachy
David H. DeWolf wrote:
Ted Husted wrote:
Both the datetimepicker and the action-redirect prefix worked in the
2.0.1 beta but don't work now. Both are outright bugs, and it's
unlikely we would get positi
Ted Husted wrote:
Both the datetimepicker and the action-redirect prefix worked in the
2.0.1 beta but don't work now. Both are outright bugs, and it's
unlikely we would get positive votes for a build with know defects.
AFAIK, the JavaScript error (WW-1559) doesn't impede functionality. It
mi
I don't know about that one, it isn't ajax related :) , but it looks
like a trivial change.
musachy
Ted Husted wrote:
OK, it's in r490569
Any feedback on WW-1573 - Handling of If-Modified-Since header for
static content
Should we apply that too?
-Ted.
On 12/27/06, Musachy Barroso <[EMAIL
OK, it's in r490569
Any feedback on WW-1573 - Handling of If-Modified-Since header for
static content
Should we apply that too?
-Ted.
On 12/27/06, Musachy Barroso <[EMAIL PROTECTED]> wrote:
When you apply the one for the autocompleter; I will create one for
datepicker against head svn, and w
Both the datetimepicker and the action-redirect prefix worked in the
2.0.1 beta but don't work now. Both are outright bugs, and it's
unlikely we would get positive votes for a build with know defects.
AFAIK, the JavaScript error (WW-1559) doesn't impede functionality. It
might keep people from
That's fine with me, just help me understand the difference between this
and the datetimepicker and action-redirect issues. . .what makes them
showstoppers?
not trying to be a pain, just trying to understand :)
David
Ted Husted wrote:
The problem is that we have a an issue report, but no sug
When you apply the one for the autocompleter; I will create one for
datepicker against head svn, and we'll just ignore the old one.
regards
musachy
Ted Husted wrote:
I tried to apply the patch, but there were a great many conflicts,
perhaps because of other changes. I'm happy to apply as many
I tried to apply the patch, but there were a great many conflicts,
perhaps because of other changes. I'm happy to apply as many patches
as we need to bring the Ajax theme up to speed, but I don't know dojo
well enough to resolve conflucts with overlapping changes.
-Ted.
On 12/27/06, Musachy Bar
The problem is that we have a an issue report, but no suggestions as
to a resolution. If we have a patch to apply for 2.0.2, that would be
great. But, otherwise, we might want to keep it as a known issue to
fix as soon as we figure out how. A 2.0.2 release is not going to a a
GA candidate anyway
Thanks, Musachy. I'm in and out today, but I'll try to apply this patch soon.
On 12/27/06, Musachy Barroso <[EMAIL PROTECTED]> wrote:
I attached the patch to WW-1562. It is a fairly long ticket, not
everything is fixed, but the most important stuff is:
* Add a way to hide the dropdown arrow
* R
Hi,
Anyone knows how to iterate over a collection of object each object has
string property:
public class Door {
String color;
public void setColor(String color){
this.color=color;
}
public String getColor(){
return color;
}
}
public class House {
Lis
It seems like the patch for reverting the datepicker to its old name was
never applied. (https://issues.apache.org/struts/browse/WW-1555) Does
any one know what is the status of this one?
regards
musachy
-
To unsubscribe, e-ma
I attached the patch to WW-1562. It is a fairly long ticket, not
everything is fixed, but the most important stuff is:
* Add a way to hide the dropdown arrow
* Reload options on type, and be able to specify minimum text length for
reload
* Remember selected values is there is a validation erro
Hi guys, I was out f town. About the problem with the autocompleter, it
is missing a css file, 'cause Don asked me to create another patch and
I had started to work on the big autocompleter ticket already so I
missed it. Please don't rollback anything, I will submit today a patch
for the autoc
After some more testing, it appears as though the javascript issues
associated with the optiontransferselect (WW-1559) are actually
effecting it's behavior. I think we should add this back to the 2.0.2 list.
I'm not all that familiar with dojo, but I'll start to look into it today.
David
Ted
Ted,
I just released XWork 2.0RC1. All required files are uploaded to the
OpenSymphony repos. Please crosscheck if everything works for you as
expected.
If you'd like to download the distribution bundles, go to
https://xwork.dev.java.net/servlets/ProjectDocumentList?folderID=6088
tia,
Rainer
> W
40 matches
Mail list logo
