Assets for Android build

[sabine]

For the android build, I have no idea how to include assets (images, css, font). Can you give me a hint how to do that?

While trying to learn about how to use Reflex, I've been adapting and compiling some example code (peg solitaire from https://github.com/gspia/reflex-examples/tree/master/peg-solitaire) using this project skeleton with great success: It builds and runs with ghcjs, webkit and android and I'm delighted to see how decent the apk runs on my 2012 phone.

Is handling of assets something that would make sense to be part of this repo?

[ElvishJerricco]

/cc @ryantrinkle. He probably knows more about how to handle assets than I do.

[marcotoniut]

I am also interested to learn about how to efficiently handle static assets. As of right now, I'm running a command after build that, among other things, generates a symlink to my static folder; problem is that nix's requisite to derive the target folder can become quite crippling for my development process for things such as highly dynamic css files. Any simple change to the css demands that I run the entire build again, a 1 minute process.

[ryantrinkle]

@ElvishJerricco https://github.com/obsidiansystems/obelisk handles this stuff fairly well; do you think it would make sense to suggest more advanced users move over to that for this kind of thing?

[ElvishJerricco]

@ryantrinkle Yea obelisk is a good suggestion. But it'd be good if there were a decent story for assets here as well. Is it too complex a problem for a minimal solution in this skeleton?

[ryantrinkle]

Ah, well if you don't care about preprocessing (minification, compression, content hashing, etc) then it should be pretty straightforward. I wouldn't recommend going to production like that, but it's no problem for an example.

…

On Sun, Jul 15, 2018, 23:53 Will Fancher ***@***.***> wrote: @ryantrinkle <https://github.com/ryantrinkle> Yea obelisk is a good suggestion. But it'd be good if there were a decent story for assets here as well. Is it too complex a problem for a minimal solution in this skeleton? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#15 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABGlYGBA4ftsPXE69U52lQPXlfJsmrvwks5uHA4qgaJpZM4TiV6O> .