Move from Javavfx Webkit

[SwipeX]

The UI should be an electron wrapper (http://electron.atom.io/)

Using either memory mapping or a socket connection to transfer data between the backend and frontend.

This will solve memory issues related to javafx webkit, and allow more of a MVC feel to the frontend.

[kylestev]

I'd love to work on this. I've made electron prototypes before. should I
get started on a base app?
On Wed, Jul 27, 2016 at 08:06 Tim Dekker notifications@github.com wrote:

The UI should be an electron wrapper (http://electron.atom.io/)

Using either memory mapping or a socket connection to transfer data
between the backend and frontend.

This will solve memory issues related to javafx webkit, and allow more of
a MVC feel to the frontend.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#119, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAyBczHaldzR6ZqdI1qOAXQHgporosRSks5qZ0m2gaJpZM4JWHpL
.

[SwipeX]

yeah, i guess we can branch /electron

[BurakDev]

http://nwjs.io/ Can be used too, on the main project we can create a RESTful API allowing any interaction with the UI (or any other external program can interact with it)

[andrewmd5]

https://www.teamdev.com/jxbrowser

They offer an open source license