If anyone interested, this is also one of mine, with surely some mistakes and omissions , sorry : https://m.youtube.com/watch?v=TE-s5522v0Y
In french: https://m.youtube.com/watch?v=lU6J01XB4pc
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
Wondering if any up to date overview / architecture schemas available somewhere ?
Last one i know of are from old Cannonical Ubuntu Touch days: https://www.slideshare.net/chihchun/ubuntu-phone-engineering and https://www.slideshare.net/tusharkute/introduction-to-ubuntu-edge-operating-system-ubuntu-touch
We might create some in documentation overview section.
Working behind proxy is sometimes so painfull ;-), i share my experience to get
clickable working behind a corporate proxy:
clickable setup-lxd, then it will hang when trying to fetch apt updates
/var/lib/lxd/containers/clickable-armhf/rootfs/etc/apt/apt.conf.d/01proxywith proxy settings:
Acquire::http::Proxy "url:port"; Acquire::https::Proxy "url:port";
lxc exec clickable-armhf -- apt-get update lxc exec clickable-armhf -- apt-get upgrade
lxc exec clickable-armhf -- apt-get install click
it should work now.
On Qt Creator I can develop "normal" Qt programs. If I want to open a Clickable project, there are a lot of Errors with the CMakeLists.txt and I cannot edit this project.
If you want to stay on QtCreator, you can have autocompletion for Ubuntu Components by importing them on your PC:
(see topic 1 or 2 ) https://gist.github.com/lduboeuf/dcf22607207d5b7abc8ac966d20942ce
as @LarreaMikel says, a Phone that can be easily hacked. A fast browser . I would prefer easy data sync (calendar, contacts, notes,... ) than convergence.
if anyone interested in my presentation held today (in french)
slides available here:
http://codedarmor.fr/labs/slidedecks/slides/OS mobiles alternatifs.pdf
I will do a presentation of UT along with other projects in French in Mai 15th at my local developer community, here is my initial work: https://github.com/lduboeuf/ut-helloworld-py/raw/master/osmobiles.odp
I used some schemas from canonical, if anyone can have a look if they are fine. UT slides starts on page 26, architecture schemas are at 31-33.
Comments or PR welcome.
Well, i'm engaged now at the local developer community to talk a bit about UT, and UT apps. Will do a small presentation beside from presenting projects like LuneOS, PostmarketOS, Plasma Mobile, Librem5...
How can i convice them to develop apps for UT, Plasma and Others ?
IMO they could be interested if most of their code base can be shared among OSes. Are there any app examples around that target cross mobile platform ? heard of kaidan https://github.com/KaidanIM/Kaidan .
@mark-volpetti you can contribute then to make it more clear :). You can start by filing a bug
https://github.com/ubports/devices.ubports.com (not sure if it is that one)
or even better, propose a Pull Request
@mymike not sure but i had that also, try replacing in apparmor file
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 ?
Hi, did you already checked UBports documentation ? https://docs.ubports.com/en/latest/appdev/index.html
Clickable allows you to test your app on your desktop before submitting on your device
hey all, would like to know if anyone start to work in "official" slides about ubuntu touch. would love to talk about the project to my local developer community but don't have all the clue and time to make my own. Some OS architecture schemas, general overviews would be nice and useful as well in documentation.