Date/time class changes to handle extended date ranges

[R.F. Pels]

On Monday 20 February 2006 12.15, David Faure wrote:

> Yes, go on until KAction and its relation to QAction (which was developed
> later on) : there is no relation between the two, except at a very high
> conceptual level. So the argument doesn't work.

At which point I say that that is the level from which newcomers start to 
operate. I did not maintain it is a hard-and-fast rule. It /is/ a pattern 
that quite quickly emerges.

> However Ruurd has a point: it would make sense that all KDate* widgets can
> actually work with KDate objects. If the APIs are similar then it shouldn't
> be too difficult to port them to KDate (and assuming there's a KDate(const
> QDate&) constructor, passing QDates to those widgets would still work.

I think we're trumped by:

http://www.trolltech.com/developer/tasktracker.html?method=entry&id=102140

-- 
R.F. Pels,  3e Rompert 118,  5233 AL  's-Hertogenbosch,  The Netherlands
+31736414590        ruurd at tiscali.nl       http://home.tiscali.nl/~ruurd