Figure out a new name

[TKK13909]

It's probably time to actually decide on a new name for this project before it gains any more traction. Whether it's Darkly, Brightly, or you just decide to keep the original one. I'm willing to help with the name transition once the decision gets made.

[Bali10050]

I think Darkly sounds the best, but I'm interested in @DeltaCopy's opinion too, because he has probably spent at least as much time on this project as me, with probably better coding skills than me. Also, if we rename the project we can close #10 pretty quickly. It looks like ./kstyle/lightly.json changes the name that shows up in the system settings, but I haven't yet found what else needs to be changed to make it work, and I don't know how I can rename everything at once

[DeltaCopy]

Darkly misconstrued may mean a darker orientated style which it isn't. Although I am not good with coming up with names, I think that an original name would be better suited. We already have Lightly, Glassly, Klassly .. For inspiration maybe looking at the style contrast between Breeze and Lightly may help. The minimalist, clean, and yet still modern looks this application style offers. breathe, liquid, fluid, zenith, clarity comes to mind.

Whatever is chosen there will be several activities required to reflect the name change

• [ ] refactoring the code
• [ ] updating build instructions
• [ ] validating the application style still works properly, and there are no regressions
• [ ] updating the GitHub Actions CI pipeline which generates the release assets
• [ ] validating the release assets installs still work across the different distributions
• [ ] replacing the AUR and Copr repositories to use the new name as currently both point to "lightly-qt6"

[TKK13909]

You mentioned 'Clarity' and that gave me an idea. I know some other projects that use Esperanto words for their name (Forgejo is the only one coming to mind at the moment) and the Esperanto word for Clarity is 'Klareco' which incidentally starts with a K like a lot of other stuff in the KDE world.

Just a thought...

By the way, @Bali10050, do you want to use this issue for brainstorming or would you prefer some other method?

[Bali10050]

By the way, @Bali10050, do you want to use this issue for brainstorming or would you prefer some other method?

If it works, don't fix it

Also, the name will be decided by the first person who finds out how to properly rename the project, because I have failed miserably in that part.

[DeltaCopy]

Can you elaborate on what you mean by:

how to properly rename the project

The repository itself, as well as all the assets inc. the src code cmake build files etc.. ?

[Bali10050]

Can you elaborate on what you mean by:

how to properly rename the project

I haven't found out yet what needs to be renamed for it to not only show up in the system settings, but to make it actually selectable, and to make the default lightly installable alongside it.

[DeltaCopy]

Looking at how Klassy style works will help as it references a lot of Breeze code but still manages to have a different name. I've just renamed Lightly to Zen as a POC and it works.

Having both Lightly and this new name installed in parallel sounds too difficult to maintain in the long-term. There are multiple files which require updating including CMakeLists.txt files to reflect the new name.

To give you an idea here are some of them.

  modified:   CMakeLists.txt
  modified:   kstyle/CMakeLists.txt
  modified:   kstyle/config/CMakeLists.txt
  modified:   kstyle/config/lightlystyleconfig.cpp
  modified:   kstyle/config/lightlystyleconfigmodule.cpp
  modified:   kstyle/config/main.cpp    
  modified:   kstyle/lightlystyle.cpp
  modified:   kstyle/lightlystyleconfigdata.kcfgc
  modified:   kstyle/lightlystyleplugin.cpp
  modified:   kstyle/lightlystyleplugin.h
  modified:   liblightlycommon/CMakeLists.txt

[Bali10050]

I created a Rename branch as a first step