Proposal: move Avogadro.conf on X11 platforms to .avogadro

Development
1

Currently, it’s placed in .config/SourceForge/, and user plugins/scripts are in .avogadro
Since config of Avogadro 1.1 is incompatible with 1.0 in many sections, I think it could be safely moved

Regards,
Konstantin

2

Hi,

On Fri, Apr 16, 2010 at 07:11:33PM +0400, Konstantin Tokarev wrote:

Currently, it’s placed in .config/SourceForge/, and user
plugins/scripts are in .avogadro Since config of Avogadro 1.1 is
incompatible with 1.0 in many sections, I think it could be safely
moved

What’s the rationale for moving it?

Michael

3

I thought it’s not very good that files are scattered over two places

16.04.10, 17:15, “Michael Banck” mbanck@gmx.net:

Hi,

On Fri, Apr 16, 2010 at 07:11:33PM +0400, Konstantin Tokarev wrote:

Currently, it’s placed in .config/SourceForge/, and user
plugins/scripts are in .avogadro Since config of Avogadro 1.1 is
incompatible with 1.0 in many sections, I think it could be safely
moved

What’s the rationale for moving it?

Michael

Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev

Avogadro-devel mailing list
Avogadro-devel@lists.sourceforge.net
avogadro-devel List Signup and Options

–
Regards,
Konstantin

Яндекс.Почта. Письма есть. Спама - нет. http://mail.yandex.ru/nospam/sign

4

16.04.10, 17:15, “Michael Banck” mbanck@gmx.net:

Hi,

On Fri, Apr 16, 2010 at 07:11:33PM +0400, Konstantin Tokarev wrote:

Currently, it’s placed in .config/SourceForge/, and user
plugins/scripts are in .avogadro Since config of Avogadro 1.1 is
incompatible with 1.0 in many sections, I think it could be safely
moved

What’s the rationale for moving it?

Also, location ~/.config/SourceForge is not very intuitive. Even ~/.config/OpenMolecules would be better. But if ~/.avogadro is needed anyway, why not to use this (most obvious) place?

Michael

Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev

Avogadro-devel mailing list
Avogadro-devel@lists.sourceforge.net
avogadro-devel List Signup and Options

–
Regards,
Konstantin

Яндекс.Почта. Письма есть. Спама - нет. http://mail.yandex.ru/nospam/sign

5

On Fri, Apr 16, 2010 at 07:25:41PM +0400, Konstantin Tokarev wrote:

I thought it’s not very good that files are scattered over two places

The point of using ~/.config was so that config files are not scattered
all over the place I thought. Your proposal might converge the avogadro
files to one place, but will diverge configuration files in general
more.

Michael

6

On Fri, Apr 16, 2010 at 11:11 AM, Konstantin Tokarev annulen@yandex.ru wrote:

Currently, it’s placed in .config/SourceForge/, and user plugins/scripts are in .avogadro
Since config of Avogadro 1.1 is incompatible with 1.0 in many sections, I think it could be safely moved

I’m not sure why SourceForge is used there but .config/ is the proper
place according to to the XDG specs. In fact, it’s the user
plugins/scripts that should be moved, to .local/share/avogadro/ most
likely. If the “SourceForge” bit is troublesome I expect that
.config/avogadro/ should be perfectly fine.

-Jordan

7

Run
ls -a | grep ‘^.’
in your $HOME and see how many applications don’t live in .config :slight_smile:

16.04.10, 20:05, “Michael Banck” mbanck@gmx.net:

On Fri, Apr 16, 2010 at 07:25:41PM +0400, Konstantin Tokarev wrote:

I thought it’s not very good that files are scattered over two places

The point of using ~/.config was so that config files are not scattered
all over the place I thought. Your proposal might converge the avogadro
files to one place, but will diverge configuration files in general
more.

Michael

Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev

Avogadro-devel mailing list
Avogadro-devel@lists.sourceforge.net
avogadro-devel List Signup and Options

–
Regards,
Konstantin

Яндекс.Почта. Письма есть. Спама - нет. http://mail.yandex.ru/nospam/sign

8

I’m not sure why SourceForge is used there but .config/ is the proper
place according to to the XDG specs. In fact, it’s the user

