This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
i had a shower-thought today that since uber-jarring the whole project would mean including fluid-r3 as a mandatory dependency, the resulting binary file is going to be pretty big, probably too big to host the file on github
probably good for it not to be in the same git repo as the rest of the alda codebase, anyway -- the git repo would take up a huge amount of hard drive space
you’d probably want to distribute it separately to final binary - so if you have an old version + sound font you don’t need to download again when upgrading
@crisptrutski: hmm... i guess we could circumvent the whole maven dependency business and just wget the soundfont via bash
- asks you where you want to store your soundfonts, default to ~/.soundfonts or whatever
maybe use reflection to check if fluidr3 is present on classpath, and make it default only then?
i don't really fully understand how the classpath works... how would one add FluidR3 to it?
if using boot to run alda (either via the current script, or via
boot alda -x ...), you can add it to the dependencies in build.boot or as a CLI parameter to boot
so boot handles downloading/locating deps and adding to classpath, but you can just add known classpaths straight if you’re running a jar with java