Spring RTS Engine

bloat is a consequence of bad interface and code architecture design

AF wrote:bloat is a consequence of bad interface and code architecture design

lol. true. I'm not that great with programming, but it's my experience that programs with more features consume more memory.

But I'm all for features, and as it looks now, I don't think there's going to be much pressure to cut out features for more memory, even on the lower end systems.

I don't want spring lobby to become bloatware, while it's nice with features I don't think there should be too many ether.

cong06: The battle list sotring feature you mentioned earlier will be there as soon as all the vital features are implemented.

Progress has been slow the last week now because I haven't had access to a properly working computer. Hopefully I will be able to start working again next week.

Thanks for the update! Please don't die on us like most of the other lobbies!

Well TC i do hope you continue to work on it, and to be honest "bloat" is different to everyone what is and what isn't, you could have a million features implemented in a good way that they don't become "bloat", well that is my opinion.

I intend to work on SpringLobby for a long time forward. I will probably slow down the development phase when I consider it beeing done but I will not stop maintaining it.

Imo bloat is features that only a selected fiew have use for, and for the rest only take up ui space and or resources.

Unfortunately I haven't been able to work on SpringLobby during the last few weeks, and I don't really expect that to change. I now have a full-time work and I still have all my personal unfinished projects to work on my spare time. Maybe on my summer holiday, except that I have planned actually using that for relaxing (which I really need to) and possibly traveling around Europe.

Features, when implemented correctly, don't really add any bloat. C++ code, compiled into binary, is quite small, so you won't notice if there are many features. What you do notice is unneeded abstraction and bad algorithms/structures (if we decided to use an XML-based database that is interfaced with Java, for example).

As long as the design is done well, performance will not be a problem no matter how slow computer you have, as long as it can run wxGTK, which unfortunately is quite heavy.

tc- wrote:Imo bloat is features that only a selected fiew have use for, and for the rest only take up ui space and or resources.

yeah, your program's going to be amazing. I probably shouldn't have brought up bloat.

First test windows binary available from:
http://www.osrts.info/~heze/SpringLobby ... _alpha.zip

It's at a very early stage still

Nice one. The first impression I got was "wow, looks neat". Obviously there's not much features yet but the basic feeling about the client is very positive.

Looking forward to see more. :) Thanks guys.

Can we stick to getting it a good feature set for linux users before you sort it out for windows users?

Thanks!

I didn't intend to make the windows version work yet, but sadly I will be stuck with a windows box for the rest of the summer The only alternative would be to halt all development or the whole summer, that would be worst The features I add in the windows version will also work in linux with litte or no modification.

That is good then, well i wish you luck with programming, i just hope it does work fine on linux

If the box is somewhat recent, you can compile on a vmware instance.

Or work with someone else for a bit who has linux to do the linux side of things till your ready again?

And if the source is updated in such a way that us with linux can compile it, then we can test your updates so you can work on linux too. (sorta)

Well, there have been some incompabilities allready. Semi has been nice and sent me patches for them It is still a multi-platform lobby and there is no need for worrying, the linux version is still the one I prioritize (when I'm back on my system again I wan't a working linux lobby) even tough I can't test the changes in it properly right now

If anyone has problems or bugs in the linux version please report them because most likely I'm not aware of them, and if you know how to code a patch is always nice

I dont run linux yet my own suerbase is primarily linux users, why should this be a problem for tc? imo I consider it an advantage.

Any updates TC?