by Hooray » Sat Jun 21, 2014 3:21 pm
have you had a chance to review our changes yet ? I am just asking in case you need help fixing some issue on the MapStructure side of things - testing-wise, the functionality can also be tested via the new map-canvas.xml dialog (equipment) menu. Functionality should be mostly identical, but ND-specific stuff needs obviously to be tested using the 747-400 or 777-200. IIRC, the WXR/storms layer may need to be reviewed, because that's something that you developed originally, but which we ported to MapStructure. The other layers ported by Philosopher were mostly tested already by Hyde.
I'd just like to avoid any major problems/bugs - also, to ensure that the MapStructure framework can be more widely adopted in 3.2, i.e. by people developing their own layers, or variations of existing layers through custom styling.
Besides, the recent GUI work committed by TheTom means that we can phase out the PUI map-canvas.xml dialog and create the whole dialog procedurally using a native canvas window, because we really only need two types of widgets: buttons and checkboxes, which are both supported now, thanks to the new "Aircraft Center".
Regarding the PFD, I'd prefer not to add too much to that code, until it is sufficiently generalized, too - currently, it's suffering from very real design limitations, and we cannot easily support multiple instances, or different aircraft. Before anybody adopts/integrates the 747 PFD code, please do get in touch so that we can coordinate the necessary steps. It is not necessarily much work, and not even very difficult - but it may take a few iterations to be sufficiently generic. But anybody who understands basic Nasal OOP, and maybe even Canvas, should be able to work through the necessary steps within 3-4 weekends. We wouldn't be changing any functionality, it would be just about refactoring, generalization and modularization - very much in line with the original ND restructuring efforts. In other words, I'd urge anybody interested in a Canvas-based PFD to get in touch first, and not to use the code directly "as is".