<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>minuteFForts &#187; GWT</title>
	<atom:link href="http://minutefforts.com/blog/?cat=12&#038;feed=rss2" rel="self" type="application/rss+xml" />
	<link>http://minutefforts.com/blog</link>
	<description>It would only take minute efforts, they said.</description>
	<lastBuildDate>Tue, 21 May 2013 00:12:25 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
		<item>
		<title>A class diagram of the GWT MVP model [Update]</title>
		<link>http://minutefforts.com/blog/?p=50</link>
		<comments>http://minutefforts.com/blog/?p=50#comments</comments>
		<pubDate>Mon, 17 Oct 2011 19:20:54 +0000</pubDate>
		<dc:creator>Hans-Joachim Belz</dc:creator>
				<category><![CDATA[GWT]]></category>

		<guid isPermaLink="false">http://minutefforts.com/blog/?p=50</guid>
		<description><![CDATA[<a href="http://minutefforts.com/blog/?p=50" title="A class diagram of the GWT MVP model [Update]"></a>Since 2009 Google has advocated the MVP pattern as the preferred architecture for large scale GWT applications. With GWT 2.1 Google introduced the concept of &#8220;Activity&#8221; and &#8220;Place&#8221; (borrowing from the Android UI framework). Apart from providing a standard way &#8230;<p class="read-more"><a href="http://minutefforts.com/blog/?p=50">Read more &#187;</a></p>]]></description>
			<content:encoded><![CDATA[<a href="http://minutefforts.com/blog/?p=50" title="A class diagram of the GWT MVP model [Update]"></a><p><a href="http://www.youtube.com/watch?v=PDuhR18-EdM" target="_blank">Since 2009</a> Google has advocated the <a title="Large scale application development and MVP" href="http://code.google.com/intl/de-DE/webtoolkit/articles/mvp-architecture.html" target="_blank">MVP pattern</a> as the preferred architecture for large scale GWT applications. With GWT 2.1 Google introduced the <a title="GWT Development with Activities and Places" href="http://code.google.com/intl/de-DE/webtoolkit/doc/latest/DevGuideMvpActivitiesAndPlaces.html" target="_blank">concept of &#8220;Activity&#8221; and &#8220;Place&#8221;</a> (borrowing from the Android UI framework). Apart from providing a standard way for history management, it can be elegantly combined with GWT UI components to form an MVP architecture with easy device-dependent views making it <a title="Google I/O 2011: Using GWT and Eclipse to Build Great Mobile Web Apps" href="http://www.youtube.com/watch?v=N1aCo5LvMf8" target="_blank">a great starting point for mobile web development</a>.</p>
<p>While I found the framework to be very powerful, it also has put quite a strain on my ability to memorize classes and their relationships. In the end &#8211; since I found no good rendition in the Internet &#8211; I ended up creating my own diagram of the MVP frameworks&#8217;s main classes around the concepts of &#8220;Activity&#8221;, &#8220;View&#8221; and &#8220;Place&#8221;.</p>
<p><span id="more-50"></span></p>
<p>Here is the class diagram in in PDF format. I will publish the original OmniGraffle file later on GitHub. Any comments are welcome.</p>
<p><a href="http://minutefforts.com/blog/wp-content/uploads/2011/10/gwt-mvp-classes2.pdf">gwt-mvp-classes_pdf</a></p>
]]></content:encoded>
			<wfw:commentRss>http://minutefforts.com/blog/?feed=rss2&#038;p=50</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
