I totally agree. The
wrapper, API and tag also require improvements.
See http://jscalendar.sourceforge.net
it seems very robust and flexible. Contact them. Maybe they are willing to add
another license in addition to LGPL.
From: Martin
Marinschek [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 09, 2005
8:10 AM
To: MyFaces Discussion
Subject: Re:
<x:inputCalendar> bugs
If we could finally get
rid of this whole calendar _javascript_ - I don't like it at all... it's a
written mess, horribly buggy, not skinable (except to one skin per page).
Isn't there a good _javascript_ solution out there on BSD or MIT or ASL license
base?
We can't use the LGPL things, though...
regards,
Martin
On 8/9/05, Zhai, Warren
[IT] <[EMAIL PROTECTED]>
wrote:
1. No _javascript_ onchange event?
Currently looking at this. Here is the latest code I got from the
.js file:
function jscalendarCloseCalendar() {
jscalendarHideCalendar();
if( jscalendarMyFacesCtlType!="x:inputDate" )
{
jscalendarCtlToPlaceValue.value
=
jscalendarConstructDate(jscalendarDateSelected,jscalendarMonthSelected,jscalendarYearSelected)
var
if(onchange)
{
eval(onchange);
}
}
which is supposed to execute the onchange code, but it doesn't seem to work
correctly. I have changed it to
if(onchange)
{
//eval(onchange);
jscalendarCtlToPlaceValue.fireEvent('onchange');
eval(onchange);
}
which is IE 5.5+ only and doesn't work in FireFox. Anybody has any
ideas?
2. If one deletes a few digits from yyyy values, then try to select a calendar
date from the control, the date value shown would be wrong.
3. left1.gif and right1.gif not showing onload. Refer to my previous
post for a workaround.
Wondering what more I can do to help and if anybody else has any thoughts.
Warren
