116
edits
Feature Requests / Proposals / Ideas: Difference between revisions
Jump to navigation
Jump to search
m
Feature Requests / Proposals / Ideas (view source)
Revision as of 09:48, 1 October 2008
, 1 October 2008We already left Shapefiles behind
Martin.spott (talk | contribs) m (Stay within design goals) |
Martin.spott (talk | contribs) m (We already left Shapefiles behind) |
||
| Line 211: | Line 211: | ||
* The current Property Tree code is not thread safe, sooner or later it may come in handy if this feature was added (FWIW, threaded PropertyTree implementations are provided by these two open source libraries: [http://pocoproject.org/poco/info/index.html poco] [http://www.boost.org boost]) | * The current Property Tree code is not thread safe, sooner or later it may come in handy if this feature was added (FWIW, threaded PropertyTree implementations are provided by these two open source libraries: [http://pocoproject.org/poco/info/index.html poco] [http://www.boost.org boost]) | ||
* Meanwhile, FlightGear has become a pretty monolothic piece of software, in the long run it would be desirable if the code could become somewhat more modularized and structured, eventually this should also make it easier for new contributors to get started. | * Meanwhile, FlightGear has become a pretty monolothic piece of software, in the long run it would be desirable if the code could become somewhat more modularized and structured, eventually this should also make it easier for new contributors to get started. | ||
* add support for decoding ESRI shapefiles, so that we can later on render them to a texture to be displayed on certain instruments, Dave Luff recently mentioned that he would need similar functionality for his KLN89, too. This would probably also be useful for scenery creation in general and in order to modify scenery appearance [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg15699.html according to region specific information] http://freshmeat.net/projects/shapelib/ http://sourceforge.net/projects/shpread/ | * add support for decoding ESRI shapefiles, so that we can later on render them to a texture to be displayed on certain instruments, Dave Luff recently mentioned that he would need similar functionality for his KLN89, too. This would probably also be useful for scenery creation in general and in order to modify scenery appearance [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg15699.html according to region specific information] http://freshmeat.net/projects/shapelib/ http://sourceforge.net/projects/shpread/ | ||
** NOTE: The Scenery generation process is already several steps ahead of this proposal and uses a PostgreSQL/PostGIS database which, as an additional feature, offers Shapefiles to be exported on-the-fly. Visit: [http://mapserver.flightgear.org/download.psp Landcover-DB Shapefile download] | |||
* Extend VRML/X3D or XGL support, so that proprietary formats such as *.ac can be entirely replaced using open standards http://en.wikipedia.org/wiki/COLLADA https://collada.org/public_forum/welcome.php (search the archives for COLLADA) | * Extend VRML/X3D or XGL support, so that proprietary formats such as *.ac can be entirely replaced using open standards http://en.wikipedia.org/wiki/COLLADA https://collada.org/public_forum/welcome.php (search the archives for COLLADA) | ||
* <strike>Helicopter FDM: either extend current FDM engines (i.e. yasim) to provide better support for helicopter flight dynamics, or come up with an entirely new dedicated helicopter FDM engine altogether</strike>-'''Support for helicopter flight simulation has been significantly improved meanwhile, and is still being worked on''' | * <strike>Helicopter FDM: either extend current FDM engines (i.e. yasim) to provide better support for helicopter flight dynamics, or come up with an entirely new dedicated helicopter FDM engine altogether</strike>-'''Support for helicopter flight simulation has been significantly improved meanwhile, and is still being worked on''' | ||