On Mon, Dec 5, 2016 at 1:26 PM, Geoffrey Hutchison
<[email protected]> wrote:
> One thing I’d like to discuss as part of the Avo2 development is a set of 
> user directories (i.e., where should plugins, molecular fragments, etc. be 
> stored)?
>
> That is, we have places we install code and data files that are part of 
> Avogadro, but we should also have a default set of paths for user-accessible 
> files:
>
> This relates to Ethan’s pull request 
> (https://github.com/OpenChemistry/avogadrolibs/pull/135)
>
>
> “First Party” directories - something like this:
> - Mac @package@/Contents/share/avogadro/fragments
> - Linux /usr/local/share/avogadro/fragments
Linux would be @prefix@/share/avogadro/fragments I think, /usr vs
/usr/local vs /opt etc, but I get what you mean.
> - Windows C:\Program Files\Avogadro\fragments

I think all three should be well taken care of by CMake.
>
> Here’s my proposal for user directories
>
> - Mac   ~/Library/Application Support/Avogadro/fragments (generators, etc.)
> - Linux ?

I would favor ~/.avogadro/fragments as a pretty natural place on
Linux. This matches many other applications I have used.

> - Windows?

I would probably go with %homedir%/Avogadro/fragments or similar, but
we might want to see if there are better options.
>
> For temporary files, I think plugins should load them into a string, forcing 
> the user to save at a path of their own choosing.

I would tend to avoid temporary files unless they are needed, but if
we have a user directory couldn't we use a temp there. I think Qt has
a notion of finding an appropriate temporary directory if we want to.

------------------------------------------------------------------------------
_______________________________________________
Avogadro-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/avogadro-devel

Reply via email to