Spring RTS Engine

At the moment this database is the only way of acquiring widgets enmasse outside of ripping them from games and spending hours trawling the lua forum.

Yes, I think it has some use for game makers but not for players.
But even in that case:
camera widget:
version on widgetDB: Entry-Date: 2010-09-07
http://widgets.springrts.de/springinfo/index.php#155
version in zero-K:
http://code.google.com/p/zero-k/source/ ... start=3382
has a dozen commits/changes/fixes made to it, more up to date.
Which one would you get?

Problem is that once things that are still wip are uploaded to multiple sites, some mirrors do not get updated. So is why I never used it either for up/download.
I do not know how that could be solved...
There are some interessting things on the widgetDB that afaik currently no game uses, ie the "dynamic blob shadows."

having widgets in a separate repo, and including this as a submodule in the engine could work. it should not be in base then though, as that would introduce the need to use git submodules to sync.
it could also be in the engine repo directly, but that would allow less flexible rights management.

knorke: well, pull them out of widget db and make a best of...

vbs, can you do a dump of all widgets? possibly creating a text file for thier page description info?

smoth wrote: vbs, can you do a dump of all widgets? possibly creating a text file for thier page description info?

Thats probably even more work than just copying the DB and the scripts to another host. Also such a dump is harder to use and to distribute. What would be the advantage?
If I want to keep the DB I would just keep it online as it is I guess.

the idea was to take the widgets and put them in a subversion server.

that way there is versioning and version history. but for the widgets I would like to see them with at least a small document saying whatever details the creator may have posted.

I think a db is bad, versioning is the right approach.

smoth wrote: that way there is versioning and version history. but for the widgets I would like to see them with at least a small document saying whatever details the creator may have posted.

I think a db is bad, versioning is the right approach.

There currently is versioning and also a version history (not SVN though).
This was primarly meant as a source for players (hence the auto-installer and updater and stuff). I understand your viewpoint but it was not aimed to be a repository of source code for developers with code comparison facilities and stuff.
Developers know quite good how to get their stuff but you cant tell players to install an svn client and get their widgets from a repo (or from ZK or from some forum posts...).

Dunno about GIT but even modelers were willing to use SVN (springrts.com still has original svn hosted).

If you can stomach using a non-relational database, see http://code.google.com/appengine/

Oh we are now moved to new server, contact me to get some account