I’m wondering if there’s a way to set up multiple inheritance. In this instance with conflicting classes that basically do the same thing, but are positioned with an entirely different class hierarchy, and so become incompatible, with no easy way to fix that without a ton of work and breaking backward compatibility. This might help resolve these types of issues, though they do seem luckily fairly rare? I installed a bunch of quarks, and I think these were the only conflicting Class warnings I got.
I’m not entirely clear on what the difference between Extensions and Quarks really are. Why do you prefer one over the other?
I like the management features of Quarks.
Git was and still is difficult for me to grasp beyond just a place to go and download stuff from. But recently I’ve been getting a bit more into it, and using a program with a GUI has been sort of helpful for bridging the gap… Though what I think would be awesome is a Git interface that had some training wheels that explain all the terminology in a mouse position aware help browser, like Ableton, or being able to search through the documentation in the same interface, SuperCollider style. The workflow is the toughest part I think, and after learning some of it, I’m finding the command line no more difficult than the software I’ve been using to help manage it, aside from the GUI’s snapshot of the entire repository’s file structure and branches.
The Quarks interface helps hide that in a way that Extensions don’t if you want the ability to autoupdate.
Also, you have very good documentation: SuperClean was one of the first extra things I installed, and it was super easy because of it. But I encountered the documentation at the source of the download link, and the Quarks interface does obscure that. But I found myself clicking on all the Git links anyway to figure out what the libraries were actually all about to see if they were relevant to me or not.