<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" media="screen" href="/styles/xslt/rss.xslt"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:media="http://search.yahoo.com/mrss/" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:c9="http://channel9.msdn.com">
<channel>
	<title>Comment Feed for Channel 9 - Client-side Model-View-Presenter</title>
	<atom:link rel="self" type="application/rss+xml" href="http://channel9.msdn.com/Blogs/AndrewDavey/Client-side-Model-View-Presenter/RSS"></atom:link>
	<image>
		<url>http://ecn.channel9.msdn.com/o9/previewImages/100/257882_100x75.jpg</url>
		<title>Channel 9 - Client-side Model-View-Presenter</title>
		<link></link>
	</image>
	<description>
The model-view-presenter pattern is a very powerful way to manage user interaction. It seems popular to use it on the server-side when creating HTML, but why not use it client-side instead?
Our computers are powerful enough to run fairly complex JavaScript. Why burden the server with having to render the page contents?

In this screencast I use 
Script# to compile a C# project into JavaScript. This project contains the Model, View and Presenter logic.
The HTML page then uses the generated JavaScript.

There is a simple REST service on the server that returns data which is called by the Model. No HTML generation occurs on the server.

Download the source code. You must have
Script# installed as well.
 
</description>
	<link></link>
	<language>en</language>
	<pubDate>Tue, 21 May 2013 22:38:21 GMT</pubDate>
	<lastBuildDate>Tue, 21 May 2013 22:38:21 GMT</lastBuildDate>
	<generator>Rev9</generator>
	<item>
		<title>Re: Client-side Model-View-Presenter</title>
		<description>
			<![CDATA[Thanks for the screencast, i'm going to take a closer look into Script#.<br>
<br>
Have you had a look at <a href="http://www.codeplex.com/ProMesh/">ProMesh.Net</a>?<br>
<br>
I realise ProMesh is a server side MVC framework but still thought you might be interested in it...<p>posted by Cyonix</p>]]>
		</description>
		<link>http://channel9.msdn.com/Blogs/AndrewDavey/Client-side-Model-View-Presenter#c633266596180000000</link>
		<pubDate>Sat, 29 Sep 2007 10:46:58 GMT</pubDate>
		<guid isPermaLink="true">http://channel9.msdn.com/Blogs/AndrewDavey/Client-side-Model-View-Presenter#c633266596180000000</guid>
		<dc:creator>Cyonix</dc:creator>
	</item>
	<item>
		<title>Re: Client-side Model-View-Presenter</title>
		<description>
			<![CDATA[Seeing as client-side MVP is viable, the next step would be create a framework to reduce some of the boiler-plate coding required. For example, the View class that basically maps to and from DOM elements could probably be code generated.<br>
<br>
Thanks for the link to ProMesh.NET, I like the use of attributes making the whole process much more declarative. I'll certainly be considering similar approachs when expanding my client-side MVP framework.<p>posted by Andrew Davey</p>]]>
		</description>
		<link>http://channel9.msdn.com/Blogs/AndrewDavey/Client-side-Model-View-Presenter#c633266745980000000</link>
		<pubDate>Sat, 29 Sep 2007 14:56:38 GMT</pubDate>
		<guid isPermaLink="true">http://channel9.msdn.com/Blogs/AndrewDavey/Client-side-Model-View-Presenter#c633266745980000000</guid>
		<dc:creator>Andrew Davey</dc:creator>
	</item>
	<item>
		<title>Re: Client-side Model-View-Presenter</title>
		<description>
			<![CDATA[Nice job Andrew! <p>posted by codewiz</p>]]>
		</description>
		<link>http://channel9.msdn.com/Blogs/AndrewDavey/Client-side-Model-View-Presenter#c633266886480000000</link>
		<pubDate>Sat, 29 Sep 2007 18:50:48 GMT</pubDate>
		<guid isPermaLink="true">http://channel9.msdn.com/Blogs/AndrewDavey/Client-side-Model-View-Presenter#c633266886480000000</guid>
		<dc:creator>codewiz</dc:creator>
	</item>
	<item>
		<title>Re: Client-side Model-View-Presenter</title>
		<description>
			<![CDATA[
<p>So I reckon phase two is to use my tier-splitting macro to enable certain model methods to be decorated with [RunAtServer] attributes.<br>
The macro would do all the plumbing to call the server and execute the model there. This would allow a totally seemless Model class to be written. With the client part&nbsp;ending up in JavaScript and the server part being C#.</p>
<p>posted by Andrew Davey</p>]]>
		</description>
		<link>http://channel9.msdn.com/Blogs/AndrewDavey/Client-side-Model-View-Presenter#c633266903010000000</link>
		<pubDate>Sat, 29 Sep 2007 19:18:21 GMT</pubDate>
		<guid isPermaLink="true">http://channel9.msdn.com/Blogs/AndrewDavey/Client-side-Model-View-Presenter#c633266903010000000</guid>
		<dc:creator>Andrew Davey</dc:creator>
	</item>
	<item>
		<title>Re: Client-side Model-View-Presenter</title>
		<description>
			<![CDATA[Andrew:<br>
<br>
The last post is from September.... just wanted to know how did you do with this design?
<br>
You mentioned you was doing a project, how did it go?<br>
Is there an updated version of the framework?<br>
<br>
Thanks<br>
<br>
<p>posted by mamadero</p>]]>
		</description>
		<link>http://channel9.msdn.com/Blogs/AndrewDavey/Client-side-Model-View-Presenter#c633369876200000000</link>
		<pubDate>Sat, 26 Jan 2008 23:40:20 GMT</pubDate>
		<guid isPermaLink="true">http://channel9.msdn.com/Blogs/AndrewDavey/Client-side-Model-View-Presenter#c633369876200000000</guid>
		<dc:creator>mamadero</dc:creator>
	</item>
</channel>
</rss>