How grassmunk/chicago95 works
Project type and purpose
• Chicago95 is an open-source “total conversion” theme package and helper tool for Linux desktops (XFCE, GTK2/3, Cinnamon, Gnome-Shell, KDE SDDM, Lightdm, Plymouth).
File structure
• Cursors (multiple sub-themes with build scripts)
• Fonts (bitmap, VGA)
• Theme (GTK2, GTK3, Cinnamon, Gnome-Shell, XFWM4)
• Plymouth (boot splash)
• KDE (SDDM theme, splash screen)
• Lightdm (greeter HTML/CSS/JS)
• Sounds (audio theme)
• Extras (backgrounds, LibreOffice iconset, config snippets, helper scripts)
• Plus (Python tool: Plus.py, PlusGUI.py, pluslib.py)
• Build & installer scripts at root and in subfolders (Makefile, installer.py, Build.sh, cursors_gen.py, recolor.py) form the packaging layer.
README for architecture insights
• It lists included modules, dependencies (GTK engines, xfce4-panel-profiles, Python, bash), and usage scenarios.
• Emphasizes separation of asset domains and existence of an automated installer plus a GUI tool.
Main components & their relationships
• Asset Modules → Build & Packaging Layer → Installer/Makefile → System directories
• Chicago95 Plus! (UI) ←→ pluslib (core logic) invokes installer API and previews assets
• Desktop Environment Integration reads from installed asset directories:
• X server applies cursors
• GTK engines load theme CSS
• GNOME Shell reads SCSS/CSS assets
• Lightdm loads HTML/CSS/JS
• KDE SDDM uses QML/metadata
• Plymouth uses .plymouth and script
Architectural patterns & design principles
• Modular asset domains: each folder is a self-contained theme module
• Layered build pipeline: scripts transform raw assets into installable packages
• MVC-like separation in Plus!: PlusGUI (view) ↔ Plus.py/pluslib (controller/model)
• Extensibility via Extras folder for custom iconsets, backgrounds, configurations