Ext GWT 3.0 Developer Preview 5 http://www.sencha.com/blog/ext-gwt-3-developer-preview-5 The Ext GWT team has been hard at work on Ext GWT 3.0 and we’re happy to announce the availability of Ext GWT 3.0 PR5. This will be the last developer preview release as we move toward our 3.0 beta releases. There are a tremendous number of improvements and features added since PR4. As a result, we are closing in on being feature complete. en-us darrell@extjs.com Copyright 2011 2011-10-19T16:00:58+00:00 Comment by sblommers It’s missing. There is a boolean password but it is not (yet) used. It’s missing. There is a boolean password but it is not (yet) used.

]]> Fri, 02 Dec 2011 12:09 GMT http://www.sencha.com/blog//ext-gwt-3-developer-preview-5#id:29971#date:12:09 Comment by Tony I’ve been testing this release for quite a while now and I think it really excellent.  I wasn’t a very experienced GWT developer when I started the testing, but I’ve still managed to make an text application which looks quite good and behaves quite nicely. One question ... I haven’t seen a password text box.  Is there someplace and I’ve just overlooked it?   I’ve been testing this release for quite a while now and I think it really excellent.  I wasn’t a very experienced GWT developer when I started the testing, but I’ve still managed to make an text application which looks quite good and behaves quite nicely.

One question ... I haven’t seen a password text box.  Is there someplace and I’ve just overlooked it?

 

]]> Fri, 02 Dec 2011 11:41 GMT http://www.sencha.com/blog//ext-gwt-3-developer-preview-5#id:29970#date:11:41 Comment by ani786 Darrell, Once again u r doing a wonderful job…. I read some of the above posts and the delays in GXT some ranting , we need all of that . I understand the delay was due to dependency on GWT and their releases…. my 2 cents again… Y dont we create a Shield[layer] around the GXT , to ensure such changes done by the mother framework or another child framework have minimum impact we just modify that layer. Otherwise this is going to become a nightmare as we grow, and other frameworks take a different path , that way GXT can concentrate on what best it can do by itself rather than the lookups and assumptions,ther will be no end to this route. I wite what i observe with my own eyes s i am an implementer not a hoax architect who just talk the crap ....The Roads about US is what i loved they plannned it quite quite ahead the space and the width where as other countries keep reworking on the same rather than other progress Regards Ani Darrell,
Once again u r doing a wonderful job….
I read some of the above posts and the delays in GXT some ranting , we need all of that smile.
I understand the delay was due to dependency on GWT and their releases….
my 2 cents again…
Y dont we create a Shield[layer] around the GXT , to ensure such changes done by the mother framework or another child framework have minimum impact we just modify that layer.
Otherwise this is going to become a nightmare as we grow, and other frameworks take a different path , that way GXT can concentrate on what best it can do by itself rather than the lookups and assumptions,ther will be no end to this route.
I wite what i observe with my own eyes s i am an implementer not a hoax architect who just talk the crap ....The Roads about US is what i loved they plannned it quite quite ahead the space and the width where as other countries keep reworking on the same rather than other progress smile
Regards
Ani

]]> Sat, 05 Nov 2011 01:05 GMT http://www.sencha.com/blog//ext-gwt-3-developer-preview-5#id:28991#date:01:05 Comment by William You decide on the indication for the generator through inheritance, ex: interface FooBeanProperties extends PropertyAccess<FooBean> How will it look like when the bean extends other ? Ex: class FooBean extends BarBean ? It seems that annotaion indication could be better. Ex: @PropertyAccess(FooBean.class) interface FooBeanProperties extends BarBeanProperties You decide on the indication for the generator through inheritance, ex:
interface FooBeanProperties extends PropertyAccess<FooBean>
How will it look like when the bean extends other ? Ex:
class FooBean extends BarBean ?
It seems that annotaion indication could be better. Ex:
@PropertyAccess(FooBean.class)
interface FooBeanProperties extends BarBeanProperties

]]> Fri, 04 Nov 2011 11:27 GMT http://www.sencha.com/blog//ext-gwt-3-developer-preview-5#id:28974#date:11:27 Comment by Sebastiaan Hi there, I just ported my projects to use GXT 3.0.0 DP5. I had some troubles but I managed to rewrite everything (including the extensive use of ModelData). I am very happy with the performance but also the clean API. I must agree with Ani/ani786, some choices seem a bit strange on behalf of readability. Very nice job Sencha !! Hi there, I just ported my projects to use GXT 3.0.0 DP5. I had some troubles but I managed to rewrite everything (including the extensive use of ModelData). I am very happy with the performance but also the clean API. I must agree with Ani/ani786, some choices seem a bit strange on behalf of readability.

