Some comments about various suggestions: [non US-keyboards] * gerard robin -- Tuesday 13 November 2007: > Some time ago (i must say some years), we where talking about the > difficulties > to get an easy use of the keyboard but the ENGLISH one which is the ONLY > one :) > As far i remember, you, Melchior were asking the question, and you got NO > ANSWER.
Yes, no interest whatsoever. Didn't bother me much. It only meant less work for me. While such keyboard mappings for non-US keyboards would be nice, there is the problem that it would break about any documentation for fgfs, including help dialogs (fixable), and XML tutorial messages. This would then basically require to translate *everything*, and I'm not sure if we are ready for that, especially after the whole locale system is outdated and broken, and hundreds of strings in Nasal files aren't translatable at the moment. My suggestion back then was to load a keyboard-<lang-code>.xml file from $FG_ROOT/Translations/ on top of the generic keyboard.xml file. This could contain some mapping information, and wouldn't actually have to define bindings. [pluggable keyboard system] * Tobias Nielsen -- Wednesday 14 November 2007: > Is it possible to consider it as a plugable keyboard system? The sim > would include a standard keyboard layout that was simular to the > normal layout as we know it uptil now, and then if some could use a > more sophisticated layout, they could themselves swap in a keyboard > layout file that supported several keystrokes as seen in the file > initialy described? That's already possible in the current system. Just put this into your ~/.fgfsrc: --config=/home/foo/.fgfs/keyboard.xml and put your definitions in this file. You can overwrite, extend, "delete" any existing bindings from the generic keyboard.xml file. I don't think we need (nor want) any further support for user defined key bindings. * Christian Buchner -- Monday 12 November 2007: > can we please get an optional keyboard mapping for "Microsoft Flight > simulator converts" ? This is to lower the barrier of entry for those > who know nothing else but FS004/FSX and would like to check out > FlightGear. If someone contributes *and* *maintains* an alternative keyboard-MSFS.xml file, then I could imagine to put that in CVS, and people could edit their preferences.xml to use this file rather than the regular one. (Or a distributor could use this file by default, and adapt all documentation for it.) But I'm strictly against any further support. FlightGear doesn't define itself through the differences from MSFS. We define our bindings in a the way that makes the most sense to us. "Converts" are supposed to adopt our way. An MSFS binding file wouldn't make the transition from MSFS to fgfs easier, it would only delay or even *prevent* a full transition. Free Software isn't about cloning closed/commercial software! :-P m. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
