Hi, thanks for the patch. I am already applying it.
thanks! On Thu, Jul 3, 2008 at 10:42 AM, Gregor Sfiligoj <[EMAIL PROTECTED]> wrote: > Hi all! > > As suggested by Matthias I provide a new patch for the InputDate problem > (see TRINIDAD-790). This one is against the 1.0.X trunk. I'm interested in > resolving this annoying bug because I have these components in production. > I quote my previous post about the patch: > > [...] > there were two problems: > 1) DateField.js, function _dfsv(): daylight saving correction is no more > needed. Also there are 2 duplicated functions (same name) > _getLocaleTimeZoneDifference() in DateField.js and DateFormat.js. Results > are different, because one needs difference in minutes and GMT (in > DateFormat.js), the other one in millis with locale timezone correction. I > renamed the function located in DateField.js. Without renaming there are > conflicts because during creation of Common1_0_X.js one of them is > overwritten. > 2) SimpleInputDateRenderer.java: the _uixLocaleTZ variable should be setted > also if no icon is rendered for the InputDate component. This happens when > we use the ChooseDate component in combination with InputDate. > > I tested patches trying different <time-zone> settings in > trinidad-config.xml, with and without DateTimeConverter and with different > Locale settings in client browser (this affects javascript code). > > Tried also with the trinidad-demo application and works. > [...] > > > Best regards, > Gregor Sfiligoj > -- Matthias Wessendorf further stuff: blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf mail: matzew-at-apache-dot-org