Very nice job Sencha !!

]]> Sat, 29 Oct 2011 09:47 GMT http://www.sencha.com/blog//ext-gwt-3-developer-preview-5#id:28764#date:09:47 Comment by ani786 Apolgogies for the Repost the above one was copied from word doc so lots of ? instead of pl ignore above post and consider this one here… Darrell, Wonderful Job I did not go through the details but as a developer and being in this field for 14+ my 2 cents at a high level or bird’s eye view: 1&gt;All modules Can be inherited by inheriting com.sencha.gxt.ui.GXT.&nbsp; I feel this will become Readability problem. Detail like full names and having non standard acronyms has always made life not easy but tough. They have Street names with no meaning if we had meaningful street names I would have navigated without maps 3&gt;sencha [com.sencha.] in the API names. Were we not taught in the school of Magic [Harry Potter:)] not to name things after such Proper Nouns will sencha always Remain sencha? Later it might be oracle sencha or IBM sencha who knows also one word less in each file. I would have gone for a)com.gxt.shared.event instead of com.sencha.gxt.core.shared.event b) All widgets have a core just eliminate the core and leave it as com..gxt.widget.client.treegrid instead of com.sencha.gxt.widget.core.client.treegrid In nutshell sencha and core avoidable and unnecessary clutter,&nbsp; eliminating them will make it clean. 2 years down the line you may add another 2 periods already on 6 now. Which you can make it to 4 by removing core and sencha 4&gt;On reset.css, what if we have some apps which need a override and include some proprietary things don’t make anything strict we need to be flexi, nothing strict has worked. We all reach the same cross roads after all we are Homo sapiens somewhere we share a common gene . I have gone through the above when I write my simple classes and simple programs Apolgogies for the Repost the above one was copied from word doc so lots of ? instead of smile pl ignore above post and consider this one here…

Darrell,
Wonderful Job I did not go through the details but as a developer and being in this field for 14+ my 2 cents at a high level or bird’s eye view:
1>All modules Can be inherited by inheriting com.sencha.gxt.ui.GXT.  I feel this will become Readability problem. Detail like full names and having non standard acronyms has always made life not easy but tough. They have Street names with no meaning if we had meaningful street names I would have navigated without maps smile
3>sencha [com.sencha.] in the API names. Were we not taught in the school of Magic [Harry Potter:)] not to name things after such Proper Nouns will sencha always Remain sencha? Later it might be oracle sencha or IBM sencha who knows also one word less in each file.
I would have gone for
a)com.gxt.shared.event instead of com.sencha.gxt.core.shared.event
b) All widgets have a core just eliminate the core and leave it as com..gxt.widget.client.treegrid instead of com.sencha.gxt.widget.core.client.treegrid
In nutshell sencha and core smile avoidable and unnecessary clutter,  eliminating them will make it clean. 2 years down the line you may add another 2 periods already on 6 now. Which you can make it to 4 by removing core and sencha
4>On reset.css, what if we have some apps which need a override and include some proprietary things don’t make anything strict we need to be flexi, nothing strict has worked.

