Talk:Catalog metadata: Difference between revisions

From FlightGear wiki
Jump to navigation Jump to search
m (Switch to the {{forum link}} template for all forum links.)
 
Line 2: Line 2:
See [[Release plan]].
See [[Release plan]].


We still keep seeing issues due to aircraft developers contributing resources with files, file names, paths  that would break support on OS with case-sensitive OS or a different locale setting, it would make sense to add some form of optional and automated/scripted validation during startup to detect such issues, without requiring a manual review, possibly through [[Catalog metadata]] [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40407.html] [http://flightgear.org/forums/viewtopic.php?f=17&t=20214&p=186020&hilit=xml+french#p185963]
We still keep seeing issues due to aircraft developers contributing resources with files, file names, paths  that would break support on OS with case-sensitive OS or a different locale setting, it would make sense to add some form of optional and automated/scripted validation during startup to detect such issues, without requiring a manual review, possibly through [[Catalog metadata]] [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40407.html] {{forum link|hilit=xml+french|p=185963}}


Things that could be checked by using Nasal and corresponding SimGear bindings:
Things that could be checked by using Nasal and corresponding SimGear bindings:
Line 8: Line 8:
* file/path look-up
* file/path look-up
* texture dimensions
* texture dimensions
* max texture size [http://flightgear.org/forums/viewtopic.php?f=23&t=14232&hilit=zakalawe+traffic&start=165#p185864]
* max texture size {{forum link|hilit=zakalawe+traffic&start=165|p=185864}}
* check for rgb, png, dds textures [http://flightgear.org/forums/viewtopic.php?f=5&t=16092&p=156059&hilit=texture+dimensions#p156029]
* check for rgb, png, dds textures {{forum link|hilit=texture+dimensions|p=156029}}
* check for stereo files [http://flightgear.org/forums/viewtopic.php?f=19&t=20332]
* check for stereo files {{forum link|t=20332}}
* try to resolve shader references
* try to resolve shader references
* try to compile shaders
* try to compile shaders
* validate effects [http://flightgear.org/forums/viewtopic.php?f=14&t=19824&p=183221&hilit=+effect#p183221]
* validate effects {{forum link|hilit=+effect|p=183221}}
* resolve dependencies to external resources (aircraft, instruments)
* resolve dependencies to external resources (aircraft, instruments)



Latest revision as of 11:44, 8 June 2019

2.12 lessons learned

See Release plan.

We still keep seeing issues due to aircraft developers contributing resources with files, file names, paths that would break support on OS with case-sensitive OS or a different locale setting, it would make sense to add some form of optional and automated/scripted validation during startup to detect such issues, without requiring a manual review, possibly through Catalog metadata [1] [2] This is a link to the FlightGear forum.

Things that could be checked by using Nasal and corresponding SimGear bindings:

  • XML validation
  • file/path look-up
  • texture dimensions
  • max texture size [3] This is a link to the FlightGear forum.
  • check for rgb, png, dds textures [4] This is a link to the FlightGear forum.
  • check for stereo files [5] This is a link to the FlightGear forum.
  • try to resolve shader references
  • try to compile shaders
  • validate effects [6] This is a link to the FlightGear forum.
  • resolve dependencies to external resources (aircraft, instruments)

What is this?

The purpose of this may need further explanation. From this page alone I am not able to figure out the purpose of this, only make educated guesses. My best guess is that this is about a more or less fixed set of tags that probably is added to aircraft in the aircraft-set.xml that may or may not be parsed as of now, in essence being an experimental or developing feature.

Johan G (Talk | contribs) 16:05, 12 March 2014 (UTC)

It's basically Formalizing Aircraft Status, but more in line with the original proposal. The whole idea is to allow aircraft to be categorized and classified based on meta information, i.e. for downloading/installing (GUI frontend, integrated GUI and/or website) (Simplifying Aircraft Deployment). --Hooray (talk) 16:35, 12 March 2014 (UTC)
That was still a bit too vague. However, a few days ago I came across this and together with results from a recent search triggered by this post I had an Aha! moment.
I have now added a first section describing what the article is all about, an example of how to use the metadata tags and tried to link together some other resources and a relevant devel list thread.
Johan G (Talk | contribs) 15:41, 3 October 2014 (UTC)

Suggestions for further tags