Simplifying Aircraft Deployment: Difference between revisions

Jump to navigation Jump to search
m
→‎Status (06/2014): http://sourceforge.net/p/flightgear/mailman/flightgear-devel/thread/53804519.3080009%40bham.ac.uk/#msg32375688
m (→‎Status (06/2014): http://sourceforge.net/p/flightgear/mailman/flightgear-devel/thread/53804519.3080009%40bham.ac.uk/#msg32375688)
Line 4: Line 4:
== Status (06/2014) ==
== Status (06/2014) ==
This article is purely kept for reference here, it should be considered depreciated, the feature itself is currently being worked on as part of [[Catalog metadata]].
This article is purely kept for reference here, it should be considered depreciated, the feature itself is currently being worked on as part of [[Catalog metadata]].
{{cquote
  |<nowiki>Well, if we make a manual catalog.xml from the current fgdata/Aircraft (which I have parts of a script to do), and we treat the current aircraft zip URLs as canonical, that is possible with current code right now - since it can do the zip download + extraction to a directory of our choice. We could throw an (ugly) PUI UI around that, and then if someone with more talent than me wants to Canvas-GUI-ify it, that will be great.</nowiki><br/><nowiki>
</nowiki><br/><nowiki>
I will attempt to get a prototype version of this working tonight / tomorrow. I don’t promise to produce anything usable but as you say, anything would be an improvement.</nowiki>
  |{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32397779/
    |title=<nowiki>Re: [Flightgear-devel] select/download aircraft</nowiki>
    |author=<nowiki>James Turner</nowiki>
    |date=<nowiki>2014-05-30</nowiki>
  }}
}}


{{cquote
{{cquote

Navigation menu