We all reach the same cross roads after all we are Homo sapiens somewhere we share a common gene smile . I have gone through the above when I write my simple classes and simple programs smile

]]> Wed, 26 Oct 2011 00:39 GMT http://www.sencha.com/blog//ext-gwt-3-developer-preview-5#id:28646#date:00:39 Comment by ani Darren, Wonderful Job I did not go through the details but as a developer and being in this field for 14+ my 2 cents at a high level or bird’s eye view: 1&gt;All modules Can be inherited by inheriting com.sencha.gxt.ui.GXT.&nbsp; I feel this will become Readability problem. Detail like full names and avoiding no standard acronyms have always made life not easy but tough. They have Street names with no meaning if we had meaningful street names I would have navigated without maps ? 3&gt;sencha [com.sencha.] in the API names. Were we not taught in the school of Magic [Harry Potter?] not to name things after such Proper Nouns will sencha always Remain sencha? Later it might be oracle sencha or IBM sencha who knows also one word less in each file. I would have gone for a)com.gxt.shared.event instead of com.sencha.gxt.core.shared.event b) All widgets have a core just eliminate the core and leave it as com..gxt.widget.client.treegrid instead of com.sencha.gxt.widget.core.client.treegrid In nutshell sencha and core ? avoidable and unnecessary clutter eliminate them will make it clean 2 years down the line you may add another 2 periods already on 6 now. Which you can make it to 4 by removing core and sencha 4&gt;on reset.css, what if we have some apps which need a override and include some proprietary things don’t make anything strict we need to be flexi, nothing strict has worked. We all reach the same cross roads after all we are Homo sapiens somewhere we share a common gene ? . I have gone through the above when I write my simple classes and simple programs ? Darren,
Wonderful Job I did not go through the details but as a developer and being in this field for 14+ my 2 cents at a high level or bird’s eye view:
1>All modules Can be inherited by inheriting com.sencha.gxt.ui.GXT.  I feel this will become Readability problem. Detail like full names and avoiding no standard acronyms have always made life not easy but tough. They have Street names with no meaning if we had meaningful street names I would have navigated without maps ?
3>sencha [com.sencha.] in the API names. Were we not taught in the school of Magic [Harry Potter?] not to name things after such Proper Nouns will sencha always Remain sencha? Later it might be oracle sencha or IBM sencha who knows also one word less in each file.
I would have gone for
a)com.gxt.shared.event instead of com.sencha.gxt.core.shared.event
b) All widgets have a core just eliminate the core and leave it as com..gxt.widget.client.treegrid instead of com.sencha.gxt.widget.core.client.treegrid
In nutshell sencha and core ? avoidable and unnecessary clutter eliminate them will make it clean 2 years down the line you may add another 2 periods already on 6 now. Which you can make it to 4 by removing core and sencha
4>on reset.css, what if we have some apps which need a override and include some proprietary things don’t make anything strict we need to be flexi, nothing strict has worked.

We all reach the same cross roads after all we are Homo sapiens somewhere we share a common gene ? . I have gone through the above when I write my simple classes and simple programs ?

]]> Wed, 26 Oct 2011 00:28 GMT http://www.sencha.com/blog//ext-gwt-3-developer-preview-5#id:28645#date:00:28 Comment by Yaniv great work on the new release. just one thing - it might help to be specific about what dependencies gxt 3.0 has. it took me a few hours to realize that a runtime compilation error i was getting was caused by not including gwt-user.jar (not a dependency for gxt 2.5) great work on the new release. just one thing - it might help to be specific about what dependencies gxt 3.0 has. it took me a few hours to realize that a runtime compilation error i was getting was caused by not including gwt-user.jar (not a dependency for gxt 2.5)

]]> Tue, 25 Oct 2011 04:56 GMT http://www.sencha.com/blog//ext-gwt-3-developer-preview-5#id:28615#date:04:56 Comment by Travis Webb What version of GWT will DP5 work best with? What version of GWT will DP5 work best with?

]]> Sun, 23 Oct 2011 22:05 GMT http://www.sencha.com/blog//ext-gwt-3-developer-preview-5#id:28571#date:22:05 Comment by Viacheslav Dobromyslov RegExValidator seems to be broken. No email validator. ToolTip is awful class. It doesn’t provide convenient methods for title and body change. And doesn’t work with standard GWT textfields. But all other improvements are awesome. Thank you, Darrell. RegExValidator seems to be broken. No email validator.
ToolTip is awful class. It doesn’t provide convenient methods for title and body change. And doesn’t work with standard GWT textfields.

