Bug 503432

Summary: cross-platform kclock
Product: [Applications] KClock Reporter: GK <hgkamath>
Component: GeneralAssignee: Devin Lin <espidev>
Status: RESOLVED INTENTIONAL    
Severity: wishlist CC: hanyoung, kde, kde
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Microsoft Windows   
OS: Microsoft Windows   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description GK 2025-04-27 13:50:03 UTC 
SUMMARY
One wonders if KClock could be made to be cross platform with binaries available for each OS.
There are many KDE apps which are already cross platform, filelight, krita, digikam etc 

It would be desirable to have the same clock app (KClock) for a multi-OS user to have a uniform cross-platform experience.
Consider the following OS-es in order of desirability
1. Windows
2. Android
3. Mac
4. IOS 
One will need a location such as github/gitlab releases to download the artifact for a given OS.

Its also desirable for KClock to able to run, using only the QT libraries without pulling-in or necessitating the KDE desktop.

For windows, scoop manifest entry will also allow one to easily fetch and install on windows.

STEPS TO REPRODUCE
1.  google for Kclock binaries for windows

OBSERVED RESULT
Presently KClock seems to be available only on Linux

EXPECTED RESULT
want kclock everywhere

SOFTWARE/OS VERSIONS
Windows: win11 23h2
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: Fedora-42 
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
na
Comment 1 Kai Uwe Broulik 2025-04-30 15:52:13 UTC 
Literally every system has a clock like this. I don’t see a compelling reason for the maintenance overhead, especially for the daemon-app architecture and scheduling wakeups and what not.
Comment 2 GK 2025-05-02 07:53:59 UTC 
- I was hoping 3 things 
  - (a) maintenance overhead for cross platform is minimal
  - (b) not strongly coupled to the desktop-environment
  - (c) an simple/basic app like this is almost feature complete once one gets the tabs for clock, alarm, timer, stopwatch is done
- > every system has a clock like this
  - The compelling reason is want of uniformity
    - presently each such app on its own system has its own personality/quirks.
    - they may look similar but they are not identical, certain button locations, labeling, settings etc will be different.
    - a user has to get used to each app, and not rely on finger memory when using the app on each different system
    - low level system api like for getting time, setting timers, backgrounding, etc do not change as much, perhaps even from one OS kernel version to another, but the GUI does. If QT abstracts that change across various systems. one as an identical clock app across those systems.