Re: Dart and GWT
The Dart Editor team is primarily focused on the standalone RCP-based editor as it gives a much better experience (e.g., smaller and much faster) than would an Eclipse plugin running in Eclipse. At the moment, we don't have plans to provide a plugin for Eclipse, but most of the pieces are there if someone else wanted to do it (that would be a great open source contribution from someone in the community). The plugins used by the Dart Editor could likely be reused and and new plugin would need to be created to support the Eclipse-integrated solution. -- 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/-/zDs9EuwZyecJ. 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: Dart and GWT
Hi Eric, I saw the Dart Editor (Linux, Mac, Win). It's a standalone editor based on Eclipse UI. Is there a real Dart plugin for Eclipse ? If not, do you plan to provide one ? 2011/11/11 Eric Clayberg (Google) > See... http://googlewebtoolkit.blogspot.com/2011/11/gwt-and-dart.html > > The Google Web Toolkit team has been asked recently about our plans > following the announcement of the Dart programming > language<http://dartlang.org/> a > few weeks ago. > > > Dart and GWT both share the goal of enabling structured web programming. > In fact, many of the same engineers who brought you GWT are working on > Dart. We view Dart as an ambitious evolution of GWT’s mission to make web > apps better for end > users<http://code.google.com/webtoolkit/makinggwtbetter.html#introduction>, > and we’re optimistic about its potential. As Dart evolves and becomes ready > for prime time, we anticipate working closely with the GWT developer > community to explore Dart. > > > Meanwhile, rest assured that GWT will continue to be a productive and > reliable way to build the most ambitious web apps — and even games like > Angry Birds. Key projects within Google rely on GWT every day, and we plan > to continue improving (and open-sourcing) GWT based on their real-world > needs. > > -- > 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/-/WzBPyXZ1GdgJ. > 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: Dart and GWT
See... http://googlewebtoolkit.blogspot.com/2011/11/gwt-and-dart.html The Google Web Toolkit team has been asked recently about our plans following the announcement of the Dart programming language<http://dartlang.org/> a few weeks ago. Dart and GWT both share the goal of enabling structured web programming. In fact, many of the same engineers who brought you GWT are working on Dart. We view Dart as an ambitious evolution of GWT’s mission to make web apps better for end users<http://code.google.com/webtoolkit/makinggwtbetter.html#introduction>, and we’re optimistic about its potential. As Dart evolves and becomes ready for prime time, we anticipate working closely with the GWT developer community to explore Dart. Meanwhile, rest assured that GWT will continue to be a productive and reliable way to build the most ambitious web apps — and even games like Angry Birds. Key projects within Google rely on GWT every day, and we plan to continue improving (and open-sourcing) GWT based on their real-world needs. -- 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/-/WzBPyXZ1GdgJ. 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: Dart and GWT
Thank you for your responses. It is good to here that GWT will continue to evolving. -- 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/-/o4gfAjnn03wJ. 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: Dart and GWT
According to leaked Google mail(https://gist.github.com/1208618) : What is the future of the JSCompiler and GWT? JSCompiler and GWT were already on a merger path. This effort gives us a direction for that unification around the Dash language. We will actively support teams for a long time on the current generation of JSCompiler and GWT and provide fantastic co-existence and migration tools to Dash. -- 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/-/yu4dVxtM5E8J. 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: Dart and GWT
It's probably worth keeping Google's corporate culture in mind. A lot of more or less autonomous teams go about their daily work, trying to solve their own particular problems. There's very little top-down control of the process (unlike, to pick an example at random, a well known company based in Cupertino). FWIW, David Chandler posted some initial thoughts on his personal blog: http://turbomanage.wordpress.com/2011/10/10/first-thoughts-on-dart/ On Oct 17, 3:52 am, Dimitrijević Ivan wrote: > What will be the future of GWT regarding Google's involvement in DART > language development? -- 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.
Dart and GWT
What will be the future of GWT regarding Google's involvement in DART language development? -- 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/-/0jS_q0cESwsJ. 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.
