<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: XAJAX &amp; Smarty</title>
	<atom:link href="http://blogs.linux.ie/aj/2005/12/31/xajax-smarty/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.linux.ie/aj/2005/12/31/xajax-smarty/</link>
	<description>babblings!</description>
	<lastBuildDate>Fri, 09 Jun 2006 00:48:42 +0100</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.4</generator>
	<item>
		<title>By: Robert Ewald</title>
		<link>http://blogs.linux.ie/aj/2005/12/31/xajax-smarty/comment-page-1/#comment-205</link>
		<dc:creator>Robert Ewald</dc:creator>
		<pubDate>Wed, 01 Feb 2006 10:07:50 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.linux.ie/aj/2005/12/31/xajax-smarty/#comment-205</guid>
		<description>Hi there,

I was looking for a shorter way to integrate xajax &amp; smarty and that&#039;s what I ended up with.
I use this similarly to popup_init/popup and at the moment it works quite well.
The code is cut but you can still get the idea. So what do you think of it?

(Actually instead of inheritance it should be aggregation since multiple inheritance is not an option.)

&lt;code&gt;
Smarty();
		$this-&gt;xajax =&amp; new xajax( $sRequestURI, $sWrapperPrefix, $sEncoding, $bDebug );
	}
	
	function display( $resource_name, $cache_id=null, $compile_id=null ) {
		$this-&gt;xajax-&gt;processRequests( );
		parent::display( $resource_name, $cache_id, $compile_id );
	}
}

?&gt;
&lt;/code&gt;

&lt;code&gt;
xajax-&gt;getJavascript( $sJsURI, $sJsFile, $sJsFullFilename ) );
}
?&gt;
&lt;/code&gt;

&lt;code&gt;
 $value) {
		switch( $key ) {
			case &#039;onchange&#039; : case &#039;onclick&#039; : case &#039;onkeydown&#039; :
			case &#039;onkeyup&#039; : case &#039;onsubmit&#039; : case &#039;onfocus&#039; :
				$ret .= &#039; &#039;.$key.&#039;=&quot;&#039;.$value.&#039;(this);&quot;&#039;;
				break;
		}
	}
	return( $ret );
}
?&gt;
&lt;/code&gt;</description>
		<content:encoded><![CDATA[<p>Hi there,</p>
<p>I was looking for a shorter way to integrate xajax &amp; smarty and that&#8217;s what I ended up with.<br />
I use this similarly to popup_init/popup and at the moment it works quite well.<br />
The code is cut but you can still get the idea. So what do you think of it?</p>
<p>(Actually instead of inheritance it should be aggregation since multiple inheritance is not an option.)</p>
<p><code><br />
Smarty();<br />
		$this-&gt;xajax =&amp; new xajax( $sRequestURI, $sWrapperPrefix, $sEncoding, $bDebug );<br />
	}</p>
<p>	function display( $resource_name, $cache_id=null, $compile_id=null ) {<br />
		$this-&gt;xajax-&gt;processRequests( );<br />
		parent::display( $resource_name, $cache_id, $compile_id );<br />
	}<br />
}</p>
<p>?&gt;<br />
</code></p>
<p><code><br />
xajax-&gt;getJavascript( $sJsURI, $sJsFile, $sJsFullFilename ) );<br />
}<br />
?&gt;<br />
</code></p>
<p><code><br />
 $value) {<br />
		switch( $key ) {<br />
			case 'onchange' : case 'onclick' : case 'onkeydown' :<br />
			case 'onkeyup' : case 'onsubmit' : case 'onfocus' :<br />
				$ret .= ' '.$key.'="'.$value.'(this);"';<br />
				break;<br />
		}<br />
	}<br />
	return( $ret );<br />
}<br />
?&gt;<br />
</code></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aj</title>
		<link>http://blogs.linux.ie/aj/2005/12/31/xajax-smarty/comment-page-1/#comment-204</link>
		<dc:creator>Aj</dc:creator>
		<pubDate>Mon, 23 Jan 2006 00:46:03 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.linux.ie/aj/2005/12/31/xajax-smarty/#comment-204</guid>
		<description>Yeah it is nice, but it would be nice to have logic for handeling the back and forward mouse presses built into it. That way I would not have to rely on the Really Simple History Framework (O&#039;Reilly)</description>
		<content:encoded><![CDATA[<p>Yeah it is nice, but it would be nice to have logic for handeling the back and forward mouse presses built into it. That way I would not have to rely on the Really Simple History Framework (O&#8217;Reilly)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel P Dykes, Rogue Connect</title>
		<link>http://blogs.linux.ie/aj/2005/12/31/xajax-smarty/comment-page-1/#comment-203</link>
		<dc:creator>Daniel P Dykes, Rogue Connect</dc:creator>
		<pubDate>Sun, 22 Jan 2006 23:00:38 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.linux.ie/aj/2005/12/31/xajax-smarty/#comment-203</guid>
		<description>I&#039;ve recently begun to use Xajax in a very similar fashion, using onblur to do live validation of fields in Rogue Connect&#039;s application process. I have to say, it works an absolute treat. I haven&#039;t had to do any form of Javascript (bar for the call xajax function) and all my validation is in PHP.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve recently begun to use Xajax in a very similar fashion, using onblur to do live validation of fields in Rogue Connect&#8217;s application process. I have to say, it works an absolute treat. I haven&#8217;t had to do any form of Javascript (bar for the call xajax function) and all my validation is in PHP.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

