I think that the only way to do the properly is by setting the server into practice mode, and allowing the InSim application to take over race control completely. This would allow for example things like a warm up lap, and a cool down lap.
DoP? It's defiantly possible, but each car's driver would have to be known to the InSim application, so that when a new driver comes in they can take over that car's position and continue to move the race forward for that car.
I think this is taking it too far again. Setting the server into practice mode would render the LFS Remote (which is used a lot during the race by team managers/other drivers) useless for checking gaps, split times etc..
Forgive me for my observation (especially if I'm wrong) but, is it just me or is this thread kind of going into the direction of "let's do everything other than the (now) simple original idea"?
As with any project there must be a planning stage. That and no one has said that they are actually going to do this. I've expressed an interest, and that's why I keep on replying to this thread. Anyway what's wrong with having ideas and sharing them?
I am quite familiar with product development stages and the stage of idea generating techniques, but mostly everyone agrees that they should converge on the original goal of the project or a solution to a problem. When ideas start to generate new problems instead of aiming to solve the original problem, the whole process should be reconsidered.
Here we have an already working application, the WolleT/Boothy tracker. This application handles a great amount of data and is already set up to process and display it in a way familiar (and useful) to everyone. Your expertise in matters of PHP came highly recommended and that is why I came here and asked for this small update to an already working application.
However, and forgive my observations but, all that I've seen is a group of coders that (maybe rightfully) think their PRISM project is the be all end all of PHP and InSim, and immediately want to convert and/or change completely the whole tracker application. I understand if some sort of a plugin needs to be written for the W/B tracker to communicate with PRISM, especially if that is the easiest way for you to complete the project with the least amount of work. But ideas to completely forget the W/B tracker and just have some completely new PRISM InSim application handle everything on it's own seems to me like a huge project that would take months to complete, and for what? Just so the original modification can be implemented?
I will not reflect on other ideas that also lead away from the original aim of the project, some of them not even being possible in the first place.
What I'm asking is, with all this energy being spent on nothing very productive, why don't we channel it towards something like implementing the pretty simple mathematical model on which this idea rests?
Maybe one more question: has anyone even downloaded the W/B tracker + source/documentation and had a look at how this update could be done?
My goal is not to hurt anyone's feelings or call you out, but I'm afraid from an outside perspective that things are going exactly in the wrong direction..