20,741
edits
FGPythonSys: Difference between revisions
Jump to navigation
Jump to search
→Vision
(→Vision) |
(→Vision) |
||
| Line 47: | Line 47: | ||
| date = Jan 25th, 2016 | | date = Jan 25th, 2016 | ||
| added = Jan 25th, 2016 | | added = Jan 25th, 2016 | ||
| script_version = 0.23 | |||
}} | |||
}} | |||
== Getting involved == | |||
{{FGCquote | |||
|1= It would be awesome if you could fork the main flightgear repository to your personal SourceForge account, track my python/r3 branch, create a new branch for this change, and push the branch. This way your contributions will be far more valuable to the advancement of FGPythonSys, and we could work in a much better collaboration. | |||
|2= {{cite web | |||
| url = http://forum.flightgear.org/viewtopic.php?p=273989#p273989 | |||
| title = <nowiki>Re: FGPython an propose for Python as an nasal alternative</nowiki> | |||
| author = <nowiki>bugman</nowiki> | |||
| date = Jan 25th, 2016 | |||
| added = Jan 25th, 2016 | |||
| script_version = 0.23 | |||
}} | |||
}} | |||
{{FGCquote | |||
|1= I look forward to seeing your private branches, and to start pulling them into mine :) If this works well, then maybe I can set up a FGPythonSys development team on SourceForge, with a bug tracker and other open source infrastructure set up. Be prepared for a lot of feedback, as [http://www.nmr-relax.com/manual/Coding_conventions.html my Python coding standards are very high] ;) To have Python accepted, we should aim for very well commented, documented, and nicely formatted code! I suggest we aim at about 30% documentation/comments, as I did with the [https://sourceforge.net/u/edauvergne/code-py-ogel/ci/python/tree/test.py py-ogel test.py file]. The standard for acceptance should be set much higher than if you code normally. | |||
|2= {{cite web | |||
| url = http://forum.flightgear.org/viewtopic.php?p=274097#p274097 | |||
| title = <nowiki>Re: FGPython an propose for Python as an nasal alternative</nowiki> | |||
| author = <nowiki>bugman</nowiki> | |||
| date = Jan 26th, 2016 | |||
| added = Jan 26th, 2016 | |||
| script_version = 0.23 | |||
}} | |||
}} | |||
{{FGCquote | |||
|1= For implementing a minor feature, the best would be if you wrote [https://sourceforge.net/u/edauvergne/code-py-ogel/ci/python/tree/test.py a Python test like I did with the py-ogel]. So for example with the navdb, write a single unit test that performs a single operation. If you could write a test_*() Python function for each individual feature you would like, that would be ideal! I hope to take all of these tests and integrate them into a CppUnit test suite for FlightGear. If we have unit tests for each small bit of functionality you'd like implemented (ideally a few tests for each), then FGPythonSys would very quickly become the most stable and reliable part of FG - by far. | |||
|2= {{cite web | |||
| url = http://forum.flightgear.org/viewtopic.php?p=274097#p274097 | |||
| title = <nowiki>Re: FGPython an propose for Python as an nasal alternative</nowiki> | |||
| author = <nowiki>bugman</nowiki> | |||
| date = Jan 26th, 2016 | |||
| added = Jan 26th, 2016 | |||
| script_version = 0.23 | | script_version = 0.23 | ||
}} | }} | ||