Re: [LineControl-development] what's going on...

[S. F. <lin...@sr...>]

Hello,

> >    I've lost interest to continue on WLC2 because I'm not running
> >    windows anymore. Well... sometimes... every other month or so I
> >    boot it because I can't avoid it.
> 
> Hmm, what a pity. Personally I'm still using WLC1 here because WLC2
> never got stable enough and has problems with starting minimized. It
> would be really cool if somebody with windows-coding knowledge could
> take over WLC, all I know about is Delphi (and that's ugly).

There was once a DC or LC client written in Delphi ;)
Well, I've given up...

The problem with the existing WLC2 bugs is, that my Win coding
knowledge is too small / non-existent to fix them.

> 6. The last thing I have to add to klcc before a new release is
> kwallet support (it's in my code already but not properly done yet).
> I plan on ditching the "save in config" option and allow either
> fetching it off kwallet or typing it in on connect. As kwallet is
> part of KDE since 3.2 I think people AND applications should finally
> start using it. Apart from that I fixed a few things and added
> support for some KDE 3.2 specific items. The next release will most
> probably only work with KDE 3.2, I hope this is ok for most users.

Sounds great. I just checked out the latest CVS version and tried to
compile it. There was no 'configure.in' but instead I found a
'configure.in.in'. It didn't seem to contain stuff needing
preprocessing so I just moved it to configure.in and tried the usual
'aclocal ; autoheader ; automake --foreign --add-missing ; autoconf'.
It seems configure.in.in is a bit too minimal... ;). I didn't
investigate it further, probably no output directives for the
Makefiles in configure.in or something like that I guess.

Did I do something wrong or is it at the moment effectively in a
non-working state? No problem for me... just wondering...

Greetings

Stefan Fuchs