Ask / Submit
4

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

rdmo gravatar image

updated 2015-03-27 19:26:32 +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.

edit retag flag offensive close delete

Comments

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 )edit
1

And 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 )edit
1

Perhaps it is time for together.sailfishos.org - a virtual environment to develop Sailfish Apps collaboratively?

sifartech ( 2015-01-15 02:51:34 +0300 )edit

I added tags json and svg since these can be expected in possible solution implementations. The together tag went away because solutions need not depend on tjc infrastructure to work. A single curl urlfile|bash instruction 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 jpeg screenshots.

Working on the idea of simplifying by reduction.

rdmo ( 2015-02-06 00:44:44 +0300 )edit

3 Answers

Sort by » oldest newest most voted
5

answered 2015-01-15 09:58:33 +0300

Keto gravatar image

Interesting idea, but to be honest: No, it would not be simple.

Also I'm not sure how well this would fit in together.jolla.com in it's current form. Although developers are of course welcome to discuss also in here, the Sailfish OS mailing lists and IRC channels are probably a more suited place for development related discussion and collaboration at the moment. (I haven't been following any application development related questions, so I don't know how active that side of the community is here)

What comes to setting up a working development environment, installing and using the Sailfish SDK is not overly complex operation and prototyping user interfaces in QML is fairly simple. Yes, one needs to learn a thing or two, but there really isn't a short cut to get the "full development skills" without putting in some time, attention and mental energy :)

edit flag offensive delete publish link more

Comments

Yes, I guess if it were simpler it might have been implemented everywhere already. Thanks for the IRC tip and the mailing list reminder.

rdmo ( 2015-01-15 12:21:33 +0300 )edit

The GUI parts would perhaps be an easier part than the processing parts they'd hook into. Maybe the latter could be arcs out of the GUI picture into labels or icons denoting features and functions, if a full stack (or any other) is impractical on this forum. These in turn would link to other questions on this site and into (Qt, etc) elsewhere on the net.

rdmo ( 2015-01-26 21:20:35 +0300 )edit
1

answered 2015-01-15 10:00:01 +0300

tortoisedoc gravatar image

http://qt-project.org/forums/viewthread/4347

edit flag offensive delete publish link more

Comments

Thanks for the link to the asm.js and other related info.

rdmo ( 2015-01-15 12:23:53 +0300 )edit
0

answered 2015-01-15 00:31:15 +0300

foss4ever gravatar image

I'm not sure Together is the best possible forum or site for code reviews, emulator views, or any kind of SDK/IDE-related functionalities. There is in sailfishos.org ofc the SDK/QtCreator available for download and installation and no-one surely does not intend to use Jolla device for QML/Qt-dev work, right? And, I still don\t understand what the use-cases for inline Qml in this forum would be, cause it's just so easy and much nore practical to use SCM-repos for that, and if u want to discuss abt code segments or demonstrate UI mashups etc isn't it much easier to post links to those? Or are u just wanting to see QML-code that is posted recognized as such (keywords highlighted, etc) and/or some qmlviewer to show how the code looks like and performs?

edit flag offensive delete publish link more
Login/Signup to Answer

Question tools

Follow
1 follower

Stats

Asked: 2015-01-13 23:41:33 +0300

Seen: 449 times

Last updated: Jan 26 '15