Tearnote/Playnote
Watch
1
0
Fork
You've already forked Playnote
 0
Code Issues 25 Pull requests Releases 4 Wiki Activity Actions

Theme adoption #202

New issue
Closed
opened 2026-08-02 16:41:44 +01:00 by Tearnote · 1 comment
Tearnote commented 2026-08-02 16:41:44 +01:00
Owner
Copy link

Move Playnote’s existing hard-coded presentation onto the theme system so the default theme genuinely owns the game’s appearance and visual behavior. Shared widgets, game-specific UI components, and gameplay presentation should consume stylesheet and script capabilities rather than retain parallel C++ styling paths.

Move Playnote’s existing hard-coded presentation onto the theme system so the default theme genuinely owns the game’s appearance and visual behavior. Shared widgets, game-specific UI components, and gameplay presentation should consume stylesheet and script capabilities rather than retain parallel C++ styling paths.
Tearnote added this to the v0.2 milestone 2026-08-02 16:41:44 +01:00
Tearnote commented 2026-08-19 09:23:12 +01:00
Author
Owner
Copy link

Implemented

Implemented
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
dev
v0.2
v0.1.2
v0.1
v0.1.1
Labels
Clear labels   
bug
Something isn't working

  
documentation
Improvements or additions to documentation

  
explore
Checking the viability of an idea before committing to it

  
improvement
It works, but it can work better

  
roadmap
Planned as part of core development

No labels
bug
documentation
explore
improvement
roadmap
Milestone
Clear milestone
No items
No milestone
v0.2
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Depends on
#212 Theme shared widgets
Tearnote/Playnote
#213 Theme game UI components
Tearnote/Playnote
#214 Theme gameplay presentation
Tearnote/Playnote
#223 Adopt KDL-defined views
Tearnote/Playnote
Reference
Tearnote/Playnote#202
No description provided.