While we post the source code to every release of webOS, we have held back in posting the changes directly to webkit org for several reasons:
* webOS versions 1.0.x-1.3.x have been based on webkit3, and the code on webkit-trunk has changed significantly since then * many changes we have made are specific to making our JavaScript framework run fast, and quite frankly I suspect these would be rejected by the group since they are JS framework-specific; i.e., I do not want to waste the group's time. That being said, with webOS 1.4 (released last week) we are now only several months off of trunk, so we plan on being much more active now that we are closer to TOT. We will always lag TOT due to our own internal product requirements. Greg On 3/10/10 10:13 AM, "Darin Adler" <[email protected]> wrote: On Mar 10, 2010, at 10:06 AM, Greg Simon wrote: > This would be a really great topic for the webkit meeting in April. At Palm > we spend a significant amount of development time dealing with memory > "growth" (not so much leaks). Google perf tools has worked very well for us > on desktop as it gives the complete call stack showing how the allocation was > made. On device, we use a lot of live object instance monitoring. Anyway it > would be great to share some tips and tricks with other folks. I would love to hear more about it. Did any of this development work lead to bug fixes for WebKit? Please note that the meeting in April is for WebKit contributors. People using WebKit but not yet contributing to the open source project should not attend. I mention this because I don't remember contributions from engineers working at Palm, although I may have missed them. -- Darin
_______________________________________________ webkit-dev mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
