Re: [LineControl-development] LineControl -- cvs / svn

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

Hallo,

> > Is it maybe more logic to put klcc and klcmonitorapplet
> > into klcc/client and klcc/monitorapplet ? I don't
> > know how much they're related to each other.
> 
> To be honest, I have never even looked at the monitorapplet and
> just discovered some months ago, that it's part of klcc. I don't
> know what it actually does or if it works at all, probably have to
> check that ;)

ok, no problem, don't hurry ;).
what about moving to svn?

> > What about the Qt linux/win client project?
> > Is it dropped or still in progress / planned?
> 
> There's even something called a "release" out already:
> http://metz.gehn.net/projects/qlinecontrol/
> 
> So far I have it installed on 2 linux machines and about 5 win32
> systems, didn't receive any feedback from externals users yet (not
> that I really want any right now, I know tons of stuff is missing).

Hey... cool, nice to know.
In case I write a gentoo ebuild, shall I provide the package on my
own server or will you keep the release files at the same location
over a long period of time?

Hmm... seems I have to rewrite the linecontrol homepage. ;)

Btw, if you want some user feedback, then just announce your client
on freshmeat. The feedback for the server and my clients was usually
more or less coincident with the announcements.

> Sorry for not having posted this in here earlier but I'm busy with
> other stuff right now, qlinecontrol-0.1 is just there because I

You don't have to be sorry about that. That's just the way I'm
writing software.

> needed a win32-client that is less weird than wlc2 (this is
> probably all Borlands fault, I know parts of it from Delphi and
> have learned to hate it with a passion *g*) ;)

Hey, that was at the beginning of my coding engagement. The start
to teach myself C++ (not to say object orientation... ;).
I like the GUI, but the code is horrible and I not going to look
at it again. It's always shocking to look at old code after one
learned quite a few things more.

> > Regarding linesrv-3: I have to sort out a problem
> > during line shutdown (uncought signal initiates
> > shutdown of the server...;). Due to several other
> > projects (mainly hw) and my diploma thesis this has
> > quite low priority. Growing 24/7 broadband access
> > makes the project needless anyway... but I planned
> > to bring linesrv 3 at least to a halfway usable
> > alpha state.
> 
> I use linesrv2 for my 2MBit line and I'm quite happy with it. There
> are a few things that need fixing but it works quite well most of
> the time :)

I'm running linesrv2 myself to monitor the throughput of my cable modem.
What needs fixing in linesrv2 at your opinion? Might be good to know...

Greetings

Stefan Fuchs