Not too sure where to ask that, feel free to redirect me!

I'm currently working on getting better support between SDL and Ubuntu Touch. I've written code for SDL to add support for more features, and I'm working on a Clickable template to that effect. I hope with this to give developers an easier time porting SDL apps (including games ) to Ubuntu Touch, and perhaps to give another way of writing Ubuntu Touch apps

After some reflection and discussion with other developers, I believe that it would be beneficial to ship SDL with the base system, if that would be reasonable.

• It would avoid packing one copy of SDL with each app that uses it, and instead have one single copy of SDL on the system. SDL takes about 3-4Mb of space; the satellite libraries (there are 4) takes a few 100's of kbs each.
• It would make it easier for device maintainers to apply device-specific fixes to SDL and other kinds of tweaks when necessary.
• It would simplify the build process for SDL apps that expect SDL to be installed on the system. (CMake's "find_package(...)")
• It would allow the base system to ship SDL updates without app developers needing to update their apps, leading to better global support of SDL apps, especially when an app maintainer becomes inactive Essentially, it would "patch" apps without developers needing to do anything. And in case a device developer ships an outdated SDL, nothing prevents the app from shipping a newer copy of SDL.

I'm not sure what are all the variables to consider when making such a decision, but I suppose that I won't know unless I start the conversation!

@hlbkv Noted! I won't make any promises about the timeframe, but I'll do that when I get a chance

Is it possible, when developing a non-Qt app, to obtain some information about the current app, such as the "name" as written in manifest.json (like appname.yourname), as well as the name of the hook that launched the executable? (Excluding hardcoding them in the executable, of course)

I'm thinking something like environment variables. I've seen variables like APP_ID which seem to be derived from the app name and the hook, but I haven't seen anything like APP_NAME or APP_HOOK that correspond exactly to the fields I need.

My situation is that I'm porting SDL3 to Ubuntu Touch, and the app name and hook are needed to perform certain operations on Ubuntu Touch. Since SDL3 is a library, it can't make some presumptions about the executable.

Hello!

I'm currently working towards porting the recently-released SDL3 to Ubuntu Touch.

Most of the essential stuff like creating a window already works, but some OS-specific features like the HDPI scaling factor are available only to Qt-based program (through GRID_SIZE_PX).

Wayland has mechanisms to communicate that information to apps, which SDL use, but Lomiri doesn't seem to expose them, so they don't work on Ubuntu Touch. Would it be feasible and reasonable to implement them?

Some of the features I'm thinking about:

• HDPI scaling
• Clipboard
• Dark theme
• Cameras
• ...

I'm willing to provide help to implement those features! However, I would need confirmation that this is desirable, and I would need the help of people who are familiar with Lomiri's internals to point me in the right direction.

Thanks!

Hey! I don't have a lot of knowledge myself, but I'll reply since nobody else replied so far. I'll be corrected if I got something wrong!

The base Ubuntu Touch install is immutable, e. g. the filesystem is read-only and you can't install anything with APT. This is I believe for security and to simplify OTA updates. I believe you can change it to make it read-write, but this will prevent some other stuff from working fine. The only well-supported way to add stuff on Ubuntu Touch is though Click packages, that you can get from the Open Store.

That being said, I believe Ubuntu Touch already supports OpenVPN-style configuration in the Settings app, so there should be no need to install anything extra. I'm not sure if you can provide it a ready-made configuration file, but I know you can at least configure it manually.

EDIT: I just remembered that you can install stuff from APT on your phone, but only in a Libertine container (Creating a container can be all done from GUI, or from CLI, at your preference). That works for local apps, but not for anything that may need full access to the system like a VPN does, so it won't be useful in this instance.

I've added the undo/redo buttons! They're in the toolbar on the right. I've also made the toolbar scrollable for narrower devices.

Sorry for the delay! I said I would upload frequently, and here I go three weeks in complete silence It's harder than expected to balance real life and benevolent app development.

If there isn't any particular feature request (do post them here, on GitHub or to my committer email if you have any!), I'll probably work on resizing text areas and adding images in documents. It's not particularly long to add features, I just need to find the time to do it

I've added a new tool: the typewriter! It lets you type text with a keyboard on the document.

To edit the text area, you must pull up the toolbar and tap the edit button.

I'd like to stress that the tool is still quite uncomfortable to use, though all the basic features should be there. Some notable issues for now is the line wrapping which cuts in the middle of words, the lack of support for resizing text areas, the lack of support for different colors within a text area, and the PDF export which makes the text not look the same (different font, different support for line wrapping).

I released it in this state because of the time it took me to get it working at all, but also because I wanted to call for ideas about how the tool should work for it to be comfortable to use by everybody. If you have any idea or preference for how the ideal typewriter tool should work, you can send ideas here or on the GitHub discussion at https://github.com/Semphriss/Annotate/discussions/11

Is there any long-term plan to add different "flavors" of Ubuntu Touch with different desktop environments, like GNOME?

This is probably very low priority, but I wondered what it would feel like to use GNOME with Ubuntu Touch.

Alternatively, if someone were to do the work, would it be welcome as a contribution sometime in the far future?

@domubpkm I'm not familiar with the epub format or with the libraries that exist to edit epub documents in JS, but I can keep a note to check that later.

@domubpkm I've been planning to do a little demo document to serve as a tutorial, but I haven't taken the time to finish it yet. I'll try to get something out soon!

@AppLee Hey!

I just finished adding support for zooming. It should be on the OpenStore in a few minutes.

Sorry for the delay, and no worries, I understand it's not easy to draw on phone

As for QML, I'd really like to get started whenever I can, but despite spending quite some time learning, I don't think I'll be familiar with QML soon enough to be able to provide support for a native app.

If you'd like to create a basic WebView with minimal bindings for file operations, I would be happy to merge it and finally throw away the C++ web server. If you'd like to give it a try, all the relevant JS functions are in www/js/file_manager.mjs. If what you had in mind was closer to converting Annotate to a fully native app, UI included, I'd need to take the time to learn QML enough to be able to provide maintenance for it.

That being said, any attention Annotate can receive will be beneficial in the long run, so contributions are always appreciated.

I've added a new tool: the lasso, which selects existing strokes and moves them around.

I'll probably adopt a "release early, release often" approach with Annotate, so expect many small new features each few days

@matteo It's on my to-do list! I haven't yet found a way to keep the toolbar "sticky" and zoom-free in HTML. I still have to do some research on how to implement that.

I'll keep it high on my priority list!

Now, a longer post to describe what Annotate can and can't do at the moment. I've put this in the app description on the OpenStore, but I'm copying it here for convenience.

Currently supported:

• Create new, empty documents
• Import existing PDF files
• Draw on the pages
• Highlight elements
• Erase elements
• Rename files (characters are limited)
• Delete files
• Export files to PDF and share them with other apps

On my to-do list:

• Text and images
• Add/duplicate pages
• Share a document in Annotate format, for transfer between devices
• Undo/redo
• Proper support for zooming
• Translation to other languages

Known issues:

• Exporting files with highlighter will make the highlighter look opaque (#3 on GitHub)
• Exporting shows a download pop-up (#4 on GitHub)
• Sharing a document from another app to Annotate won't work (#5 on GitHub)
• Large PDF files (>10Mb) may take a lot of time to load on less performant devices

Is there any feature you'd like to have? Any feature you like more than the others? Any bug I've missed?

Hello! I've just uploaded Annotate to the OpenStore. Since it's my first personal Ubuntu Touch app, I'd like to collect some feedback about the app and the release process.

Annotate is an app that lets you draw/highlight PDF files. You can import PDF files, draw on them, rename them, reorganize them, and export them back to PDF files and send them to other apps.

I'm looking for any kind of feedback people may have, be it bug reports, feature requests, questions, clarifications, or anything else. The repo is here on GitHub, but I'm opening this thread in hopes that I reach more people, so feel free to post here.

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!

I'm about to upload my app to the Open Store. I'm pretty excited!

I'm used to distributors like Steam that have whole processes to promote new apps. Does the Ubuntu Touch community have something where I can announce my new app, like a forum category? Is it standard to just upload on the Open Store without any announcement?

What is the recommended way to "present" my app to the community?

@AppLee It works! Many, many thanks!

For exporting, I will let the user tap the document in the download pop-up, and the webview will handle exporting. I tested it, and it seems to export as intended.

I really should switch my app to use QML with a WebView object, but unfortunately I'm not remotely familiar enough with QML to implement it without help.

If you (or any passerby) is curious about the app in question, it's here: https://github.com/Semphriss/Annotate. I'll upload it to the Open Store in a few days, after fixing the last few rough edges.

Thanks again for the help! I'll see if I can switch this thread to a Q&A one so that I can accept your answer.

@AppLee Hey, thanks for checking!

Here's a basic reproducible project: https://gitlab.com/Semphriss/ut-webapp-contenthub

The first commit is a basic project as generated by Clickable, all the defaults except the project type set to HTML. I did not change any file.

The second commit is the basic steps I followed to attempt to make it work, which will give the same behavior as I described.

I'm developing a webapp and I'd like to let users export files from my app. I planned to do this using an <a href="data:image/png;base64,..." download="myfile.png">.

I added the "content-hub": "appname-contenthub.json" line in the manifest, set destination, share and source to "all" in that file, and I added the "content_exchange" policy group in the apparmor file.

It seems to be the intended way of working because it unlocks the Content Hub, but whenever I download the file and try to share it elsewhere, whenever I tap an external application, it doesn't react.

When I check the log, I see these 3 lines whenever I tap an app in the content hub view:

Jun 01 11:07:37 ubuntu-phablet aa-exec[14559]: Dbus error:  QDBusError("org.freedesktop.DBus.Error.AccessDenied", "An AppArmor policy prevents this sender from sending this message to this recipient; type=\"method_call\", sender=\":1.458\" (uid=32011 pid=14559 comm=\"webapp-container --app-id=appname.yourname www/ind\" label=\"appname.yourname_appname_1.0.0 (enforce)\") interface=\"com.lomiri.content.dbus.Transfer\" member=\"Direction\" error name=\"(unset)\" requested_reply=\"0\" destination=\"com.lomiri.content.dbus.Service\" (uid=32011 pid=14637 comm=\"/usr/bin/content-hub-service \" label=\"unconfined\")")
Jun 01 11:07:37 ubuntu-phablet aa-exec[14559]: Dbus error:  QDBusError("org.freedesktop.DBus.Error.AccessDenied", "An AppArmor policy prevents this sender from sending this message to this recipient; type=\"method_call\", sender=\":1.458\" (uid=32011 pid=14559 comm=\"webapp-container --app-id=appname.yourname www/ind\" label=\"appname.yourname_appname_1.0.0 (enforce)\") interface=\"com.lomiri.content.dbus.Transfer\" member=\"SelectionType\" error name=\"(unset)\" requested_reply=\"0\" destination=\"com.lomiri.content.dbus.Service\" (uid=32011 pid=14637 comm=\"/usr/bin/content-hub-service \" label=\"unconfined\")")
Jun 01 11:07:37 ubuntu-phablet aa-exec[14559]: Dbus error:  QDBusError("org.freedesktop.DBus.Error.AccessDenied", "An AppArmor policy prevents this sender from sending this message to this recipient; type=\"method_call\", sender=\":1.458\" (uid=32011 pid=14559 comm=\"webapp-container --app-id=appname.yourname www/ind\" label=\"appname.yourname_appname_1.0.0 (enforce)\") interface=\"com.lomiri.content.dbus.Transfer\" member=\"State\" error name=\"(unset)\" requested_reply=\"0\" destination=\"com.lomiri.content.dbus.Service\" (uid=32011 pid=14637 comm=\"/usr/bin/content-hub-service \" label=\"unconfined\")")

Is this a problem with my app, or an issue with Ubuntu Touch security?