<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" 
	xmlns:dc="http://purl.org/dc/elements/1.1/" 
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" 
	xmlns:admin="http://webns.net/mvcb/" 
	xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/" 
	xmlns:atom="http://www.w3.org/2005/Atom">
	
	<channel>
	
		<title>Extensions, Extensions, Extensions</title>
		<link>http://www.sencha.com/blog/extensions-extensions-extensions</link>
		<description>Extensions provide developers with valuable features beyond those that ship in Sencha&#8217;s frameworks, and are a very important part of the Sencha platform. At Sencha, we are investing to improve the ecosystem of extensions on our platform and I wanted to share an early look at our progress.</description>
		<dc:language>en-us</dc:language>
		<dc:creator>ted.patrick@sencha.com</dc:creator>
		<dc:rights>Copyright 2012</dc:rights>
		<dc:date>2012-07-24T16:38:17+00:00</dc:date>
		<admin:generatorAgent rdf:resource="http://expressionengine.com/" />
		<atom:link href="http://www.sencha.com/blog/comments-rss/11787" rel="self" type="application/rss+xml" />
  
		
  
		<item>
      <title>Comment by Azhagu Rajan</title>
      <description>Hi We are looking for Sencha Touch Developer position in Newt global. 
The position is in INDIA If you are interested please share your updated profile to sazhagu@newtglobal.com.</description>
      <content:encoded><![CDATA[<p>Hi We are looking for Sencha Touch Developer position in Newt global. <br />
The position is in INDIA If you are interested please share your updated profile to sazhagu@newtglobal.com.</p>]]></content:encoded>
      <pubDate>Tue, 11 Sep 2012 12:48 GMT</pubDate>
      <guid isPermaLink="false">http://www.sencha.com/blog//extensions-extensions-extensions#id:32147#date:12:48</guid>
    </item>
  
		<item>
      <title>Comment by Allenbrooch</title>
      <description>Is Ext JS 4  OpenAjax Specification conformant?</description>
      <content:encoded><![CDATA[<p>Is Ext JS 4  OpenAjax Specification conformant?</p>]]></content:encoded>
      <pubDate>Wed, 29 Aug 2012 03:36 GMT</pubDate>
      <guid isPermaLink="false">http://www.sencha.com/blog//extensions-extensions-extensions#id:32095#date:03:36</guid>
    </item>
  
		<item>
      <title>Comment by Mike Griffin</title>
      <description>We would like to see a Sencha market place for software and SaaS applications built around Sencha. We have an SaaS Dashboard product that has a Wonderful Widget Wonderland of Ext JS 4.1 widgets! We&#8217;re doing fine signing up users with Adwords but it is a bit expensive. Having a place to feature stuff like ours on the Sencha site would be awesome! http://www.otusanalytics.com/widgets/DashboardSoftwareWidgets.html</description>
      <content:encoded><![CDATA[<p>We would like to see a Sencha market place for software and SaaS applications built around Sencha. We have an SaaS Dashboard product that has a Wonderful Widget Wonderland of Ext JS 4.1 widgets! We&#8217;re doing fine signing up users with Adwords but it is a bit expensive. Having a place to feature stuff like ours on the Sencha site would be awesome! <a href="http://www.otusanalytics.com/widgets/DashboardSoftwareWidgets.html">http://www.otusanalytics.com/widgets/DashboardSoftwareWidgets.html</a></p>]]></content:encoded>
      <pubDate>Thu, 16 Aug 2012 13:17 GMT</pubDate>
      <guid isPermaLink="false">http://www.sencha.com/blog//extensions-extensions-extensions#id:32035#date:13:17</guid>
    </item>
  
		<item>
      <title>Comment by EthanZ</title>
      <description>Congrats, ST2 is a fantastic framework/library to build web/mobile applications. Looking forward good extensions and like to contribute.</description>
      <content:encoded><![CDATA[<p>Congrats, ST2 is a fantastic framework/library to build web/mobile applications. Looking forward good extensions and like to contribute.</p>]]></content:encoded>
      <pubDate>Tue, 07 Aug 2012 02:19 GMT</pubDate>
      <guid isPermaLink="false">http://www.sencha.com/blog//extensions-extensions-extensions#id:31952#date:02:19</guid>
    </item>
  
		<item>
      <title>Comment by Ted Patrick</title>
      <description>Adam and Milan,

On Market we will be making Ext/Touch versioning very specific to subversion releases. Allowing extensions to show subversion level compatibility is important and will help developers choose compatible extensions.

Extension compatibility today is tightly coupled to the ExtJS/Touch framework apis and as the apis change, extensions must be updated to remain compatible. I feel like we should define an extension interface within the framework apis that will not change in time. This would give extensions that used this interface a longer lifespan and allow for better extensions to be written. In my experience, 80% of the problem is knowing what to use and what to avoid. Provided that an extension interface is well defined and documented, Sencha would have the ability to change the internal implementation and extensions would remain compatible over a longer timeframe.</description>
      <content:encoded><![CDATA[<p>Adam and Milan,</p>

<p>On Market we will be making Ext/Touch versioning very specific to subversion releases. Allowing extensions to show subversion level compatibility is important and will help developers choose compatible extensions.</p>

<p>Extension compatibility today is tightly coupled to the ExtJS/Touch framework apis and as the apis change, extensions must be updated to remain compatible. I feel like we should define an extension interface within the framework apis that will not change in time. This would give extensions that used this interface a longer lifespan and allow for better extensions to be written. In my experience, 80% of the problem is knowing what to use and what to avoid. Provided that an extension interface is well defined and documented, Sencha would have the ability to change the internal implementation and extensions would remain compatible over a longer timeframe.</p>]]></content:encoded>
      <pubDate>Tue, 31 Jul 2012 11:33 GMT</pubDate>
      <guid isPermaLink="false">http://www.sencha.com/blog//extensions-extensions-extensions#id:31906#date:11:33</guid>
    </item>
  
		<item>
      <title>Comment by Nick Vidal</title>
      <description>It would be interesting if Sencha Market could mimic the plugin/module ecosystem nurtured at open&#45;source projects like Wordpress or Drupal. Issue queues and git integration to promote collaboration would greatly benefit everyone.</description>
      <content:encoded><![CDATA[<p>It would be interesting if Sencha Market could mimic the plugin/module ecosystem nurtured at open-source projects like Wordpress or Drupal. Issue queues and git integration to promote collaboration would greatly benefit everyone.</p>]]></content:encoded>
      <pubDate>Mon, 30 Jul 2012 19:29 GMT</pubDate>
      <guid isPermaLink="false">http://www.sencha.com/blog//extensions-extensions-extensions#id:31899#date:19:29</guid>
    </item>
  
		<item>
      <title>Comment by Milan</title>
      <description>@Ted Patrick &#45; I think you completely missed Adam&#8217;s point. He didn&#8217;t mention license anywhere in his question. He was worried that one day ExtJS or Touch would be updated to version 5 (just for example) and extensions will not follow. Then whoever used that extension will have problem and &#8220;trilema&#8221;:
&#45; Update extension&#8217;s code yourself (tedious and time consuming)
&#45; Never update to newer Sencha framework
&#45; Abandon used extension and rewrite your app to use newer Sencha framework (tedious and time consuming)

Have Sencha put any thought into this and are there any guidelines?</description>
      <content:encoded><![CDATA[<p>@Ted Patrick - I think you completely missed Adam&#8217;s point. He didn&#8217;t mention license anywhere in his question. He was worried that one day ExtJS or Touch would be updated to version 5 (just for example) and extensions will not follow. Then whoever used that extension will have problem and &#8220;trilema&#8221;:<br />
- Update extension&#8217;s code yourself (tedious and time consuming)<br />
- Never update to newer Sencha framework<br />
- Abandon used extension and rewrite your app to use newer Sencha framework (tedious and time consuming)</p>

<p>Have Sencha put any thought into this and are there any guidelines?</p>]]></content:encoded>
      <pubDate>Fri, 27 Jul 2012 17:29 GMT</pubDate>
      <guid isPermaLink="false">http://www.sencha.com/blog//extensions-extensions-extensions#id:31897#date:17:29</guid>
    </item>
  
		<item>
      <title>Comment by Sharad Chandra</title>
      <description>How to append url in proxy. 
There are two variable strUserId and strPassword.where strUserId =Doe and strPassword =xyz.
my url is http://localhost:51047/SenchaTest/Default.aspx I hav.e to append url like below :&#45;
http://localhost:51047/SenchaTest/Default.aspx?Username=Doe &amp;amp;Password=xyz

Please suggest me as soon as posible.</description>
      <content:encoded><![CDATA[<p>How to append url in proxy. <br />
There are two variable strUserId and strPassword.where strUserId =Doe and strPassword =xyz.<br />
my url is <a href="http://localhost:51047/SenchaTest/Default.aspx">http://localhost:51047/SenchaTest/Default.aspx</a> I hav.e to append url like below :-<br />
<a href="http://localhost:51047/SenchaTest/Default.aspx?Username=Doe">http://localhost:51047/SenchaTest/Default.aspx?Username=Doe</a> &amp;Password=xyz</p>

<p>Please suggest me as soon as posible.</p>]]></content:encoded>
      <pubDate>Thu, 26 Jul 2012 16:08 GMT</pubDate>
      <guid isPermaLink="false">http://www.sencha.com/blog//extensions-extensions-extensions#id:31891#date:16:08</guid>
    </item>
  
		<item>
      <title>Comment by interfaSys</title>
      <description>Looking forward to publishing our first extensions for ST2</description>
      <content:encoded><![CDATA[<p>Looking forward to publishing our first extensions for ST2 <img src="/images/smileys/smile.gif" width="19" height="19" alt="smile" style="border:0;" /></p>]]></content:encoded>
      <pubDate>Thu, 26 Jul 2012 16:00 GMT</pubDate>
      <guid isPermaLink="false">http://www.sencha.com/blog//extensions-extensions-extensions#id:31889#date:16:00</guid>
    </item>
  
		<item>
      <title>Comment by Rost</title>
      <description>Ted Patrick, 
the issue which blocks me from usage of ExtJS 4.1 is a bug EXTJSIV&#45;6055 (http://www.sencha.com/forum/showthread.php?198640&#45;ExtJS&#45;4.1&#45;does&#45;not&#45;work&#45;in&#45;iframe&#45;in&#45;IE)
and it does not seem to be fixed in 4.1.1. I&#8217;ve looked at the list of fixes here http://www.sencha.com/forum/showthread.php?228753&#45;Ext&#45;JS&#45;4.1.1&#45;(GA)&#45;Now&#45;Available and it is absent there.
Should I wait for 2 months more?
C&#8217;mon guys, this is working in ExtJS 4.0.7, take a look at your old code and fix this.</description>
      <content:encoded><![CDATA[<p>Ted Patrick, <br />
the issue which blocks me from usage of ExtJS 4.1 is a bug EXTJSIV-6055 (<a href="http://www.sencha.com/forum/showthread.php?198640-ExtJS-4.1-does-not-work-in-iframe-in-IE">http://www.sencha.com/forum/showthread.php?198640-ExtJS-4.1-does-not-work-in-iframe-in-IE</a>)<br />
and it does not seem to be fixed in 4.1.1. I&#8217;ve looked at the list of fixes here <a href="http://www.sencha.com/forum/showthread.php?228753-Ext-JS-4.1.1-GA">http://www.sencha.com/forum/showthread.php?228753-Ext-JS-4.1.1-(GA</a>)-Now-Available and it is absent there.<br />
Should I wait for 2 months more?<br />
C&#8217;mon guys, this is working in ExtJS 4.0.7, take a look at your old code and fix this.</p>]]></content:encoded>
      <pubDate>Thu, 26 Jul 2012 07:23 GMT</pubDate>
      <guid isPermaLink="false">http://www.sencha.com/blog//extensions-extensions-extensions#id:31869#date:07:23</guid>
    </item>
  
		<item>
      <title>Comment by Jamie Nicholson</title>
      <description>Fantastic, great step in the right direction, ExtJS 3.4 is nice because it has lots of extensions which can be used after giving them some tender love and care.&amp;nbsp; So ExtJS 4 &amp;gt; having this extension process and focus will be excellent, extensions are the icing on the cake and a good extension base should encourage ExtJS 3.4 users to upgrade.</description>
      <content:encoded><![CDATA[<p>Fantastic, great step in the right direction, ExtJS 3.4 is nice because it has lots of extensions which can be used after giving them some tender love and care.&nbsp; So ExtJS 4 &gt; having this extension process and focus will be excellent, extensions are the icing on the cake and a good extension base should encourage ExtJS 3.4 users to upgrade.</p>]]></content:encoded>
      <pubDate>Thu, 26 Jul 2012 04:38 GMT</pubDate>
      <guid isPermaLink="false">http://www.sencha.com/blog//extensions-extensions-extensions#id:31868#date:04:38</guid>
    </item>
  
		<item>
      <title>Comment by Phil Strong</title>
      <description>Peter, apologies for the long release cycle regarding Architect but I think your going to be very happy with 2.1 which will be here soon enough.</description>
      <content:encoded><![CDATA[<p>Peter, apologies for the long release cycle regarding Architect but I think your going to be very happy with 2.1 which will be here soon enough.</p>

]]></content:encoded>
      <pubDate>Wed, 25 Jul 2012 17:22 GMT</pubDate>
      <guid isPermaLink="false">http://www.sencha.com/blog//extensions-extensions-extensions#id:31867#date:17:22</guid>
    </item>
  
		<item>
      <title>Comment by Ted Patrick</title>
      <description>Rost, Peter, Miller,

On July 5 we shipped ExtJS 4.1.1 http://www.sencha.com/products/extjs/download/ and the teams are heads down on new versions of tools and frameworks. Improving the quality of the frameworks is very important work and takes time to do it right. 

Both Sencha Market and Sencha Try are managed within the Developer Relations group at Sencha which is 100% independent of engineering. We are working to improve the ecosystem surrounding Sencha products and allowing engineering to focus on improving the features and quality of the frameworks.</description>
      <content:encoded><![CDATA[<p>Rost, Peter, Miller,</p>

<p>On July 5 we shipped ExtJS 4.1.1 <a href="http://www.sencha.com/products/extjs/download/">http://www.sencha.com/products/extjs/download/</a> and the teams are heads down on new versions of tools and frameworks. Improving the quality of the frameworks is very important work and takes time to do it right. </p>

<p>Both Sencha Market and Sencha Try are managed within the Developer Relations group at Sencha which is 100% independent of engineering. We are working to improve the ecosystem surrounding Sencha products and allowing engineering to focus on improving the features and quality of the frameworks.</p>]]></content:encoded>
      <pubDate>Wed, 25 Jul 2012 15:09 GMT</pubDate>
      <guid isPermaLink="false">http://www.sencha.com/blog//extensions-extensions-extensions#id:31866#date:15:09</guid>
    </item>
  
		<item>
      <title>Comment by Ted Patrick</title>
      <description>Adam,

We are addressing licensing on Sencha Market in 2 ways. 

First, we have added a &#8220;Sencha License&#8221; which is a model license that is compatible with both the GPL and Commercial framework licenses. Any component using &#8220;Sencha License&#8221; is license compatible with all versions of Sencha Touch and ExtJS frameworks. 

Second, we are only approving components with licenses compatible with our frameworks. For example, if extensions developers use only a GPL license, we require they add the &#8220;Sencha License&#8221; to be listed within Sencha Market.

We want developer looking for extensions to feel comfortable in using extensions on Sencha Market and simplify the downstream licensing issue.</description>
      <content:encoded><![CDATA[<p>Adam,</p>

<p>We are addressing licensing on Sencha Market in 2 ways. </p>

<p>First, we have added a &#8220;Sencha License&#8221; which is a model license that is compatible with both the GPL and Commercial framework licenses. Any component using &#8220;Sencha License&#8221; is license compatible with all versions of Sencha Touch and ExtJS frameworks. </p>

<p>Second, we are only approving components with licenses compatible with our frameworks. For example, if extensions developers use only a GPL license, we require they add the &#8220;Sencha License&#8221; to be listed within Sencha Market.</p>

<p>We want developer looking for extensions to feel comfortable in using extensions on Sencha Market and simplify the downstream licensing issue.</p>]]></content:encoded>
      <pubDate>Wed, 25 Jul 2012 15:00 GMT</pubDate>
      <guid isPermaLink="false">http://www.sencha.com/blog//extensions-extensions-extensions#id:31865#date:15:00</guid>
    </item>
  
		<item>
      <title>Comment by Miller</title>
      <description>New products&#8230;? I am sorry but my company is not  happy with extjs 4 (Performance and Bugs), We are considering moving to other UI technology.</description>
      <content:encoded><![CDATA[<p>New products&#8230;? I am sorry but my company is not  happy with extjs 4 (Performance and Bugs), We are considering moving to other UI technology.</p>]]></content:encoded>
      <pubDate>Wed, 25 Jul 2012 14:52 GMT</pubDate>
      <guid isPermaLink="false">http://www.sencha.com/blog//extensions-extensions-extensions#id:31864#date:14:52</guid>
    </item>
  
		<item>
      <title>Comment by Peter</title>
      <description>100% agree with Rost.. ExtJS 4.1 consumes my time due to hell of bugs, and same with sencha architect 2 (one big bug itself) No updates for weeks&#8230; :&#45;(</description>
      <content:encoded><![CDATA[<p>100% agree with Rost.. ExtJS 4.1 consumes my time due to hell of bugs, and same with sencha architect 2 (one big bug itself) No updates for weeks&#8230; :-(</p>]]></content:encoded>
      <pubDate>Wed, 25 Jul 2012 12:55 GMT</pubDate>
      <guid isPermaLink="false">http://www.sencha.com/blog//extensions-extensions-extensions#id:31863#date:12:55</guid>
    </item>
  
		<item>
      <title>Comment by Rost</title>
      <description>IMHO you&#8217;d better concentrate on fixing bugs of ExtJS 4.1. It is already 2 month since I&#8217;ve posted a bugreport to your bugtracker and it is still not fixed.</description>
      <content:encoded><![CDATA[<p>IMHO you&#8217;d better concentrate on fixing bugs of ExtJS 4.1. It is already 2 month since I&#8217;ve posted a bugreport to your bugtracker and it is still not fixed.</p>]]></content:encoded>
      <pubDate>Wed, 25 Jul 2012 08:15 GMT</pubDate>
      <guid isPermaLink="false">http://www.sencha.com/blog//extensions-extensions-extensions#id:31862#date:08:15</guid>
    </item>
  
		<item>
      <title>Comment by Adam</title>
      <description>This sounds like a valuable and useful development and I look forward to seeing it. However I wonder if you could answer a concern that I&#8217;ve had for a long time about using extensions with ExtJS?

We have always avoided them in our product for the simple reason that there is no guarantee of compatibility when a new version of ExtJS is released (e.g., ExtJS 4). I would hate for us to build our product on an extension, only to find that there an update to ExtJS for which no version of the extension is made available. This would leave us having to upgrade the extension ourselves (which we wouldn&#8217;t have time to do), remain stuck on an older version of ExtJS, or have to abandon that extension. None of these are attractive options.

I always accepted this as just &#8220;how things were&#8221; in the past as the extensions were (for the most part) unofficial releases by the community. But with a Sencha Marketplace, they are in a much more official repository. Do you have a strategy for how to address this issue with Marketplace extensions?

Many thanks and I look forward to reading your comments.</description>
      <content:encoded><![CDATA[<p>This sounds like a valuable and useful development and I look forward to seeing it. However I wonder if you could answer a concern that I&#8217;ve had for a long time about using extensions with ExtJS?</p>

<p>We have always avoided them in our product for the simple reason that there is no guarantee of compatibility when a new version of ExtJS is released (e.g., ExtJS 4). I would hate for us to build our product on an extension, only to find that there an update to ExtJS for which no version of the extension is made available. This would leave us having to upgrade the extension ourselves (which we wouldn&#8217;t have time to do), remain stuck on an older version of ExtJS, or have to abandon that extension. None of these are attractive options.</p>

<p>I always accepted this as just &#8220;how things were&#8221; in the past as the extensions were (for the most part) unofficial releases by the community. But with a Sencha Marketplace, they are in a much more official repository. Do you have a strategy for how to address this issue with Marketplace extensions?</p>

<p>Many thanks and I look forward to reading your comments.</p>]]></content:encoded>
      <pubDate>Wed, 25 Jul 2012 06:18 GMT</pubDate>
      <guid isPermaLink="false">http://www.sencha.com/blog//extensions-extensions-extensions#id:31861#date:06:18</guid>
    </item>
  
		<item>
      <title>Comment by Loiane</title>
      <description>First Sencha Try, now Sencha Market. It is very nice to see Sencha investing in all these cool tools!
Great work guys!</description>
      <content:encoded><![CDATA[<p>First Sencha Try, now Sencha Market. It is very nice to see Sencha investing in all these cool tools!<br />
Great work guys! <img src="/images/smileys/smile.gif" width="19" height="19" alt="smile" style="border:0;" /></p>]]></content:encoded>
      <pubDate>Wed, 25 Jul 2012 00:02 GMT</pubDate>
      <guid isPermaLink="false">http://www.sencha.com/blog//extensions-extensions-extensions#id:31859#date:00:02</guid>
    </item>
  
		
	</channel>
</rss>