feat: initial writeup of Chirp 1 #3
No reviewers
Labels
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
BuddiesOfBudgie/site!3
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/chirp-1-article"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Fixes #2
Just a couple of little grammar things.
@ -0,0 +64,4 @@For context, we currently leverage [toml11](https://github.com/ToruNiina/toml11) for serialization and deserializing of our display configuration in Budgie Desktop Services. While the library is great and the TOML format is preferred for "user-facing" files, the current implementation results in a few pain-points:1. It requires a fair bit of code to translate between internal Qt and standard C++ types.Extra spaces after Qt.
@ -0,0 +72,4 @@1. It is schema-first, utilizing codegen to handle generating code for reading and writing the respective schema.2. It facilitates migrations and supports layered or cascading configurations, which is ideal for overlaying user settings onto vendor or distribution defaults.3. By leveraging `KConfigWatcher`, our goal is enable configuration-driven panel changes."[..] our goal is to enable [...]"
@ -0,0 +98,4 @@- Notifications (we are still evaluating how notifications will integrate with Raven to avoid specific pain points related to the notification server)- PanelsNothing fancy in the repo yet."is in"
Shouldn't this PR have
Closes: #2in it as well?Other than that, just address @EbonJaeger's feedback and then I think this is probably good to go.