What could the next step be towards configuring this site (together.jolla.com) to parse inline QML file content?
asked 2015-01-13 23:41:33 +0300
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.
Which "site" do you mean - together.jolla.com? (I like the idea!).
sifartech ( 2015-01-14 21:02:27 +0300 )edit@sifartech: Yes I do. Thanks for making me aware of that implicit reference, I'll amend the question text.
rdmo ( 2015-01-14 22:47:59 +0300 )editAnd please note, parsing Qml is not the same thing as executing it which would require a whole lot of Q-libs and complete engine env etc..After all, this is a discussion forum not Qml-viewer or SCM-repo..
foss4ever ( 2015-01-15 00:36:52 +0300 )editPerhaps it is time for together.sailfishos.org - a virtual environment to develop Sailfish Apps collaboratively?
sifartech ( 2015-01-15 02:51:34 +0300 )editI added tags
jsonandsvgsince these can be expected in possible solution implementations. Thetogethertag went away because solutions need not depend on tjc infrastructure to work. A singlecurl urlfile|bashinstruction to retrieve a file and run it might be enough to set up a working visualisation system for an OS' code, commands and object connections. I'm just thinking out loud for now.When tjc supports SVG uploads we won't have to make do with only static
jpegscreenshots.Working on the idea of simplifying by reduction.
rdmo ( 2015-02-06 00:44:44 +0300 )edit