[FEAT]: Installer should install applications.yaml, generate komorebi.json and modify the start menu shortcut to load komorebi.json #263

New Issue

2026-01-05T14:49:21+01:00

adam commented

2026-01-05 14:49:21 +01:00

Originally created by @nascentt on GitHub (Nov 18, 2023).

The installer-based komorebi is not user friendly, and is in fact counter intuitive as komorebi expects manual configuration parameters given to it, but the start menu shortcut prevents that.

Originally created by @nascentt on GitHub (Nov 18, 2023). The installer-based komorebi is not user friendly, and is in fact counter intuitive as komorebi expects manual configuration parameters given to it, but the start menu shortcut prevents that.

adam added the enhancement label 2026-01-05 14:49:21 +01:00

adam closed this issue

2026-01-05 14:49:21 +01:00

adam commented

2026-01-05 14:49:21 +01:00

@LGUG2Z commented on GitHub (Nov 18, 2023):

I have never tried launching komorebi from the start menu, I think it's worth seeing either if Wix has an option to potentially modify start menu entries when building the installer, or if not, patching the start menu entry using a CLI command after installation.

For the provisioning of files I think it's a good idea to be able to run a single command to be able to execute all of the download commands for the example files listed in the current readme.

With regards to bundling them with the installer, I don't think that it's possible to move individual files into arbitrary locations like the user home dir with the installer toolchain we are using, this is something that needs investigating.

However, one thing I think we can definitely do on the application side is offer to download the same configurations for the user if komorebi is run trying to point at configurations that don't exist on the disk.

These are all really great ideas that I'm sure will make the setup process a lot easier for non-technical folks. 🙏

@LGUG2Z commented on GitHub (Nov 18, 2023): I have never tried launching komorebi from the start menu, I think it's worth seeing either if Wix has an option to potentially modify start menu entries when building the installer, or if not, patching the start menu entry using a CLI command after installation. For the provisioning of files I think it's a good idea to be able to run a single command to be able to execute all of the download commands for the example files listed in the current readme. With regards to bundling them with the installer, I don't think that it's possible to move individual files into arbitrary locations like the user home dir with the installer toolchain we are using, this is something that needs investigating. However, one thing I think we can definitely do on the application side is offer to download the same configurations for the user if komorebi is run trying to point at configurations that don't exist on the disk. These are all really great ideas that I'm sure will make the setup process a lot easier for non-technical folks. 🙏

adam commented

2026-01-05 14:49:21 +01:00

@LGUG2Z commented on GitHub (May 12, 2024):

Most of this is covered by the quickstart command, but starting komorebi from a start menu shortcut upon reflection is out of scope.

@LGUG2Z commented on GitHub (May 12, 2024): Most of this is covered by the `quickstart` command, but starting `komorebi` from a start menu shortcut upon reflection is out of scope.

adam referenced this issue

2026-01-05 14:53:23 +01:00

[PR #405] [MERGED] Feat/initial window rule #911

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/komorebi#263