Ugly but usable and cross-platform tkinter UI coming together for desktop ! 🙂

c8c3d8c5-c4f0-402e-abc0-7673c3be64ce-image.png

Thanks! Seems like announcing it here is the best idea.

I'll upload my app in a few moments, and I'll start a thread here!

@R9_Dev Oh, I was not asking for myself, just asking followup questions to make the intentions clearer.

@Plarde
I'm glad it worked.

Sure, I understand it's easier to start with a basis you master.
I personally forced myself to use pure QML as much as I can to teach me how it works.
And we have people that can help as well as good example to borrow some code.

Thanks for your contribution, it's always appreciated.
People usually agree that we need more native apps for Ubuntu Touch.

@AppLee
thanks for the tip, i tried with ascii converter, didn't think of that, it works 🙂
I'll have to parse the resulting ascii (lots of escaped character, and html in it )

@Kamisori You can put skip_review: true in clickable.yaml, or you can run clickable build --skip-review and then clickable install and clickable launch. I think you can't upload it to the Open Store if you skip review.

@danfro I don't know anything precisely!! I cleared Tedit's cache. Then I turned the smartphone off and on again. Turning it off and on or rebooting is often a quick fix..

@arubislander I changed the "chromium.sh" in the exec field to just "chromium". To my knowledge, I'm pretty sure I can just set a command in the Exec field, and the "chromium" command is another way to open chromium. However, upon opening the app from the launcher, nothing happens still.

@lduboeuf I had a look to your link. I can see the following line:

framework: ubuntu-sdk-16.04.5

However, your CMakeList.txt file shows:

set(CLICK_FRAMEWORK "ubuntu-sdk-20.04")

I guess it does not matter since you can build the app.
I am struggling with this issue. I installed clickable in my desktop machine (20.04) but want to develop the app for my BQ 4.5 (Xenial, 16.04). Although I have manually changed the lines in the apparmor file from 20.04 to 16.04,

{ "policy_groups": [], "policy_version": 16.04 }

it still complains when I tried to build the click package:

- security:policy_version_matches_framework:phonehome.apparmor 16.04 != 20.04 (ubuntu-sdk-20.04.1) http://askubuntu.com/q/686347

The provided link does not consider this ubuntu versions, but I guess 16.04 should be valid. I have consistently introduce

set(CLICK_FRAMEWORK "ubuntu-sdk-16.04")

in the json file, but without luck.
I do not know why clickable insists in 20.04, when none file has this version number typed.

@zezba9000 said in Ubuntu 16.04 BQ Aquaris M10 Mir app dev issues.:

I'm not familiar with "Libertine". Does this make it easier to dev on X11? You have more info on this?

There is some information on using Libertine containers in the UBports documenten. It can be found by following this link.

It is framed in the context of running desktop applications, but it works just as well for commandline applications also.

@Bolly I actually stopped backing up teleports. It doesn't make sense anyway since all data are in the cloud. They were just old backups I did years ago. I think I included everything in the app data folder 😅

@PerlMax said in Custom builder for a library:

How can I start a app from the terminal, so that I can see error messages?

Running clickable logs should let you see the log messages for your app, if there are any. However, given what you've posted already, it seems you are running a bash script, which runs some other process, which has hit a SIGABRT condition.

Perl is not really a supported language for building UT applications, so we'd need to see your code (preferably in a git repository) to be able to help much further. Whatever you are running on the first line of your script is failing. If it is perl, then you might want to also check the system log on your device (/var/log/syslog) for possible apparmor DENIALs.

Here I am with answer to the my own question.
RTFM!
clickable log command very useful. 🙂

Volla X23:

ubuntu-sdk-20.04

sysbench --test=cpu --num-threads=2 --cpu-max-prime=20000 run
1924 events per second

sysbench --test=cpu --num-threads=2 --cpu-max-prime=20000 run
1927 events per second

sysbench --test=cpu --num-threads=8 --cpu-max-prime=20000 run
4222 events per second

sysbench --test=memory --num-threads=4 run
Total operations: 69640008 (696072.68 per second)
68007.82 MiB transferred (6799.51 MiB/sec)

sysbench --test=mutex --num-threads=64 run
total time: 4.2907s