Ubuntu.components ? ( Developpment guidelines )
-
Hi all,
I've finally started to write a small project in pure QML , so i'm gathering examples and informations from everywhere i know...
I've heard but not sure that "Ubuntu.components" is intended to be replaced, am i right ?
Would Like to start a project that can be has much as cross platform possible.
What would be your advises ?cheers
-
After a few tests, found that replacing commons features such as hamburger menu, swipeable ListItem, PageStack add lots of code.
So do we still use in future components such as MainView/PageStack/PageHeader with leading/trailing actions so that we do not have all that boilerplates code ?Any up to date app example using suru and QQC2 ?
-
-
-
But in fact there isnt a decision yet what the future toolkit of Ubuntu Touch will be, right?
Thats not an ideal situation for app developers who would like to create future proof apps...
-
@krille Indeed a good question for next Q&A...
-
@libremax said in Ubuntu.components ? ( Developpment guidelines ):
@krille Indeed a good question for next Q&A...
Hi, exactly my point. I also just started to play with QML and I think that Ubuntu packages were meant to ease on development and to ensure more UX consistency on uTouch apps. It would be a shame to throw it all away. But it's hard to tell, how much work is it to keep it compatible with used (latest) QT.
I don't know C++ and for example phone and messaging apps are complicated to me right now. It would be much easier to have QML object wrapping whatever C++ implementation to make a call and simply call it from QML code.
So I could focus on different design of a phone app instead of learning deep C++ and its interactions with some system/backend service.
-
@myii said in Ubuntu.components ? ( Developpment guidelines ):
@lduboeuf Maybe @kugiigi can be more specific but I know he was working on this recently. Probably:
Yes, Palitan is an app written mainly with QQC2 but mixed with some UITK especially for icons
If you really want cross-platform possibility, then I suggest you use pure QQC2.
There are still things that doesn't work yet in UT though such as text operations in text fields but QQC2 does work quite well already. A great cross-platform app that uses QQC2 is nymea-app. You should definitely check it out.
It looks and works the same in Android, iOS and UT
https://open-store.io/app/io.guh.nymeaapp -
Well, my first native app just landed on Openstore. https://open-store.io/app/ttbn.lduboeuf
I've only used QQC2 components and imported needed svg icons from suru theme.
I admit that as a QML beginner, it was sometimes hard to make things work and displayed correctly... color theme is still not that good.But i'm happy that i can now build for multi os and still use QtCreator.
Thanks for all your examples -
Congratulations!!
