SpringLobby
Moderators: Moderators, Lobby Developers
SpringLobby
SpringLobby is a lobby client for the Spring RTS engine, developed in C++ and it's licensed under the GPL. The client is designed with the following goals in mind:
* Implemented in modern C++
* Multiplatform, depends only on wxWidgets so works on many more platforms than Spring itself
* License is GPL 2 (free as in freedom)
* Clean and intuitive user interface
* Full UTF-8 support
* Clean design, clean codebase, well documented (soon at least)
SpringLobby starts to become quite stable and has all the needed features to play and host online. You can also use it to play singleplayer games offline. The first official release will be released soon.
If you want to know more about the project, download it or help out then go to our website at:
http://springlobby.info/
Screenshots can be found here:
http://springlobby.info/wiki/ScreenShots
Last edited by tc- on 04 Sep 2007, 11:40, edited 14 times in total.
Lolz, another one, its becoming a fad now. I have an idea; why don't all the Linux lobby developers merge together to make Uberlobby. It would be like captain planet...
Secky
In all seriousness, good luck.
Secky
In all seriousness, good luck.
Last edited by Relative on 22 Dec 2007, 13:25, edited 1 time in total.
hmm, lobby rivalry, we have AFLobby, lobby++ and spring lobby all vieing for the linux ppl. I assume your going after the lightweight lobby niche? AFLobby is lightyears ahead in the all rounder heavy weight lobby arena.
You might want to think of a name change, its rather close to iamacups 'spring client' fork fo tasclient.
hint: try and seperate tasserver protocol specifics into a wrapper for future support of other protocols. Itll help a lot, and I wish I'd done it sooner.
A quick reminder, this is the same person who posted this:
http://tc.serveftp.net/layout.jpg
Would I be right in assuming this is what we're to go by?
You might want to think of a name change, its rather close to iamacups 'spring client' fork fo tasclient.
hint: try and seperate tasserver protocol specifics into a wrapper for future support of other protocols. Itll help a lot, and I wish I'd done it sooner.
A quick reminder, this is the same person who posted this:
http://tc.serveftp.net/layout.jpg
Would I be right in assuming this is what we're to go by?
TradeMark: I'm trying to make a modular design with as litle dependencies as possible beetween the various modules. With that kind of design it should not be too difficult to rip the underlaying code and put a new gui on top of it.
The protocol code could also be easily ripped ( since it's totally independent ) and used to write bots and other goodies
The protocol code could also be easily ripped ( since it's totally independent ) and used to write bots and other goodies
But could you build it?
I think running autogen.sh will do the job of fixing those files.
I think running autogen.sh will do the job of fixing those files.
Code: Select all
./autogen.sh