This is set in avogadro/src/main.cpp by QCoreApplication::organizationDomain() or organizationName().
http://doc.trolltech.com/4.6/qcoreapplication.html#organizationDomain-prop

I set these for Mac, where we were originally at http://avogadro.sourceforge.net, so the config file is net.sourceforge.Avogadro.plist.

plugins/scripts that should be moved, to .local/share/avogadro/ most

As far as scripts, my idea was that there would be two (or more) search paths. One for a machine as a whole, and one for the user. Consider, for example, multi-user desktops.

Cheers,
-Geoff

9

16.04.10, 13:30, “Geoffrey Hutchison” geoff.hutchison@gmail.com:

I’m not sure why SourceForge is used there but .config/ is the proper
place according to to the XDG specs. In fact, it’s the user

This is set in avogadro/src/main.cpp by QCoreApplication::organizationDomain() or organizationName().
http://doc.trolltech.com/4.6/qcoreapplication.html#organizationDomain-prop

I set these for Mac, where we were originally at http://avogadro.sourceforge.net, so the config file is net.sourceforge.Avogadro.plist.

plugins/scripts that should be moved, to .local/share/avogadro/ most

As far as scripts, my idea was that there would be two (or more) search paths. One for a machine as a whole, and one for the user. Consider, for example, multi-user desktops.

For global installation there’s /lib/avogadro/1_1/ . I guess ‘.local/share’ was not meant to be /share

Cheers,
-Geoff

Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev

Avogadro-devel mailing list
Avogadro-devel@lists.sourceforge.net
avogadro-devel List Signup and Options

–
Regards,
Konstantin

Здесь спама нет http://mail.yandex.ru/nospam/sign

10

On Fri, Apr 16, 2010 at 1:30 PM, Geoffrey Hutchison
geoff.hutchison@gmail.com wrote:

I’m not sure why SourceForge is used there but .config/ is the proper
place according to to the XDG specs. In fact, it’s the user

This is set in avogadro/src/main.cpp by QCoreApplication::organizationDomain() or organizationName().
http://doc.trolltech.com/4.6/qcoreapplication.html#organizationDomain-prop

I set these for Mac, where we were originally at http://avogadro.sourceforge.net, so the config file is net.sourceforge.Avogadro.plist.

plugins/scripts that should be moved, to .local/share/avogadro/ most

As far as scripts, my idea was that there would be two (or more) search paths. One for a machine as a whole, and one for the user. Consider, for example, multi-user desktops.

On linux the system wide plugin/scripts would go in /usr/ (or
/usr/local/ if installed by the system admin from a tarball) and for
the user in ~/.local/ . These are all obtained from the XDG directory
spec and so are widely used.

-Jordan

11

On Friday 16 April 2010 13:47:14 Jordan Mantha wrote:

On Fri, Apr 16, 2010 at 1:30 PM, Geoffrey Hutchison

geoff.hutchison@gmail.com wrote:

I’m not sure why SourceForge is used there but .config/ is the proper
place according to to the XDG specs. In fact, it’s the user

This is set in avogadro/src/main.cpp by
QCoreApplication::organizationDomain() or organizationName().
http://doc.trolltech.com/4.6/qcoreapplication.html#organizationDomain-pr
op

I set these for Mac, where we were originally at
http://avogadro.sourceforge.net, so the config file is
net.sourceforge.Avogadro.plist.

plugins/scripts that should be moved, to .local/share/avogadro/ most

As far as scripts, my idea was that there would be two (or more) search
paths. One for a machine as a whole, and one for the user. Consider, for
example, multi-user desktops.

On linux the system wide plugin/scripts would go in /usr/ (or
/usr/local/ if installed by the system admin from a tarball) and for
the user in ~/.local/ . These are all obtained from the XDG directory
spec and so are widely used.

I think if anything we should push closer to the spec, rather than further
away. On each platform we should strive to behave as close to native
applications as is possible whilst maintaining a consistent GUI.

Marcus

12

What about versioned config? E.g., ~/.avogadro/1_0/Avogadro.conf for stable and ~/.avogadro/1_1/Avogadro.conf for unstable?
If new version id installed, it will copy stable config if unstable is missing

–
Regards,
Konstantin