New downloading system

[Licho]

If course, if that was the case Auswaschbar :)

.NET is part of the windows, its already installed on Vista and Win7.
XP have it in autoupdate too, those with pirated/update off windows need to download and install 20MB.

Those libs are of course not all loaded in ram :) It's using just 2 of them and even then .NET does not load whole dll into ram but just used parts.

And complaining about that is like claiming that program X needs 3GB windows/linux installed and loaded in ram to work. (Just "system32" folder with libs takes 2.6GB on win7)

[Auswaschbar]

.NET is part of the windows, its already installed on Vista and Win7.
XP have it in autoupdate too, those with pirated/update off windows need to download and install 20MB.

In case you didn't notice, I am talking about linux here.

And complaining about that is like claiming that program X needs 3GB windows/linux installed and loaded in ram to work. (Just "system32" folder with libs takes 2.6GB on win7)

I didn't complain, I just pointed out something SL devs should consider when deciding if they use springdownloader or not.

[hoijui]

30MB is mono for linux in HD space, or is that RAM space the downloader uses under linux?

[Licho]

How was I supposed to notice that you talk about linux?

I will check how big it's on linux. Springie process (also mono) needs about 16-20MB of RAM so certainly it does not load all mono libs to ram either..

[Agon]

Oh come on if it takes 20MB or 60MB ram. If you have 4GB or even 2GB it doesnt make much difference.
And with time more and more Linux distributions will add Mono to Gnome due some Gnome apps which require Mono.

[Licho]

I tested on my ubuntu, I let it on for 5 minutes, it takes 16mb still:



16MB is the least it can take.
It always allocates 16MB heap afaik to speed up further memory allocs.

[AF]

As great as it is, I personally would have re-implemented it in my own project purely out of User interface considerations

[Licho]

Having both server and client in 1 instance and managed by same project/people has huge benefits too.
It would always be up-to-date and can easilly be extended/improved.
This means best experience for the user.

By contrast take tasserver - changes to protocol are slow and unpopular, because there are many different clients.

[Pxtl]

What version of Mono is needed? Iirc, the current version of Mono in Ubuntu Stable is the paleolithic 1.2.6.

Oh, and being a CA player with a thin pipe, I love SpringDownloader and incremental updates. My only problem is that I never trust leaving the lobby or SD open since I don't want to hit my bandwidth cap if I should wander away from the computer for a day or two and then return to discover I've uploaded a few gigs of data and my cable company has decided to start charging me.

[Auswaschbar]

Having both server and client in 1 instance and managed by same project/people has huge benefits too.
It would always be up-to-date and can easilly be extended/improved.
This means best experience for the user.

By contrast take tasserver - changes to protocol are slow and unpopular, because there are many different clients.

http://en.wikipedia.org/wiki/Monoculture

[AF]

There's also the element of competition, and the advantages it brings

[Licho]

Wtf Auswaschbar is your problem? You are just trolling here.

Moderator should not behave like this.
First completely random lies about mono and now this.

SD is open source project and has 5 contributors, its not some ultrasecret licho's only closed source.



And pxtl you dont have to worry about uploads now, it's turned off, there are plenty of webmirrors.

AF competition? Sure - if you create completely different system, but otherwise it hurts development if both clients use same server/resources and heavily depend on them.
Face it, downloader does not need fancy gui, its all about what it does not about how it looks.

[Auswaschbar]

Moderator should not behave like this.

I am not a moderator (well, technically I am, but I am not moderating).

First completely random lies about mono and now this.

I didn't lie when I said that mono is an additional dependency (and not a small one), and thats all I said.

SD is open source project and has 5 contributors, its not some ultrasecret licho's only closed source.

I didn't wanted to say that, and if it sounded like that I'm sorry.
But my point remains valid: TASClient also was opensource all the time, but neither it nor the tasclient protocol improved much until SL came out.

[Licho]

Afaik tasclient stopped improving after SL was released. Because there was little point to maintain it!

Satirik came back only recently and maintains/fixes bug. Tasclient also never had many contributors because its problematic to compile it.

For SD you just get sources from repository and it opens and compiles in both visual studio and monodevelop.


Since this is as good place as any to give credits I should list people who contributed to current SD/system:

det - design of package system, implementation of pool for engine, server side tools and maintenance

very_bad_soldier - widget module, widget database/website and management tool

quantum - multiplatform compatibility, unitsync replacement and wrapper (to prevent lag/slowdowns caused by unitsync operations and allow operation even if unitsync fails to work)

YotaXP - GUI improvements (he made transfers tab)

Licho - old p2p coordinator and new server, rest of the SD itself.

[Licho]

Also, there is no competition. If SpringLobby implements its own downloader, there will be no point to keep working on SpringDownloader. Why would I work on it if lobby has another and why would anyone use it??


Problem is that SpringLobby will likely never implement as many features (missions, widgets, modstatistic submissions). Last plan was to even skip packages/incremental pool system completely.

Thats why I would rather see lobby interface to SD. Its already done, it works and can be improved easilly and updated/maintained independently from SpringLobby.

[very_bad_soldier]

[*] allow downloading multiple widgets at once

Its possible. Select multiple widgets by holding CTRL and then right-click for context menu.

when the list gets actualized (eg. when downloading a widget finnished), reset the position to the previous one, instead of showing position 0 in the list

Thats how it is in latest version (dunno, probably not yet release I guess).

-maybe remove some outdated widgets (thinking on the multiple transporter widgets eg.)
-allow tagging widgets, for example: grapic, functional, important, must-have (eg CustomFormations2)[/list]
minor things.. not such a big issue, as usually you dont do much widgets fiddling except after a fresh install, could be usefull for noobs though.

Added to Todo-list

[AF]

When I say UI considerations, I don't talk about aesthetics, Id want the functionality integrated very tightly with the workflow of how my programs work, to that end a more library like approach is necessary.

In the meantime I welcome future development

[Satirik]

But my point remains valid: TASClient also was opensource all the time, but neither it nor the tasclient protocol improved much until Satirik came out.

fixed ... and pls ... don't talk about things you don't know

[hoijui]

ehh cool!
thanks very_bad_soldier!
about installing multiple widgets at once:
i did select multiple ones with CTRL or SHIFT, and then clicked on Install. ... it kind of makes sense that it only installs the first one in the selection then, as the Install button is (GUI wise) tied to a single widget. maybe the button could be moved to under/above the list, and then install all selected widgets. maybe it is only me, but at least for me.. i did not get into mind that there could be a context menu in the list.
no problem for me anymore, now that i know, thanks again!

[AF]

Actually I think it rich to say that the burst fo atsclient and TASServer activity was Springlobbys responsibility, or satiriks, sure they helped move it along...

Instead the original AFLobby and most of all Unity Lobby played a huge role here. Unity Lobby for bringing competition, an AFLobby for the slew of features that got stolen from it.