an other Win only lobby...
what is the license you use? where is the code? what language is it written in?
It would also be good if you would use something else for the CPU field then what ZK lobby uses, if you use a static value. it would make distinction of users lobbies easier, which is good for troubleshooting, as it often requires ~5min of chat with a user to find out which lobby he is using.
As far as windows-only goes, my gfx card isn't supported in linux, so i can't run spring from anything but windows. Otherwise I probably would have worked in gtk2. Personally I don't like cross-platform toolkits though. You end up looking slightly wrong everywhere.
I just ran it under wine and there were a lot of small issues. Listview Groups didnt show, it was hugely slow and it looked ugly as win95.
I could get a linux binary to work using winelib, but I don't think anyone would use it. wxWidgets has far better linux support than wine ever will.
Its all in C. There are plenty of lobbies around and writing in C means I'll always have a performance edge; I'm not going to out-feature Zero-K, and I don't find I'm much more productive in c++ than c.
String manipulation can be a little tedious though.
Its not just about performance either, I'm writing the lobby I would want to use. Starts up instantly, never loses responsiveness, and doesn't ever get in the way of the one thing i want to to: get into a game.
I haven't released the code. I intend to though, but I would need to do a lot of work to get it to that stage. Until recently my build process was little more than "gcc *.c".
right now the repository is on my hard-drive (with backups elsewhere).
As for licencing, I'll probably use GPL2, but I haven't given it too much thought.
Its a good idea to use a static value for cpu so that lobbies can be identified.
As an aside, I regret calling this RC. AlphaLobby alpha would have been more appropriate, even more appropriate would be to keep it away from the internet for a while longer.