Am 2012-09-26 11:19, schrieb James Turner:
> I'm testing some architectural changes in the code, and have hit upon an area 
> that's causing some structural problems. Specifically, we have two kinds of 
> instruments:
> 
>       - 'computational' ones which read and write some values and model a 
> system (steam gauges, navradio, GPWS, ....)
>       - 'display' ones which are based on RenderTexture / the Canvas and do a 
> small amount of simulation, but contain a large amount of rendering code.

I like the idea very much because most aircrafts are build like this.

An amount of blackboxes and sensors are spread over the aircraft -
invisible to the cockpit - which provide data. Either just raw or
filtered sensor readings or more complex things with
processed/interpreted data like nav, gpws, radar, tcas, etc.
Some devices also require data from other instruments for being able to
work (eg. tcas needs radalt, wow, ...). So we could just have the single
bricks and wire them together using properties - just like in the real
thing.

The second part are the displays which today are mostly multipurpose and
can show data in various ways from different sources. Even older steam
gauges just show data from sensors - normally just limited to a specific
data source.

This separation would be great for reusable but nevertheless highly
customizable instruments/displays.

Tom

-- 
Thomas Geymayer  www.tomprogs.at / C-Forum und Tutorial: www.proggen.org
------------------------------------------------------------------------
      Student of Computer Science @ Graz University of Technology
------------------------------- Austria --------------------------------

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Reply via email to