maybe, but that's only true because of TheTom, and the fact that he is now among the top 2 committers and maintaining and extending Canvas almost daily - otherwise, most FlightGear coding docs tend to be "good enough" for
at least a decade, especially anything related to glass avionics
If the "Canvas Development" article contains outdated code snippets, I'll try to update those shortly - we've been getting lots of feedback in response to such articles, i.e. that particular article has seen over 9k views, and the MapStructure article is close to 20k now - and even the NavDisplay article is way beyond 5k - which still is interesting given that there are apparently more people interested in extending the Canvas system than aircraft developers who want to adopt the ND ... i.e. potential core contributors.
I could obviously just delete outdated paragraphs and remove obsolete information, but I'd rather keep things up to date there - we've been seeing only a handful of feature requests in the context of future canvas developments (and sooner or later the thing will be pretty much complete), and we should make sure that people are aware of those discussions, to avoid wasted efforts, or even just conflicting approaches. And you cannot possibly implement all these feature requests by yourself - still, some people have different priorities obviously. I've seen two guys who played with hacking viewmgr.cxx to render to a canvas, and they asked for even more information than we've got there already ... so, I'll probably extend things over time to cover at least those examples that are unlikely to make it into Canvas anytime soon. The GLSL/Effects code would be another code snippet that I could add there.