Wt

h1. Ideas for Google SoC

This page lists ideas for Google SoC 2010 applications for Wt, pending the approval of Emweb as a mentoring organisation.

Contact information: koen@emweb.be or the Wt interest mailinglist: witty-interest@sourceforge.net.

h3. WebKit integration

The idea is to integrate WebKit into Wt. The level of integration may evolve over time, as are the possible applications.

The first step is to combine WebKit with the built-in httpd to provide a desktop application using Wt. This could be useful for distributing an off-line version of a Wt application or during development. The webkit would be configured to act as a single application (instead of as a general purpose browser). Some preliminary work has been done and the project has been bootstrapped by Pau, which can be found at http://gitorious.org/wtdesktop.

In a second step, some of the widgets provided by Wt could be made aware of the integration with webkit to provide improved functionality. For example, WFileUpload could use a native file open widget instead of HTML. Other features are the binding of WApplication::quit() to exit the actual application, and the ability to control and use the native menu provided by the Qt or GTK toolkit from Wt code.

A third level of integration is to allow introspection of the DOM inside WebKit from a Wt application session. This could become the basis for an automated testing framework which verifies that the widget tree and the DOM tree are in sync. By querying the DOM for information on the location and CSS properties of widgets, it can be checked that the application works properly. By allowing for events to be simulated on the DOM tree, the application can be checked for correct event handling.

The fourth level of integration is to by-pass the HTML/JavaScript and HTTP protocol for certain rendering steps. For example, a new WPaintDevice could be developed which paints directly instead of encoding it first as SVG or HTML Canvas5 JavaScript. This would allow significant speedups for vector graphics.

Required expertise: Good C++ knowledge, knowledge of or willing to learn the CMake build system, familiarity with GTK or Qt application development.

The scope and goals of this idea can be adapted to the skill set of the student, since for every additional level of integration, more detailed intimate knowledge of WebKit and Wt are required. Since the project has already been bootstrapped, the student will be able to more directly start actual development rather than be busy with setting up and configuring the build system.

h3. Widget set mode

Since about a year, Wt includes a so-called widget-set mode. In this mode, a Wt application does not take responsibility to render the entire user interface, but only selected 's. The Wt application is loaded as a JavaScript library, which then renders into these <div>'s, which then correspond to a set of "top-level" widgets. Any of Wt's features may be used inside such a widget, including portable vector graphics.

This would allow a Wt application to also expose a JavaScript API, such as for example Google Maps, but this has not yet been provided. To provide support for this in the Wt library, it would require that a Wt application can extend its JavaScript object with JavaScript methods that map onto C++ methods, which assumes a system that helps as much as possible to convert between JavaScript objects and C++ data structures (for example based on maps).

Improvements to widget set mode will allow easy development of OpenSocial applications in Wt.

Required expertise: Good C++ knowledge, some JavaScript knowledge.

h3. Wt Designer

Since Wt shares alot with Qt, in terms of API and programming model, it should be possible to adapt Qt Designer to design Wt widgets.

In a first step, the .ui format used by the Qt Designer tool and User Interface Compiler (UIC) could be adapted to so that it can be used to instantiate a custom Wt widget at runtime, or can be used to compile to a C++ file.

More details (detailed steps, roadmap, possible blockers, etc) here: http://article.gmane.org/gmane.comp.web.witty.general/4293

Required expertise: Good C++ knowledge, experience with Qt Designer is a plus.

h4. MVC integration of Wt::Dbo models with Wt views.

• Implement a WAbstractItemModel (e.g. WDboQueryModel) that allows iteration of query results.
• There could also be support for editing/viewing data of a single Dbo.

Required expertise: Good to Expert C++ knowledge (template meta programming)

h3. WSocketNotifier

Implement WSocketNotifier (like QSocketNotifier) properly with a custom select loop. The current implementation (on httpd) tries to tie into asio's select loop, but asio does not support this use-case very well (with socket numbers instead of boost asio's socket abstraction).
It is also possible to wrap a socket completely to WSocket and define specific use cases for Wt applications communicating with other applications/web services ect.

h3. Modifications of WTemplate to provide a full grown templating system

Goals:

• Wt will create widgets based on tags in message bundles.
• Each property can be set through an attribute.
• Creating a declerative markup that can be generated by an IDE.
• Creating a templating language that can take a model and generate a display for it. Possible commands are: If, Else, Foreach, While, Query

All of those features should be disabled to discard this overhead when working on thight embedded machines.
Instead of binding widgets like now you would just get them using resolve.