GWT 1.4 TO 2.0 UiBinder

I am updating a project with approximately 60 Java classes, from 1.4 to 2.0. In addition to replacing obsolete functions, adding generics, the entire project will be transformed into a UI Binder routine, that is, XML and the corresponding Java working classes. Or will I add new user interface requirements using Ui Binder and leave the existing code as it is?

+3
source share
1 answer

I would go with UiBinder completely - this way you will greatly benefit from the benefits of UiBinder (e.g. good CSS handling / minification / obfuscation). And rewriting will be a good chance to take a look at the old code and do some refactoring - like reorganizing Widgets to be easier (cleaner HTML via UiBinder, less Widgets, but not overboard;)), perhaps a href = "http: // google-web-toolkit.googlecode.com/svn/javadoc/2.0/com/google/gwt/user/client/History.html "rel =" nofollow noreferrer "> Historysupport, i18n, etc. I had the same dilemma some time ago and I took the full UiBinder approach and do not regret it;) This makes it easier to work with the code, since the user interface code is consistent.

+3
source

Source: https://habr.com/ru/post/1739094/


All Articles