Re: Smart GWT / GWT Ext.... which one is better?
smartgwt is only a wrapper over a js library... you can get problem between browser... After some test, i think GXT 3 is the best choice, very easy to use, good documentation. Sure is not free... but the time saved...you buy easily a licence you can also check vaadin (it use gwt for widget) ... it's a server centric framework... but vaadin 7 will support client side too... Le jeudi 13 septembre 2012 21:29:00 UTC+2, Manuel a écrit : Hi everyone, I just started on GWT and reading alot on that guides and tutorials. Actually i try to find out, which tool to use, to design UI. Regarding to this post http://code.google.com/p/gwt-ext/ I should use smartgwt, but... I looked these showcases up: http://www.gwt-ext.com/demo/#gridGrouping http://www.smartclient.com/smartgwt/showcase/#grid_summaries I think, gwt ext feel more smooter to use and its not as laagy as smartgwt. So, I just started and try to figure out whats the pros / cons on each tool... Hope you can help me with that, and give me maybe some hints I missed. Thanks Regards, Manuel -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/s8yl2Z5rHTwJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Smart GWT / GWT Ext.... which one is better?
(d) does not apply to SmartGWT. No GWT update has ever broken SmartGWT or broken backcompat. (e) does not apply to SmartGWT. Nightlies are available for all editions - see smartclient.com/builds (c) presumably means customizing a widget by messing with it's DOM or overriding internal methods. SmartGWT has a big range of documented and supported customization APIs that don't involve low-level hacking, and if these break, we consider it a bug and fix it. (a) (b) [performance stuff] needs to be considered in light of what actually drives performance for your application. SmartGWT is designed for complex enterprise applications, so we do not optimize for first-ever page load experience (doesn't apply to apps used repeatedly and for long sessions). Instead we optimize for maximal data reuse, since round-trips to the app server database are almost always the thing to optimize in enterprise apps. A deeper discussion is in the SmartGWT QuickStart Guide, Evaluating SmartGWT chapter. In a nutshell: - the drawbacks of Sencha are not the drawbacks of SmartGWT - get clarity on what performance characteristics will matter for your end users, *then* look at performance from that perspective. If you hyper-optimize the wrong thing, your app will be slow for your end users. On Sunday, September 16, 2012 10:26:02 AM UTC-7, Andrei wrote: I prefer the third option: I don't use either of them. I build very complex user interfaces, and so far I never regretted going with pure GWT. Here are a few advantages of this option: (a) Much smaller compiled code size. This also means faster compile times for developers and faster page load times for users. (b) Better performance. I had 3 years of experience with Sencha. Their widgets look nice (why we chose them in the first place), but in some complex UIs with lots of data you start to notice the lag relative to pure GWT. Remember that showcase widgets usually represent a very simple use case. (c) Easier customizations. The simpler the widget, the easier it is to modify it as you need. There is a lower probability of breaking something. (d) There is a lower probability that the next release of a library would break your code. I remember how much pain we had with Sencha's updates (2.0, 2.1, etc.) I hope it's much better now as Sencha moved closer to pure GWT implementation of their widgets. (e) Faster updates. Once a new feature is available in GWT, you can use it right away. With libraries you have to wait until their updates. I suggest that you use one of these libraries in two cases: 1. Your knowledge of CSS is not great, so you want a professional look for your app out of the box. 2. You see some widgets in these libraries that you absolutely must use, and you don't want to spend your time building them in pure GWT. P.S. Don't let GWT Designer drive your choice of a library. Once you learn GWT, you may end up never using the Designer. I find it much easier and faster to build new views in Ui:Binder, and then simply hit a refresh button in a browser to see how my page looks like. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/N01iJIj6y5wJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Smart GWT / GWT Ext.... which one is better?
(d) no release of GWT has ever broken SmartGWT. We don't rely on much from GWT other than Java-JavaScript translation, so there is little room for something to break. (c) This may refer to breakage from customizations like modifying a component's DOM or overriding internals. In SmartGWT we have documented extension points, and if they break, we consider it a bug and fix it (e) We provide nightly builds at smartclient.com/builds, so there is never a delay. (a), (b) [performance stuff] We focus on optimizing for enterprise applications, where first-time-ever page load is not much of a concern because the users repeatedly return to the app and use it for longer sessions. Similarly we focus on reducing trips to the server and/or database since this is usually the bottleneck in an enterprise application. A deeper discussion of this is in the SmartGWT QuickStart Guide, Evaluating SmartGWT chapter. In a nutshell: - your experience with Sencha breakage doesn't apply to SmartGWT - carefully consider what will actually drive performance for end users. If you heavily optimize the wrong thing, your users will have a slow application. On Sunday, September 16, 2012 10:26:02 AM UTC-7, Andrei wrote: I prefer the third option: I don't use either of them. I build very complex user interfaces, and so far I never regretted going with pure GWT. Here are a few advantages of this option: (a) Much smaller compiled code size. This also means faster compile times for developers and faster page load times for users. (b) Better performance. I had 3 years of experience with Sencha. Their widgets look nice (why we chose them in the first place), but in some complex UIs with lots of data you start to notice the lag relative to pure GWT. Remember that showcase widgets usually represent a very simple use case. (c) Easier customizations. The simpler the widget, the easier it is to modify it as you need. There is a lower probability of breaking something. (d) There is a lower probability that the next release of a library would break your code. I remember how much pain we had with Sencha's updates (2.0, 2.1, etc.) I hope it's much better now as Sencha moved closer to pure GWT implementation of their widgets. (e) Faster updates. Once a new feature is available in GWT, you can use it right away. With libraries you have to wait until their updates. I suggest that you use one of these libraries in two cases: 1. Your knowledge of CSS is not great, so you want a professional look for your app out of the box. 2. You see some widgets in these libraries that you absolutely must use, and you don't want to spend your time building them in pure GWT. P.S. Don't let GWT Designer drive your choice of a library. Once you learn GWT, you may end up never using the Designer. I find it much easier and faster to build new views in Ui:Binder, and then simply hit a refresh button in a browser to see how my page looks like. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/J5PA5KI8sSUJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Smart GWT / GWT Ext.... which one is better?
I'd have a look at GXT 3.x from Sencha, I can't compare to the others but I think its the best GWT add-on library available. -Dave On Thursday, September 13, 2012 1:29:00 PM UTC-6, Manuel wrote: Hi everyone, I just started on GWT and reading alot on that guides and tutorials. Actually i try to find out, which tool to use, to design UI. Regarding to this post http://code.google.com/p/gwt-ext/ I should use smartgwt, but... I looked these showcases up: http://www.gwt-ext.com/demo/#gridGrouping http://www.smartclient.com/smartgwt/showcase/#grid_summaries I think, gwt ext feel more smooter to use and its not as laagy as smartgwt. So, I just started and try to figure out whats the pros / cons on each tool... Hope you can help me with that, and give me maybe some hints I missed. Thanks Regards, Manuel -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/AO7KGrSt2HwJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Smart GWT / GWT Ext.... which one is better?
Hey, thanks for your response. I already had a look at Sencha. But as Iam a beginner in GWT I was looking for something thats free to use, but could be used for commercial purpose aswell. Sencha has a GPL License and is for Open Sorce only. SmartGWT is under LGPL licensed, so this could be used for commercial purpose, I guess. Bad thing on SmartGwt´s Version 3.0 (newest version) is, its not working with the GWT Designer... But at this point, I dont even know if the GWT Designer should be used for UI Design. Am Sonntag, 16. September 2012 16:00:48 UTC+2 schrieb dhoffer: I'd have a look at GXT 3.x from Sencha, I can't compare to the others but I think its the best GWT add-on library available. -Dave On Thursday, September 13, 2012 1:29:00 PM UTC-6, Manuel wrote: Hi everyone, I just started on GWT and reading alot on that guides and tutorials. Actually i try to find out, which tool to use, to design UI. Regarding to this post http://code.google.com/p/gwt-ext/ I should use smartgwt, but... I looked these showcases up: http://www.gwt-ext.com/demo/#gridGrouping http://www.smartclient.com/smartgwt/showcase/#grid_summaries I think, gwt ext feel more smooter to use and its not as laagy as smartgwt. So, I just started and try to figure out whats the pros / cons on each tool... Hope you can help me with that, and give me maybe some hints I missed. Thanks Regards, Manuel -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/ECJrPJUFYMoJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Smart GWT / GWT Ext.... which one is better?
I prefer the third option: I don't use either of them. I build very complex user interfaces, and so far I never regretted going with pure GWT. Here are a few advantages of this option: (a) Much smaller compiled code size. This also means faster compile times for developers and faster page load times for users. (b) Better performance. I had 3 years of experience with Sencha. Their widgets look nice (why we chose them in the first place), but in some complex UIs with lots of data you start to notice the lag relative to pure GWT. Remember that showcase widgets usually represent a very simple use case. (c) Easier customizations. The simpler the widget, the easier it is to modify it as you need. There is a lower probability of breaking something. (d) There is a lower probability that the next release of a library would break your code. I remember how much pain we had with Sencha's updates (2.0, 2.1, etc.) I hope it's much better now as Sencha moved closer to pure GWT implementation of their widgets. (e) Faster updates. Once a new feature is available in GWT, you can use it right away. With libraries you have to wait until their updates. I suggest that you use one of these libraries in two cases: 1. Your knowledge of CSS is not great, so you want a professional look for your app out of the box. 2. You see some widgets in these libraries that you absolutely must use, and you don't want to spend your time building them in pure GWT. P.S. Don't let GWT Designer drive your choice of a library. Once you learn GWT, you may end up never using the Designer. I find it much easier and faster to build new views in Ui:Binder, and then simply hit a refresh button in a browser to see how my page looks like. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/pUpHcSyL2cwJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Smart GWT / GWT Ext.... which one is better?
Couldn't agree more! On Sunday, September 16, 2012 7:26:02 PM UTC+2, Andrei wrote: I prefer the third option: I don't use either of them. I build very complex user interfaces, and so far I never regretted going with pure GWT. Here are a few advantages of this option: (a) Much smaller compiled code size. This also means faster compile times for developers and faster page load times for users. (b) Better performance. I had 3 years of experience with Sencha. Their widgets look nice (why we chose them in the first place), but in some complex UIs with lots of data you start to notice the lag relative to pure GWT. Remember that showcase widgets usually represent a very simple use case. (c) Easier customizations. The simpler the widget, the easier it is to modify it as you need. There is a lower probability of breaking something. (d) There is a lower probability that the next release of a library would break your code. I remember how much pain we had with Sencha's updates (2.0, 2.1, etc.) I hope it's much better now as Sencha moved closer to pure GWT implementation of their widgets. (e) Faster updates. Once a new feature is available in GWT, you can use it right away. With libraries you have to wait until their updates. I suggest that you use one of these libraries in two cases: 1. Your knowledge of CSS is not great, so you want a professional look for your app out of the box. 2. You see some widgets in these libraries that you absolutely must use, and you don't want to spend your time building them in pure GWT. P.S. Don't let GWT Designer drive your choice of a library. Once you learn GWT, you may end up never using the Designer. I find it much easier and faster to build new views in Ui:Binder, and then simply hit a refresh button in a browser to see how my page looks like. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/6dy-QaA06PMJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Smart GWT / GWT Ext.... which one is better?
Hey, thanks for sharing your experience. I will take a look at the UI.Binder stuff. In the meantime i had a look at vaadin (Apache License Version 2.0), another UI library. Since this library works on the server-side, Iam not sure if this is a considerable solution. Anyway, I guess I will stay with pure GWT for now. There are more interesting things to take a look at besides UI :) Am Sonntag, 16. September 2012 19:26:02 UTC+2 schrieb Andrei: I prefer the third option: I don't use either of them. I build very complex user interfaces, and so far I never regretted going with pure GWT. Here are a few advantages of this option: (a) Much smaller compiled code size. This also means faster compile times for developers and faster page load times for users. (b) Better performance. I had 3 years of experience with Sencha. Their widgets look nice (why we chose them in the first place), but in some complex UIs with lots of data you start to notice the lag relative to pure GWT. Remember that showcase widgets usually represent a very simple use case. (c) Easier customizations. The simpler the widget, the easier it is to modify it as you need. There is a lower probability of breaking something. (d) There is a lower probability that the next release of a library would break your code. I remember how much pain we had with Sencha's updates (2.0, 2.1, etc.) I hope it's much better now as Sencha moved closer to pure GWT implementation of their widgets. (e) Faster updates. Once a new feature is available in GWT, you can use it right away. With libraries you have to wait until their updates. I suggest that you use one of these libraries in two cases: 1. Your knowledge of CSS is not great, so you want a professional look for your app out of the box. 2. You see some widgets in these libraries that you absolutely must use, and you don't want to spend your time building them in pure GWT. P.S. Don't let GWT Designer drive your choice of a library. Once you learn GWT, you may end up never using the Designer. I find it much easier and faster to build new views in Ui:Binder, and then simply hit a refresh button in a browser to see how my page looks like. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/gmzdAKYlXIMJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Smart GWT / GWT Ext.... which one is better?
The best UI library i ve found so far to use with GWT on the Desktop is Flex. Hard to believe to i ve tried them all. Nothing beats Flex on the Desktop. 2012/9/16 Manuel develop.m...@gmail.com Hey, thanks for sharing your experience. I will take a look at the UI.Binder stuff. In the meantime i had a look at vaadin (Apache License Version 2.0), another UI library. Since this library works on the server-side, Iam not sure if this is a considerable solution. Anyway, I guess I will stay with pure GWT for now. There are more interesting things to take a look at besides UI :) Am Sonntag, 16. September 2012 19:26:02 UTC+2 schrieb Andrei: I prefer the third option: I don't use either of them. I build very complex user interfaces, and so far I never regretted going with pure GWT. Here are a few advantages of this option: (a) Much smaller compiled code size. This also means faster compile times for developers and faster page load times for users. (b) Better performance. I had 3 years of experience with Sencha. Their widgets look nice (why we chose them in the first place), but in some complex UIs with lots of data you start to notice the lag relative to pure GWT. Remember that showcase widgets usually represent a very simple use case. (c) Easier customizations. The simpler the widget, the easier it is to modify it as you need. There is a lower probability of breaking something. (d) There is a lower probability that the next release of a library would break your code. I remember how much pain we had with Sencha's updates (2.0, 2.1, etc.) I hope it's much better now as Sencha moved closer to pure GWT implementation of their widgets. (e) Faster updates. Once a new feature is available in GWT, you can use it right away. With libraries you have to wait until their updates. I suggest that you use one of these libraries in two cases: 1. Your knowledge of CSS is not great, so you want a professional look for your app out of the box. 2. You see some widgets in these libraries that you absolutely must use, and you don't want to spend your time building them in pure GWT. P.S. Don't let GWT Designer drive your choice of a library. Once you learn GWT, you may end up never using the Designer. I find it much easier and faster to build new views in Ui:Binder, and then simply hit a refresh button in a browser to see how my page looks like. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/gmzdAKYlXIMJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Smart GWT / GWT Ext.... which one is better?
Hi, You have a couple of other UI library choices: *GWT Bootstrap* demo: - http://gwtbootstrap.github.com/ *mgwt* demo: - http://gwt-cx.com/mgwt-basic-project/index.html Some useful links: Smart GWT tutorials: - http://uptick.com.au/blog Ext GWT demo: - http://gwt-cx.com/extgwt-serendipity/Serendipity.html Cheers Rob Kiahu.com -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/b4g4GXo59LMJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Smart GWT / GWT Ext.... which one is better?
Hi everyone, I just started on GWT and reading alot on that guides and tutorials. Actually i try to find out, which tool to use, to design UI. Regarding to this post http://code.google.com/p/gwt-ext/ I should use smartgwt, but... I looked these showcases up: http://www.gwt-ext.com/demo/#gridGrouping http://www.smartclient.com/smartgwt/showcase/#grid_summaries I think, gwt ext feel more smooter to use and its not as laagy as smartgwt. So, I just started and try to figure out whats the pros / cons on each tool... Hope you can help me with that, and give me maybe some hints I missed. Thanks Regards, Manuel -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/1zctHTngl_oJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
