Fork me on GitHub
#alda
<
2015-09-20
>
dave15:09:27

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

dave16:09:02

i suppose we could host it on bitbucket instead

dave16:09:15

where do people host binary files, if not on github?

dave16:09:23

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

dave16:09:42

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

crisptrutski19:09:43

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

crisptrutski19:09:17

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

dave21:09:16

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

dave21:09:32

and put it in ~/.soundfonts or something

dave21:09:51

is that what you were thinking?

crisptrutski21:09:33

might be a bad idea simple_smile

dave21:09:22

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

dave21:09:44

it would be useful to have the soundfont path be configurable

dave21:09:58

maybe the install/setup process could be something like:

dave21:09:07

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

dave21:09:15

- run alda setup

dave21:09:28

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

dave21:09:00

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

dave21:09:20

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

dave21:09:49

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

crisptrutski21:09:04

could even check ~/.soundfonts by default

crisptrutski21:09:29

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

crisptrutski21:09:41

so by “check” i just mean add to classpath

dave21:09:07

i don't really fully understand how the classpath works... how would one add FluidR3 to it?

dave21:09:17

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

dave21:09:23

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

crisptrutski21:09:16

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

dave21:09:48

ohh, i see

crisptrutski21:09:20

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

dave21:09:44

awesome, i didn't know you could do that

crisptrutski21:09:59

also coming to java via clojure for the most part

crisptrutski21:09:23

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

crisptrutski21:09:51

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

dave21:09:35

gtg, back later tonight probably!

crisptrutski21:09:01

laters! enjoy the remains of the weekend

crisptrutski21:09:08

later here already.. i can smell the monday