On Fri, Apr 1, 2011 at 11:36 AM, joe kolba <joekolba09@gmail.com> wrote:
1. What do you mean 'cannot run a java server efficiently'? Do you mean that you can't access an on-line service reliably on a mobile device?- I meant running tomcat or jetty on a tablet device in order to use GWT RPC for client / server communication. I know there are ways of installing jetty (iJetty) on android devices but I just don't see it being a good solution.- I agree that all of this can be done using JSNI, but I think it would be useful if the GWT Widgets supported webkit database connections in order to store and retrieve data on the client side. There is currently a project: http://code.google.com/p/gwt-mobile-webkit/ that seems to be headed in the right direction. I was just curious if Google was considering using GWT as a android app development tool.
2. Nothing is stopping you from writing a JSNI binding to anything which is available in the browser. If the browser has support for the feature, then you can determine that with one or two lines of javascript and then use it. For example, there are bindings to HTML5 features such as WebGL and other capabilities like XMPP (gwt-strophe). One of the nice things about GWT is that it is comparatively easy to extend and tune your application's capabilities because of the infrastructure work that Google has already done.
On Fri, Apr 1, 2011 at 11:29 AM, Alan Chaney <alan@mechnicality.com> wrote:Hi Joe
I'm nothing to do with google, but your question is interesting:1. What do you mean 'cannot run a java server efficiently'? Do you mean that you can't access an on-line service reliably on a mobile device?
On 4/1/2011 8:12 AM, joe kolba wrote:
Do you think GWT will eventually support offline app development by incorporating Webkit local database support? My company I work for is currently researching developing ipad/android web apps. Since we cannot run a java server efficiently on these devices we are considering going with HTML5, javascript and css3 to create large business applications.
2. Nothing is stopping you from writing a JSNI binding to anything which is available in the browser. If the browser has support for the feature, then you can determine that with one or two lines of javascript and then use it. For example, there are bindings to HTML5 features such as WebGL and other capabilities like XMPP (gwt-strophe). One of the nice things about GWT is that it is comparatively easy to extend and tune your application's capabilities because of the infrastructure work that Google has already done.
It seems to me that the bigger issue right now is that Webkit local database support doesn't actually seem to be supported in the mainstream browsers.
Regards
Alan
--
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+unsubscribe@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+unsubscribe@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+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
No comments:
Post a Comment