FGQCanvas: Difference between revisions

From FlightGear wiki
Jump to navigation Jump to search
(https://sourceforge.net/p/flightgear/mailman/search/?q=fgqcanvas)
 
m (the screenshot should probably be re-uploaded here ...)
Line 1: Line 1:
{{Stub}}
{{Stub}}


James has spent some of his time since FSWeekend 2016 figuring out how he might drive some ‘real’ CDU hardware from the in-aircraft CDU options, and went for a slightly ambitious approach: he's written an analogue of [[FGPanel]] for the [[canvas]].
Analogue is actually not quite correct - unlike FGpanel this connects at the view level (canvas properties), it doesn’t run the canvas ‘model’ locally, since that would be very tough ([[Nasal]] + whole [[property tree]] needed).
This distinction was unimportant for the canvas up until now, but it’s going to become important he expects.
This was prompted by his intention to buy something like this: http://www.flightdecksolutions.com/components/b737ng/b737ng-mipmain/fds-b737ng-pro-mx-cdu-color-vga/
Which means James needs the CDU screen running on its own screen/device nicely.
And he already wrote a page-based Canvas CDU over a year ago, it’s just sitting on Gijs’ hard-drive awaiting being merged.
This is currently proof-of-concept quality, but already works quite nicely:
* uses a websocket to send an entire property sub-tree (a canvas, but in principle could be anything) to another process / machine
* render the canvas at arbitrary sie/resolution
* it’s ten source files and very simple code
It looks like this:
(see the [http://fgfs.goneabitbursar.com/screenshots/remote-canvas-nd.png linked image])<ref>{{cite web
  |url    =  https://forum.flightgear.org/viewtopic.php?p=300990#p300990
  |title  =  <nowiki>  </nowiki>
  |author =  <nowiki> zakalawe </nowiki>
  |date  =  Dec 10th, 2016
  |added  =  Dec 10th, 2016
  |script_version = 0.40
  }}</ref>





Revision as of 19:09, 18 December 2016

This article is a stub. You can help the wiki by expanding it.

James has spent some of his time since FSWeekend 2016 figuring out how he might drive some ‘real’ CDU hardware from the in-aircraft CDU options, and went for a slightly ambitious approach: he's written an analogue of FGPanel for the canvas.

Analogue is actually not quite correct - unlike FGpanel this connects at the view level (canvas properties), it doesn’t run the canvas ‘model’ locally, since that would be very tough (Nasal + whole property tree needed).

This distinction was unimportant for the canvas up until now, but it’s going to become important he expects. This was prompted by his intention to buy something like this: http://www.flightdecksolutions.com/components/b737ng/b737ng-mipmain/fds-b737ng-pro-mx-cdu-color-vga/ Which means James needs the CDU screen running on its own screen/device nicely.

And he already wrote a page-based Canvas CDU over a year ago, it’s just sitting on Gijs’ hard-drive awaiting being merged.

This is currently proof-of-concept quality, but already works quite nicely:

  • uses a websocket to send an entire property sub-tree (a canvas, but in principle could be anything) to another process / machine
  • render the canvas at arbitrary sie/resolution
  • it’s ten source files and very simple code

It looks like this: (see the linked image)[1]


Related

References

References
  1. zakalawe  (Dec 10th, 2016).  .