Wt (pronounced 'witty') is not a 'framework', which enforces a way of programming, but a library.
The API is widget-centric, and inspired by existing C++ Graphical User Interface (GUI) APIs. To the developer, Wt offers complete abstraction of any web-specific implementation details, including graphics support and event handling.
Typical use scenarios:
· Web-based GUIs for web-enabled embedded systems benefit from the low footprint of a C++ web application server.
· Web-based GUIs that require integration with (existing) C++ libraries, for example for scientific or engineering applications.
· Creating a port of existing C++ desktop applications to the web.
Some benefits of using Wt:
· Develop web applications like you develop C++ desktop applications.
· Use the built-in httpd for easy development and deployment, or use the FastCGI connector to deploy as a FastCGI application.
· A single specification for both client- and server-side validation and event handling (when using stateless slot implementations)
· Generates standards compliant HTML or XHTML code.
· Portable, anti-aliased graphics (uses inline VML, inline SVG or the HTML 5 canvas).
· No XSS security risks since Wt has complete control over the presentation layer and proactively filters out active tags and attributes. No exposure of business logic, which stays at the server.
· Ultra-fast load time and low bandwidth usage, which are affected only by screen complexity, not application size.
Here are some key features of "Wt":
· Develop and deploy on Unix/GNU Linux (gcc) or Microsoft Windows (Visual Studio).
· Integrated Unicode support (UTF8/UTF16).
· Incremental rendering of changes to the web page (when AJAX is available).
· Two-phased rendering of changes to the web page, with first visible, and in the background invisible changes (when AJAX is available). When AJAX is not available, only visible contents is rendered.
· Configurable session tracking options that include URL rewriting and cookies.
· Supports timed events and built-in support for server-initiated updates ("server push")
· Support for browser history navigation (back/forward buttons and bookmarks) through a flexible internal path API.
· High performance, allowing deployment on low-end embedded devices, or energy-, space- and budget-friendly deployment of Internet or extranet web sites.
· Completely based on async I/O: sessions are not tied to threads, and neither do delayed responses (e.g. for server push) block threads. Instead, threads are needed only to improve concurrent request handling or for reentrant event loops.
· Listen for keyboard, mouse and focus events, and get event details (such as mouse position, modifier buttons, or keyboard key).
· Uses a template-based signal/slot system for event handling.
· By default, server-side event handling, in C++.
· Easy Drag&Drop API.
Native painting system:
· Unified painting API which uses the browsers native (vector) graphics support (inline VML, inline SVG, or HTML 5 canvas).
· Supports arbitrary painter paths, clipping, text, images, transformations, and stroke and fill styling.
· Use the painting API in conjunction with a WPaintedWidget, or directly using the SVGImage paint device.
· Basic widgets (buttons, HTML anchors, checkboxes and radio buttons, combo boxes, containers, file upload control, images, labels, line edits, buttons, etc..
· Form widgets have built-in support for client-side and server-side validation using WValidator classes.
· Composite widgets (that are built on top of basic widgets, and use only the Wt public API): calendars, sliders, trees and tree tables, menus, in-place edits, virtual images, panels.
· Modal windows (dialog and message boxes)
· Built-in internationalization using messages resource bundles.
· CSS either inline, or using internal or external style sheets.
· Flexible charting widgets (cartesian charts and pie charts) based on the native painting API, and Wt's MVC infrastructure.
· Kernel-level memory protection protects against privacy issues arising from programming bugs, since sessions can be completely isolated from each other (in dedicated-process mode).
· Supports encryption and server authentication using Secure Sockets Layer (SSL) or Transport Layer Security (TLS) through HTTPS.
· Enables continuous use of HTTPS through low bandwidth requirements (fine-grained AJAX).
· Built-in Cross-Site Scripting (XSS) prevention. Rendered text is always filtered against potentially malicious code, making XSS attacks against Wt applications (close to) impossible.
· Integrates with most common web servers (apache, lighttpd).
· Different session-to-process mapping strategies.
· Hot deployment: new sessions use the new application version while older sessions may continue with their application version.
· Simultaneous handling of requests within and in between sessions (using multi-threading)
· Debug using gdb or valgrind.
· Available only for UNIX platforms.
· Simple, high-performance web application server (multi-threaded, asynchronous I/O) based on the C++ asio library.
· Supports both HTTP and HTTPS using the OpenSSL library.
· Supports response chunking and compression
· Single process (convenient for development and debugging).
· Available for both UNIX and Win32 platforms.
· Supports deployment behind a ProxyPass'ing (and if needed, load-balancing) web server.
What's New in This Release: [ read full changelog ]
· Functionally almost the same as a WDatePicker, this class specializes WLineEdit and is thus a WFormWidget, making it much easier to use in WTemplateFormView.
· This class supports localization for number formatting and extends the simple localization support we had in the previous versions of Wt (which as only effect had the selection of a different language for the resource bundles). It's main added value of native C++ support for localization is that it also affects client-side handling and parsing of number values, i.e. in WIntValidator and WDoubleValidator.
· A navigation bar styles a menu as a typical top-level bar (currently only styled in the Bootstrap Theme).
· A base class to simplify the creation of popup widgets that typically assist in editing or provide circumstancial information for another widget.
· A split button, which combines a button and a popup menu (currently only styled in the Boots...