Ext Designer 1.1 Released http://www.sencha.com/blog/ext-designer-1-1-released We’re pleased to announce the next version of Ext Designer, version 1.1, is released and available to download. Ext Designer 1.1 brings several key features to promote the reusability of components created within Ext Designer, and brings additional stability and performance improvements. en-us jarred@sencha.com Copyright 2011 2011-03-17T07:00:17+00:00 Comment by nicotine It’s a great features, but I have a question. Is it possible to reuse the component event handlers I made between child components? Ex: a slider and a textField communicate via events to get and setValue each other. They are child of a container mySlider.ui.js . ( event implementation in mySlider.js ) If I save the container in ToolBox, can I retrieve the behavior between child components? Excuse my english !! Thanks It’s a great features, but I have a question.
Is it possible to reuse the component event handlers I made between child components?
Ex: a slider and a textField communicate via events to get and setValue each other. They are child of a container mySlider.ui.js . ( event implementation in mySlider.js )
If I save the container in ToolBox, can I retrieve the behavior between child components?
Excuse my english !!
Thanks

]]> Wed, 06 Apr 2011 14:11 GMT http://www.sencha.com/blog//ext-designer-1-1-released#id:19281#date:14:11 Comment by Jonas in forum of Sencha General Open Discussion. in forum of Sencha General Open Discussion.

]]> Thu, 31 Mar 2011 19:18 GMT http://www.sencha.com/blog//ext-designer-1-1-released#id:19078#date:19:18 Comment by Jonas Tool for creation of interfaces in Ext JS and Designer too. Tool for creation of interfaces in Ext JS and Designer too.

]]> Thu, 31 Mar 2011 19:13 GMT http://www.sencha.com/blog//ext-designer-1-1-released#id:19071#date:19:13 Comment by Jonas 25 25

]]> Thu, 31 Mar 2011 18:53 GMT http://www.sencha.com/blog//ext-designer-1-1-released#id:19064#date:18:53 Comment by Chris Thanks for the hard work on the new release. I’m glad to see a new release available for download. I’m a little disappointed about the fact that there’s no support yet for using variables in fieldLabel, headers, html, etc. Very useful for localisation. Remember these forum posts? /forum/showthread.php?114644-xds-and-multilanguage-app /forum/showthread.php?97366-Localization /forum/showthread.php?101424-DISCUSS-Set-text-string-from-a-variable (I can’t post full links) Thanks for the hard work on the new release. I’m glad to see a new release available for download. I’m a little disappointed about the fact that there’s no support yet for using variables in fieldLabel, headers, html, etc. Very useful for localisation. Remember these forum posts?
/forum/showthread.php?114644-xds-and-multilanguage-app
/forum/showthread.php?97366-Localization
/forum/showthread.php?101424-DISCUSS-Set-text-string-from-a-variable
(I can’t post full links)

]]> Sat, 26 Mar 2011 12:13 GMT http://www.sencha.com/blog//ext-designer-1-1-released#id:18834#date:12:13 Comment by Chris Kudos for the UTF-8 encoding and preservation of international Unicode characters! Kudos for the UTF-8 encoding and preservation of international Unicode characters!

]]> Fri, 18 Mar 2011 10:20 GMT http://www.sencha.com/blog//ext-designer-1-1-released#id:18552#date:10:20 Comment by Chris I posted something yesterday with links to the forum about localization. After submitting the post, it reported that it may be spam, probably due to the links. Could you approve the post and put it here? You may delete this message after it’s done. I posted something yesterday with links to the forum about localization. After submitting the post, it reported that it may be spam, probably due to the links. Could you approve the post and put it here? You may delete this message after it’s done.

]]> Fri, 18 Mar 2011 10:13 GMT http://www.sencha.com/blog//ext-designer-1-1-released#id:18551#date:10:13 Comment by Simon Wong Any pre-sale for ExtJS 4 and Designer? Any pre-sale for ExtJS 4 and Designer?

]]> Fri, 18 Mar 2011 07:47 GMT http://www.sencha.com/blog//ext-designer-1-1-released#id:18532#date:07:47 Comment by Elgs Fingers crossed to th ux support. Or at least other more elegant way to use a 3rd party extension in the code. Fingers crossed to th ux support. Or at least other more elegant way to use a 3rd party extension in the code.

]]> Fri, 18 Mar 2011 03:05 GMT http://www.sencha.com/blog//ext-designer-1-1-released#id:18528#date:03:05 Comment by Jarred Nicholls @Naveed In certain cases the save function was breaking, which has been resolved in a 1.1.1 build that is available now. @Naveed In certain cases the save function was breaking, which has been resolved in a 1.1.1 build that is available now.

]]> Thu, 17 Mar 2011 22:11 GMT http://www.sencha.com/blog//ext-designer-1-1-released#id:18521#date:22:11 Comment by Naveed I am running in eval mode. The export feature and “save to toolbox” is not working in the eval, is this by design or else…. I am running in eval mode. The export feature and “save to toolbox” is not working in the eval, is this by design or else….

]]> Thu, 17 Mar 2011 21:26 GMT http://www.sencha.com/blog//ext-designer-1-1-released#id:18520#date:21:26 Comment by Les Basic question: Why the Designer needs to be downloaded?  I thought I should be able to access it as any other Web application by following a URL. Basic question: Why the Designer needs to be downloaded?  I thought I should be able to access it as any other Web application by following a URL.

]]> Thu, 17 Mar 2011 19:36 GMT http://www.sencha.com/blog//ext-designer-1-1-released#id:18511#date:19:36 Comment by Bob Obringer Oops… meant @Mats, not @Bostjian Oops… meant @Mats, not @Bostjian

]]> Thu, 17 Mar 2011 14:39 GMT http://www.sencha.com/blog//ext-designer-1-1-released#id:18497#date:14:39 Comment by Bob Obringer @Bostjan:  Found this in the forums (but I can’t locate it again, so kudos to the author… but I’m pasting here).  I create placeholder components in my designer (form fields should use a text field placeholder, containers should use container placeholders).  You can fully configure the options that are available right in designer and then use this code to replace the placeholder with your custom component.  Has worked like charm for me so far… /** * Replaces a component with another, preserving the original config * @param {Component} newComponent the new component to replace this one with * @return {Component} this the replaced component */ Ext.override(Ext.Component, {   replaceWith : function(newComponent){       var ctnr = this.ownerCt;       // if the refOwner is a form or if newComponent.ownerForm config is set to the form       var form = newComponent.ownerForm ? newComponent.ownerForm : this.refOwner.form;       var i = ctnr.items.indexOf(this);       // apply initialConfig       Ext.applyIf(newComponent, this.initialConfig);       ctnr.remove(this, true);       var added = ctnr.insert(i, newComponent);       // if the component is in a form       if (form){         // remove the old component from the form         form.remove(this);         // add the new component to the form         form.add(added);       }   }  }); @Bostjan:  Found this in the forums (but I can’t locate it again, so kudos to the author… but I’m pasting here).  I create placeholder components in my designer (form fields should use a text field placeholder, containers should use container placeholders).  You can fully configure the options that are available right in designer and then use this code to replace the placeholder with your custom component.  Has worked like charm for me so far…

