|
From: <mer...@al...> - 2023-06-05 16:01:45
|
On 05.06.2023 16:24, James Turner wrote: > (There is actually code to fake the ‘Aircraft’ prefix if it’s > not present on disk, that’s why it works without such a directory > right now) Thanks for clarifying. >> Can't we just scan for the normal livery xmls? So we don't add >> another thing to look for? > > Well, then we need to extend them with whatever meta-data is necessary > to make packages: which I can guess is: > > - human readable name > - description > - author > - tags (for searching) > - list of compatible aircraft variants > - etc, etc > > Because this information is orthogonal (I think) to what’s in the > XML right now, I’d propose a new livery-meta-data.xml is simpler (I > probably should have done this for aircraft, but the existing -set.xml > was …. close enough) > > But, if you think you can fit the required meta-data into the existing > XML, then sure, we can do that. Looking at the Python code that scans > the aircraft -set.xmls to build the current packages might give you > some idea which option is easier: > > > https://sourceforge.net/p/flightgear/fgmeta/ci/next/tree/python3-flightgear/flightgear/meta/aircraft_catalogs/catalog.py#l46 I guess this stuff can be added in connection with an updated livery site where people can contribute liveries. (variants is not relevant cause as we have it right now, each variant got its dedicated directory) As for the original question, we'd then just take the Aircraft dirs... where in the prop tree can we find them? |