<?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: Tips for Developing jQuery UI 1.8 Widgets</title>
	<atom:link href="http://www.erichynds.com/jquery/tips-for-developing-jquery-ui-widgets/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.erichynds.com/jquery/tips-for-developing-jquery-ui-widgets/</link>
	<description>Web Developer&#039;s Ramblings on JavaScript, jQuery, ColdFusion, MySQL, and other technologies.</description>
	<lastBuildDate>Wed, 04 Jan 2012 16:01:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Harinatha Php</title>
		<link>http://www.erichynds.com/jquery/tips-for-developing-jquery-ui-widgets/#comment-7237</link>
		<dc:creator>Harinatha Php</dc:creator>
		<pubDate>Thu, 29 Dec 2011 11:46:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.erichynds.com/?p=543#comment-7237</guid>
		<description>Nice article to start creating widgets.</description>
		<content:encoded><![CDATA[<p>Nice article to start creating widgets.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Xtol Lord</title>
		<link>http://www.erichynds.com/jquery/tips-for-developing-jquery-ui-widgets/#comment-4991</link>
		<dc:creator>Xtol Lord</dc:creator>
		<pubDate>Mon, 29 Aug 2011 12:42:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.erichynds.com/?p=543#comment-4991</guid>
		<description>hi, 

how could i create say a menu

Title

... HTML CONTENTS ...


and add an accordion to it?

I&#039;d call it 
$(&quot;#menu&quot;).menuWidget();


in the _create() function in the widget, I&#039;d add something like:

uiMenu = (uiMenu.uiMenuOne = $(&#039; and the rest of the content...&#039;))
					.addClass(&#039;menuone&#039;)
					.appendTo(fwMenu)
					.accordion({ collapsible: true });But its not working.I&#039;m I doing something wrong?I&#039;d appreciate any hint.Like add accordion or drag/drop functionalites when creating the widget components



</description>
		<content:encoded><![CDATA[<p>hi, </p>
<p>how could i create say a menu</p>
<p>Title</p>
<p>&#8230; HTML CONTENTS &#8230;</p>
<p>and add an accordion to it?</p>
<p>I&#8217;d call it <br />
$(&#8220;#menu&#8221;).menuWidget();</p>
<p>in the _create() function in the widget, I&#8217;d add something like:</p>
<p>uiMenu = (uiMenu.uiMenuOne = $(&#8216; and the rest of the content&#8230;&#8217;))<br />
					.addClass(&#8216;menuone&#8217;)<br />
					.appendTo(fwMenu)<br />
					.accordion({ collapsible: true });But its not working.I&#8217;m I doing something wrong?I&#8217;d appreciate any hint.Like add accordion or drag/drop functionalites when creating the widget components</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Younos Aboulnaga</title>
		<link>http://www.erichynds.com/jquery/tips-for-developing-jquery-ui-widgets/#comment-4319</link>
		<dc:creator>Younos Aboulnaga</dc:creator>
		<pubDate>Tue, 14 Dec 2010 13:19:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.erichynds.com/?p=543#comment-4319</guid>
		<description>Great article.. really helpful. I want to add a little warning about how _trigger() handles names of the custom events : AFTER ADDING THE PREFIX THAT EVERYBODY TALKS ABOUT, IT CALLS toLowerCase().. i don&#039;t know the logic behind this, but what matters it, when you bind a function to this custom event, make sure to write all the name in lowercase, no matter what the real names are.</description>
		<content:encoded><![CDATA[<p>Great article.. really helpful. I want to add a little warning about how _trigger() handles names of the custom events : AFTER ADDING THE PREFIX THAT EVERYBODY TALKS ABOUT, IT CALLS toLowerCase().. i don&#8217;t know the logic behind this, but what matters it, when you bind a function to this custom event, make sure to write all the name in lowercase, no matter what the real names are.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://www.erichynds.com/jquery/tips-for-developing-jquery-ui-widgets/#comment-4037</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Tue, 21 Sep 2010 13:38:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.erichynds.com/?p=543#comment-4037</guid>
		<description>do it up</description>
		<content:encoded><![CDATA[<p>do it up</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://www.erichynds.com/jquery/tips-for-developing-jquery-ui-widgets/#comment-4036</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Tue, 21 Sep 2010 02:02:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.erichynds.com/?p=543#comment-4036</guid>
		<description>Can I use parts of this for a school project? </description>
		<content:encoded><![CDATA[<p>Can I use parts of this for a school project?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ehynds</title>
		<link>http://www.erichynds.com/jquery/tips-for-developing-jquery-ui-widgets/#comment-3526</link>
		<dc:creator>ehynds</dc:creator>
		<pubDate>Tue, 18 May 2010 05:47:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.erichynds.com/?p=543#comment-3526</guid>
		<description>Not exactly sure what you&#039;re doing, but it sounds like you&#039;ve got it.  I&#039;d say the best approach is to build the buttons into your widget if possible, so the developer does not need to worry about it at all.&lt;br&gt;&lt;br&gt;I wouldn&#039;t provide an option to specify an ID of some other element; that immediately limits you to one instance of the widget on the page, and requires that all buttons have an ID.  An API where you can provide a selector to access certain elements is much more flexible.</description>
		<content:encoded><![CDATA[<p>Not exactly sure what you&#39;re doing, but it sounds like you&#39;ve got it.  I&#39;d say the best approach is to build the buttons into your widget if possible, so the developer does not need to worry about it at all.</p>
<p>I wouldn&#39;t provide an option to specify an ID of some other element; that immediately limits you to one instance of the widget on the page, and requires that all buttons have an ID.  An API where you can provide a selector to access certain elements is much more flexible.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ehynds</title>
		<link>http://www.erichynds.com/jquery/tips-for-developing-jquery-ui-widgets/#comment-3389</link>
		<dc:creator>ehynds</dc:creator>
		<pubDate>Tue, 18 May 2010 01:47:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.erichynds.com/?p=543#comment-3389</guid>
		<description>Not exactly sure what you&#039;re doing, but it sounds like you&#039;ve got it.  I&#039;d say the best approach is to build the buttons into your widget if possible, so the developer does not need to worry about it at all.&lt;br&gt;&lt;br&gt;I wouldn&#039;t provide an option to specify an ID of some other element; that immediately limits you to one instance of the widget on the page, and requires that all buttons have an ID.  An API where you can provide a selector to access certain elements is much more flexible.</description>
		<content:encoded><![CDATA[<p>Not exactly sure what you&#39;re doing, but it sounds like you&#39;ve got it.  I&#39;d say the best approach is to build the buttons into your widget if possible, so the developer does not need to worry about it at all.</p>
<p>I wouldn&#39;t provide an option to specify an ID of some other element; that immediately limits you to one instance of the widget on the page, and requires that all buttons have an ID.  An API where you can provide a selector to access certain elements is much more flexible.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://www.erichynds.com/jquery/tips-for-developing-jquery-ui-widgets/#comment-4014</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Mon, 10 May 2010 14:35:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.erichynds.com/?p=543#comment-4014</guid>
		<description>test</description>
		<content:encoded><![CDATA[<p>test</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael M</title>
		<link>http://www.erichynds.com/jquery/tips-for-developing-jquery-ui-widgets/#comment-3366</link>
		<dc:creator>Michael M</dc:creator>
		<pubDate>Sun, 09 May 2010 21:06:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.erichynds.com/?p=543#comment-3366</guid>
		<description>Thanks very much for such a clear explanation - the new approach with Widgets in UI 1.8 is finally making sense of Plug-In development.

One question for you all - what approach would you use to have the Widget react to external events, say a click on a previous or next button, without having to explictly hook up the event in page markup, and call in to the Widget instance? 

I hope I am making sense here - it would be neater for me to specify the button IDs in the Widget options, and have it bind to their click events, and act accordingly, without the developer hand coding the bind.</description>
		<content:encoded><![CDATA[<p>Thanks very much for such a clear explanation &#8211; the new approach with Widgets in UI 1.8 is finally making sense of Plug-In development.</p>
<p>One question for you all &#8211; what approach would you use to have the Widget react to external events, say a click on a previous or next button, without having to explictly hook up the event in page markup, and call in to the Widget instance? </p>
<p>I hope I am making sense here &#8211; it would be neater for me to specify the button IDs in the Widget options, and have it bind to their click events, and act accordingly, without the developer hand coding the bind.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael M</title>
		<link>http://www.erichynds.com/jquery/tips-for-developing-jquery-ui-widgets/#comment-3904</link>
		<dc:creator>Michael M</dc:creator>
		<pubDate>Sun, 09 May 2010 21:06:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.erichynds.com/?p=543#comment-3904</guid>
		<description>Thanks very much for such a clear explanation - the new approach with Widgets in UI 1.8 is finally making sense of Plug-In development.

One question for you all - what approach would you use to have the Widget react to external events, say a click on a previous or next button, without having to explictly hook up the event in page markup, and call in to the Widget instance? 

I hope I am making sense here - it would be neater for me to specify the button IDs in the Widget options, and have it bind to their click events, and act accordingly, without the developer hand coding the bind.</description>
		<content:encoded><![CDATA[<p>Thanks very much for such a clear explanation &#8211; the new approach with Widgets in UI 1.8 is finally making sense of Plug-In development.</p>
<p>One question for you all &#8211; what approach would you use to have the Widget react to external events, say a click on a previous or next button, without having to explictly hook up the event in page markup, and call in to the Widget instance? </p>
<p>I hope I am making sense here &#8211; it would be neater for me to specify the button IDs in the Widget options, and have it bind to their click events, and act accordingly, without the developer hand coding the bind.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

