Moving 3 widgets to kdelibs.

Bram Schoenmakers bramschoenmakers at kde.nl
Sun Sep 18 08:43:30 BST 2005


Op zaterdag 17 september 2005 21:08, schreef Tom Albers:

> > I don't think we should give developers too many options. The power of a
> > good API does only work if it's used. So either you see your widgets as
> > superiour and then you should help with porting the applications and
> > replace the kdatewidget and kdatetimewidget or I would say there is
> > little point in having yet another k*date* class
>
> I think it is more user friendly then the kdatetimewidget, but if i recall
> correctly the kdatetimeedit allows users to enter 'next week','next month'
> and 'tomorrow', which makes little sense for a birthday field for example.
> So I doubt it will - unchanged - fit in all applications.

You're talking about KDatePickerPopup. It is possible to disable these extra 
words, so only the date picker is left. The "No date" entry is also optional.

Kind regards,

-- 
Bram Schoenmakers
KDE Netherlands (www.kde.nl)

What is mind? No matter. What is matter? Never mind.
  (Punch, 1855)




More information about the kde-core-devel mailing list