Thank you for your investigation and for dialing down the tone a bit.
I'm pleased that the GWT team has done such a good job in the past
that you've come to expect not only a great, free toolkit, but also
updates delivered within days of new browser and OS releases. Unfortunately,
the Google instant search team hasn't yet tackled the instant dev mode
plugin problem ;-) The recent FF and Safari changes caught us by
surprise. The timing is particularly bad as lots of folks are on
summer vacation, and hiring doesn't happen overnight. Rest assured
that engineering management is aware of the "plugin crisis" and we are
working to address the situation; however, I cannot give you an ETA.
Please be patient.
Also, please be advised that I will be on vacation for the next couple
weeks. I will not be reading this group during that time, and very
likely no one will be responding to general GWT inquiries during that
time, although engineers will continue to chime in on specific
technical issues as always. New member moderation may also be slower
than usual. It is not typical to announce vacation on the GWT group,
but I wanted to give Thomas Broyer a message to link to in response to
any "Why hasn't the GWT team responded to X" threads that may emerge.
Thanks for all you do, Thomas :-)
Best,
/dmc
On Tue, Jul 26, 2011 at 12:11 PM, Eric Ridge <eebbrr@gmail.com> wrote:
> On Mon, Jul 25, 2011 at 6:29 PM, Eric Ridge <eebbrr@gmail.com> wrote:
>> On Mon, Jul 25, 2011 at 5:55 PM, David Chandler <drfibonacci@google.com> wrote:
>>> Good luck, Eric :-) It likely requires non-trivial changes (which is
>>> why the GWT team hasn't done it yet).
>>
>> It's not clear yet what'll be required. It looks like whoever wrote
>> the current plugin did a pretty decent job of separating concerns.
>
> What's required is a ton of work. The current plugin is tied directly
> to the JavaScriptCore API which, as best I can tell, can't be made
> available via the NPAPI. (if it could, the conversion would likely be
> straight forward).
>
> And since Safari 5.1 (WebKit2) runs plugins out-of-process, it makes
> me think that the plugin would be terribly slow... similar to Chrome's
> performance. But that's just conjecture.
>
> If I had 2-3 weeks I could definitely get the plugin working, but
> alas, hacking GWT Plugins is not in my RealJob description. Jurriaan
> Mous' workaround is good enough for now.
>
> And David, for what it's worth, the fact that this "likely requires
> non-trivial changes" is all the more reason why the GWT team should
> have started on it already. GWT is billed as being cross-platform,
> and y'all have definitely put in tremendous effort making that true.
> You've created something extremely powerful and developed a very large
> and dedicated community. With that comes responsibility.
>
> Your other email that said "Dev mode plugins are open source, so if
> someone has interest in keeping them up to date, we're all ears..." is
> a bit disingenuous. Sure, all of GWT is open source, but frankly, the
> community views it as being developed and maintained solely by Google.
> If what you're saying is that Google isn't going to maintain the
> plugins anymore, that's a pretty big deal. But if you're just
> complaining that the GWT team doesn't have the internal resources to
> keep pace with browser vendors, then my previous suggestion stands...
> hire someone to do that work.
>
> eric
>
--
David Chandler
Developer Programs Engineer, GWT+GAE
w: http://code.google.com/
b: http://turbomanage.wordpress.com/
b: http://googlewebtoolkit.blogspot.com/
t: @googledevtools
--
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