Re: [forge-dev] Opinion poll: Jackson vs Errai
Luca,
that's feedback I was hoping for :-)
My plans in short for aerogear-goes-errai:
- exchange Jackson ser/deser provider with Errai databinding for
entities
- create simple templated UI for entities
- extend entities with base set of annotations
- provide GWT compiler options in plugin (e.g. --style PRETTY)
Summary: produce a simple yet extendable app using Metawidget based
scaffolding mechanism "fromEntity"
Step 1: revamp a generated Aerogear app to use Errai - see the delta
Step 2: analyze possible improvements / best practices
Step 3: introduce experience into Metawidget scaffold
Step 4: implement forge commands for controlling generation/update of
source
Timeframe: Jan, 2013
It would be great to have you provide input e.g. on step 2, experience
is key in this step - and that's not what I can provide yet.
Regards,
Thomas
Am 22.12.2012 09:52, schrieb Luca Masini:
Hi Thomas, we are using GWT from 2006 (a beta version 1.0) and we
stopped developing with pure JavaScript (not for Internet sites
indeed), and from there we developed about 200 Intranet applications
with a very good impact on management.
I think that handcrafted JS is not suitable for Enterprise.
About communication, we first used my own framework for JSON
serialization
(http://code.google.com/p/productive-gwt/source/browse/#svn%2Ftrunk%2Fgwt-...)
but now I'm going to upgrade to Errai which is a framework that will
us to develop in an homogeneus way client/server.
And also I can stop mantaining that home made framework :)
Which kind of PoC do you plan to write ?
_______________________________________________
forge-dev mailing list
forge-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev
Attachments:
- attachment.html (text/html — 3.1 KB)