31-07-2017, 11:46 PM
----------------------------------------------
News about development 31 july 2017
----------------------------------------------
Much thanks to all for your messages.
I'm sorry to not read all of them at this time but I'm a bit ...busy with FsPassengers programming
Actually I still explore many way & hack to do the job with short testing programs and fork modifications. It would be useless to rush doing every line by hand (with all human error possible) when one can find a better system or write a utility that can simplify the process and make it more robust and less prone to errors & bugs.
For example: When I started the prepar3d version, instead of making a separate project (was the evident solution at this time) I spent two month modifying all the code so I can compile for both version with only change in the specific code. That was a loss of time at this time, but a great gain later for the updates.
Unfortunately, it's not possible anymore with the v4 (Or at least I still didn't find a way to do so)
---------------------
About the release date, I expect at last for the end of year but it's very hard to give a date yet: I can suddenly find a way that speed the process by a factor ten, or I may be blocked on a specific problem during three weeks or more.
Anyway, I'm working very hard on it.
Kind regards
Dan
PS: I may shortcut some things as the "dangerous area" of course to speed the release and your db will still be compatible, that's not a problem.
News about development 31 july 2017
----------------------------------------------
Much thanks to all for your messages.
I'm sorry to not read all of them at this time but I'm a bit ...busy with FsPassengers programming
Actually I still explore many way & hack to do the job with short testing programs and fork modifications. It would be useless to rush doing every line by hand (with all human error possible) when one can find a better system or write a utility that can simplify the process and make it more robust and less prone to errors & bugs.
For example: When I started the prepar3d version, instead of making a separate project (was the evident solution at this time) I spent two month modifying all the code so I can compile for both version with only change in the specific code. That was a loss of time at this time, but a great gain later for the updates.
Unfortunately, it's not possible anymore with the v4 (Or at least I still didn't find a way to do so)
---------------------
About the release date, I expect at last for the end of year but it's very hard to give a date yet: I can suddenly find a way that speed the process by a factor ten, or I may be blocked on a specific problem during three weeks or more.
Anyway, I'm working very hard on it.
Kind regards
Dan
PS: I may shortcut some things as the "dangerous area" of course to speed the release and your db will still be compatible, that's not a problem.