But all other improvements are awesome. Thank you, Darrell.

]]> Sat, 22 Oct 2011 13:33 GMT http://www.sencha.com/blog//ext-gwt-3-developer-preview-5#id:28554#date:13:33 Comment by Darrell Meyer @Alain You make a good point about us being in silence mode. Going forward we will make sure to keep the community better informed of current development status and release dates. @Alain You make a good point about us being in silence mode. Going forward we will make sure to keep the community better informed of current development status and release dates.

]]> Fri, 21 Oct 2011 17:53 GMT http://www.sencha.com/blog//ext-gwt-3-developer-preview-5#id:28528#date:17:53 Comment by andr83 Great news! Great news!

]]> Fri, 21 Oct 2011 11:56 GMT http://www.sencha.com/blog//ext-gwt-3-developer-preview-5#id:28520#date:11:56 Comment by Jackson Looks excellent. Downloading! Also looking forward to final version release. Cheers. Looks excellent. Downloading! Also looking forward to final version release. smile Cheers.

]]> Thu, 20 Oct 2011 17:58 GMT http://www.sencha.com/blog//ext-gwt-3-developer-preview-5#id:28499#date:17:58 Comment by Robert La Ferla @Darrell Meyer Thanks.&nbsp; I used GXT 2.x to develop some rather large sites like Xilinx Semiconductor’s software licensing center, Allscripts and Misys Banking.&nbsp; I think what you guys have done is amazing.&nbsp; The GXT platform is an excellent one and 3.0 is a big step towards minimizing the pain associated with the gain.&nbsp; I strongly urge you to make mobile support (gestures/themes/etc..) the next critical feature post 3.0 and implement it as quickly as you can.&nbsp; I have been experimenting with Sencha Touch and it pains me to code directly in Javascript.&nbsp; I looked at nextinterfaces.com and if they were more feature complete, I’d dump Sencha Touch.&nbsp; However, if GXT 3.1 had Android/iPhone support, that would be best. @Darrell Meyer Thanks.  I used GXT 2.x to develop some rather large sites like Xilinx Semiconductor’s software licensing center, Allscripts and Misys Banking.  I think what you guys have done is amazing.  The GXT platform is an excellent one and 3.0 is a big step towards minimizing the pain associated with the gain.  I strongly urge you to make mobile support (gestures/themes/etc..) the next critical feature post 3.0 and implement it as quickly as you can.  I have been experimenting with Sencha Touch and it pains me to code directly in Javascript.  I looked at nextinterfaces.com and if they were more feature complete, I’d dump Sencha Touch.  However, if GXT 3.1 had Android/iPhone support, that would be best.

]]> Thu, 20 Oct 2011 17:14 GMT http://www.sencha.com/blog//ext-gwt-3-developer-preview-5#id:28497#date:17:14 Comment by Darrell Meyer @Bill We are targeting early 2012 for the GA 3.0 release. @Robert La Ferla At this time, 3.0 does not support mobile gestures. @raivis I can understand your frustration with the delivery dates of 3.0. GWT is a moving target, and we are trying to keep Ext GWT as powerful as possible, using the latest concepts from GWT for as long as possible. Two changes that we originally did not scope for were Appearances and Cells, which we felt were important to implement. Supporting Cells required us to rewrite most of our fields and data widgets. Implementing the Appearance pattern required us to rewrite most of our existing CSS, HTML, and images. These are changes the community has requested and are consistent with the direction of GWT. We will have a beta release out before end of year which will be feature complete with a stable API. @Bill We are targeting early 2012 for the GA 3.0 release.

