lmzintgraf / multimaus Goto Github PK

Question for @lmzintgraf : do we want a more user-friendly Java API?

Currently, as you can see in here, I have a hardcoded filepath to where I installed the "jpy" library (which I use for the Java-Python bridge). This is obviously not ideal.

The main problem with jpy is... it's based on C. This means that it's actually impossible to share the library directly, or have users install it somewhere. It's one of those things where basically every user has to go through an entire build process themselves, to build it for their specific platform. This is not an easy process.

The jpy license does give permission to basically redistribute the entire jpy project though. What this means is, I could put everything necessary for a jpy build (all the jpy source code etc.) inside your MultiMAuS project. Then, if a user goes through the entire build process, we'll at least know where it is located and a relative filepath to the library can be used.

I'm not sure if that's worth it though, to include a huge other library inside your project, just to make the Java API slightly less annoying to use (but still annoying, because there's still the C build process). If you think it'd be useful to have the Java API more accessible, I can look into it... otherwise I'll just selfishly continue using my hardcoded filepath and anyone else who is interested in a Java API will have to do more work themselves.