[nebula-dev] CalendarCombo + CDateTime Mashup

["Peter Centgraf" <peter@xxxxxxxxxxxx>]

Hi all,

The date picker portion of CDateTime suffers from a major scalability
problem on Windows because it relies on a matrix of SWT Buttons to render
the days.  Since each Button consumes at least one Win32 window handle, it
is easy to hit the 10k handles-per-application limit with only a few
CDateTime instances.

IMHO, there's no point in rewriting the current CDateTime code when Nebula
already has multiple calendar implementations.  I would like to adapt the
date picker from the CalendarCombo widget so that it can be used with
CDateTime.  This would allow me to retain the advantages of CDateTime
(access to a SWT.FLAT style, combined date and time pickers, full keyboard
input...) and gain a picker that is more friendly with Windows.

I have some practical questions to resolve before I attempt this, and that's
why I'm posting here.  Specifically, how should I combine the two projects?

1. Should I subclass the CalendarCombo classes in the CDateTime project and
then reference CalendarCombo as a dependency?

2. Should I fork CalendarCombo and move the code directly into the CDateTime
project?

3. Should I modify CalendarCombo's classes to conform to CDateTime from
within the CalendarCombo project?

As always, feedback would be appreciated!

P.S. I'd like to put together some kind of decision matrix to help people
decide when to use each of the 4 date widgets
(DateTime/CDateTime/CalendarCombo/DatePickerCombo).  We should do the same
thing for PShelf and CollapsibleButtons.  Should I screen this past the
other committers here, or just put it right up on the wiki?

--
Peter