2,561
edits
m (Removing items related to the navdb) |
|||
Line 172: | Line 172: | ||
* allow nasal scripts in AI object XM files, so that nasal code can move AI objects along predefined routes | * allow nasal scripts in AI object XM files, so that nasal code can move AI objects along predefined routes | ||
* allow instrument update interval to be configurable (export to property tree) | * allow instrument update interval to be configurable (export to property tree) | ||
* add additional updates to the splash screen during startup, so that it is more responsive, possibly using some sort of progress bar | * add additional updates to the splash screen during startup, so that it is more responsive, possibly using some sort of progress bar | ||
* allow aircraft to be reloadable at runtime (could be a first big step towards making aircraft switchable at runtime!) | * allow aircraft to be reloadable at runtime (could be a first big step towards making aircraft switchable at runtime!) | ||
Line 179: | Line 178: | ||
* the replay system is very nice, but it is not very convenient to use: improve usability | * the replay system is very nice, but it is not very convenient to use: improve usability | ||
* add texture paging support to simgear/flighgear | * add texture paging support to simgear/flighgear | ||
* saving/loading flights is not very convenient, currently loading a flight requires the user to remember its path and filename, a better way would be some sort of file picker dialog, so that the user can actually browse his file system and view all files. Also, we will probably want to have some sort of standard location for saved flights, possibly in the ~/.fgfs home directory? Additionally, it may be desirable to save additional meta information with each flight (i.e. a description) so that we could show this information as some sort of preview for all flights that were saved. | * saving/loading flights is not very convenient, currently loading a flight requires the user to remember its path and filename, a better way would be some sort of file picker dialog, so that the user can actually browse his file system and view all files. Also, we will probably want to have some sort of standard location for saved flights, possibly in the ~/.fgfs home directory? Additionally, it may be desirable to save additional meta information with each flight (i.e. a description) so that we could show this information as some sort of preview for all flights that were saved. | ||
* there is a great number of aircraft in FlightGear that cannot yet be reliably reset due to problems relating to tied properties that cannot properly be untied, obviously there are various parts in FlightGear that still do not make proper use of the property tree, we should get rid of such problems eventually | * there is a great number of aircraft in FlightGear that cannot yet be reliably reset due to problems relating to tied properties that cannot properly be untied, obviously there are various parts in FlightGear that still do not make proper use of the property tree, we should get rid of such problems eventually |
edits