/**
* Replaces a component with another, preserving the original config
* @param {Component} newComponent the new component to replace this one with
* @return {Component} this the replaced component
*/
Ext.override(Ext.Component, {
  replaceWith : function(newComponent){
      var ctnr = this.ownerCt;
      // if the refOwner is a form or if newComponent.ownerForm config is set to the form
      var form = newComponent.ownerForm ? newComponent.ownerForm : this.refOwner.form;
      var i = ctnr.items.indexOf(this);
      // apply initialConfig
      Ext.applyIf(newComponent, this.initialConfig);
      ctnr.remove(this, true);
      var added = ctnr.insert(i, newComponent);
      // if the component is in a form
      if (form){
        // remove the old component from the form
        form.remove(this);
        // add the new component to the form
        form.add(added);
      }
  } 
});

]]> Thu, 17 Mar 2011 14:39 GMT http://www.sencha.com/blog//ext-designer-1-1-released#id:18496#date:14:39 Comment by Bostjan Rihter Thanks Jarred, great news! Thanks Jarred, great news!

]]> Thu, 17 Mar 2011 13:48 GMT http://www.sencha.com/blog//ext-designer-1-1-released#id:18491#date:13:48 Comment by Jarred Nicholls @Bostjan Ext JS 4 support is underway.  There will be a short gap between Ext JS 4 RTM and Designer 1.2 RTM (1.2 will have Ext JS 4 support).  So yes, there are definitely plans @Mats 3rd-party UXs are not supported by the component import feature, only components that originated in the Designer.  UX support is on the roadmap, and I look forward to sharing those details in the near future. @Bostjan Ext JS 4 support is underway.  There will be a short gap between Ext JS 4 RTM and Designer 1.2 RTM (1.2 will have Ext JS 4 support).  So yes, there are definitely plans grin

@Mats 3rd-party UXs are not supported by the component import feature, only components that originated in the Designer.  UX support is on the roadmap, and I look forward to sharing those details in the near future.

]]> Thu, 17 Mar 2011 13:47 GMT http://www.sencha.com/blog//ext-designer-1-1-released#id:18489#date:13:47 Comment by Mats Nice work Jarred, any ideas on when we can expect to be able to import 3rd party extensions (or is that possible now using the Import feature?). Nice work Jarred, any ideas on when we can expect to be able to import 3rd party extensions (or is that possible now using the Import feature?).

]]> Thu, 17 Mar 2011 08:50 GMT http://www.sencha.com/blog//ext-designer-1-1-released#id:18481#date:08:50 Comment by Bostjan Rihter Guys, are there any plans on making ExtDesigner compatible with ExtJS4 as it becomes available? Guys, are there any plans on making ExtDesigner compatible with ExtJS4 as it becomes available?

]]> Thu, 17 Mar 2011 08:05 GMT http://www.sencha.com/blog//ext-designer-1-1-released#id:18480#date:08:05 Comment by Martin Awesome work, this makes designer much more useful now! Awesome work, this makes designer much more useful now!

]]> Thu, 17 Mar 2011 07:57 GMT http://www.sencha.com/blog//ext-designer-1-1-released#id:18479#date:07:57