[LineControl-development] Future of KLCC

[Stefan G. <sg...@gm...>]

Moin,

as WLC is kind of dead and KLCC hasn't seen a release for quite some time=20
either I decided to finish kwallet support in cvs now and get KLCC 2.2.0 ou=
t=20
of the door. I dropped saving passwords in the config, only kwallet will be=
=20
supported now.

=46rom then on I will probably not do another release (compiling fixes and=
=20
compatiblity with newer KDE3/Qt3 versions is a reason to do another one of=
=20
course) and instead use the lcpio backend to create a Qt4-based=20
LineControl-Client. This step will have a few pros and cons:


+ only one application for both Unix and Windows (and Mac if I find a fello=
w=20
Mac-Developer who helps me with the few system-dependent things)

+ will have no external dependency except for Qt, no need for KDE anymore=20
(yes, not everybody wants to install kdelibs just for a small app)

=2D less framework help as if using KDE, stuff like systemtray, standard di=
alog=20
layouting (ok, abort buttons, tabbed dialogs) etc. are not provided by Qt,=
=20
fortunately I already have some helper classes and a systray source that is=
=20
said to work on both Windows and Unix (didn't try it yet)


I'll announce in here when KLCC 2.2.0 is finally done and probably some tim=
e=20
after that come back with the Qt4 rewrite (it's not going to be a port=20
because I want to change some things drastically, the mainwindow contents f=
or=20
instance).

Btw, if any of the KLCC translators is reading this, you can have a new=20
tarball with a few new/changed strings to translate ;)

Bye, Stefan aka mETz
=2D-=20
ICQ#51123152 | Moege der Pinguin mit euch sein