[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-pim
Subject:    Re: [Kde-pim] Say hello and a proposal...
From:       Rik Hemsley <rik () kde ! org>
Date:       2002-02-25 12:32:54
[Download RAW message or body]

#if Carlos Fernandez Moro

>     As seen in actual calendar implementation, it reads date information
> from QDate. I think it would ve very nice to keep data and widget
> presentacion apart, so it maybe would not be a good idea implement
> conversion routines, etc... into the calendar widget.

Sounds great to me.
 
>     There would be other 3 possibilities:
>                 1.- Making QDate a kind of abstract class extended by QGDate
> and GHDate and so....   Then we could instantiate whichever we desired...
> and let the calendar show the dates through interface defined in the root
> QDate.
>                 2.- If it's out of our scope changing QT's implementation,
> there could be a class for hijri calendar, HDate (taken from hdate package)
> and the calendar just will work with QDate for Gregorian and with HDate for
> Hijri. I will implement in HDate all the functions requires for the widget
> calls. This design isn't quite consistent... inside calendar widget...
>                 3.- Fully KDE support for dates in independiently of their
> kind. Create an utility root and abstract class KDate ? and her derived,
> KGDate and KHDarte, and so.... Maybe some scheme of this type will make easy
> conversion operators in furure plans....

How many calendar types are in use in the world ? If there are only 2
or 3, perhaps it would be easiest to simply provide conversions, rather
than using an abstract calendar and deriving from it ?

I'm no date guru :)

Rik

_______________________________________________
kde-pim mailing list
kde-pim@mail.kde.org
http://mail.kde.org/mailman/listinfo/kde-pim
kde-pim home page at http://pim.kde.org/
[prev in list] [next in list] [prev in thread] [next in thread]