[KVIrc] Next tasks to be done

Szymon Stefanek pragma at kvirc.net
Sun Feb 24 19:25:50 CET 2008


Here is a list of small tasks that can be done in relatively
small amounts of time.

Each task will be pushing towards a PureQt4 HEAD branch.

Pick one that you think you can finish, declare in the list
that you're working on it so no-one collides with you.

In order of increasing complexity/time needed (probably):


- Take care of KviTalHBox (src/kvilib/tal/kvi_tal_hbox.h) by writing
  a portable but independent implementation of it.
  Use QWidget as base and stick a QLayout on it.
  Take a look at kvi_tal_wizard.h for an example.

  When finished, drop the kvi_tal_hbox_*.h files.

- Take care of KviTalVBox in the same way.

- Take care of KviTalWidgetStack in the same way.

- Take a look at the behaviour of KviTalToolTip under Qt4.
  It has to be fixed.

- Take care of the "tip of the day" dialog and by the way
  try to rationalize it. Gather opinions about the question: "do we
  really need it ?".

- Take care of KviTalGroupWidget. Evaluate if it's easier
  to provide a separate Qt4 only implementation or to
  write a portable one for all the platforms.

- Take care of KviTalTabDialog. Evaluate if it's easier
  to provide a separate Qt4 only implementation or to
  write a portable one for all the platforms.

- Take care of KviTalScrollView. Evaluate if it's easier
  to provide a separate Qt4 only implementation or to
  write a portable one for all the platforms.

- Backport the Alexey's work on the help module from qmake to HEAD.
  Make the "panel" mode work again.

- Plan a possible approach to introduce the cmake build system
  in a clean, portable and non destructive manner.
  Express it in the list and maybe start it.

- Improve qt4 autotools support: detect qt4 automatically
  and use it unless instructed otherwise.
  Find a way to find the correct moc compiler automatically.

- Try to provide a Qt4 only implementation for KviTalTextEdit.

- Evaluate the usage of Q3MimeSourceFactory around the kvirc sources.
  Find a portable approach, maybe inside TAL.

- Evaluate the usage of Q3SimpleRichText around the kvirc sources.
  Find a portable approach, maybe inside TAL.
 
- Take a look at KviIrcView bugs under Qt4 with different background
  modes. fastScroll() has some bugs that duplicate lines of text.

- Take a look at KviInput. It has problems with font metrics.

I can come out with more, if you want :D

-- 

Szymon Stefanek

------------------------------------------------------------------------------
-
- When least expected... cloud connected.
-
------------------------------------------------------------------------------



More information about the KVIrc mailing list