Re: GwtMaterialDesign vs gwt-polymer-elements
I just don't get this trend with "burying" widgets and UiBinder. Even with Errai I don't see any meaningful replacement for composite UI, i.e. design simple blocks as ... and then reuse them with Though with Polymer it looks like it's possible by defining web component for each logical block. On Wednesday, November 23, 2016 at 2:40:45 PM UTC-8, Amit Munwes wrote: > > I decided to go with Polymer: > 1. Very active framework and not specific to GWT developers - so you can > find answers/examples etc. easily as well as a growing set of web > components that can be used within your app > 2. High-end material design components, in browsers as well as mobile > devices > 3. Great documentation > 4. Future-proofing regarding GWT 3.0, using only JS-Interop with no widgets > 5. I use Vaadin's generator directly (not the packaged JAR) so we can > upgrade Polymer version any time a new version is available > > On Friday, November 18, 2016 at 1:45:26 AM UTC+2, tbb wrote: >> >> Hi all, >> >> I've got a 3 year old enterprise GWT app which also has a mobile app >> based on GWT. Our current design style is based on Bootstrap. As things >> change, I'd like to freshen the UX by using Material Design. I've seen 2 >> libraries: GwtMaterialDesign and gwt-polymer-elements. >> >> From what I can see: >> - Both showcases look great, esp both seem to have an "enterprise" class >> table/grid control. >> - GwtMaterialDesign: Read quite positive things in terms of community. >> - gwt-polymer-elements: By Vaadin which are quite active in the GWT world >> now, based on "real" Polymer elements and the new GWT 2.8 elemental (?) >> >> Would be great if anyone could comment on using either of them as I think >> once we've decided for one of the libraries, it will be hard to switch. >> >> Any feedback would be great! >> >> Thanks, >> Thomas >> >> >> >> -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: GwtMaterialDesign vs gwt-polymer-elements
Hi there, GWT Material contributor here. It is frequently said that one of the "cons" of using GWT Material is that it is based on Widgets and it is not "future-proof". Well, about that, what I can say is: we support the current, stable version of GWT. So you can use GWT Widgets alongside GWT Material Widgets, and/or port your old GWT app to Material piece by piece, instead of having to port everything right away. That said, when GWT 3.0 will be released, GWT Material will support it. If that means dropping support of Widgets, we will do, while not breaking existing code whenever possible. If you want to stay away from UiBinder and use a more designer-friendly framework, GWT Material also works with Errai, It's nice to know that some of your are mixing Polymer and GWT Material. That can really empower your apps in nice ways. Keep the feedback coming =) -- Gilberto -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: GWT 2.8 generates code 14% bigger than GWT 2.7
Do you use SSO ? SSO script is smaller then no SSO. Did you run CC on it ? 29 нояб. 2016 г. 17:29 пользователь "Etienne Basso" написал: > Hi Ignacio, > > This is not only about loading time over the network, but also about > script parsing by the web browser. > In 98% of the case this is not an issue, but I have a very specific use > case were the code is directly embedded on a special device which doesn't > even have a real CPU but an ASIC emulating one. This device is really > really not powerful and GWT is the only framework providing decent speed. > I noticed significant differences in the script parsing delay as js sources > are getting bigger. > > In my case 100KB are a huge deal. > > Le samedi 26 novembre 2016 09:56:27 UTC+1, Ignacio Baca Moreno-Torres a > écrit : >> >> But IMO if you really care user experience you have other places to >> improve your page. I thinks updating to the last version is always a good >> idea, if any security or compatibility blocker problem is detected in your >> version you will need to update, and having a old version won't help. Also >> this helps move forward the community and the lib (GWT), because everyone >> focused in the last version, also focus the issues and improvements in that >> version. >> >> The small step back eliminating the closure compiler just increase a bit >> the code size of your app. But 100k?! did you see the trends and the >> average code size of webs? http://httparchive.org/t >> rends.php?s=All&minlabel=Nov+15+2014&maxlabel=Nov+1+2016, you should >> note that even google.com uses 500k in 13request to load, and it's >> ""just"" a text inbox in the center of your window ( >> http://httparchive.org/viewsite.php?pageid=70036564). >> >> I might be wrong, but probably trying to embed the app.nocache.js in your >> index.html will gain some milliseconds, probably just that dummy change >> will get more ms than the cache-ables 100k you have lose without the >> closure pass. If your app is quite big, various MBs, you should take care >> than the first split point load a minimum as possible to show something to >> the user. But, in your case, less than a 1M, I think that using split point >> is not a good idea. Your code will get cached, and most of static apps >> already has more than 500k of JS, so your single page app having a 500k-1M >> of JS is pretty reasonable. >> >> You can go forward and apply the progressive web concepts ( >> https://developers.google.com/web/progressive-web-apps/checklist). >> Pretty sure you get there without the closure compiler ;). Service workers >> will allow maximum control to preload other split point or resources, and >> to absolutely control how your app caches, so you can use previous version, >> load the next one and in the next page reload the new app version will be >> used. This is not easy at all, but... some time we focus on the >> optimization we have no control of (like the closure pass) and we don't >> apply other we have control of, but that requires our effort. >> >> So, 😀 update to GWT 2.8! it's awesome!, try other solutions to improve >> page loads and share how you do it! >> >> On Friday, November 25, 2016 at 10:39:44 PM UTC+1, Slava Pankov wrote: >>> >>> @Jens >>> >>> I've tried WITHOUT any success to use closure compiler externally with >>> GWT 2.8 >>> See my question here: https://groups.google.co >>> m/forum/#!searchin/google-web-toolkit/closure$20compiler% >>> 7Csort:date/google-web-toolkit/k_kjIv9Klsg/LZAZiUf9BAAJ >>> Still want to find out exact steps to get it working :-( >>> >>> >>> On Friday, November 25, 2016 at 2:43:11 AM UTC-8, Kirill Prazdnikov >>> wrote: Hi Jens, What if we have SSO linker ? Then no hacks is needed, right ? Then just run the Google Closure Compiler on the output. >>> -- > You received this message because you are subscribed to a topic in the > Google Groups "GWT Users" group. > To unsubscribe from this topic, visit https://groups.google.com/d/ > topic/google-web-toolkit/IIQk4xH0-g8/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > google-web-toolkit+unsubscr...@googlegroups.com. > To post to this group, send email to google-web-toolkit@googlegroups.com. > Visit this group at https://groups.google.com/group/google-web-toolkit. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: GWT 2.8 generates code 14% bigger than GWT 2.7
Hi Ignacio, This is not only about loading time over the network, but also about script parsing by the web browser. In 98% of the case this is not an issue, but I have a very specific use case were the code is directly embedded on a special device which doesn't even have a real CPU but an ASIC emulating one. This device is really really not powerful and GWT is the only framework providing decent speed. I noticed significant differences in the script parsing delay as js sources are getting bigger. In my case 100KB are a huge deal. Le samedi 26 novembre 2016 09:56:27 UTC+1, Ignacio Baca Moreno-Torres a écrit : > > But IMO if you really care user experience you have other places to > improve your page. I thinks updating to the last version is always a good > idea, if any security or compatibility blocker problem is detected in your > version you will need to update, and having a old version won't help. Also > this helps move forward the community and the lib (GWT), because everyone > focused in the last version, also focus the issues and improvements in that > version. > > The small step back eliminating the closure compiler just increase a bit > the code size of your app. But 100k?! did you see the trends and the > average code size of webs? > http://httparchive.org/trends.php?s=All&minlabel=Nov+15+2014&maxlabel=Nov+1+2016, > > you should note that even google.com uses 500k in 13request to load, and > it's ""just"" a text inbox in the center of your window ( > http://httparchive.org/viewsite.php?pageid=70036564). > > I might be wrong, but probably trying to embed the app.nocache.js in your > index.html will gain some milliseconds, probably just that dummy change > will get more ms than the cache-ables 100k you have lose without the > closure pass. If your app is quite big, various MBs, you should take care > than the first split point load a minimum as possible to show something to > the user. But, in your case, less than a 1M, I think that using split point > is not a good idea. Your code will get cached, and most of static apps > already has more than 500k of JS, so your single page app having a 500k-1M > of JS is pretty reasonable. > > You can go forward and apply the progressive web concepts ( > https://developers.google.com/web/progressive-web-apps/checklist). Pretty > sure you get there without the closure compiler ;). Service workers will > allow maximum control to preload other split point or resources, and to > absolutely control how your app caches, so you can use previous version, > load the next one and in the next page reload the new app version will be > used. This is not easy at all, but... some time we focus on the > optimization we have no control of (like the closure pass) and we don't > apply other we have control of, but that requires our effort. > > So, 😀 update to GWT 2.8! it's awesome!, try other solutions to improve > page loads and share how you do it! > > On Friday, November 25, 2016 at 10:39:44 PM UTC+1, Slava Pankov wrote: >> >> @Jens >> >> I've tried WITHOUT any success to use closure compiler externally with >> GWT 2.8 >> See my question here: >> https://groups.google.com/forum/#!searchin/google-web-toolkit/closure$20compiler%7Csort:date/google-web-toolkit/k_kjIv9Klsg/LZAZiUf9BAAJ >> Still want to find out exact steps to get it working :-( >> >> >> On Friday, November 25, 2016 at 2:43:11 AM UTC-8, Kirill Prazdnikov wrote: >>> >>> Hi Jens, >>> >>> What if we have SSO linker ? >>> Then no hacks is needed, right ? >>> Then just run the Google Closure Compiler on the output. >>> >> -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Dikalo early access
We are not quite ready yet. But if you like to see what we have in mind with Dikalo please visit https://www.dklo.co Expect lots of bugs. Specially on mobile. Cheers, Alain -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: GWT 2.8.0 released
Hi Daniel, I am using GWT 2.8.0 and using -generateJsInteropExports with Polymer to access GWT elements, however I was able to get it successfully with 2.8 RC2 but getting error with 2.8 final version, gwt-elements.html:72 Uncaught ReferenceError: com is not defined(…)attached @ gwt-elements.html:72_invokeBehavior @ polymer-micro.html:455_doBehavior @ polymer-micro.html:445(anonymous function) @ polymer-micro.html:227whenReady @ polymer-micro.html:107attachedCallback @ polymer-micro.html:225attachedCallback @ polymer-mini.html:104QX_g$ @ MBAApp-0.js:6137Awc_g$ @ MBAApp-0.js:14157a2b_g$ @ MBAApp-0.js:10126initializeModules_0_g$ @ MBAApp-0.js:28Rp_g$ @ MBAApp-0.js:4391Up_g$ @ MBAApp-0.js:4461(anonymous function) @ MBAApp-0.js:4427t1b_g$ @ MBAApp-0.js:41(anonymous function) @ MBAApp-0.js:24127 getting this error. Can you please suggest. Thanks, Gaurav On Saturday, 22 October 2016 00:51:41 UTC+5:30, Daniel Kurka wrote: > > Hi all, > > I am very happy to announce GWT 2.8.0 on behalf of the GWT steering > committee and the GWT team at Google. > > You can download the release from http://www.gwtproject.org/download.html > or from maven central. > > The release notes can be found at > http://www.gwtproject.org/release-notes.html#Release_Notes_2_8_0 > > Daniel, > on behalf of the GWT team > -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: Adding Material Design Inherits elements to already existing vanilla GWT project changes the main look of the application
This is normal behaviour. Material will change the css of many default elements like textboxes. If you want only your loginscreen to look as Material, than write your own css styles (by looking at material css styles) with specific names that you only use on loginpanel. -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
