<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments for deVpartment</title>
	<atom:link href="http://www.devpartment.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.devpartment.com</link>
	<description>Code and much much more</description>
	<pubDate>Fri, 21 Nov 2008 03:14:40 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>Comment on JS content rotator by craig</title>
		<link>http://www.devpartment.com/posts/js-content-rotator/#comment-3300</link>
		<dc:creator>craig</dc:creator>
		<pubDate>Wed, 20 Aug 2008 00:45:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.devpartment.com/posts/js-content-rotator/#comment-3300</guid>
		<description>I've tried to get this script to work with mootools 1.2 but I'm having problems, can you help?</description>
		<content:encoded><![CDATA[<p>I&#8217;ve tried to get this script to work with mootools 1.2 but I&#8217;m having problems, can you help?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Again mootools, woow! by Again mootools, woow! [ DeVpartment ]</title>
		<link>http://www.devpartment.com/posts/again-mootools-woow/#comment-390</link>
		<dc:creator>Again mootools, woow! [ DeVpartment ]</dc:creator>
		<pubDate>Sun, 08 Jun 2008 16:57:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.devpartment.com/posts/again-mootools-woow/#comment-390</guid>
		<description>[...] 19th 2007 10:59am  [-] From: devpartment.com  [...]</description>
		<content:encoded><![CDATA[<p>[...] 19th 2007 10:59am  [-] From: devpartment.com  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on mootools + PHP = mooHP by norman784</title>
		<link>http://www.devpartment.com/posts/mootools-php-moohp/#comment-130</link>
		<dc:creator>norman784</dc:creator>
		<pubDate>Wed, 26 Mar 2008 13:55:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.devpartment.com/posts/mootools-php-moohp/#comment-130</guid>
		<description>I think it will be more good if manipulate the js mootool code with PHP like xajax. It would be nice. And dont try to use this kind of programming, try the MVC Model and less hardcoding, stay looking the other frameworks like codeigniter, cake, symphony, etc</description>
		<content:encoded><![CDATA[<p>I think it will be more good if manipulate the js mootool code with PHP like xajax. It would be nice. And dont try to use this kind of programming, try the MVC Model and less hardcoding, stay looking the other frameworks like codeigniter, cake, symphony, etc</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on JS content rotator by David</title>
		<link>http://www.devpartment.com/posts/js-content-rotator/#comment-123</link>
		<dc:creator>David</dc:creator>
		<pubDate>Mon, 17 Mar 2008 21:14:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.devpartment.com/posts/js-content-rotator/#comment-123</guid>
		<description>this is script is a good example of what I would like to do.  I was wondering if it is possible to do the same things this script does except have it only rotate through the content "set" once?  

Thanks</description>
		<content:encoded><![CDATA[<p>this is script is a good example of what I would like to do.  I was wondering if it is possible to do the same things this script does except have it only rotate through the content &#8220;set&#8221; once?  </p>
<p>Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on mootools + PHP = mooHP by Chris</title>
		<link>http://www.devpartment.com/posts/mootools-php-moohp/#comment-62</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Mon, 28 Jan 2008 00:45:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.devpartment.com/posts/mootools-php-moohp/#comment-62</guid>
		<description>Also see http://meta20.net/phpQuery which is a jQuery port.</description>
		<content:encoded><![CDATA[<p>Also see <a href="http://meta20.net/phpQuery" rel="nofollow">http://meta20.net/phpQuery</a> which is a jQuery port.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on mootools + PHP = mooHP by Chris</title>
		<link>http://www.devpartment.com/posts/mootools-php-moohp/#comment-61</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Mon, 28 Jan 2008 00:36:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.devpartment.com/posts/mootools-php-moohp/#comment-61</guid>
		<description>Haha, really amusing to read the comments of all the software architects ;). Nevertheless mooHP is exactly what I was searching for. An easy tool to work on the DOM in PHP. Not for composing a website, but for unittesting html. Great stuff :). Don't let these guys discourage you. I would be more than happy to see a permanent project spin-off from your draft. Please email me if there are updates.</description>
		<content:encoded><![CDATA[<p>Haha, really amusing to read the comments of all the software architects ;). Nevertheless mooHP is exactly what I was searching for. An easy tool to work on the DOM in PHP. Not for composing a website, but for unittesting html. Great stuff :). Don&#8217;t let these guys discourage you. I would be more than happy to see a permanent project spin-off from your draft. Please email me if there are updates.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on mootools + PHP = mooHP by Christian</title>
		<link>http://www.devpartment.com/posts/mootools-php-moohp/#comment-9</link>
		<dc:creator>Christian</dc:creator>
		<pubDate>Fri, 02 Nov 2007 12:19:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.devpartment.com/posts/mootools-php-moohp/#comment-9</guid>
		<description>Well I must disagree with this comments. If you take it from other side,  you can separate the business from presentation logic  by creating Template and putting ID's on the elements that need to have content, and than trough mooHP assign  the content you want to the elements trough the ID's.  It's simply manipulates the DOM of the template.</description>
		<content:encoded><![CDATA[<p>Well I must disagree with this comments. If you take it from other side,  you can separate the business from presentation logic  by creating Template and putting ID&#8217;s on the elements that need to have content, and than trough mooHP assign  the content you want to the elements trough the ID&#8217;s.  It&#8217;s simply manipulates the DOM of the template.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on mootools + PHP = mooHP by Bastian Buch</title>
		<link>http://www.devpartment.com/posts/mootools-php-moohp/#comment-8</link>
		<dc:creator>Bastian Buch</dc:creator>
		<pubDate>Thu, 01 Nov 2007 08:21:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.devpartment.com/posts/mootools-php-moohp/#comment-8</guid>
		<description>Oh no! For me, to discover this blog post was kind of horrible. Since I am working as a Software Architect in a company that handles large data sets with PHP i am struggling to convince my colleagues to develop our software in a way that makes code maintainable. We are using a PEAR-Package called Quickform... And this as terrible as the code above. This war of leading people to see software (especially in the web (http) world) as an organized structure where every part has its own responsibilities and where transitions between those modules follow a well defined communication and interface model, is a hard one because it seems that this is not just a change in understanding coding but also a change in mind and the programmers personality :). I hope that someday PHP will provide ways to code in ways JEE does. The lack of architectural foundations of PHP leads us to migrate some of our applications to the JEE world. 

... I think the times of coding that ugly way should be over, especially in times where web applications become more complex (AJAX...).</description>
		<content:encoded><![CDATA[<p>Oh no! For me, to discover this blog post was kind of horrible. Since I am working as a Software Architect in a company that handles large data sets with PHP i am struggling to convince my colleagues to develop our software in a way that makes code maintainable. We are using a PEAR-Package called Quickform&#8230; And this as terrible as the code above. This war of leading people to see software (especially in the web (http) world) as an organized structure where every part has its own responsibilities and where transitions between those modules follow a well defined communication and interface model, is a hard one because it seems that this is not just a change in understanding coding but also a change in mind and the programmers personality :). I hope that someday PHP will provide ways to code in ways JEE does. The lack of architectural foundations of PHP leads us to migrate some of our applications to the JEE world. </p>
<p>&#8230; I think the times of coding that ugly way should be over, especially in times where web applications become more complex (AJAX&#8230;).</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on mootools + PHP = mooHP by Jon G.</title>
		<link>http://www.devpartment.com/posts/mootools-php-moohp/#comment-5</link>
		<dc:creator>Jon G.</dc:creator>
		<pubDate>Wed, 31 Oct 2007 19:43:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.devpartment.com/posts/mootools-php-moohp/#comment-5</guid>
		<description>This is so wrong on so many levels, I don't even know where to begin.

By going this route, you've LOCKED your application logic into the presentation layer.  Maintenance would be a nightmare.  Furthermore, it isn't obvious or clear what in the hell is going on in your code nor why.</description>
		<content:encoded><![CDATA[<p>This is so wrong on so many levels, I don&#8217;t even know where to begin.</p>
<p>By going this route, you&#8217;ve LOCKED your application logic into the presentation layer.  Maintenance would be a nightmare.  Furthermore, it isn&#8217;t obvious or clear what in the hell is going on in your code nor why.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on mootools + PHP = mooHP by Drew</title>
		<link>http://www.devpartment.com/posts/mootools-php-moohp/#comment-3</link>
		<dc:creator>Drew</dc:creator>
		<pubDate>Wed, 31 Oct 2007 16:53:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.devpartment.com/posts/mootools-php-moohp/#comment-3</guid>
		<description>This whole idea makes me cry. This goes against everything that any decent programmer would look to do. 

The top of that list would be the separation of logic domains, indicating, let you html be formatted like HTML and let your code be code, but keep them apart.

I weep for the designer that has to make changes to this document. Hell, I weep for the coder who has to modify the logic. 

My number one rule with producing HTML, is that as little of it should be done programmatically as possible. There are of course exceptions that should be kept to a minimum, but for the most part, static HTML should represented as static HTML. Why abstract it away from that? It is just confusing for everyone involved.

The DOM is to HTML as XPATH is to XML. It provides a great way to represent an already existing document and to query and target within it. Building with it because a conceptual and maintenance nightmare. This is basically formalized spaghetti code.

I don't want to sound as harsh as I have, but please, let HTML do what it does well. It really is a great way to conceptualize a document. I promise.</description>
		<content:encoded><![CDATA[<p>This whole idea makes me cry. This goes against everything that any decent programmer would look to do. </p>
<p>The top of that list would be the separation of logic domains, indicating, let you html be formatted like HTML and let your code be code, but keep them apart.</p>
<p>I weep for the designer that has to make changes to this document. Hell, I weep for the coder who has to modify the logic. </p>
<p>My number one rule with producing HTML, is that as little of it should be done programmatically as possible. There are of course exceptions that should be kept to a minimum, but for the most part, static HTML should represented as static HTML. Why abstract it away from that? It is just confusing for everyone involved.</p>
<p>The DOM is to HTML as XPATH is to XML. It provides a great way to represent an already existing document and to query and target within it. Building with it because a conceptual and maintenance nightmare. This is basically formalized spaghetti code.</p>
<p>I don&#8217;t want to sound as harsh as I have, but please, let HTML do what it does well. It really is a great way to conceptualize a document. I promise.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
