Quote from CLRS530 :

Also the time should be changeble to hundreds of seconds.

Using 1/100th's of a second is a bit of a bad idea since LFS might, at some point, start filling in the thousands.

I've found "m.s.h.t" extremely simple to work with.

Latest revision of my stuff,

Fri_13_Apr_2007_17_05_23_+0200.xml

Fri_13_Apr_2007_17_05_23_+0200.png

Quote from Brilwing :

Namespaces only make sense if other kind of data is also included in the XML file, and that is not the cause with the stats file format. If you want a valid XML file so that the parser has no problems, than a XML-Schema is the right way.
So we need no namespaces here, it only make things complicated.

As i see it, namespaces do not complicate things, they create an extensible format where you can put other kinds of data in the file. Since i want to be able to add extra data for rendering live progress, using namespaces makes alot of sense.

Surely it is possible to validate an extracted node / namespace instead of the entire file.

Quote from Brilwing :

As I wrote earlier in this thread I don't like abbreviations. You sometimes use full names in your example, and sometimes use abbreviations.
So always use full names like username instead of uname, or position instead of p.

I agree.

Quote from Brilwing :

Also the time should not be formated. XML is mostly read by programs so a unnecessary parsing could be avoided.

The time is actually not formatted, i've dumped it straight from LFS as m.s.h.t

Quote from Brilwing :

If the flag tags have lap numbers, than put them directly into the lap tag. Also the split times. e.g.:


<lap count="23" position="3" time="1429400">
<split number="1" time="0282100"/>
<split number="2" time="1059700"/>
<flag colour="blue"/>
<flag colour="blue"/>
</lap>


There should only be one result tag, so the result and finish should be merged to avoid duplicated informations.

I agree.

Quote from CLRS530 :

1. it looks like it want to look "professionell" in my eyes the "lfs:" is totally needless.
2. Why is there a live section. I see your idea but if you send this live you won´t send all the other data or am I wrong?
[Second Look]Ah I see it has another tag, not "lsf" is that a sort of case of? Will read something about it. But Iam confused because you have both in one file[/Second Look]

They are namespaces. For example, it's very simple to discard unknown namespaces, thus letting authors embed any kind of data without causing any trouble for a parser (since the parser never even sees data outside of known namespaces).

http://www.w3.org/TR/REC-xml-names/

This is sort of what i have in mind, should be fairly suitable for more or less complete post-race stats as well as "live" stats.

Sun_08_Apr_2007_13_25_33_+0200.xml

This thing contains quite a few redundant entries, is missing some stuff, generally unpolished and unfinished.

Incomplete rendering using templates from LFS Stats! can be viewed right here, original.

Quote from CLRS530 :

And you mean thats better?
I don´t think so

It makes XPath'ing the document easier / more sensible, for example.

Quote from Dygear :

Alright. What do we want to see in it? What name space should it take?

I'd like to see a format with profiles, a "light" profile could be the equivalent of the CSV output from LFS Stats!, and a "full" profile could contain more details such as lap by lap data. I'd want everything to be namespaced and i'd like parsers to properly discard unknown namespaces, expecting unknown data to be present. I'd also like the format to be fairly suitable for rendering live race progress.

Quote from Brilwing :

I think we should start with a xml-schema file that discribes the format.

+1

Quote from Brilwing :

attributes makes the XML easier to read (by humans).
[...]
the main goal for the stats file format should be that it is processed by programs.

I'd like a consistent design pattern.

Quote from CLRS530 :

I made such a format so the best for me would be to use that

Your format has a few problems (imho), it doesn't stick to field names from the InSim documentation and it under-uses attributes, ie.

look for live for speed player hacker

Sure.

in

Namespaced XML, extensible.

Quote from liveforspeed.net :

SMX Files
The SMX files are required for the replay analyser to display an image of the track. Click this link to download the SMX files. Create a "smx" folder inside your "lfs\data" folder and place the contents of this zip file in that folder.

http://www.liveforspeed.net/?page=analysers

Quote from AFS :

* Make sure to copy the track segment files (.tsf) in your AFS folder into LFS\data\smx folder if you don't already have them there.

In AFS: View, Preferences, LFS Directory.

Quote from Shotglass :

some slider to set the resolution would be neat

+1

Great vid, great tune.

http://www.machinaesupremacy.com/

The PHP scripts still work.

Due to FEL being increasingly drawn to balls, What's Cookin' has now moved to Wednesdays, 19:00 UTC. We've also decided to start running the event every other week, starting from the 28th.

Quote from Albieg :

You can start getting Process Explorer at www.sysinternals.com.

You can also still get the pre-Microsoft versions, last time i tried the MS versions each app had some horrid EULA popup.

http://www.sysinternals.com/files/ProcessExplorer9x.zip
http://www.sysinternals.com/files/ProcessExplorerNt.zip
http://www.sysinternals.com/files/ProcessExplorerAmd64.zip

Big archive here (oldversion.com forums).

On topic. follow Albieg's advice and backup your files.

:bump: http://www.lfsforum.net/showthread.php?t=15771 :bump:

Stats from today -> results_race.html

Last edited by filur, Mon, 12 Feb 2007 22:21.

Tyrion getting held up by people crashing, extra points for me again. :ouch:
Could almost keep up with pie-munching mr Mooney but i wasnt consistent enough, got infront when he slipped on some pie for once, got passed back a few laps later. Followed his trail of pie crumbs 'til the end and just managed not to get lapped by Hyperactive.

Good season, thanks everyone.

Stats from today -> results_race.html

Ideas.

• Don't allow premium usage unless a key has been set to allow it.
  
• Add request function to account pages at liveforspeed.net, push button-receive idkey.
  
• LFS(W) command /idkey, put response in clipboard, echo "go paste the key in your app". Don't accept paste from clipboard in LFS until contents have changed.
  
• LFS command line switch /idkey, popup dialog "do you want to request a key", returns key.
  

UK is GMT/UTC, Sweden and Norway is CET (UTC+1).

and here's the stats:

2007-01-30_21.27.00_results_race.html