matterhorn103

Actually, it works with the keyboard too, but you have to use fn +delete.

Qt maps a Mac’s delete key to backspace, and the combination with fn to forward delete (as in, what del does on Windows and Linux).

That means Avogadro actually has the same behaviour as in other apps like Finder.

Yeah, that makes a lot of sense.

I think it’s best to say:

Avogadro is extended by plugins that can be downloaded using the plugins manager and can be uploaded to the Avogadro/plugins repo

I think it’s also reasonable to say:

one of the forms that a plugin can take is a Python package

In this case “package” retains its usual Python meaning. But that refers then to a specific subset of plugins, not all of them.

What I had originally envisaged the directory structure to look like was something like:

OpenChemistry/Avogadro
├── autosave
└── plugins
    ├── bin
    │   └── fortran-nonsense
    ├── pypixi
    │   └── avo_xtb
    ├── pypkg
    │   └── avogenerators
    └── pyscript
        └── simplecommand

or

OpenChemistry/Avogadro
├── autosave
└── plugins
    ├── bin
    │   └── fortran-nonsense
    └── python
        ├── avo_xtb
        ├── avogenerators
        └── simplecommand

At the moment it seems to be the case that all plugins are stored in a single directory, regardless of type? I.e.:

OpenChemistry/Avogadro
├── autosave
└── plugins
    ├── fortran-nonsense
    ├── avo_xtb
    ├── avogenerators
    └── simplecommand

which is also an entirely reasonable approach.

So yes, I’d definitely go for plugins wherever the term is meant to refer to all kinds of plugins.

If I understand the current implementation correctly, I’d say “plugins”, for sure.

But to clarify:

• Unless something has changed, we are supporting plugins that consist of scripts, right? What I have been referring to in various places as pyscript plugins?

• Script plugins are definitely not Python packages in either of the two usual senses.

• So my question would be, where are pyscript-type plugins saved to? And where would hypothetical Julia plugins be saved to, or binary ones (which I’m keen for Avogadro to support in the near future, at least for local installation)?

  • If the answer is “the same directory”, then I don’t think “packages” is the correct catch-all term

• “package” would also be a third term on top of “extension” and “plugin” that’s used in the code, documentation, forum etc. to refer to very similar concepts