The zoom behaviour of Morph is currently being improved. I'm not sure what changes are in stable, but webapps in dev channel certainly have access to zoom settings by the user. There is no option to set it in the command line for webapps, but I recall seeing the suggestion out there. Maybe in time. edit for command line options that are available see: https://docs.ubports.com/en/latest/appdev/webapp/guide.html#command-line-arguments

@lduboeuf thx!

@Mick21367 You have creator rights in the writable folder so it's doable to replace or delete the imported file.

Thanks. Well it's only intended to be a working solution until a better native app is made. Likely Kaidan will fill that spot in the future. But I'll likely still make some improvements such as a nicer login page and a dark mode. Given the limitations of the current HTML5 app support in UT, I have shelved more advanced plans. I just hope the switch to IndexDB that is happening with ConverseJS 6.0 isn't going to break it on the old qtwebengine UT uses.

It is currently not possible to use camera from browser, because QtWebEngine isn't using QtMultimedia for camera yet.

@poVoq have a good new year....when will the Update be avaliabel? Thanks .

On a mobile phone using mobile data represents an extra expense for ads, web pages that are reloaded, especially, online newspapers ... The best thing to do is, edit the "hosts" file and add, as the previous partner the web address to the resolution of domain name 127.0.0.1 which is the internal network card and will not load anything at all, and who wants to support a web page because it is hard for the creator of it to do what he does, you can click and put it on the white list as advocatux says, but you don't bother to read, you don't pay attention, people just want to be heard but they don't listen, anyway. HAPPY YEAR 2020. (Google Traslator, Hello of Spain) ;).

Good guy, I love him!

@tusharsaurabh Really? Strange, I still get the same error? where did you change the architecture field? In the manifest.json.in file?

VLC will still have issues, as it's not using hardware decoding, and likely would still need to run under xmir, depending on what it's actually using to render video.

Anyone got an idea why qtCreator complains about importing pyotherside as done in the tutorial: qml module does not contain information about components contained in plugins The program itself runs fine on my Kubuntu18.04 system, so it seems to be an qtCreator specific problem. Edit: hmm, seems to be a pyotherside 1.4 specific issue, but I guess not such a good idea to upgrade as UT is also still stuck on 1.4

At first I will start to port the minifb https://github.com/emoon/rust_minifb crate to Ubuntu Touch. It think so more projects could be profit and ported to Ubuntu Touch. We use minifb it as main window library. The first port will wrap QWindow.

What I alternative want to check is to draw in the frame buffer of a QWindow.

@AppLee I'm actually not using the OpenStore at all but just doing all my development work locally at the moment. I'm not using clickable because my app cannot be cross-compiled. It relies on a rust dbus crate that doesn't allow cross-compiling (see https://github.com/diwic/dbus-rs/blob/master/libdbus-sys/cross_compile.md for details).

@Aury88 ok. build completed and app launched correctly on desk. Thank you again

@mirroronthewall Porting android apps is not the best way to achieve your goal I think. The best course of action is to create a native app which can integrate libs or some algorithm from Open Source projects like the one you mentioned. AR and VR requires some work but it's doable, just need someone motivated and with enough time to do the job. If I win the lottery (but I don't bet) I'll be happy to try out the AR

If we start with HERE, see their API first. We need search (address->coordinates), routing and reverse search (coordinates->address). Pure Maps uses REST API to communicate with the servers. So, check their REST API and see if you can get trucks support if you use it. Docs are at https://developer.here.com/documentation Routing at https://developer.here.com/documentation/routing/dev_guide/topics/request-a-simple-route.html If routing seems OK, then let's start with search. Its API at https://developer.here.com/documentation/geocoder/dev_guide/topics/what-is.html That API we will translate to code in https://github.com/rinigus/pure-maps/tree/master/geocoders , so Pure Maps will understand it