I was wondering what was the preferred method to store snippets? I come across quick ideas I want to quickly store away for future.
There seems to be two choices..make a .opmo file or 'save the last file as .xml' under the File menu. Are there any others? I guess an xml file is good for seeing the notation rapidly but effectively renders the snippet dead as it loses the reference to the code and an .opmo file keeps the code... though this needs to be evaluated to see the notation quickly.
I updated my library tot (https://github.com/tanders/tot) in various ways. In particular, there are many new functions available.
You can now read the documentation online at https://tanders.github.io/tot/. However, remember that you can directly evaluate the many examples in the documentation when (after installing the library) you drag the library folder into your Opusmodus project navigator and open the documentation within Opusmodus.
If you are interested in the details of how the library developed, you can see a changelog at https://github.com/tanders/tot/commits/master .
NOTE: When you install/upgrade this library, make sure you also install/upgrade all its dependencies, as described in the detailed installation instructions at https://github.com/tanders/tot.
PS: This is not an official release. As I am primarily developing this library for my own purposes, I keep it rather informal and extend it on a continuous basis for my own composition projects. Anyway, I thought at least some of you might be interested to learn that there have been many developments 🙂
Is there a way a way to extend an existing library? For example, for a specific composition I may want to collect a library of rhythms, melodic fragments etc., to arrange and transform these later with existing library features. Is it possible to by and by extend a library so that instead of, say, defining
(setf rhythm1 (length-divide 1 3 '(q)))
I instead may write something like
(setf (library 'new-piece 'rhythms 'rhythm1) (length-divide 1 3 '(q)))
Asked differently: what is the internal data structure of the existing library feature(s)? Is it possible to get access to that data for user-defined functions etc.?
Also, is it possible to export an existing library into a file?
BTW: Why are all these quotes necessary in calls to functions like library and many others -- why is the function library not a macro instead (only at the top-most level of course as syntactic sugar, I am certainly not suggesting to have macros instead of functions in principle).
Thank you very much!