Signal UT: Signal-Desktop for Ubuntu Touch
-
@danfro Thank you for your comment. It is good to know what one can expect when it comes to the graphic user interface. No text adjustment to be expected anytime soon. I am glad to know that this text resizing functionality has been brought up before (not visible in this forum by search). I understand that the Ubuntu Touch design did not permit for text adjustment. Maybe in version 26.04-1.0, 28.04-1.0, 30.04-1.0 it is a good time to consider text adjustment when everything needs to be adjusted anyway.
Thank you! Now we know what to expect in this part. That was really good information.
-
@mango I remember discussions from TG groups every now and then. And @pparent I am sorry if my comment about glasses was misleading. I didn't wanted to be disrespectful for people with reduced sight.
The qml code does in theory allow to use relative text sizes. See: https://ubports.gitlab.io/docs/api-docs/index.html?p=lomiriuserinterfacetoolkit%2Fqml-lomiri-components-label.html
I think this might even be a Lomiri adjustment, because I don't see textSize property in normal Qt Label.
Maybe we should bring up this topic into develompent groups again.But for instance buttons generally don't have word wrapping available by design. So increasing a label by using a larger text (not mentioning longer translations, German is bad in that regard
) may make the button label being cut off. Just as one example on how complex this is.
I guess I should start by using this setting in my apps and try to rework them at least step by step. -
Long text in short, size defined buttons is a classic... The buttons need to resize according to the text on a new line if there is little space. Sometimes landscape mode reveals more text in buttons. This is especially notable when using a translations file to set the labels based on locale setting.
-
@danfro said in Signal UT: Signal-Desktop for Ubuntu Touch:
There needs to be made a setting, all app codes need to be adapted to use that setting.
By the way question: does anyone know any way to get the GRID_UNIT_PX configured in Ubuntu tweaks?
Because the following command seems to allways give the default value for the device:
echo $GRID_UNIT_PX -
I'm not sure that @danfro's answer is painting a full picture.
In fact, I'd say that the main current development effort may bring accessibility improvements.Most of the work around accessibility is not done by individual unpaid developers, but by professionnal devs working to develop the framework that the individual developers are widely using to help them. In the case of native UT applications, the framework is QT.
The bulk of the work done currently with UT is to upgrade the framework from QT5 to QT6.
Although this is done because QT5 is now obsolete and unsupported, this will bring the general improvements done in QT6 to support better accessibility. In your case, this means the flexbox layout that allows developers to design redimensioning interfaces more easily.
What you could do to help is reading about the works of people more advanced in accessibility with QT6 than UT, I mean KDE, and look at the things they have already done, because that's where the easier part to do is, and as such can be a beginning. Most enormous work has been done not in a mammoth project with big resources, but slowly over years. The important part is to actually begin. If the settings do not exist in the UI, it's not so important. What the UI does is mostly calling an interface to change the settings, gsettings, that can be also called from the command line. As UT relies on an existing distro, the APIs to set accessibility features may already exist. That don't mean that all will work automatically, but identifying what should work and don't is called bug searching. Once it's a bug, it can be added to the big TODO list (gitlab issues).
After all that, it's sure that devs will not work automatically on bugs that don't inspire them.
But something more meaty than a forum post could trigger some progress. -
@pparent Looks like its somehow working with a config file: https://gitlab.com/myii/ut-tweak-tool/-/blob/master/src/app/qml/behaviourTab/LomiriScaling.qml?ref_type=heads#L32
-
@gpatel-fr I do admit, I didn't look into Qt6 yet. Maybe that will bring us ways to improve. And you are right, since we use components like Qt or Ubuntu, there are professionals working on that. But it still needs people to make use of it in UT.
-
@danfro said in Signal UT: Signal-Desktop for Ubuntu Touch:
working with a config file:
Thanks for this hint, I stand corrected, I was thinking that settings in UT were done via a dbus mechanism covered by the gsettings interface - dbus allows to notify running applications of the change, an environment variable does not. So setting this value will not apply to running applications, leading to inconsistencies between applications if started before or after the change.
-
@danfro said in Signal UT: Signal-Desktop for Ubuntu Touch:
Looks like its somehow working with a config file
But I don't have the authorizations to access a config file of another app from within an app like Signal UT? Is there another way to get the value, compatible with a confined app?
-
@gpatel-fr We certainly can als use gsettings. I made a proof of concept for ThemeSwitch app a while ago (https://gitlab.com/Danfro/themeswitch/-/tree/gsetting_focal?ref_type=heads).
I am almost sure we can't use other apps values without loosing confinement. The value would need to be provided by the system. I guess if GRID_UNIT_PX could be changed in system settings and apps read that, that might work. Or it may need another apparmor rule. But I am really not that knowledgable to answer all details.
