You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @sharpie7 / anyone else! I don't know if you know anything about Android? I saw that you don't have time to maintain this, but since you did the original GWT port, hopefully you can give some pointers.
I may be interested in trying to port this (back) to Android as a course project.
1. porting
I saw it noted that this is a port of the Java applet to GWT, which apparently uses a Java-to-Javascript compiler or something like that.
How hard would it be to re-use this codebase directly for use in an Android application, so that there isn't divergence from this upstream? What should be done to port to Android?
The original reason I got this idea is because I tested the web app on Android both with Firefox/Fennec and with Chrome (I'm not sure about this, and I need to check again.), and on both of my devices it freezes after the simulation runs for a few moments. There may just be an issue with memory usage patterns, and this is an architecture, not a web app vs native android app issue, but this probably warrants investigation.
The text was updated successfully, but these errors were encountered:
Hi @sharpie7 / anyone else! I don't know if you know anything about Android? I saw that you don't have time to maintain this, but since you did the original GWT port, hopefully you can give some pointers.
I may be interested in trying to port this (back) to Android as a course project.
1. porting
I saw it noted that this is a port of the Java applet to GWT, which apparently uses a Java-to-Javascript compiler or something like that.
How hard would it be to re-use this codebase directly for use in an Android application, so that there isn't divergence from this upstream? What should be done to port to Android?
xref #633
2. performance on android
The original reason I got this idea is because I tested the web app on Android both with Firefox/Fennec and with Chrome (I'm not sure about this, and I need to check again.), and on both of my devices it freezes after the simulation runs for a few moments. There may just be an issue with memory usage patterns, and this is an architecture, not a web app vs native android app issue, but this probably warrants investigation.
The text was updated successfully, but these errors were encountered: