Clockwork
Clockwork allows you to customize launcher icons and dynamically update them.
Notes
- You have to install icon packs separately
- Not tested with Theme pack support for Sailfish OS enabled
Usage
At first, install any icon pack compatible with Theme pack support for Sailfish OS. You may skip this step if you want to use only built-in dynamic icons.
Go to Settings ⟶ Clockwork and choose any of installed icon packs. Icon packs are applied immediately (no Lipstick restart required). Also you can set arbitrary icons from pack for any application.
By default, Clockwork enables dynamic icons for Clock and Calendar applications. This can be disabled in settings.
Source
See on GitHub: https://github.com/dseight/clockwork
Screenshots:
Category:
Application versions:
| Attachment | Size | Date |
|---|---|---|
 clockwork-0.2.8-1.aarch64.rpm | 93.5 KB | 08/06/2021 - 02:21 |
| clockwork-0.2.8-1.armv7hl.rpm | 87.04 KB | 08/06/2021 - 02:21 |
| clockwork-0.2.8-1.i486.rpm | 103.77 KB | 08/06/2021 - 02:21 |
| clockwork-0.2.7-1.armv7hl.rpm | 86.89 KB | 11/09/2020 - 21:52 |
| clockwork-0.2.7-1.i486.rpm | 97.57 KB | 11/09/2020 - 21:52 |
| clockwork-0.2.6-1.armv7hl.rpm | 86.7 KB | 11/09/2020 - 15:14 |
| clockwork-0.2.6-1.i486.rpm | 97.2 KB | 11/09/2020 - 15:14 |
| clockwork-0.2.5-1.armv7hl.rpm | 84.59 KB | 07/09/2020 - 02:19 |
| clockwork-0.2.5-1.i486.rpm | 94.77 KB | 07/09/2020 - 02:19 |
| clockwork-0.2.4-1.armv7hl.rpm | 84.61 KB | 07/09/2020 - 01:29 |
| clockwork-0.2.4-1.i486.rpm | 94.75 KB | 07/09/2020 - 01:29 |
| clockwork-0.2.3-1.armv7hl.rpm | 84.12 KB | 04/09/2020 - 01:43 |
| clockwork-0.2.3-1.i486.rpm | 94.2 KB | 04/09/2020 - 01:43 |
| clockwork-0.2.2-1.armv7hl.rpm | 82.84 KB | 03/09/2020 - 22:34 |
| clockwork-0.2.2-1.i486.rpm | 92.5 KB | 03/09/2020 - 22:34 |
| clockwork-0.2.1-1.armv7hl.rpm | 82.46 KB | 01/09/2020 - 19:27 |
| clockwork-0.2.1-1.i486.rpm | 92.36 KB | 01/09/2020 - 19:27 |
| clockwork-0.2.0-1.armv7hl.rpm | 81.09 KB | 21/07/2020 - 15:52 |
| clockwork-0.2.0-1.i486.rpm | 90.59 KB | 21/07/2020 - 15:52 |
| clockwork-0.1.0-1.armv7hl.rpm | 77.04 KB | 16/07/2020 - 03:19 |
| clockwork-0.1.0-1.i486.rpm | 85.91 KB | 16/07/2020 - 03:19 |
Changelog:
* 0.2.8
- Add aarch64 build
- Fix preview for icon packs without icons for Jolla apps
* 0.2.7
- Fix icon customization for multiple flatpak apps
* 0.2.6
- Fix icon customization support for some native apps (#5)
- Fix icon customization for flatpak apps (#4)
* 0.2.5
- Fix dynamic calendar icons not working for some of the days
* 0.2.4
- Spanish translation (thanks to @carmenfdezb)
* 0.2.3
- Update Android apps icons after Android Support service start (fixes #1)
* 0.2.2
- Chinese translation (thanks to @dashinfantry)
* 0.2.1
- Fix dynamic icons freeze
* 0.2.0
- Dynamic icons now support theming by icon pack
- Dynamic icons preview is properly updated
* 0.1.0
- First release
Comments
carmenfdezb
Mon, 2020/09/07 - 07:43
Permalink
My pleasure :)
dfstorm
Fri, 2020/09/04 - 10:15
Permalink
Is that the https://openrepos.net/content/dfstorm/newaita-icon-theme icon pack I made a while ago in the screenshoot ? ;) nice ^^'
In anycase, as for me, I think you should try to work with fravaccaro :) The communauty would have much to gain and both of you too by sharing experiences and joining forces.
If I were in your position and had put a loot of effort in my own app; I too wouldn't want to stop working on it like that... But you still can help the other app and work on your own at the same time ^^' And decide later if you keep doing one or the other ;)
cheers
fravaccaro
Tue, 2020/09/08 - 13:47
Permalink
The only thing that matters to me is giving people the best tools possible and you can see my words being put in action as the code on GitHub is on a team account, not my own. I don't have any ego problem and I'd be more than happy to collaborate with someone who is far better than me in coding, sharing the experience I got in hacking the OS and focusing my effort in documentation and translation managing. Since a project already exists and some third party themes are already out there to me it makes no sense to reinvent the wheel.
But the author may think otherwise, since he didn't even bother replying to my last message.
dseight
Tue, 2020/09/08 - 14:25
Permalink
> ... to me it makes no sense to reinvent the wheel.
Why do you think about this project as about "reinvinting the wheel"? It's just a different point of view on the same problem: launcher icon customization. While themepack-support is about whole system customization (like system icons, sounds, etc.), this project is focused only on launcher icons. Customization of launcher icons is the only thing that clockwork will ever support.
> But the author may think otherwise, since he didn't even bother replying to my last message.
Sorry, maybe I'm missed something... There were no questions in your previous message, so I just treated it as statement.
fravaccaro
Tue, 2020/09/08 - 20:14
Permalink
So reusing the ideas I've had in the past years to a limited set of what my apps are doing, exploiting the work I have done (you know, there are themes available in the first place cause I spent sleepless nights writing the documentation) it is not reiventing the wheel?
When themepacksupport came out, a guy made the first GUI, I contacted him and asked to join forces, he said he left and that I could fork the GUI if I wanted, so UI Themer was born. My history In the community has been about collaborating in order to make this ecosystem better, if I knew you were working on this we could have agreed to a solution, even removing the icon code from themepacksupport altogether for example, because you know what? The themes require themepacksupport! Yourself said in the description that you have not tested Clockwork with themepacksupport, so what's the advantage to the user? Possibly messing up his device? Wasn't it more logical to drop a line to me?
"please keep in mind that both me and the themepacksupport project are happy to get people onboard"
Does this require to be a question? Not talking about the tone of the rest of the "statement", which was far from not wanting to open any kind of dialogue.
dseight
Wed, 2020/09/09 - 04:36
Permalink
First of all, I would like to sorry if any of my words sounded rude or even offensive. That wasn't intentional. It may happen just because English is not my native language and it's hard for me to "feel" it.
> So reusing the ideas I've had in the past years to a limited set of what my apps are doing, exploiting the work I have done (you know, there are themes available in the first place cause I spent sleepless nights writing the documentation) it is not reiventing the wheel?
I wouldn't really call normal themes use as "exploiting". There is also no any code or graphics from themepacksupport in there (even calendar and clock icons are custom-made svgs), so it's hard to mark it as "exploiting".
By the way, the idea behind icon theming is not a new thing. I really remember the times when LauncherPro was the only good Android launcher (it was somewhere around 2010). Even then it had icon theming support: both by applying icon pack and by picking individual icons for apps. Idea of dynamic clock icon isn't new either: iPhones had this since iOS 7 release in 2013.
And while you may call this project as "reinventing the wheel", I would prefer to call it as "alternative solution". Yes, it allows to customize only launcher icons — and this is a completely deliberate decision.
> The themes require themepacksupport! Yourself said in the description that you have not tested Clockwork with themepacksupport, so what's the advantage to the user? Possibly messing up his device?
Yep, I'm aware of themepacksupport requirement in some themes. It was taken into account, and it's possible to use such themes with only clockwork installed since the first release.
Though clockwork wasn't heavily tested with themepacksupport enabled, it was always tested with themepacksupport installed. Also I've done some smoke-tests to make sure that nothing goes wrong when icon pack from themepacksupport is applied and clockwork is enabled on top of it. Speaking about advantages, here they are:
While it's defenitely possible to have all of above advantages in themepacksupport as well, it would require heavy rework.
> Does this require to be a question? Not talking about the tone of the rest of the "statement", which was far from not wanting to open any kind of dialogue.
Once again, sorry. It's really hard for me to feel the tone of the message.
If you have any particular ideas about what advantages themepacksupport could take from this project, or any specific suggestions, feel free to dm me in tg.
fravaccaro
Tue, 2020/08/18 - 14:51
Permalink
I would have not minded for collaboration, as I've been calling for it for years, but I guess it's more profitable to reinvent the wheel :)
dseight
Wed, 2020/08/19 - 21:26
Permalink
This project started with a simple idea: dynclock without dependency on ImageMagick (because, hey, we have Qt to do the job!). But then I realized that I have a cool mechanism to update any icons without lipstick restart — and that's where icon pack support was added.
While this project intended only for app icons theming (and will always be), harbour-themepack supports theming of all system resources. So, I think that both of them might co-exist. It's always nice to have alternative solution :)
fravaccaro
Fri, 2020/08/21 - 01:20
Permalink
I sincerely admire your achievement, although I think it's partly overlapping themepacksupport, as users may not know which one to use for what.
Themepacksupport and UI Themer have been team-oriented since their inception, as I want them to gain traction, improve and be helpful besides my (let's be honest) poor coding skills and even surviving myself.
That's why at the end of the day I don't think it makes a lot of sense to split efforts and make apps which "work but could be better" - this is true for themes as well as other apps which have seen devs working on basically duplicates because they were not willing to join forces.
Of course feel free to take your own path, just my 2 cents, but please keep in mind that both me and the themepacksupport project are happy to get people onboard.
pvcn
Mon, 2020/08/10 - 19:56
Permalink
I like this function a lot, thank you! It worked perfectly untill three days ago, since then, it shows one particular time (clock) and date (calendar). Restart or deactivate from app doesn't solve it, app icons stay frozen three days ago...
dseight
Tue, 2020/08/18 - 19:33
Permalink
Huh... That sounds bad. I'll try to figure out why this has happened.
pvcn
Sat, 2020/08/29 - 09:07
Permalink
Would be nice to have a fix for this, deactivation of dynamic icons doesn't work, uninstalling the app neither, app icons still stay frozen at one particular time and date (7th)... Edit: restart lipstick actualises time and date to the moment after lipstick restart, but time doesn't change then but stays frozen again. Deactivation from app unresponsive, when uninstalling app, time and date fall back to old time and date (7th) but not to default icons. How can i restore default icons?
dseight
Tue, 2020/09/01 - 19:30
Permalink
Should be fixed with 0.2.1: just go to Settings after update, disable all previously enabled dynamic icons, and then enable them back.
pvcn
Wed, 2020/09/02 - 11:19
Permalink
Thanks a lot for the Fix! ☺ Just updated: Icon Freeze has gone, Clock Icon actualises as expected and Calendar Icon shows right date, deactivation and return to default icons also works. Best regards
drakegao
Thu, 2020/07/16 - 08:06
Permalink
Downloading now. Dont know how it will work. But thanks. It is very good that sailfish os app store is still on and so is the openrepo, these two keeo sailfish alive. Thanks for developers free time, although i hipe jolla store can have some paid apps.
Pages