<?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: APExt JS &#8211; Ext JS 3.1 &amp; APEX 4.0</title>
	<atom:link href="http://application-express-blog.e-dba.com/?feed=rss2&#038;p=987" rel="self" type="application/rss+xml" />
	<link>http://application-express-blog.e-dba.com/?p=987</link>
	<description>Increasing Development Productivity through Integration!</description>
	<lastBuildDate>Sat, 04 Sep 2010 07:42:15 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: mnolan</title>
		<link>http://application-express-blog.e-dba.com/?p=987&#038;cpage=1#comment-12</link>
		<dc:creator>mnolan</dc:creator>
		<pubDate>Tue, 05 Jan 2010 14:34:09 +0000</pubDate>
		<guid isPermaLink="false">http://application-express-blog.e-dba.com/?p=987#comment-12</guid>
		<description>Hi Patrick

Thanks for getting in touch, much appreciated!

I was looking at 4.0 and some of the things that were defined in the apex.jQuery.ready events, i.e. allowing text areas to be resized, cascading LOV support, dynamic actions etc. Essentially I&#039;d like to use the config defined in APEX for these things but use an Ext equivalent (I&#039;ll query the APEX data dictionary to work out what needs implementing thats why I don&#039;t want to be simply told not to use any of the features).

Already in 3.2 we are providing this sort of funcionality with an Ext.onReady equivalent. I want to ensure that no jQuery event handlers are applied on items that I&#039;ve enabled Ext ones on. So it would be nice if we could have a page template flag that excludes jQuery.ready, or disables particular types of new features in 4.0.

If you need to discuss further can you send an email to apex-sig@e-dba.com

Cheers
Matt</description>
		<content:encoded><![CDATA[<p>Hi Patrick</p>
<p>Thanks for getting in touch, much appreciated!</p>
<p>I was looking at 4.0 and some of the things that were defined in the apex.jQuery.ready events, i.e. allowing text areas to be resized, cascading LOV support, dynamic actions etc. Essentially I&#8217;d like to use the config defined in APEX for these things but use an Ext equivalent (I&#8217;ll query the APEX data dictionary to work out what needs implementing thats why I don&#8217;t want to be simply told not to use any of the features).</p>
<p>Already in 3.2 we are providing this sort of funcionality with an Ext.onReady equivalent. I want to ensure that no jQuery event handlers are applied on items that I&#8217;ve enabled Ext ones on. So it would be nice if we could have a page template flag that excludes jQuery.ready, or disables particular types of new features in 4.0.</p>
<p>If you need to discuss further can you send an email to <a href="mailto:apex-sig@e-dba.com">apex-sig@e-dba.com</a></p>
<p>Cheers<br />
Matt</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: patrickwolf</title>
		<link>http://application-express-blog.e-dba.com/?p=987&#038;cpage=1#comment-11</link>
		<dc:creator>patrickwolf</dc:creator>
		<pubDate>Mon, 21 Dec 2009 18:17:55 +0000</pubDate>
		<guid isPermaLink="false">http://application-express-blog.e-dba.com/?p=987#comment-11</guid>
		<description>Hi,

I&#039;m not sure why the use of jQuery.ready or apex.jQuery.ready is going to influence your existing use of it? It&#039;s an event handler and can be called multiple times on a page to add a function to the ready event. Can you give me more details why you think you will have problems?

Thanks
Patrick</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>I&#8217;m not sure why the use of jQuery.ready or apex.jQuery.ready is going to influence your existing use of it? It&#8217;s an event handler and can be called multiple times on a page to add a function to the ready event. Can you give me more details why you think you will have problems?</p>
<p>Thanks<br />
Patrick</p>
]]></content:encoded>
	</item>
</channel>
</rss>
