Moving 3.5 development into branches/KDE/3.5
mo85 at cornell.edu
Tue May 31 16:38:53 BST 2005
> On Tuesday 31 May 2005 07:41, Maksim Orlovich wrote:
>> 1) No new use of the old-style socket classes.
>> 2) No new use of QPtrList, and in general, of setAutoDelete
> these have been the bane of my existence in kicker. removing them has not
> fun. a word to the wary =)
>> 3) No new use of raster ops.
>> 4) No new code painting on widgets outside paint events
> we ought to capture these items somewhere accessible, e.g. on a website.
> up an area on developer.k.o for KDE4 porting. one could also use the wiki
> that's more your cup of tea, but at least link to that page from d.k.o so
> that it's easily findable.
OK, but lets collect a list first? Now, I think I'll add a few more:
5. In new dialogs, try not to use QHBox, QVBox, QGrid. Prefer layouts
6. Do not try to play with frames of groupboxes, labels, or lineedits to
fake a different widget. Use the appropriate widget instead.
(e.g., instead of setting a label to have a sunken lineedit border, how
about using a readonly KLineEdit instead? And instead of using a lineedit
without a border for a copyable widget, use KActiveLabel. Ditto for: do
not use a groupbox without border to group widgets! Just use a layout)
More information about the kde-core-devel