@Robert La Ferla At this time, 3.0 does not support mobile gestures.

@raivis I can understand your frustration with the delivery dates of 3.0. GWT is a moving target, and we are trying to keep Ext GWT as powerful as possible, using the latest concepts from GWT for as long as possible. Two changes that we originally did not scope for were Appearances and Cells, which we felt were important to implement. Supporting Cells required us to rewrite most of our fields and data widgets. Implementing the Appearance pattern required us to rewrite most of our existing CSS, HTML, and images. These are changes the community has requested and are consistent with the direction of GWT. We will have a beta release out before end of year which will be feature complete with a stable API.

]]> Thu, 20 Oct 2011 17:02 GMT http://www.sencha.com/blog//ext-gwt-3-developer-preview-5#id:28496#date:17:02 Comment by Ali @raivis Such a negative post on a very positive news. I am not giving excuses, but if you have done any serious development, you would have been much more tolerant to those deadlines. @raivis
Such a negative post on a very positive news. I am not giving excuses, but if you have done any serious development, you would have been much more tolerant to those deadlines.

]]> Thu, 20 Oct 2011 14:33 GMT http://www.sencha.com/blog//ext-gwt-3-developer-preview-5#id:28490#date:14:33 Comment by raivis @Bill Yes, it had to be out at the end of the summer. 2 month overdue and yet another DP version. Epic fail gxt team. ty so much, I switched to pure gwt. bye bye @Bill
Yes, it had to be out at the end of the summer. 2 month overdue and yet another DP version. Epic fail gxt team. ty so much, I switched to pure gwt. bye bye

]]> Thu, 20 Oct 2011 06:22 GMT http://www.sencha.com/blog//ext-gwt-3-developer-preview-5#id:28488#date:06:22 Comment by Robert La Ferla This is excellent.&nbsp; Does GXT 3.x support mobile devices (gestures, themes, etc..)? This is excellent.  Does GXT 3.x support mobile devices (gestures, themes, etc..)?

]]> Thu, 20 Oct 2011 00:42 GMT http://www.sencha.com/blog//ext-gwt-3-developer-preview-5#id:28486#date:00:42 Comment by Piotr Kosmowski So cool… Grid, RF, UiBinder! Can’t wait for the final version. Thank you guys. So cool… Grid, RF, UiBinder! Can’t wait for the final version. Thank you guys.

]]> Wed, 19 Oct 2011 20:44 GMT http://www.sencha.com/blog//ext-gwt-3-developer-preview-5#id:28484#date:20:44 Comment by Bill Is there an announced GA date for Ext Gwt 3.0 ?&nbsp; Q4 2011 ?&nbsp; Q1 2012 ? Is there an announced GA date for Ext Gwt 3.0 ?  Q4 2011 ?  Q1 2012 ?

]]> Wed, 19 Oct 2011 20:37 GMT http://www.sencha.com/blog//ext-gwt-3-developer-preview-5#id:28483#date:20:37 Comment by Ali Wonderful news! I have been waiting to see this, and you guys managed to deliver as usual. Thank you so much, downloading Wonderful news! I have been waiting to see this, and you guys managed to deliver as usual. Thank you so much, downloading smile

]]> Wed, 19 Oct 2011 20:10 GMT http://www.sencha.com/blog//ext-gwt-3-developer-preview-5#id:28482#date:20:10 Comment by diego gxt 3.0 will support form like extjs4 (http://dev.sencha.com/deploy/ext-4.0.2a/examples/form/contact-form.html)? great job! gxt 3.0 will support form like extjs4 (http://dev.sencha.com/deploy/ext-4.0.2a/examples/form/contact-form.html)?

great job!

]]> Wed, 19 Oct 2011 19:07 GMT http://www.sencha.com/blog//ext-gwt-3-developer-preview-5#id:28481#date:19:07