September 18, 2013 Talking about Q4 goals: * Separate compilation: more people to help John? How to divide the work? Java / JavaScript integration: Ray says he's going to be working on this for Q4, along with Closure compiler integration. * SuperDevMode: fast compile cycles is most important. Brian: got experimental debugger working with Showcase; going to look again at Eclipse plugin. Ray: wrote a servlet to integrate with SuperDevMode so it's always on for dev server. Maybe create a common Super Dev Mode servlet? Performance dashboard (Daniel's project) * Open source: 2.6 Release (Matthew); Hangout next week. * Goktug: want to work on Gin improvements. (Shouldn't take a lot of time.) * More resources on deprecation cleanup? Brian: Matthew doing a great job, continue as-is? Maybe do more in Q1. * John's status: half the generators depend on property values; will have to re-run in each Library when properties change. GWT-RPC generator will need to be global. Ray: maybe CompilationStateBuilder should start with entry points? John: looks like it would be 20% gain. Ray: cheap pruning pass in UnifyAST? Roberto: already happens pretty early. Ray: reports about unused files? Roberto: made some but not useful so far. Brian: intern starting on Sept 30 who will be working on soyc reporting. Talked about what he could do. * Goktug: HTMLUnit upgrade is about ready. Not submitting because HTMLUnit is about to do a release so he will wait and pick that up. * Ray: has a patch to watch filesystem in Super Dev Mode. Brian: great, send it to me.
September 11: - Goktug: GWT incubator needs be officially deprecated and removed 400 references to incubator. - Brian's debugger demo: (An alternate Chrome debugger frontend written in Dart; testbed for experiments.) Ray: Nodeclipse looks interesting. (Fork of Chrome's Eclipse plugin) - Daniel talked about opportunities for making GWT run faster on V8. Need to avoid changing object shapes. Lazy initialization is an issue. Ray: maybe revert to the old way of doing it? However we need to avoid increasing code size; for example, using any DOM method once pulled in the whole implementation. Brian: put lazy initialized fields in a sub-object? - Roberto talked about code-splitting Fixed a bug in Codesplitter v1 (which most people are using). v2 is less correct than v1 because it's missing some JavaScript-level dependency fixups. Refactoring the common code that will also be used for v3. Goktug and Ray: we also need a way for developers to manually force a splitpoint. -- 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.
