search

viktorthang / mgwt

Automatically exported from code.google.com/p/mgwt
Other
0 stars 0 forks source link

less classes #252

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
Hello,

I'm currently trying to make a mockup with mgwt (after having done one with 
jqm4gwt, codename and rikulo)... The framework seems powerful and well done, 
nevertheless to verbose ; the mount of classes and interfaces we have to write 
before having something running is too big in my opinion... I'm not sure having 
decided to follow the MVP pattern is a good idea finally... too many mapper, 
places, observers, eventbus,  view, activities in interface or classe forms to 
have at the end a clear view where the things are and what not to forget...
I suggest to simplify the plumbing or at least to hide it behind some simple 
concepts...

best regards
Xavier

Original issue reported on code.google.com by xavier.m...@gmail.com on 5 Oct 2012 at 12:55

GoogleCodeExporter commented 8 years ago 
MVP is meant for developing big apps where you are going to need all that 
structuring.

You can use MGWT widgets together with AnimationHelper so it ends up being much 
lighter. For a simple mockup I would not setup places, mappers and everything.

Original comment by kurka.da...@gmail.com on 5 Oct 2012 at 1:14

GoogleCodeExporter commented 8 years ago

Original comment by kurka.da...@gmail.com on 5 Oct 2012 at 1:14

GoogleCodeExporter commented 8 years ago 
thanks for the answer ; I personnaly not find MVP relevant even for a big 
application and especially on mobile. 
It is in my case a mockup but I would have wished to do according the state of 
art of the framework ; I'll do but it is painfil wrt the other frameworks I've 
tried.

regards
Xavier

Original comment by xavier.m...@gmail.com on 5 Oct 2012 at 1:26