Feature Requests / Proposals / Ideas: Difference between revisions

m
m (Feature Requests / Proposals moved to Feature Requests / Proposals / Ideas)
Line 155: Line 155:
* consider setting up a subversion server, so that we can stop using CVS-subversion can easily import an entire repository, preserving all revision history etc.
* consider setting up a subversion server, so that we can stop using CVS-subversion can easily import an entire repository, preserving all revision history etc.
* http://scan.coverity.com/ - offers free code checks to open source projects
* http://scan.coverity.com/ - offers free code checks to open source projects
* 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 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.
* 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.