Revision history [back]

If this were possible, it could enhance collaborative efforts and help user-developers to learn about and tweak their design ideas, with community feedback possible and with easier, quicker development iteration than on Github. QML succeeding on this forum could then be copied to Github repositories when they would be considered ready. Even though the Jolla device has git, and using repositories from there is as easier as git clone CUT-AND-PASTE-REPO-NAME-HERE and git up, the code itself might be better discussed and explained on this site, too. The value, as I imagine it, would come from being able, from a Jolla phone, to browse to this site and submit or edit existing QML content, and see the rendered image of an emulated GUI with links or arrows indicating the code associated with various widgets.

I suppose it could be nice as both a collaborative workflow enhancement and might help market devices and the Qt/Digia development products.

Additionally, users attempting development from their Jollas or without ready access to sufficient computing power for building, compiling and automated testing, could submit their work here instead. Rather than consuming their time and limited attention and mental energy setting up a working build environment their efforts could focus on the other aspects of interface design and the contingent processes behikd them - at least to start more gently towards full development skills.

If this were possible, it could enhance collaborative efforts and help user-developers to learn about and tweak their design ideas, with community feedback possible and with easier, quicker development iteration than on Github. QML succeeding on this forum could then be copied to Github repositories when they would be considered ready. Even though the Jolla device has git, and using repositories from there is as easier as git clone CUT-AND-PASTE-REPO-NAME-HERE and git up, the code itself might be better discussed and explained on this site, too. The value, as I imagine it, would come from being able, from a Jolla phone, to browse to this site and submit or edit existing QML content, and see the rendered image of an emulated GUI with links or arrows indicating the code associated with various widgets.

I suppose it could be nice as both a collaborative workflow enhancement and might help market devices and the Qt/Digia development products.

Additionally, users attempting development from their Jollas or without ready access to sufficient computing power for building, compiling and automated testing, could submit their work here instead. Rather than consuming their time and limited attention and mental energy setting up a working build environment their efforts could focus on the other aspects of interface design and the contingent processes behikd behind them - at least and also to start more gently towards full development skills.

If this were possible, it could enhance collaborative efforts and help user-developers to learn about and tweak their design ideas, with community feedback possible and with easier, quicker development iteration than on Github. QML succeeding on this forum could then be copied to Github repositories when they would be considered ready. Even though the Jolla device has git, and using repositories from there is as easier as git clone CUT-AND-PASTE-REPO-NAME-HERE and git up, the code itself might be better discussed and explained on this site, too. The value, as I imagine it, would come from being able, from a Jolla phone, to browse to this site and submit or edit existing QML content, and see the rendered image of an emulated GUI with links or arrows indicating the code associated with various widgets.

I suppose it could be nice as both a collaborative workflow enhancement and might help market devices and the Qt/Digia development products.

Additionally, users attempting development from their Jollas or without ready access to sufficient computing power for building, compiling and automated testing, could submit their work here instead. Rather than consuming their time and limited attention and mental energy setting up a working build environment their efforts could focus on the other aspects of interface design and the contingent processes behind them - and also to start more gently towards full development skills.

If this were possible, it could enhance collaborative efforts and help user-developers to learn about and tweak their design ideas, with community feedback possible and with easier, quicker development iteration than on Github. QML succeeding on this forum could then be copied to Github repositories when they would be considered ready. Even though the Jolla device has git, and using repositories from there is as easier as git clone CUT-AND-PASTE-REPO-NAME-HERE and git up, the code itself might be better discussed and explained on this site, too. The value, as I imagine it, would come from being able, from a Jolla phone, to browse to this site and submit or edit existing QML content, and see the rendered image of an emulated GUI with links or arrows indicating the code associated with various widgets.

I suppose it could be nice as both a collaborative workflow enhancement and might help market devices and the Qt/Digia development products.

Additionally, users attempting development from their Jollas or without ready access to sufficient computing power for building, compiling and automated testing, could submit their work here instead. Rather than consuming their time and limited attention and mental energy setting up a working build environment their efforts could focus on the other aspects of interface design and the contingent processes behind them - and also to start more gently towards full development skills.

If this were Wrrr this possible, it could enhance collaborative efforts and help user-developers to learn about and tweak their design ideas, with community feedback possible and with easier, quicker development iteration than on Github. QML succeeding on this forum could then be copied to Github repositories when they would be considered ready. Even though the Jolla device has git, and using repositories from there is as easier as git clone CUT-AND-PASTE-REPO-NAME-HERE and git up, the code itself might be better discussed and explained on this site, too. The value, as I imagine it, would come from being able, from a Jolla phone, to browse to this site and submit or edit existing QML content, and see the rendered image of an emulated GUI with links or arrows indicating the code associated with various widgets.

