Howto:Coding a simple Nasal Framework: Difference between revisions

Jump to navigation Jump to search
Line 1: Line 1:
{{WIP}}
{{WIP}}


{{FGCquote
  | the main challenge remains thinking in terms of building blocks and frameworks that are simple and generic enough to satisfy all existing use-cases.<br/>
We have a number of people doing heavily related work without any collaboration, or even just coordination, going on here unfortunately. And obviously, skills, experience and expertise vary greatly. Unfortunately, some of the most skilled contributors are least willing to collaborate efficiently, while some of the most active contributors have yet to wrap their heads around important Nasal/Canvas concepts. All this is further complicated by the fact that some people write exceptionally good code that is never generalized and committed, while others write pretty poor code, that is directly committed to fgdata. So there's that, too ... <br/>
<br/>
Organizing this whole mess takes up a lot of energy, and usually turns out to take away all the "fun" for people unfortunately.<br/>
But there's at least a dozen people here, with varying Nasal/Canvas expertise, that are doing heavily redundant work due to lack of coordination and collaboration, sometimes it's even up to 60-80% of their work/time that could be saved by communicating up-front and getting in touch with people who've done similar things. Unfortunately, that's something that still has to happen ...
  |{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=215262#p215262
    |title=<nowiki>Re: Garmin gns530</nowiki>
    |author=<nowiki>Hooray</nowiki>
    |date=<nowiki>Wed Jul 23</nowiki>
  }}
}}
== Objective ==
== Objective ==
Illustrate the basic thought process required to come up with Nasal/Canvas code that is sufficiently generic to meet the following requirements
Illustrate the basic thought process required to come up with Nasal/Canvas code that is sufficiently generic to meet the following requirements

Navigation menu