OK, it’s been a while since I’ve posted anything. But now it’s time to discuss a few ideas I have about chemmacros. As you are probably aware if you are a user of the package: it provides lots of different stuff. At least in my experience it is rarely the case that you need all of its features.
So the idea is to make chemmacros a modular packages. By default let it activate only the basic features, the particle macros, say, and all other features are then loadable per use case. My idea is to have a similar mechanism like TikZ/pgf:
chemmacros then would be split in the libraries particles, iupac, units, acid, charges, redox, mechanisms, thermodynamics, spectroscopy, reactions, phases, newman and orbitals, say.
My questions to you:
- What do you think in general of this idea?
- What do you think about the library list? Is this a sensible list or should features be bundled in a library, particles and phases, say?
- Which library or libraries should be loaded as default? What should be the basic functionality of chemmacros?
On other new concerning the active development of chemmacros please see the post chemmacros development. I am very interested in you opinion oder there, too!