I have solved this, in case anyone hits the same brick wall:

In the .pro file, the one selected in my screenshot, I needed to specify that it should install those aditional files.
In my case I mentioned that it should install the DISTFILES, like the following:

DISTFILES +=
weathericons-regular-webfont.ttf
Ubuntu-C.ttf
fontawesome.ttf

#set the path where to install distfiles aswell as adding which files to be added
dist_files.path = /Cumulus
dist_files.files += $${DISTFILES}

#you can see that at the the end I've mentioned that dist_files should be installed aswell
INSTALLS+=config_files qml_files desktop_file dist_files

Might seem dumb of me for not knowing, that the files should be manually set to install, but I haven't used it before since for Android Qt Creator does that for me because it has a special directory where I need to add the aditional files.
And on desktop I manually copied the files in the build directories without thinking I can tell qmake which files should also be deployed.
So in case any other has this issue might help them out.

1. Are there plans to make a pre-built kit for Qt 5.9.x for Ubuntu Touch?
2. What do you guys think of moving the applications action bar from top to bottom, or at least having a setting?
   In my opinion this would improve navigations because you would have the options at the tips of your thumbs. Android and Windows solved this with their back buttons(don't know about IOS), but UT requires you to move your hand to the top of the device.
   As an example, I find it mildly annoying that for toggling between calls history and dialer requires me to move my hand up and down on the phone while on my Android phone all I need to move my left thumb....what can I say....I like comfort :P.

PS: If I think of any more I will edit this :).

Hopefully You don't mind if I also add my opinions on the matter.
I like the second proposal most, the one just with the header sections.
Moving just the installed apps button on the bottom doesn't make sense, controlls for the app will be all over l, they should stay close to eachother.
Badge on installed app to show how many applications need to update.
I agree that the Uninstall / Open buttons should be next to eachother and also they should have a fixed size, leaving them long would look a bit unprofessional for my taste.
Aswell I agree that the application detail Page should not slide up from bottom edge.

True, but not only the predictions are counterintuitive, the size of the predictions also is an issue.
I think the size should be bigger and font changed, If this limits the current visible predictions to 3-4 words shouldn't be an issue as it will help those with sight issues.

I was thinking on scopes and want to open a discussion about the current state of them and possibility for future.
I was thinking that the scopes could be QML applications simply loaded inside an Qt/QML application.
This could bring a lot of scopes opportunities:

• any QML app can be set as scope and be at the user's fingertips
• a lot of UI customisation possibilities
• webapps can be loaded as scopes through WebView / WebEngine to support HTML / Javascript scopes
• they can interract with the OS instead of just providing static content
• support is provided through Qt updates

Downside:

• no support for Golang

How scopes are built now lack a lot, you have little customisation and little freedom for them and they can't do anything but show some information.
They could be given the option to be started / closed when they get focused / hidden through QML Loader to reduce memory footprint or kept always on, in case someone wants to leave it running(a music player scope can be given as example).

I wasn't sure where this could be discussed, so since this comes into user experience(more or less) I thought here it's the best place to do it.
What do you think?

@mitu said in Scopes current and future:

This is definitely not a good idea in my opinion. Apps' navigation patterns would interfere with desktop navigation, what would mean that having set unav as a scope you would not be able to swipe between desktops.

I am not talking about the possibility of allowing every application to run as scopes.
There can and should be standards to allow this feature, for example:

1. an application should be a pure QML application which doesn't start from an executable file, but from a QML file(where the main view of the application is loaded through Loader to MainView and not declared as a child of it to decouple from it)
2. there should be a standard to communicate to the system that it can be loaded as a scope, and which QML file should be the main view of the scope.

If I will have the time I will try to make a desktop prototype for testing to show what I am talking about.

I agree with @alan_g , I think the project should be more important than the fact that MS bought a website UBports, lots of Linux and FOSS developers are using.
Especially since we don't if that affects the project in any way, yet we know that the move would probably cost the project time.

I see, thanks both of you for your answers.

Hi,
I want to build UT Qt applications but don't know where to start to have a working Qt IDE as everything seems to fail me.
I am currently on Ubuntu 16.04, latest updates.
Ubuntu-SDK can't seem make a kit for armhf, the sdk is from the ppa in the docs, lxd is the backported version.
I was thinking of building official Qt(5.9.x), Creator included, to compile for UT but I don't know where to start from.
I know that I need to build the mir QPA plugin aswell, but aside from that I am a bit lost.
Any advice, what to read, is extremely welcomed.

@mitu said in Scopes current and future:

This is definitely not a good idea in my opinion. Apps' navigation patterns would interfere with desktop navigation, what would mean that having set unav as a scope you would not be able to swipe between desktops.

I am not talking about the possibility of allowing every application to run as scopes.
There can and should be standards to allow this feature, for example:

1. an application should be a pure QML application which doesn't start from an executable file, but from a QML file(where the main view of the application is loaded through Loader to MainView and not declared as a child of it to decouple from it)
2. there should be a standard to communicate to the system that it can be loaded as a scope, and which QML file should be the main view of the scope.

If I will have the time I will try to make a desktop prototype for testing to show what I am talking about.

I was thinking on scopes and want to open a discussion about the current state of them and possibility for future.
I was thinking that the scopes could be QML applications simply loaded inside an Qt/QML application.
This could bring a lot of scopes opportunities:

• any QML app can be set as scope and be at the user's fingertips
• a lot of UI customisation possibilities
• webapps can be loaded as scopes through WebView / WebEngine to support HTML / Javascript scopes
• they can interract with the OS instead of just providing static content
• support is provided through Qt updates

Downside:

• no support for Golang

How scopes are built now lack a lot, you have little customisation and little freedom for them and they can't do anything but show some information.
They could be given the option to be started / closed when they get focused / hidden through QML Loader to reduce memory footprint or kept always on, in case someone wants to leave it running(a music player scope can be given as example).

I wasn't sure where this could be discussed, so since this comes into user experience(more or less) I thought here it's the best place to do it.
What do you think?

True, but not only the predictions are counterintuitive, the size of the predictions also is an issue.
I think the size should be bigger and font changed, If this limits the current visible predictions to 3-4 words shouldn't be an issue as it will help those with sight issues.

@mihael
I am not an Ubports official either but want to help clarify.
Ubuntu touch is as safe as the users make it: installing software from safe sources and reading the permissions the application requires should, in theory, keep You safe.
For example, a simple camera app should not require network permissions, neither voice a recording application, unless is an application which can upload them to a server.
Another thing I know related to UT is that third party applications should not have permissions to run in background (someone tell me If I am wrong on this).

@sverzegnassi

I forgot you also posted that in my post.....https://forums.ubports.com/topic/733/some-opinions-related-to-the-latest-community-update/21

Hopefully You don't mind if I also add my opinions on the matter.
I like the second proposal most, the one just with the header sections.
Moving just the installed apps button on the bottom doesn't make sense, controlls for the app will be all over l, they should stay close to eachother.
Badge on installed app to show how many applications need to update.
I agree that the Uninstall / Open buttons should be next to eachother and also they should have a fixed size, leaving them long would look a bit unprofessional for my taste.
Aswell I agree that the application detail Page should not slide up from bottom edge.

@RandomUser How come? it seems random to me, it doesn't match nor they are consistent throughout cycling the info.