So the strategy is now: check if a prefs file or data directory exists in ~/.fltk/Vendor/Application, we will use that for everything. If not, we use $XDG_DATA_HOME/Vendor/Application/ (not fltk) for user data files, and $XDG_CONFIG_HOME/Vendor/Application.prefs are used for preferences.

Yes, but... If one of the "vendors" is "fltk(.org)" so we can use $XDG_CONFIG_HOME/fltk.org/fluid.prefs etc. But then, the "standard" appears to be to use "application" as the primary key in $XDG_CONFIG_HOME, hence fltk.org would look a little strange. I have such subdirectories like Code, brasero, vlc, VirtualBox, xviewer, pulse, google-chrome, gnome-session to name only a few.

On a first look fltk would be fine, but then ... other applications/vendors might want to have their own top level directory in $XDG_CONFIG_HOME. I don't know.

Porting would be done calling ... Did I catch everything?

No, I don't think what you wrote is correct, but we might have a "problem" here. The spec separates "config" (i.e. preferences) in $XDG_CONFIG_HOME and "data" in $XDG_DATA_HOME. I believe that preference files belong in $XDG_CONFIG_HOME which defaults to $HOME/.config (not .local/share). According to the spec data files belong in $XDG_DATA_HOME which defaults to $HOME/.local/share/. I would think that our additional FLTK data directory which is currently side by side with the preference file could be placed in $XDG_DATA_HOME which would require a split of preference aka "config" files and "data" files. I would not recommend to do this and rather leave the structure as it is, i.e. preference file and additional data directory side by side, even if this means that everything is in $XDG_CONFIG_HOME.

But I may have misunderstood or misinterpreted something. In my "simple" model porting would only require one directory to be moved but ... it's maybe not that simple.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you are subscribed to this thread.Message ID: <fltk/fltk/issues/303/1019374989@github.com>