Kevin Dangoor <[EMAIL PROTECTED]> writes:
> On 1/13/06, Jorge Godoy <[EMAIL PROTECTED]> wrote:
>> And then I have this on my method:
>>
>> "data_envio":validators.DateConverter(month_style='dd/mm/yyyy'),
>
> Ahh... So it looks like the first thing needed is a date validator
> that handles locales reasonably and possibly lets you override the
> style for a locale. That validator would be the default on the widget.
>From the CalendarDatePicker class it looks like a lot of this is already done
and I'd need just to fix the JS part:
================================================================================
class CalendarDatePicker(Widget):
css=[CSSLink(static, "calendar-system.css")]
javascript=[JSLink(static, "calendar.js"),
JSLink(static, "lang/calendar-en.js"),
JSLink(static, "calendar-setup.js")]
================================================================================
Since 'calendar-en.js' is only suitable for English and not for other
languages... Maybe adding a new variable to pass the language (how I still
don't know since the names used by the calendar aren't what is sent by the
browser or what we inform to cherrypy.session['locale']...
> I *think* that problem is fixed. It's worth trying.
Me too. At least the problem of restarts *without* widgets is fixed...
> I certainly wouldn't have guessed that "envio" means send. I just know
> the little bit of Spanish and French that one picks up in American
> public schools, plus a little more German from classes in college
> (more than a decade ago, so you can probably imagine how much I still
> remember!) One wouldn't want me to do any translations on an app. I'd
> be worse than Google!
;-) Actually, 'envio' is from the verb 'enviar' that means 'to send'. :-)
Anyway, it seems that things are already as I need them to be, I just have to
find out how to fix the JS stuff above. The validator is already in place.
is
also
--
Jorge Godoy <[EMAIL PROTECTED]>
