Feature Detection
Hello, I question on doing 2 things. I was wondering what works best. So please feel to offer any advice you may think apropiate. *1e* Feature detection.: We want to know wheter a device is touch enabled. Some feedback should work different when handled with a mouse. Title and such do not add value on a tablet but can save space on a desktop when using a mouse. Anybody doing this. *2e* Form Factor detection. We want to do some things different when on a phone or tablet than for instance on a desktop. Mostly disable thing of breakup flows. For the form factor we where using mgwt but it just adds to much overhead and stuff. Thanks -- 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-interop-utils release on Maven Central
Thank you! On Saturday, June 18, 2016 at 5:28:57 PM UTC-7, Paul Stockley wrote: > > I have pushed an initial version of gwt-interop-utils to Maven Central. > Thanks for everyone's feedback. I have incorporated what I think makes > sense. The documentation has been updated to reflect the changes. > > I am sure the library will evolve as GWT2.8 gets closer to release and we > see what elemental 2 brings. > > I have updated all of the GWTReact projects to use gwt-interop-utils and > pushed new versions to Maven Central. > > My focus now is to make React and MobX production ready. > > https://github.com/GWTReact/gwt-interop-utils > -- 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 Material Design Addins
I'd recommend posting such issues on https://github.com/GwtMaterialDesign You can also visit those guys on https://gitter.im/GwtMaterialDesign/gwt-material It's quite active in there so give it a try :) On Monday, 20 June 2016 00:39:47 UTC+2, Velusamy Velu wrote: > > Thank you, your response triggered me to revisit this issue. I made two > changes to my code and tested successfully. > >1. Upgraded to gwt-material-1.5.1.jar >2. Changed the name space to >xmlns:ma="urn:import:gwt.material.design.addins.client.window" >and declared the window as--> > It works now. If I follow what's suggested in the documentation ( > http://gwtmaterialdesign.github.io/gwt-material-demo/#window) it still > fails. > > I hope it helps. > > On Sunday, June 19, 2016 at 5:40:51 AM UTC-4, Jaroslav Záruba wrote: >> >> Reading your message again I believe I misunderstood your issue. I got >> nothing rendered, you are referring to invalid UiBinder XML. >> >> Dne středa 11. května 2016 18:07:09 UTC+2 Velusamy Velu napsal(a): >>> >>> I followed these steps to use the MaterialWindow addin from the >>> gwt-material-addins-1.5.0.jar in an application. >>> >>>1. Downloaded gwt-material-addins-1.5.0.jar and added to >>>application's build path in Eclipse. >>>2. Added the line in the ..gwt.xml >>>3. Added the line >>>xmlns:ma="urn:import:gwt.material.design.addins.client" in the >>>UiBinder. >>>4. Then started adding the line >>"window" width="50%" title="Documents"> in the UiBinder >>> >>> But MaterialWindow is not visible to the UiBinder. Any idea what could >>> be wrong? >>> >> -- 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: Unable to access exported JsType from JavaScript
Hi, > Looking at your code, the class would be available at "blah.WebUI", but > you'd have to create a new instance before your can call your method, and > given how you initialize it you'd have to call onModuleLoad before that. > Maybe if you make your method and all the fields 'static' that'd work; > either that or move the initialization in the class constructor (and maybe > use another class as the EntryPoint to avoid a double initialization). > Thanks for the pointer, it works! I can do the following in JS: x = new blah.WebUI(); x.onModuleLoad(); x.runAndGetRegisters(); I don't know how I missed it. :) Again, thanks a lot for the pointer. Cheers, Andrea -- 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: Unable to access exported JsType from JavaScript
Hi, > Did you forgot to add -generateJsInteropExports to the compiler parameters? > I set it for both devmode and production code: https://github.com/lupino3/edumips64/blob/jsinterop/build.xml#L104 Is it set in the right way? Thanks! Andrea -- 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.
