diff options
Diffstat (limited to 'packages/Xwt.0.2.40/README.markdown')
| -rw-r--r-- | packages/Xwt.0.2.40/README.markdown | 221 |
1 files changed, 0 insertions, 221 deletions
diff --git a/packages/Xwt.0.2.40/README.markdown b/packages/Xwt.0.2.40/README.markdown deleted file mode 100644 index 54de416..0000000 --- a/packages/Xwt.0.2.40/README.markdown +++ /dev/null @@ -1,221 +0,0 @@ -This document is an introduction to XWT, a cross-platform UI toolkit -for creating desktop applications. - -If you have any question about XWT or do you want to contribute -a discussion group for XWT is available here: - -http://groups.google.com/group/xwt-list - -Introduction -============ - -Xwt is a new .NET framework for creating desktop applications that run -on multiple platforms from the same codebase. Xwt works by exposing -one unified API across all environments that is mapped to a set of -native controls on each platform. - -This means that Xwt tends to focus on providing controls that will -work across all platforms. However, that doesn't mean that the -functionality available is a common denominator of all platforms. -If a specific feature or widget is not available in the -native framework of a platform, it will be emulated or implemented -as a set of native widgets. - -Xwt can be used as a standalone framework to power the entire application -or it can be embedded into an existing host. This allows developers -to develop their "shell" using native components (for example a Ribbon -on Windows, toolbars on Linux) and use Xwt for specific bits of the -application, like dialog boxes or cross platform surfaces. - -Xwt works by creating an engine at runtime that will map to the -underlying platform. These are the engines that are supported on -each platform: - -* Windows: WPF engine, Gtk engine (using Gtk#) -* MacOS X: Cocoa engine ( |