Clojurians Log v2

@doppioslash has joined the channel

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

i suppose we could host it on bitbucket instead

where do people host binary files, if not 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

especially with different versions of the binary at different points in history

https://github.com/jedbrown/git-fat might help

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

downloading a file and adding it to the classpath could just be bash logic

@crisptrutski: hmm... i guess we could circumvent the whole maven dependency business and just wget the soundfont via bash

and put it in ~/.soundfonts or something

is that what you were thinking?

pretty much

might be a bad idea simple_smile

as far as i can tell, i think it would work

it would be useful to have the soundfont path be configurable

maybe the install/setup process could be something like:

- download the alda binary, put it in your $PATH

- run alda setup

- this checks whether you have an alda config file, and if not, starts one for you

- asks you where you want to store your soundfonts, default to ~/.soundfonts or whatever

- asks you if you want to fetch FluidR3 and use that

and if the user skips alda setup, it will just use the stock JVM soundfont by default

sounds good

could even check ~/.soundfonts by default

maybe use reflection to check if fluidr3 is present on classpath, and make it default only then?

so by “check” i just mean add to classpath

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

but what if you're running alda as a standalone binary?

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

ohh, i see

java -classpath ~/.soundfonts -jar alda.jar i think

awesome, i didn't know you could do that

also coming to java via clojure for the most part

learning stuff about this “low level” jvm layer too all the time

but somehow i can still pass putting “full stack” on my CV (oh the farce simple_smile)

laters! enjoy the remains of the weekend

later here already.. i can smell the monday