this doesn't seems be a valid strategy for Android...

# android

[elect]

this doesn't seems be a valid strategy for Android, where there is no URI. Reading around, it seems I should use InputStream to fetch the files (from asset), is that right?

[wasyl]

elect: If you’re reading from your app then yes. Also if your implementation works against InputStream then one way or another you’ll be able to get files in Android as `InputStream`s

[elect]

Actually I have this user having troubles, https://github.com/java-graphics/assimp/issues/5

[elect]

I don't know if he is reading from his app, I assume so.

[wasyl]

Take a look here http://stackoverflow.com/questions/24869323/android-import-java-nio-file-files-cannot-be-resolved

[elect]

my actualy implementation is using URI

[elect]

I am wondering now if I should switch to InputStream completely

[elect]

I'd like to have an unique code path for desktop and android if possible..

[wasyl]

You can, you just have to be careful that classes that use Java APIs that aren’t available on Android aren’t even initialized

[wasyl]

Basically you can’t even touch them (as in call static method on a class which has java.nio.file.* imports)

[elect]

what would you suggest to do?

[elect]

two different path code or an unique one?

[wasyl]

Probably one router to check the environment, and two implementations of an interface

[wasyl]

That’s what I used to do when I had to do different things if there was google play services library available and if there wasn’t