QmlWeb: Difference between revisions
Akreuzkamp (talk | contribs) (Add a page for the QmlWeb project) |
Jangmarker (talk | contribs) |
||
(3 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
== | == Vision == | ||
The QML language is well-suited for building web applications. Goal is to develop the required technologies for that. This is a runtime environment in JavaScript and the required QML modules to render in web browsers. Other applications can be considered. | |||
Main focus is on developing hybrid-applications using native (Qt) and web technologies of any scale, not forgetting the creation of sole web applications. QmlWeb is not intended to run native QtQuick applications using QmlWeb without migration effort. | |||
== | == Subprojects == | ||
* [[QmlWeb/Qml.js]] | |||
* [[QmlWeb/QmlWeb Modules]] | |||
==Organization== | |||
* Documentation on KDE Community Wiki | |||
* Communication using mailto:qmlweb@kde.org and IRC #kde-qmlweb | |||
* Task and bug tracking on https://bugs.kde.org | |||
* Development Style: Test driven (QTest and QUnit) |
Latest revision as of 14:01, 8 February 2015
Vision
The QML language is well-suited for building web applications. Goal is to develop the required technologies for that. This is a runtime environment in JavaScript and the required QML modules to render in web browsers. Other applications can be considered. Main focus is on developing hybrid-applications using native (Qt) and web technologies of any scale, not forgetting the creation of sole web applications. QmlWeb is not intended to run native QtQuick applications using QmlWeb without migration effort.
Subprojects
Organization
- Documentation on KDE Community Wiki
- Communication using mailto:[email protected] and IRC #kde-qmlweb
- Task and bug tracking on https://bugs.kde.org
- Development Style: Test driven (QTest and QUnit)