Talk:Sign Specification Proposal
Jump to navigation
Jump to search
The markup looks okay, but just for clarification: why is the specification restricted to being one ASCII string? The majority of other FlightGear configuration is using XML, while this is much more verbose, it is also much more intuitive for an average user, that is you don't necessarily have to provide any complicated markup explanations for people who aren't familiar with the syntax. Basically, using the existing infrastructure code from SimGear, shouldn't be more complicated than writing a parser for the proposed syntax?
<?xml ...> <PropertyList> <sign> <type>MANDATORY_INSTRUCTION</type> <!--DIRECTION, LOCATION, RWY DIST. --> <size>1</size> <!--1-5 --> <face> <glyphs>down</glyphs> <glyph>2</glyph> <glyph>3</glyph> <glyph>R</glyph> <arrow-up/> <arrow-down/> ... </face> </sign> </PropertyList>
--FlightZilla 16:46, 18 June 2006 (EDT)