Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
VDrift data manager discussion
08-19-2007, 02:23 PM,
#1
VDrift data manager discussion
We are here again for some brainstorming on this hot topic.

At the moment their is a basic implementation that downloads car/track information from svn. At the moment it is very slow (and blocking the UI-thread) because it should download several small files (each for each car/track) from a slow (SF) svn server.

My idea was to put all car/track information in one (ini like) file.

It should look something like this:

Code:
[Cars]
[CarID]
Version=VersionID
Author=Name
License=GPLv2 (or whatever)
Description=A very powerfull car
MinVDriftVersion=2007-08-03
MaxVDriftVersion=2007-08-03 (I invented a date)
Dir=data/cars/carnamedir/:1234


[OtherCarID]
Version=VersionID
....

[CarID] (not that this CarID is already used...)
Version=VersionID+1
...
Description=An expiremental update to a very powerfull car to make it even more powerfull.
...
Dir=data/cars/carnamedir/
[Tracks]
... Something similar but for tracks.

If the same ID is found several times (in two different sources, or in the same source), the user could choose what version it wants to download.
This format could be used for all sources (Ftp/Http/Whatever you want)

The only thing that is svn specific is the Dir. the :1234 at the end represents the svn revision. If not available the car/track isn't listed.
Reply
08-27-2007, 01:39 PM,
#2
 
Might make sense to separate the SVN revision number from the directory, unless we plan on having several directories under one listing, which I don't see as necessary. A config file representing all the sources is a good idea though.

I haven't had time to look at this recently and one big problem was that it wasn't working on my 64-bit desktop, so it's hard for me to mess with it, but I'll try it again sometime soon and try to make some contributions.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)