Quarks and Extensions

Resources Libraries and Quarks
5

Thank you for the update. It seems that the fix addressed the duplicate instance variable name 'data' issue, which is appreciated.

However, the current installation path for FOSC inside your quark still creates a problem.

Users who have already installed FOSC following the official installation instructions still need to:

  • remove the existing FOSC path from SC-IDE Preferences, and
  • delete Platform.userAppSupportDir +/+ "SuperCollider/downloaded-quarks/Fosc" in Finder (or an equivalent file manager)

This creates extra work for users and unnecessary confusion for beginners.

To avoid conflicts and respect existing installations, I kindly suggest considering one of the following approaches:

  • Do not include FOSC inside your quark, and simply instruct users to install it separately as described in the official guide.
  • Or adjust the installation path of FOSC in your quark so that it matches the directory specified in the official FOSC documentation.

This would help prevent issues for users who already have FOSC installed and ensure compatibility with the original author’s instructions.

Thank you for your work on these tools, and I hope this feedback is helpful.

Added 1:

I opened two PRs related to this:

Added 2:
@madskjeldgaard If you would like to keep the FOSC installation in
Platform.userAppSupportDir +/+ "SuperCollider/downloaded-quarks/Fosc",
perhaps you could consider opening a PR at
Pull requests · n-armstrong/fosc · GitHub to make FOSC a proper Quark.

This would help avoid conflicts for users, as resolving issues caused by bundled extensions is generally not something beginners can easily manage on their own.

Added 3:

If some users happen to find and install your Quark even though you have not officially published or announced it, then of course you are free to structure it however you prefer, and in that situation any issues would naturally be handled by the users who chose to install it.

However, since you have publicly introduced and promoted your Quark, it would be appreciated if you could follow the recommended installation paths for third‑party extensions. Doing so helps prevent conflicts for users and ensures smoother interoperability within the SuperCollider ecosystem.