I suppose it could be nice as both a collaborative workflow enhancement and might help market devices and the Qt/Digia development products.

Additionally, users attempting development from their Jollas or without ready access to sufficient computing power for building, compiling and automated testing, could submit their work here instead. Rather than consuming their time and limited attention and mental energy setting up a working build environment their efforts could focus on the other aspects of interface design and the contingent processes behind them - and also to start more gently towards full development skills.

Wrrr Wete this possible, it could enhance collaborative efforts and help user-developers to learn about and tweak their design ideas, with community feedback possible and with easier, quicker development iteration than on Github. QML succeeding on this forum could then be copied to Github repositories when they would be considered ready. Even though the Jolla device has git, and using repositories from there is as easier as git clone CUT-AND-PASTE-REPO-NAME-HERE and git up, the code itself might be better discussed and explained on this site, too. The value, as I imagine it, would come from being able, from a Jolla phone, to browse to this site and submit or edit existing QML content, and see the rendered image of an emulated GUI with links or arrows indicating the code associated with various widgets.

I suppose it could be nice as both a collaborative workflow enhancement and might help market devices and the Qt/Digia development products.

Additionally, users attempting development from their Jollas or without ready access to sufficient computing power for building, compiling and automated testing, could submit their work here instead. Rather than consuming their time and limited attention and mental energy setting up a working build environment their efforts could focus on the other aspects of interface design and the contingent processes behind them - and also to start more gently towards full development skills.

Wete this possible, it could enhance collaborative efforts and help user-developers to learn about and tweak their design ideas, with community feedback possible and with easier, quicker development iteration than on Github. QML succeeding on this forum could then be copied to Github repositories when they would be considered ready. Even though the Jolla device has git, and using repositories from there is as easier as simply to git clone CUT-AND-PASTE-REPO-NAME-HERE and git up, the code itself might be better discussed and explained on this site, too. The value, as I imagine it, would come from being able, from a Jolla phone, to browse to this site and submit or edit existing QML content, and see the rendered image of an emulated GUI with links or arrows indicating the code associated with various widgets.

I suppose it could be nice as both a collaborative workflow enhancement and might help market devices and the Qt/Digia development products.

Additionally, users attempting development from their Jollas or without ready access to sufficient computing power for building, compiling and automated testing, could submit their work here instead. Rather than consuming their time and limited attention and mental energy setting up a working build environment their efforts could focus on the other aspects of interface design and the contingent processes behind them - and also to start more gently towards full development skills.

Wete this possible, it could enhance collaborative efforts and help user-developers to learn about and tweak their design ideas, with community feedback possible and with easier, quicker development iteration than on Github. QML succeeding on this forum could then be copied to Github repositories when they would be considered ready. Even though the Jolla device has git, and using repositories from there is simply to git clone CUT-AND-PASTE-REPO-NAME-HERE and git up, the code itself might be better discussed and explained on this site, too. The value, as I imagine it, would come from being able, from a Jolla phone, to browse to this site and submit or edit existing QML content, and see the rendered image of an emulated GUI with links or arrows indicating the code associated with various widgets.

I suppose it could be nice as both a collaborative workflow enhancement and might help market devices and the Qt/Digia development products.

Additionally, users attempting development from their Jollas or without ready access to sufficient computing power for building, compiling and automated testing, could submit their work here instead. Rather than consuming their time and limited attention and mental energy setting up a working build environment their efforts could focus on the other aspects of interface design and the contingent processes behind them - and also to start more gently towards full development skills.

Wete this possible, it could Were this to enhance collaborative efforts and efforts, it might help user-developers to learn about and tweak their design ideas, front and back ends, with community feedback possible and with easier, quicker development iteration than simplified code iteration.

QML successes on Github. QML succeeding on this forum could then be copied together.jolla.com could mirror to Github repositories when they would be considered ready. and its other means of code showcasing and improvement. Even though the Jolla device has git, git, and using repositories from there is simply to git clone CUT-AND-PASTE-REPO-NAME-HEREPASTE-REPO-NAME-HERE and git up, the code itself might be better discussed and explained other code discussion could continue on this site, too.

The value, as I imagine it, value added would come from being be becoming able, from a Jolla phone, to browse to this site and any device with a web browser, to access this site, submit or edit existing QML content, and see the rendered image of an emulated SVG or other images of the GUI with links or arrows indicating the code associated with various widgets.

I suppose it could be nice Its operation as both a collaborative workflow enhancement and improvement might even help market devices and the Qt/Digia development products.

