Comments on: Why Ext-GWT MVC is broken

By: Ext-GWT MVC Pattern explained « Programming Stuff

Ext-GWT MVC Pattern explained « Programming Stuff — Fri, 19 Mar 2010 12:29:36 +0000

[...] because of the dependencies between the view and controller. I recommend you read this blog post “Why Ext-GWT MVC is broken” by Olivier Gérarding. Also have a look at this forum post “stop the [...]

By: Bristol – Google Technology User Group » Blog Archive » Introduction to the Ext-GWT (GXT) MVC Framework

Wed, 16 Sep 2009 19:30:46 +0000

[...] at the code in the mail sample application and I could not work out how it fitted in. I then read an article which talked about how the GXT MVC pattern was broken which concerned [...]

By: olivier

olivier — Tue, 30 Jun 2009 07:51:05 +0000

For an additional point of view on Ext-GWT’s design choices, you may read this post: http://extjs.com/forum/showthread.php?p=192504#post192504
Although it was written about Ext-GWT 1.0RC, it still applies to Ext-GWT 1.2.4! Obviously Ext-GWT’s developpers don’t care much.

Impression confirmed after I had a look at the recently released Ext-GWT 2.0RC, where not a bit has changed in the MVC model. The view is still responsible for feeding events to controllers, initialize() is still as badly managed, etc.

By: GWT libraries

GWT libraries — Sun, 28 Jun 2009 15:51:46 +0000

[...] Quelle: blog.gerardin.info [...]

By: olivier

olivier — Fri, 12 Jun 2009 15:38:35 +0000

You can check out gwt-mvc or PureMVC for GWT, they are both much cleaner implementations than GXT's.

By: Pepe

Pepe — Tue, 09 Jun 2009 11:06:22 +0000

Would be interesting to see a blog entry on how a better MVC implementation would look like.

By: GWT: keep thinking in Java! « try {} catch ()

GWT: keep thinking in Java! « try {} catch () — Mon, 08 Jun 2009 08:13:09 +0000

[...] and robust client code using proven techniques such as MVC, which GWT makes really easy to use (unless you’re using GXT, but that’s another [...]

By: olivier

olivier — Wed, 06 May 2009 09:07:31 +0000

Dustin Mallory :
rolling the rest ourselves.

That's what we should have done really, but when I joined the project they already had a homebrew framework using GXT's MVC classes. So we're using it, but trying to be "clean" and avoid the pitfalls (now that we know them...)

By: Dustin Mallory

Dustin Mallory — Sun, 03 May 2009 23:30:42 +0000

Good writeup, our experience with GXT MVC was similar. We gave it a try for no reason other than, else all being equal, I’m game for favoring a framework’s conventions when it makes everything else play nicer. However, because of inherent problems you describe we’ve ended up using just their Dispatcher and AppEvent and rolling the rest ourselves.