Dear Fulvio, thank you for your feedback. I will carefully go through these examples. However, I'm a litte bit concerned about the way UBtouch is going. You are leaving the QT creator IDE for new IDE with as little support for installing toolchains as possible (at the first glance). You are switching to cmake, which is new for me, too. So porting my QT based applications (using qmake) becomes more and more heavier. At the first glance I'm missing debug capabilities in ATOM. This is a major drawback for me. Please correct me if I'm wrong. So far I have reviewed the tedit code, where the c++ plugin is getting the filename from the qml part, so far nothing special on the c++side. By this configuration you are restricted to the directory space which are allowed in the qml environment. And quite this environment is the open point for my. So the next step would be to install a working toolchain under ATOM.

Ok, it turned out my issue was that the old Ubuntu SDK project had the following line set in the Transport/Transport.pro file: desktop_file.files = $$OUT_PWD/*.desktop which turned out to work fine for vivid but for xenail the desktop file was missing from the final click package. So if anyone bumps into the similar issue you may try changing the above glob with a full path like this: desktop_file.files = $$OUT_PWD/Transport.desktop Once done the build project should be working (exacutable) on Xenial. Thank you @dohbee for helping me so much with this.

@hummlbach That sounds fantastic, thank you!

@krille Brian told me that probably you need to use the old style import for the websockets because of the qt version that is in Ubuntu Touch: https://doc.qt.io/qt-5/qtwebsockets-qmlmodule.html

Rather than ditching your 18.04 installation for a 16.04 one, or running 16.04 in a virtual machine, you might want to consider running 16.04 in an LXD/LXC container. $ sudo snap install lxd ... $ sudo lxd init ... $ sudo lxc launch ubuntu:16.04 devbox -c security.nesting=true ... $ sudo lxc shell devbox That will install the lxd snap, initialize lxd for use, launch a privileged lxc container named devbox based on a 16.04 image and finally drop you in a shell in the lxc container.

@flohack thank you, i will take a look at this. hopefully i can find some information

I see, thanks both of you for your answers.

@advocatux I was going to say "It's the next level in the international cat-and-mouse game, called Your Right To Privacy", but I guess your description's more useful.

Hey, I have got it to create a working example!! https://github.com/ChristianPauly/ut-pushclient-example I have reimplemented the example code snippets from the ancient Ubuntu docs plus a button which sends the POST request and now it works inside the app. This example does not need a server to send push notifications. Maybe I can write a more polished tutorial for other developer in the next days.

@advocatux Haha fixed thx

@markalexa at the ubports gettogether in Munich @TimSueberkrueb held a presentation on that topic: https://github.com/timsueberkrueb/ubports-gettogether/blob/master/timsueberkrueb/pyotherside/presentation.md

Actually this is quite doable. Not as a native application however (though that itself IS possible using the Discord SDK, considering that there is a wonderful third-party UWP Discord application for Windows), but using the webapp-container with the user-agent string of the latest Chrome or Chromium release, will cause the webapp to request permission for Microphone and allow VOIP calling under Ubuntu Touch. It will not however, allow PTT (as PTT requires a native application).

@hummlbach thanks for your fast answer. i checked my user and he is in the group docker. i found my error. my folder "build" is owner root. i delete the folder and start clickable new as normal user

@hudson when creating a new project, which framework did you choose? Also, you can try the solution that error message suggested (use the --force-missing-framework option too) but the relevant point is you have to know for which framework you are developing