I'm working on integrating the menubar into the XML-configurable GUI infrastructure. There will be two big benefits from doing so:
1. Menu items will be bound using exactly the same mechanism as other bindings (keyboard, mouse, joystick, panel) -- that means that they'll be able to execute PSL scripts and invoke XML-configured dialogs. We will be able to prototype a large series of dialogs very rapidly in XML and activate them from drop-down menus, probably in the next few days. 2. The code separation will be cleaner and easier to maintain. Currently, the code in src/GUI shows its haphazard origins -- you'd have to be very drunk to think it represented even functional programming, much less object-oriented (and I write this as one of the contributors to it). Alas, there is also a down side to the change: 3. We will lose our current L10N support in drop-down menus, and will (temporarily) revert to English-only. I plan to try to find a solution for #3 that will work not only for menus but for all GUI work in FlightGear, but it will not be available for at least a couple of weeks. So, how does everyone feel about this? Are we willing to give up L10N for a few weeks to get a more complete GUI in place? I should have changes ready to check in in a few hours, and I'll leave the old menu in as a configure option for now. All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
