Re: [Flightgear-devel] Addon livery handling

[TheFGFSEagle <the...@gm...>]

Since it's two separate command line options, I think it would make sense
to also have two separate lists.

Am Do., 8. Juni 2023 um 11:53 Uhr schrieb James Turner <ja...@fl...
>:

>
>
> On 5 Jun 2023, at 15:24, James Turner <ja...@fl...> wrote:
>
> Right, this is not actually a change in what we allow, although it might
> need some clarification in the UI in some places.
>
> Indeed, in some places (like cross-aircraft path imports in a model.xml)
> we actually *require* the Aircraft/ prefix, eg to find stuff in
> FGData/Aircraft/Instrument (or Instruments-3D). As I said, this area is a
> bit of a mess, but the key point is we can add in other directory names
> besides Aircraft and it won’t break
>
> (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)
>
>
> I’ve had a bit more of a thought about this, and slightly changed my mind,
> but, I think it’s mostly okay for you. Basically you should use
> resolvepath(), and assume some prefix (‘Liveries’ is probably a good idea)
> in the paths you look for.
>
> This is the same as we already discussed. (Ignoring problems with Nasal
> permissions / symlinks which I’m still waiting to hear back about) - there
> is some work to be done though, see below.
>
> The longer explanation: I’ve realised the ‘Aircraft’ prefix
> needed-vs-not-needed thing makes Aircraft dirs special - again this is a
> mess caused by my good intentions some years ago.
>
> - we have data-directories which can contain any data files but *always*
> under a named prefix (eg Aircraft/ or Textures/ or Liveries/ or Fonts/ or
> whatever)
>
> - we have aircraft directories which don’t have a named prefix, and *only*
> contain aircraft
>
> According to these statements, it’s obvious that aircraft directories are
> a special case of data-dirs, and indeed the various resolve functions such
> as resolvepath() do this already; if the path starts with Aircraft/ they
> try aircraft dirs, but they always try the data dirs as well. (They try
> aircraft dirs first, as it happens)
>
> The problem: we don’t expose data dirs in the Launcher the same way we do
> for aircraft dirs, so we need to fix that. Add-ons can supply a data-dir
> (see the docs for how to do that) and the —data=/path/to/foo lets you add
> them via the command line.
>
> In the launcher we could either make a new ‘list of data paths’ box (but
> that screen is kind of full), or re-use the aircraft paths box itself but
> check when adding a path if it contains aircraft or other kinds of data.
> I’m still thinking over which solution I prefer here.
>
> Kind regards,
> James
>
> _______________________________________________
> Flightgear-devel mailing list
> Fli...@li...
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>