Why?

[PavelLoparev]

just curious why did you need to build yet another calc app? just because others do not follow theme switching or something?

[sheep-farm]

I believe it is always beneficial to create applications that reflect the identity of a specific operating system or environment. Using a KDE or GNOME calculator, for instance, results in a poor user experience, to say the least. In my view, it makes perfect sense for Omarchy to create applications that align more closely with its own philosophy.

[PavelLoparev]

Well, following this logic they should've written all the apps they use in omarchy but they haven't. calc that was used in 3x branch was perfectly fine :)

[phobot]

Just because others do not follow theme switching is good enough for me. You know you can install calc and rebind the shortcut persistently right?

[PavelLoparev]

yes I do. I don't try to be rude or something, it's just raises questions:

1. previously the approach was patching existing software. for example, dhh patched chrome, herdr and something else. why not follow this approach?
2. now we have patched soft + new soft (but the root cause is the same basically). what is the rule? when you guys decide to patch and when to develop new?
3. what to expect from new omarchy releases? the whole bunch of new unknown vibecoded software (have no objection about ai coding at all, I'm all for it jic) just because theme switching doesn't work as you guys want it to work?

this is just strange at least. this is approach of junior developer "wow, this is not what I want, I will rewrite everything!!!".

again, no offense, just want to understand the logic here.

[omarchybot]

This is an automated triage pass, so treat it as "a bot read the thread and checked the source", not as an answer from the maintainer.

There is no defect reported here. I read the issue and all four comments against the code on master and there is nothing in the thread that says Omacalc computes or does anything wrong, so there was nothing to reproduce or diagnose. The questions being asked — why build a new app instead of patching an existing one, and where that line gets drawn for future releases — are the maintainer's to answer, and a bot answering them for him would be worth nothing. I have left the issue open for that; I am not closing it or relabelling it as off-topic. Issues is also the only place in this repository where it could have been asked, since Discussions is disabled here and there is no issue template saying otherwise.

Two things that are matters of record rather than opinion, in case they are useful to whoever reads this next. The reason Omacalc exists is stated in its README: it follows the Omarchy theme and the system dark/light mode, and re-tints live when the theme changes. And the calculator it displaced was GNOME Calculator — the upgrade migration in basecamp/omarchy is literally titled "Replace GNOME Calculator with Omacalc". Neither of those settles the patch-versus-build question; they are just the facts the question is about.

While I was in here I built the project and ran its test suite on a clean Omarchy 4.0.0 VM with Qt 6.11.2: 19 of 19 pass.

Reviewed twice, by me and by Codex at xhigh reasoning. Codex independently reached the same reading — no defect claim anywhere in the thread — and it also argued, correctly, that there would be no basis for redirecting this question elsewhere given no issue template and no Discussions. I should say that its independence is not guaranteed: it can read this session's own working notes, so agreement is weaker evidence than it looks.