Demetrios Kyriakis wrote:
1. Keep the DateField API (the public Java one), but "refactor" the render method, to be like the RoR date field - the one with comboboxes. (it's not that fantastic, but it's usable, and is breaking no application code).
If we keep the DateField I suggest we just leave it as a textfield. Using selects seems like trouble e.g. how many years should there be. What about Date+Time. Using a textfield there is no way for the old values to corrupt.
2. Move the JSCalendar to a component called "Calendar(Field)" - since this is the correct name for it since it displays a calendar in that popup. It's API could remain the same as it is now, and the package too (the sf.net.xxxx) to ensure maximum compatibility with existing applications too.
Nods CalendarField sounds good. regards bob