Additionally, users attempting development from their Jollas or without ready access to sufficient computing power for building, compiling and automated testing, could submit their work here instead. Rather the outcome of their effort here.

Even with a capable home PC, rather than consuming their time and limited attention and mental energy setting up a working build environment their efforts environment, their input could focus on the other aspects of interface design and the contingent processes behind them - and also to start them.

Novices could begin more gently towards full immersion in perceived contemporary, arbitrary development skills.prerequisites.

Were this to enhance collaborative efforts, it might help user-developers to learn about and tweak their front and back ends, with community feedback possible and simplified code iteration.

QML successes on together.jolla.com could mirror to Github repositories and its other means of code showcasing and improvement. Even though the Jolla device has git, and using repositories from there is simply to git clone PASTE-REPO-NAME-HERE and git uppull, other code discussion could continue on this site, too.

The value added would be becoming able, from any device with a web browser, to access this site, submit or edit existing QML content, and see SVG or other images of the GUI with links or arrows indicating the code associated with various widgets.

Its operation as a collaborative workflow improvement might even help market the Qt/Digia development products.

Additionally, users attempting development from their Jollas or without ready access to sufficient computing power for building, compiling and automated testing, could submit the outcome of their effort here.

Even with a capable home PC, rather than consuming time and limited attention and mental energy setting up a working build environment, their input could focus on the other aspects of interface design and the contingent processes behind them.

Novices could begin more gently towards full immersion in perceived contemporary, arbitrary development prerequisites.

Were this to enhance collaborative efforts, it might help user-developers to learn about and tweak their front and back ends, with community feedback possible and simplified code iteration.

QML successes on together.jolla.com could mirror to Github repositories and its other means of code showcasing and improvement. Even though the Jolla device has git, and using repositories from there is simply to git clone PASTE-REPO-NAME-HERE and git pull, other code discussion could continue on this site, too.

The value added would be becoming able, from any device with a web browser, to access this site, submit or edit existing QML content, and see SVG or other images of the GUI with links or arrows indicating the code associated with various widgets.

Its operation as a collaborative workflow improvement might even help market the Qt/Digia development products.

Additionally, users attempting development from their Jollas or without ready access to sufficient computing power for building, compiling and automated testing, could submit the outcome of their effort here.

Even with a capable home PC, rather than consuming time and limited attention and mental energy setting up a working build environment, their input could focus on the other aspects of interface design and the contingent processes behind them.

Novices could begin more gently towards full immersion in perceived contemporary, arbitrary development prerequisites.

Were this to enhance collaborative efforts, it might help user-developers to learn about and tweak their front and back ends, with community feedback possible and simplified code iteration.

QML successes on together.jolla.com could mirror to Github repositories and its other means of code showcasing and improvement. Even though the Jolla device has git, and using repositories from there is simply to git clone PASTE-REPO-NAME-HERE and git pull, other code discussion could continue on this site, too.

The value added would be becoming able, from any device with a web browser, to access this site, submit or edit existing QML content, and see SVG or other images of the GUI with links or arrows indicating the code associated with various widgets.

Its operation as a collaborative workflow improvement might even help market the Qt/Digia development products.

Additionally, users attempting development from their Jollas or without ready access to sufficient computing power for building, compiling and automated testing, could submit the outcome of their effort here.

Even with a capable home PC, rather than consuming time and limited attention and mental energy setting up a working build environment, their input could focus on the other aspects of interface design and the contingent processes behind them.

Novices could begin more gently towards full immersion in perceived contemporary, arbitrary development prerequisites.

Were this to enhance collaborative efforts, it might help user-developers to learn about and tweak their front and back ends, with community feedback possible and simplified code iteration.

QML successes on together.jolla.com could mirror to Github repositories and its other means of code showcasing and improvement. Even though the Jolla device has git, and using repositories from there is simply to git clone PASTE-REPO-NAME-HERE and git pull, other code discussion could continue on this site, too.

The value added would be becoming able, from any device with a web browser, to access this site, submit or edit existing QML content, and see SVG or other images of the GUI with links or arrows indicating the code associated with various widgets.

Its operation as a collaborative workflow improvement might even help market the Qt/Digia development products.

Additionally, users attempting development from their Jollas or without ready access to sufficient computing power for building, compiling and automated testing, could submit the outcome of their effort here.

Even with a capable home PC, rather than consuming time and limited attention and mental energy setting up a working build environment, their input could focus on the other aspects of interface design and the contingent processes behind them.

Novices could begin more gently towards full immersion in perceived contemporary, arbitrary development prerequisites.