mvp4g for native app.

[GoogleCodeExporter]

I want to create an app that works on the web and android like google inbox 
does. I want to use mvp4g for the sake of reusing mvp4g code and I think that a 
lot of people would like to use mvp4g for regular java apps too because I think 
mvp4g is better than the any of the java mvp frameworks. Do you plan to add 
support for android? Do you have any recommendations for my project?
Once I finish porting my project to android I can contribute any relevant code 
I wrote and or documentation of how I did it.

Original issue reported on code.google.com by JGleo...@gmail.com on 22 Feb 2015 at 2:15

[GoogleCodeExporter]

This is an enhancement, not a defect.

Original comment by frank.hossfeld on 23 Feb 2015 at 9:59

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

This is a interesting request. Do you have any ideas, what has to be changed to 
fulfill the request?

What are you missing in mvp4g?

Original comment by frank.hossfeld on 23 Feb 2015 at 10:04

[GoogleCodeExporter]

The most obvious offenders are the GWT.create statements and the use of 
widgets. I'll be able to give some less obvious suggestions once I get into 
start trying to get the code to run on android. My app is simialar to Google 
inbox which has an android project, web app and a shared project with the 
shared code. In my app each of these are a gradle module(kind of like project) 
and the web and and android projects depend on the shAred project. 

Original comment by JGleo...@gmail.com on 23 Feb 2015 at 12:58

[GoogleCodeExporter]

We are thinking about  version 2,0 of mvp4g. One thing we would like to replace 
is using annotation processors instead of generators. We did our first test and 
it looks very promising.  That would help using mvp4g on Android.

The only class I know which uses the Widget class is Mvp4gEntryPoint. There is 
no need to use this class. I will check if we can remove the class.

Original comment by frank.hossfeld on 24 Feb 2015 at 9:27

[GoogleCodeExporter]

That sounds great. When I Said widgets I was referring to the way that the 
examples pass widgets into a setPage() event when doing navigation. For my app 
I'll just let the views handle navigation by themselves so that the rest of the 
code doesn't have to worry about widgets. Thanks. I'll get back to yoi once I 
finish reusing as much code as possible to Android. 

Original comment by JGleo...@gmail.com on 24 Feb 2015 at 3:18