Re: Exception whit the GWT 2.7

Excuse me for being totally ticked off. There has got to be a better way. For example, developing for Android, we get a nice visual layout building tool for eclipse, and we don't for web applications? I couldn't even imagine handing all the gui layouts manually in xml, it would be a nightmare. I think this is moving backwards and a significant setback!

Marcin

On Wed, May 6, 2015 at 2:23 PM, Vassilis Virvilis <vasvir2@gmail.com> wrote:

uibinder is pretty nice. You right XML that is mapped automatically to HTML+GWT code

I never trusted GUI editors anyway... Even the best (qt-designer) has weird corners or at least it had 10 years ago...

     Vassilis

On Wed, May 6, 2015 at 7:56 PM, Marcin Kurzawa <mkurzawa@gmail.com> wrote:

What is the preferred way to graphically design GWT gui (developing in eclipse) when GWT Designer is phased out? Does that mean we'll have to do all that tedious work all manually typing out the code for gui layouts?

On Monday, March 2, 2015 at 10:48:05 AM UTC-5, Thomas Broyer wrote:

On Monday, March 2, 2015 at 4:22:57 PM UTC+1, Meryem Alay wrote:

Why doesn't you supoort GWT designer anymore?

You're asking the wrong people actually.

GWT Designer is (was?) a Google product, maintained by Google (after they bought Instantiations), with a stripped-down version shipped with the Google Plugin for Eclipse. It's Google all the way down, and maintained by a different team inside Google than the one building GWT.

There was a need to change some internal API of GWT, and it happens that GWT Designer calls that API (hence the error); and nobody is actually actively maintaining GWT Designer. In 2.6.0, another change broke GWT Designer already, and we reintroduced the legacy code in 2.6.1 hoping GWT Designer would be fixed. It didn't happen (as far as I know). Because the GWT Team wants to move forward, even if that means breaking GWT Designer, we thought we had to mention the breaking change in GWT's release notes, but the reality is that the team behind GWT Designer don't actively maintain it anymore, and that team is not affiliated with GWT (besides many developers working in the same company).

BTW, if you're looking for GWT Designer's source code, it's there: https://code.google.com/p/gwt-designer/

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

--

Vassilis Virvilis

--
You received this message because you are subscribed to a topic in the Google Groups "Google Web Toolkit" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-web-toolkit/SRCpvbmkmTA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.