You really need to take an hour or two and learn git.
No, please do not suggest using the git
command line tool: To really use it, one has to comprehend the basic concepts of Git, which constitutes a manageable, but steep learning curve for a little while.
But I already failed multiple times to get across, that GitHub’s web-frontend is quite suitable without much knowledge about Git and also without using the command line at all.
IIRC, ultimately Andrea always failed to either access her extant GitHub account (I have no idea why resetting a forgotten password does not work for her), or to create a new one.
Maybe that has changed and offering some support when questions arise (I still do, @Seven.of.nine) is less futile than before.
you could try maybe gitlab? i once heard an excellent picture for imagining how to use git. imagine a drawer, then if you want to put content in it you first pull it with “git pull”, then you add content with “git add *” * is every file, but you can also specify a file here and then you label it with 'git commit -m “” ’ and then you close the drawer with “git push”. you don’t have to use it but maybe this also helps others in understanding git
Modifying the keyboard is easy. Example:
Files are in /usr/share/maliit/plugins/com/jolla/
and are editable with vi command.
And I don’t know another phone where the user can ssh into it.
If one has a look into the qml files in /usr/share/lipstick*
and /usr/share/sailfish*
, everyone can easily see that huge delays are implemented with intention. This is not slow software, this is not slow hardware, SFOS is intentionally coded to behave this way.
I ask myself, and I want to ask the community, why was this done this way…? Does anyone know?
I have noticed this too!
There are dozens of files, can you be more specific?
FWIW I believe most animations can be configured centrally.
Yes, here is a small example selection of the ~90 files with delays I found (I’ve set’ them mostly to 1/4 - edit: 1/3 - of original value on my phone).
/usr/share/lipstick/simplecompositor/simplecompositor.qml
/usr/share/lipstick-jolla-home-qt5/compositor/ApplicationCloseGestureHint.qml
/usr/share/lipstick-jolla-home-qt5/layers/PartnerLayer.qml
/usr/share/lipstick-jolla-home-qt5/lockscreen/EdgeIndicator.qml
Surely there are some files remaining I haven’t found yet.
Centrally configuration would be fine! Then everyone could set it from snappy to relaxed as preferred. At the moment it’s imho a disaster. But this is statically written into the qml files. I had to search and change manually.
Thanks. So duration
is the keyword.
find /usr/share/jolla* /usr/share/lipstick* -name '*\.qml' -exec grep -lw duration {} + 2>/dev/null
Yes there’s much more. And if you search /usr/share as a whole, even more (application-specific).
But before that you should check out these:
mcetool |grep -iE 'fad|dur|del|ani'
I don’t remember if setting these survives a reboot, but at least until then they take immediate effect.
Another keywords seem to be ‘interval’, ‘velocity’ and ‘delay’. Edit: and ‘FadeAnimator’
TLDR
All my research was made more or less by trying and guessing on a SFOS 4.5.0.24/25 system. And as I set it to a bad state by mishappening 2 weeks ago, and now struggling with setting my mistakes back to a working state as it was before and well working for many months, I take the opportunity to proceed to 5.0.0.67 on my other tinkerphone and have a look what’s the matter there. As soon I have results, I’ll report here.
You should make a copy of org state and version your changes
But i think we go off topic here
Couldn’t one implement some way to fix this with a variable, like a multiplier? A bit like the ‘edge swipe control’ setting package in chum (by Nephros)?
Yes, you can: It is all extant QML code on you device, which has to be parametrised.
There’s a patchmanager patch that does pretty much that, it’s called Animation Settings.
TBH this is something that needs fixing. Its like that for ages and noone at Jolla seems to care. Or at least give an answer if there is a technical issue with it.
Regarding animation speed, I see it more as a personal impatience issue rather than a technical one
Yes, but I get impatient if I have permanently to wait for the slow and delayed UI. It’s really boring and it also makes no good impression to my colleagues watching me operating the phone.
At least I found a value of 1/3 is the best, some values in the qml files also set to 1/4 and few to 1/10. I’ll post the tweak list soon in the thread
What the heck, I’ve used Sailfish for ten years and only now hear about this UI thing. Have to take a look in to it.
To my mind this would be a very good question for a community meeting as there are Jolla employees as well in that chat.
I don’t think there is a technical issue, because the tweaked version has less ‘hangs’ (timeout errors?) than the original version. It seems that the delays also desturb the working flow of the device and not only the user’s one.
Yes @Cryx please ask there if it’s possible for you and share the answer here!