08-07-2017, 11:07 AM
First of all, I won't quote your post, because then things become extremely long. 
I think we agree on almost everything, except I'm not really sure if I understand what you mean with regions and historic mode.
Regions:
Just to be clear, and I think you mean the same, I think that the historic data should be enrolled per region. So first europe is historically accurate (as you said the major airports first), then asia for example, north america, etc etc. Once all the continents are covered, we could move on and do smaller airports, again per region.
I'm just not really sure what you mean with "If the distance between 2 airports is too big for the early years, I add a Smallest - Very small airport.".
Historic Mode:
I think this could be easily fixed since we are working with xml files. It could be done by just adding a attribute isHistoric="true". Then in the code pjank could just only load the airports with the flag isHistoric. I've been looking through the old version of tap on github, and it seems like the game is being build quite modular. So based on that I think it should not be to hard to implement. The advantages ofcourse would be that you don't have to switch between files.
As you already said, I think it would be good not to include these files in the base right now. I think it should stay as an add-on for the time being. Then users have the ability to install it or not.
Cheers
I think we agree on almost everything, except I'm not really sure if I understand what you mean with regions and historic mode.
Regions:
Just to be clear, and I think you mean the same, I think that the historic data should be enrolled per region. So first europe is historically accurate (as you said the major airports first), then asia for example, north america, etc etc. Once all the continents are covered, we could move on and do smaller airports, again per region.
I'm just not really sure what you mean with "If the distance between 2 airports is too big for the early years, I add a Smallest - Very small airport.".
Historic Mode:
I think this could be easily fixed since we are working with xml files. It could be done by just adding a attribute isHistoric="true". Then in the code pjank could just only load the airports with the flag isHistoric. I've been looking through the old version of tap on github, and it seems like the game is being build quite modular. So based on that I think it should not be to hard to implement. The advantages ofcourse would be that you don't have to switch between files.
As you already said, I think it would be good not to include these files in the base right now. I think it should stay as an add-on for the time being. Then users have the ability to install it or not.
Cheers