@aarontheissueguy Bear in mind that this how-to might contain some steps that are no longer necessary. Installing Qt 5 for instance is not needed. Clickable downloads the requisite container images with everything installed necessary for the tutorial.

@josele13 Jami is already taking care of it

I figured out a good base to start with. Inside of the main QML, start with: import QtQuick import QtQuick.Window import QtWebEngine Window { width: 1024 height: 750 visible: true WebEngineView { anchors.fill: parent url: "https://www.qt.io" } } Found here: https://doc.qt.io/qt-6/qtwebengine-webenginequick-minimal-example.html

@kugiigi thanks it slipped my mind i knew it used QT i was just having a moment lol yeah in my experience with things like that it should be updatable cause it should bring all the old api and then some new ones however my experience with QT is quite limited now i wonder?

are the packages shipped with the click, or on the device - if installed on the root of the device maybe the click would need to be unconfined?

@utuser said in Changing the default version of qtcreator for Clickable: Is my setup the current standard and recommendation in UT app developement then? There is no "standard' in UT app development. clickable is a very convenient option, but not everyone uses the ide option. I for instance use VSCodium as an editor. I find QtCreator has too many options I never use. Others use Atom or Vi or Nano as code editors. A handful of developers don't even use clickable. Feel free to try QtCreator via clickable ide. If it works for you, then that is the right tool.

No idea about intents but I guess its equivalent would be content hub and URI handling. They're far from being robust but that's all we have now

I'm waiting for @beli3ver to get backend script in order to make the app work again after that, update and 20.04 will come if there is not to much code to change (more code will just means more delays)

i keep adding clickable commands prob gonna do them all over time eventually gonna put a loop on it to keep the menu open also create a clickable create instance in a non clickable directory

@jezek seabass2 app does allow to build on the device with an integrated clickable bundle.

actually im hell bent on doing it ....yeah i get it poor performance ect ect but just think of the possibilities first im looking into calling java runtime from python then loading app.jar bundling a portable java runtime implementation and any dependencies within the UT app ....now at first its just gonna be java and prob slow as hell then i will make it work for android later but that will be way harder ....one step at a time itll be in the works for awhile cause im still stumped on running python within clickable i figured out web apps simple enough but i need more programmable meat ...so to speak

@developerbayman Another good choice is Seabass2 Which does its compilation magic in a Libertine container it creates for the purpose.

yeah i have alot of java code that i would love to get in UT, for now i just have excepted waydroid is there and i should use it .....im currently attempting to tackle the learning curve with clickable slowly but surly ill get there

ok check out https://gitlab.com/myii/ut-tweak-tool/-/merge_requests/109 They have way more fixed than in my branch, will also give an idea of what needs work.

@matteo I could never really get the PDK to work reliably on my Ubuntu laptop either, to be honest. But I guess a good place to ask for help would be the Developer group chat on Telegram

Hi there, Hugo from Pl@ntNet project, the initial contact answering by email. Let us know if you had any issue, I've read some of the reply there but let me know if you need to read something from us.