Google Summer of Code 2008 WebKit Project Ideas: * SVG * [http://www.w3.org/TR/SVG/filters.html SVG Filters] - Implement a platform-independent set of c++ based SVG filters. Currently only the Mac platform has a filters implementation (CoreImage based) which is disabled in tip of tree WebKit. * Fix our [http://www.w3.org/TR/SVG11/animate.html SVG Animation] implementation - we can't pass [http://acid3.acidtests.org/ Acid3] without it * [http://bugs.webkit.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&field0-0-0=product&type0-0-0=substring&value0-0-0=svg&field0-0-1=component&type0-0-1=substring&value0-0-1=svg&field0-0-2=short_desc&type0-0-2=substring&value0-0-2=svg&field0-0-3=status_whiteboard&type0-0-3=substring&value0-0-3=svg SVG Bug] fighting (clipping redesign, xhtml/svg integration issues, a lot more, please ask) * CSS * Pass the rest of the [http://www.w3.org/Style/CSS/Test/CSS2.1/current/ CSS 2.1 test suite] (and possibly the [http://samples.msdn.microsoft.com/csstestpages/default.htm new suite from Microsoft]) * CSS3 Paged Media - Add support for [http://www.w3.org/TR/css3-page/ CSS3 Paged Media], or a subset thereof. Currently we have no support in WebKit. * Support for CSS3 calc() - See [http://www.w3.org/TR/css3-values/#calc the spec] * Other new specifications/Features * [http://www.w3.org/TR/REC-MathML/ MathML] (at least the presentational parts, can get very far with a stylesheet only) * [http://www.w3.org/TR/ruby/ Ruby Annotation] Support * [http://www.whatwg.org/specs/web-apps/current-work/ HTML 5] Offline Web Applications support - http://www.whatwg.org/specs/web-apps/current-work/#offline * [http://www.w3.org/TR/html5/#datagrid HTML 5 ] support * [http://www.mozilla.org/projects/xbl/xbl2.html XBL2] (fairly hard) * canvas 3d extensions a la [http://wiki.mozilla.org/Canvas:3D mozilla] or [http://my.opera.com/timjoh/blog/2007/11/13/taking-the-canvas-to-another-dimension opera] * canvas text drawing [http://developer.mozilla.org/en/docs/Drawing_text_using_a_canvas mozilla] * [http://www.w3.org/TR/wai-aria/ ARIA] - Accessible Rich Internet Applications * [http://www.whatwg.org/specs/web-forms/current-work/ Web Forms 2] * MHTML support (Microsoft's "web archive" equivalent) (see http://bugs.webkit.org/show_bug.cgi?id=7168 and http://bugs.webkit.org/show_bug.cgi?id=7169) * Support output of "Web page, complete" format (see http://bugs.webkit.org/show_bug.cgi?id=7211) * JavaScript Engine Work * Interruptible JavaScript evaluation * Generational JavaScript garbage collection * Improved source syntax highlighting * Platform Ports * Native Windows port -- there has been effort underway to create a Native Windows port that does not require Apple's (non-redistributable) libraries. More help in this effort would be useful. * Windows Mobile port -- there has been mention of at least 3 Windows Mobile ports of WebKit. It would be useful to create and/or consolidate a single Windows Mobile port integrated into the main WebKit trunk. * Cairo -- SVG backend completion (gradients, patterns and other bug fixes to make the test suite results match the CG backend) * Qt -- SVG backend completion * Gtk -- ATK accessibility support, or find any bug (use [http://bugs.webkit.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&field0-0-0=product&type0-0-0=substring&value0-0-0=gtk&field0-0-1=component&type0-0-1=substring&value0-0-1=gtk&field0-0-2=short_desc&type0-0-2=substring&value0-0-2=gtk&field0-0-3=status_whiteboard&type0-0-3=substring&value0-0-3=gtk this search]) that will take an appropriate length of time to fix * Developer Tools * Anything on the [wiki:"Developer Tools Hitlist" Developer Tools Hitlist] * Drosera improvements * Tree view of local variables that show properties of objects (right now we just show top-level stack variables) * Live evaluation of JavaScript in the current document's context (when the debugger isn't paused) * Inline editing of scripts * Pretty print scripts that are all on one line * Browse the DOM of the host document from within Drosera (using the Web Inspector) * Better syntax highlighting (done in the engine with HTML highlighting) * Web Inspector improvements * Viewing the render tree (with the ability to see what DOM node corresponds to a render object, and visa versa) * Set Drosera breakpoints on script elements and event handler element attributes (e.g. onclick, etc.) * Better node highlight overlay that shows margin and padding boxes * Improved JavaScript properties pane * Improved Metrics pane * Syntax highlighting for JavaScript * Syntax highlighting for CSS * Other JavaScript debugging tools * Memory allocation logging tool * Event dispatch watching * Javascript profiler * Developer tool of your own design * Development Infrastructure * Automated WebKit API regression tests (testing the Obj-C, COM, C++ APIs exposed on various platforms) * Improvements for DHTML application UI development: * Focus and Keyboard Navigation improvements for DHTML applications (see http://bugs.webkit.org/show_bug.cgi?id=7138) * Add ARIA support for adding semantics to DHTML application user interface nodes (see http://bugs.webkit.org/show_bug.cgi?id=12132) * See http://developer.mozilla.org/en/docs/Accessible_DHTML for more ideas. * ''more project ideas go here here'' 2008 Mentors: * Eric Seidel < eric at webkit >, MacDome on #webkit (administrator) * Nikolas Zimmermann < zimmermann at webkit > , WildFox on #webkit (backup administrator) * Adam Roben < adam.roben at gmail >, aroben on #webkit * Brady Eidson < beidson at gmail >, bradee-oh on #webkit * David D. Kilzer < ddkilzer at gmail >, ddkilzer on #webkit * Maciej Stachowiak < maciej at gmail >, othermaciej on #webkit * Mark Rowe < mark.rowe at gmail >, bdash on #webkit * Rob Buis < rwlbuis at gmail >, rwlbuis on #webkit * Sam Weinig < sam.weinig at gmail >, weinig on #webkit * Simon Hausmann < hausmann at gmail >, tronical on #webkit * Timothy Hatcher < timothy.hatcher at gmail >, xenon on #webkit * (Still waiting to hear from the rest of the 30+ reviewers) * Policy: All mentors must be WebKit committers (this serves two purposes: 1. you can help your student get their patches landed. 2. you've demonstrated knowledge of the webkit code base, and ability to work with the community.) Any reviewer (see http://webkit.org/coding/commit-review-policy.html) who applies to be a mentor will be accepted (and are welcome to mentor in any area they feel comfortable in). Other committers who is not yet a reviewer but would like to mentor should email me (eric at webkit), and we'll work something out.