Getting rid of GWT MVP boilerplate
Following the documentation on places & activities + MVP, for each page I
have to create:
a place
an activity
a tokenizer (I have to implement the tokenizing logic)
an interface for the presenter (the activity implements this interface)
an interface for the view
the view implementation
the ui binder xml for view implementation
a node in app activity mapper
a node in gin module for binding view interface to view implementation
I created an app with basic functionality(5 pages and a navbar) and I
already have more than 1500 lines of code and ~40 files. I think this is
completely unmaintainable, however I haven't found anything on solving
this. There are a couple of frameworks(eg GWTP) which implement MVP but
they need the same amount of boilerplate as well.
I could achieve the same functionality in ~200 lines using spring mvc or
play.
What am I doing wrong and how would you solve it?
No comments:
Post a Comment