@pparent

Yes I ack that they are open because I think I understand why. The idea is here but solving it is another story because there is always an effort for every result and sometimes the result is not worth it.

Well I don't think you should be so pessimistic:

• First because if they are showing some interest in porting their app, I don't know why suppose they are not willing to really do so.
• Second because Qt6 is supposed to enable cross-platform development easily.
• Third because you don't how the userbase of UT will evolve in the next years, let's how it could grow significantly making it more attractive to port some apps.

Of course the port might not happen overnight.

Yes I ack that they are open because I think I understand why. The idea is here but solving it is another story because there is always an effort for every result and sometimes the result is not worth it.

But did you did you read this?

https://forums.ubports.com/topic/11546/organic-maps-on-ubuntu-touch/8

@bunt7 Contacted Alexander the Co-Founder of organic maps, and managed to convince him about the importance of Ubunt Touch, and he is now open to the idea of porting his app to Ubuntu Touch.

I'm also in direct contact with him, and he posted in the topic above, mentioning explicitly mobile Linux.

I'm not sure how much of work he would be willing to invest into this, but he is clearly open at least conceptually.

Thanks for pointing me to this interesting discussion.

It's easy to mask some parts of the UI to make it more compact, however it's reducing functionality.

Bringing it back in another way more appropriate for mobile is possible but it's making code more complex with more code paths. As you are a dev yourself I don't presume learning you the basics of your job

These points are not obvious to solve and are exactly raised by the reply from 'biodranik'. Nothing is impossible of course and compromises can be done (they tend to be temporary unfortunately as users are vocal) but there are always limits to complexity. So it could happen yes; my understanding is that the project is in a 'friendly' - hum - competition with a fork that happens to only targets mobile, ie Android; or it could not happen. Depends on the talent and persistence of the PR author.

In the mean time, much also depends on the possibility to use the UT OSK with Flatpak. I have a vague idea of compiling the Qt plugin for different versions of the Kde support packs and join it to the thing after installing a flatpak application. However compiling the plugin is easier said than done, I have already some frustrating hours done on this due to me being an ignoramus about QT and that's only the beginning I would have to cross-compile it for arm next. Only after that could I check if it's a crazy idea that would never work or not :-). Obviously this would only target QT(Kde) Flatpak apps, but realistically Kde is more advanced toward a mobile convergent interface (with Plasma) than Gtk.

I use it on my desktop, like it but I find the possibility of using it on a small screen like the one of my FP5 rather unlikely.

https://github.com/orgs/organicmaps/discussions/11805

@Moem
Look a the interface it's very far from being responsive or usable on a phone screen, it's very much designed for desktop

I will take you at your word. I just noticed it because of the recent question, that came up on Telegram.

Android app and the desktop app are the same code based on Qt

Yes that's interesting. I think Okular supports also Android and I noticed with some surprise that opening the flatpak version on UT, it's possible to zoom in and out with the touch screen. If it's possible to do the same with Organic Maps, it could be interesting.

Could depend on how responsive it is really.

Well it seems to me that the Android app and the desktop app are the same code based on Qt. At least the two of them point to the same repository.

there might be a future possibility to port for Organic Maps, their desktop app seem close from responsive (but requires Qt6)

I use it on my desktop, like it but I find the possibility of using it on a small screen like the one of my FP5 rather unlikely. Could depend on how responsive it is really. I am investigating the possibility of using flatpak under UT BTW.

https://josm.openstreetmap.de/wiki/Fr:Introduction

Good candidates are applications close to being responsive.

I guess you have noted there might be a future possibility to port for Organic Maps, their desktop app seem close from responsive (but requires Qt6)

https://flathub.org/en/apps/app.organicmaps.desktop
https://organicmaps.app/news/2024-01-27/how-to-run-organic-maps-on-windows/

Also I've noted this app that could be cool:
https://snapcraft.io/openboard

The only tedious thing with this kind of package is that they have some dependencies that are not present in the system and that you have to embed inside the package. Well If it's a few dependencies it's ok but I guess when there are unmet dependencies about Qt modules it can get very tricky.

How about this? https://snapcraft.io/josm

Does it mean we can convert other snaps app to ubuntu touch ?

Well you could. But probably not directly , for most packages if you want to make it fully integrated. As you may have seen I'm now recompiling Signal-Desktop from source code, and apply some patches for different things like having a responsive interface and a functional keyboard. The whole process requires quite a bit of manual work to get close to a fully integrated and working application.

@Shapa said in Crazy stuff: sudo snap install signal-desktop:

I am thinking firefox browser could be good use case

Isn't uWolf good enough for that? uWolf is basically a custom firefox.

Does it mean we can convert other snaps app to ubuntu touch ?

I am thinking firefox browser could be good use case

https://forums.ubports.com/topic/11532/signal-ut-signal-desktop-for-ubuntu-touch

Congrats on what sounds like an amazing start on this!

I could do it reusing the work of @ChromiumOS-Guy in uWolf!

I can officially send signal messages from a native Ubuntu Touch app, without Waydroid!

Even though for now it's not convenient , since keyboard hides the text area, and the enter button of the keyboard somehow does not trigger sending the message, and the "send" button in signal is hidden until you expend the editing area. But still very usable.

For now everything is messy, but I will try to make it available soon (I think it should be possible to do a click package, but I'm not sure yet)

Ps: Note that I could do it with Mobian version only for now.

https://github.com/0mniteck/Signal-Desktop-Mobian/

That might be worth a guide/instruction with steps on how to do.

I will publish a repository and a .click file for signal-launcher, pretty dummy stuff, but it can help making it usable for reading messages only, until we find a way to make the keyboard usable.

Unfortunately its the desktop app which cannot be a "main" app, as in you always need to keep a separate phone.

Or you install it in waydroid in the same phone and open it from time to time only.

Unfortunately its the desktop app which cannot be a "main" app, as in you always need to keep a separate phone.

@pparent said in Crazy stuff: sudo snap install signal-desktop:

I've actually succeeded to start the app with acceptable scaling by creating a dummy unconfined app with simply a .desktop file with the launcher:

Exec=env GDK_SCALE=2 /snap/bin/signal-desktop --no-sandbox %U

That might be worth a guide/instruction with steps on how to do.