Re: [Flightgear-devel] Wiki keyboard page (was Re: Keyboard reorg)
On 12/11/2007, gerard robin [EMAIL PROTECTED] wrote: probably i misunderstood the rule, didn't you modify cvs before getting decision about *what* functions need keybindings. I promised to put it back if there were objections -- there were, and I plan to put it back, but I can't connect to the CVS right now (time out). My suggestion about discussing keybindings was also a response to those objections (we used to just check in changes and revert them if people didn't like them, but I can see that the project culture has changed a bit). Given the (apparent) anger and sarcasm, I'm guessing you've had a very bad experience on some other open source project. I'm sorry that's happened (I've worked on projects like that too), but please try to approach FlightGear with an open mind and not start by assuming the worst of everyone -- unless it's changed a lot in the couple of years that I was away, it's a group of very nice and talented people, and I hope they've made you feel welcome. All the best, David - 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
Re: [Flightgear-devel] Wiki keyboard page (was Re: Keyboard reorg)
On mar 13 novembre 2007, David Megginson wrote: On 12/11/2007, gerard robin [EMAIL PROTECTED] wrote: probably i misunderstood the rule, didn't you modify cvs before getting decision about *what* functions need keybindings. I promised to put it back if there were objections -- there were, and I plan to put it back, but I can't connect to the CVS right now (time out). My suggestion about discussing keybindings was also a response to those objections (we used to just check in changes and revert them if people didn't like them, but I can see that the project culture has changed a bit). Given the (apparent) anger and sarcasm, I'm guessing you've had a very bad experience on some other open source project. I'm sorry that's happened (I've worked on projects like that too), but please try to approach FlightGear with an open mind and not start by assuming the worst of everyone -- Oh yes, your are right i don't have any open mind (that was said to me before by others, mainly regarding my use of OSG, and i got a recommendation to go to the MS World). Working (playing) with FG since the beginning (i remember an FG without YAsim) i could notice a permanent progress, not a regression, when the carrier features came up, the keys where defined, probably you where not there at that moment. unless it's changed a lot in the couple of years that I was away, it's a group of very nice and talented people, and I hope they've made you feel welcome. All the best, David I don't mind to have a full rebuild of the Keyboard feature, i prefer an evolution rather than a revolution. To me the talk is closed. Regards -- Gérard http://pagesperso-orange.fr/GRTux/ - 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
[Flightgear-devel] Wiki keyboard page (was Re: Keyboard reorg)
Thanks to everyone for the suggestions so far. Just to get back on track, we have to start by seeing if we can come up with a short, priority list of stuff that's (a) applicable to most aircraft, and (b) important enough to have a key assignment. We can decide exactly what those key assignments will be (and what language[s] we'll use) after I've started my own list here: http://wiki.flightgear.org/flightgear_wiki/index.php?title=Keyboard_function_priority_list Please go to the page and edit it with your own suggestions. Collectively, I think we can come up with a priority list that's at least 80% good enough, though obviously we'll never hit 100%. All the best, David . - 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
Re: [Flightgear-devel] Wiki keyboard page (was Re: Keyboard reorg)
On lun 12 novembre 2007, David Megginson wrote:
Thanks to everyone for the suggestions so far. Just to get back on
track, we have to start by seeing if we can come up with a short,
priority list of stuff that's (a) applicable to most aircraft, and (b)
important enough to have a key assignment. We can decide exactly what
those key assignments will be (and what language[s] we'll use) after
I've started my own list here:
http://wiki.flightgear.org/flightgear_wiki/index.php?title=Keyboard_functio
n_priority_list
Please go to the page and edit it with your own suggestions.
Collectively, I think we can come up with a priority list that's at
least 80% good enough, though obviously we'll never hit 100%.
All the best,
David
.
Wouldn't it be better to say first which mains features will not have an
official KEY dedicated ?
I have made a noise before, about the Carrier feature ( i am very sensitive
with it ) , only to discover later on, that was not a problem , since we are
free to overlap the KEY (L now in use for tail lock) ).
I usually use the following keys:
Carriers features
L Launchbar
C Catapult
O o Hook
F f wings folding (or in my case with S-51 blade folding)
d door or canopy (open close)
With Turbine Engine
the start process is
} toggle Electric Master Switch On/Off
s get the external Air compressor resources
{ toggle Cutoff
in addition to it, with aircraft which have variable incidences or sweep
wings = toggle
Within a close circle of friends users this not a problem, it could be one
big problem when my hangar will be in CVS :)
Cheers
--
Gérard
http://pagesperso-orange.fr/GRTux/
-
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
Re: [Flightgear-devel] Wiki keyboard page (was Re: Keyboard reorg)
I'm probably going to get tared and feathered (or tasered?) for this, but 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. My first FlightGear experience was how the hell do I throttle up... poking the F4 button because I was used to that. The alternative keyboard mapping should in my opinion be accessible from the user interface through some kind of Reset Keyboard Mapping to FSX and Reet Keyboard Mapping to FlightGear button or menu item that can be found easily. I know that not every function of FSX is accessible in FlightGear and vice versa (in particular not the view system with the multiple sub windows), but a mapping that gets the most important features right would be a huge help for converts like me. Christian - 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
Re: [Flightgear-devel] Wiki keyboard page (was Re: Keyboard reorg)
On lun 12 novembre 2007, David Megginson wrote: On 12/11/2007, gerard robin [EMAIL PROTECTED] wrote: Wouldn't it be better to say first which mains features will not have an official KEY dedicated ? I think it's shorter to decide which ones *will* have an official key dedicated -- that's what the list is for. All the best, David Do you mean wait and see ? Developing a model is not so easy, and the less time we spend on it, the best it is, i told my disappointment regarding the use of L and your change ignoring the Carrier features (probably because it is not civilian). I know that cvs could get permanent modifications, but i know when a user has in mind the how to process , with which key it takes some time to learn the new. Vivian said it before Any major change would require our users (and developers to unlearn the old and relearn the new. Unlikely to win many friends. Regards -- Gérard http://pagesperso-orange.fr/GRTux/ - 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
Re: [Flightgear-devel] Wiki keyboard page (was Re: Keyboard reorg)
On 12/11/2007, gerard robin [EMAIL PROTECTED] wrote: Do you mean wait and see ? No, just that it makes sense to decide *what* functions need keybindings before we decide *where* to bind them. Have you had a chance to edit the wiki page yet? All the best, David - 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
Re: [Flightgear-devel] Wiki keyboard page (was Re: Keyboard reorg)
On lun 12 novembre 2007, David Megginson wrote: On 12/11/2007, gerard robin [EMAIL PROTECTED] wrote: Do you mean wait and see ? No, just that it makes sense to decide *what* functions need keybindings before we decide *where* to bind them. Oh, right , probably i misunderstood the rule, didn't you modify cvs before getting decision about *what* functions need keybindings. Have you had a chance to edit the wiki page yet? All the best, David -- Gérard http://pagesperso-orange.fr/GRTux/ - 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
