Feature Requests / Proposals / Ideas: Difference between revisions
Jump to navigation
Jump to search
Feature Requests / Proposals / Ideas (view source)
Revision as of 13:31, 18 June 2006
, 18 June 2006→General Ideas
| Line 186: | Line 186: | ||
* At http://freshmeat.net/projects/installbase/ or more specifically at http://installbase.sourceforge.net/main.shtml there's an open source cross platform GUI installer available that may be an interesting option for creating binary FlightGear installers. The whole thing is based on TK and works with statically precompiled interpreters that serve as stub for an ASCII config file that contains all relevant information for cross platform setups,including a tarball of installation specific files for each platform. The installbase installer is very convenient and works entirely with a very powerful GUI frontend that allows you to set up, test and export installer packages. Given that the final config file is ASCII, it would probably be quite possible to simply put all this into some sort of Makefile, so that the whole package creation could be handled automatically, i.e. by doing something like "make win32-package" or "make macos-package". The [http://installbase.sourceforge.net/screenshots.shtml screenshots] look very convincing. That way, all FlightGear binaries could easily use an identical installer and configuration wizard. | * At http://freshmeat.net/projects/installbase/ or more specifically at http://installbase.sourceforge.net/main.shtml there's an open source cross platform GUI installer available that may be an interesting option for creating binary FlightGear installers. The whole thing is based on TK and works with statically precompiled interpreters that serve as stub for an ASCII config file that contains all relevant information for cross platform setups,including a tarball of installation specific files for each platform. The installbase installer is very convenient and works entirely with a very powerful GUI frontend that allows you to set up, test and export installer packages. Given that the final config file is ASCII, it would probably be quite possible to simply put all this into some sort of Makefile, so that the whole package creation could be handled automatically, i.e. by doing something like "make win32-package" or "make macos-package". The [http://installbase.sourceforge.net/screenshots.shtml screenshots] look very convincing. That way, all FlightGear binaries could easily use an identical installer and configuration wizard. | ||
* Set up a cross compiler version of gcc at flightgear.org to automatically create binary packages (releases) of FlightGear for platforms such as Win32 or MacOS. FYI: all registered sourceforge developers can access the so-called "compile farm" which is comprised of a number of different hosts/platforms including various compilers, on the AMD64 Opteron machines there are also various Win32 cross-compilers installed under /var/scratch/tools/bin -if you are interested in using the sourceforge services to create FlightGear binaries, check out the [http://sourceforge.net/docman/display_doc.php?docid=762&group_id=1 sourceforge docs] --[[User:FlightZilla|FlightZilla]] 07:53, 18 June 2006 (EDT) | * Set up a cross compiler version of gcc at flightgear.org to automatically create binary packages (releases) of FlightGear for platforms such as Win32 or MacOS. FYI: all registered sourceforge developers can access the so-called "compile farm" which is comprised of a number of different hosts/platforms including various compilers, on the AMD64 Opteron machines there are also various Win32 cross-compilers installed under /var/scratch/tools/bin -if you are interested in using the sourceforge services to create FlightGear binaries, check out the [http://sourceforge.net/docman/display_doc.php?docid=762&group_id=1 sourceforge docs] --[[User:FlightZilla|FlightZilla]] 07:53, 18 June 2006 (EDT) | ||
* import the complete DAFIF data into an SQL database, including Robin Peel's database, this would offer the possibility to provide a web based interface to the corresponding data, i.e. in order to allow users to easily provide corrections or augmentations for existing data. Eventually, this could probably also be useful for the landcover DB anyway?--[[User:82.83.154.229|82.83.154.229]] 09:31, 18 June 2006 (EDT) | |||
== User Perceived Improvements == | == User Perceived Improvements == | ||