Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Porting to Android - Spike #56

Open
rajmahendra opened this issue Sep 26, 2015 · 2 comments
Open

Porting to Android - Spike #56

rajmahendra opened this issue Sep 26, 2015 · 2 comments

Comments

@rajmahendra
Copy link
Contributor

The Idea is to have a Android version of GitFx without much change to code base. This is in sync with the WORA - (write once run anywhere) paradigm. http://gluonhq.com/open-source/javafxports/ documents this better.

@rajmahendra rajmahendra changed the title Porting to Android Porting to Android - Spike Sep 27, 2015
@rohitvvv
Copy link
Member

The best way to take this forward is to make use of afterburner(3 class framework) and dependency injection. This will have most of the components within GitFx decoupled and we can pick and choose which feature to include in the android version of the GitFx. I have setup a experimental branch on GitFx Repo. We can test javafx ports and afterburner there.

@rajmahendra
Copy link
Contributor Author

+1
On Dec 15, 2015 9:48 AM, "Rohit" [email protected] wrote:

The best way to take this forward is to make use of afterburner(3 class
framework) and dependency injection. This will have most of the components
within GitFx decoupled and we can pick and choose which feature to include
in the android version of the GitFx. I have setup a experimental branch on
jughyd. We can test javafx ports and afterburner there.


Reply to this email directly or view it on GitHub
#56 (comment).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants