September 25, 2013

   -

   Hangout on air today
   -

   Matt shared the GWT 2.6 release plan
(doc<https://docs.google.com/a/google.com/document/d/1ZdMwcTjc4rkWg6nntCY1BDB1xI2PHPwaCnTYw-9uAKE/edit>
   )
   -

   feature-complete November 4th. Release on December 2.
   -

   Bhaskar: which features?
   -

      Separate compilation: experimental at best; overly ambitious.
      -

      IE10 support? Seems important.
      -

      IE6/7? Deprecate, but make sure people can still use it.
      -

      Devmode? Need to deprecate because Chrome is dropping NPAPI, Firefox
      could break at any time.
      -

      SuperDevMode? Talked about IDE support. Not fast enough; would be
      good at least get separate compilation in, perhaps as experimental.
      -

      Brian and Ray: maintaining Eclipse has been a hassle in the past.
      Ray: we should keep the Eclipse plugins decoupled from GWT
releases so that
      we don't have to do a new release with each GWT release.
      -

      Goktug: SuperDevMode is better than DevMode for me today.
      -

      Bhaskar: I thought Dart had some Eclipse code. Brian: they do but
      someone still has to maintain the plugin.
      -

   Ray: implemented the first part of JsInterop spec. Seems to be working
   well so far. Turning on exports by default would result in code bloat; need
   some user controls to trim that down; don't want to export dependencies.
   Goktug: how does this work with JSO's? Ray: if the JsInterface doesn't have
   a prototype it can be cross-cast to anything. But if it has a prototype
   then it can't. Tricky logic. Ray: ran into issues with subclassing; if you
   subclass then you're forced to implement everything; this prevents calling
   the prototype method via super.
   -

   Colin's feedback:
   -

      Still need devmode for IE. Brian: don't know status of sourcemaps on
      IE. We can keep it for IE for now but support for JsInterop will be hard.
      -

      What about code coverage? Brian: We need web mode code coverage to
      replace Emma. A patch landing soon that might help. Ray: will respond in
      the review; it's not pluggable enough.
      -

      Better typed array support in 2.6? Brian: concerned about enabling it
      by default until we have more experience. Ray: we can have a
compiler flag;
      experimental feature? Most permutations can use it.
      -

   Daniel has a fix for type checks on array stores (still on when checking
   is off). Will result in a big speedup for arrays.
   - John: has a feature-complete prototype that mostly works; now time to
   clean up. Generators need to be configured based on how local they are.
   Wants to change GWT-RPC generator to generate code from a whitelist for
   which types can be used for separate compilation. Ray: how do entry points
   work? John: currently modified existing entry points; need to revisit this.

-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors
--- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to