-
-
Notifications
You must be signed in to change notification settings - Fork 1
Legacy Import
Bobby Comet edited this page Aug 1, 2026
·
4 revisions
Project → Import Legacy Theme… points at a folder that contains a Conky configuration and related files. Import is semantic: it builds an editable Studio graph, not a guaranteed pixel-perfect clone of every theme ever written.
It is intended for both older and current Conky syntax, with known limits.
| Input | Result in Studio |
|---|---|
| *.conf / conkyrc | Canvas size, alignment, gaps, update rate, lua_load, draw hooks (where recognized) |
| own_window_type / own_window_argb_visual / own_window_transparent | Canvas window layering and transparency |
| templateN = '...' definitions | Expanded inline before TEXT is parsed |
| conky.text / TEXT block | ${goto} / offset / ${tab} layout (best-effort), fonts, colours (all 10 ${colorN} slots), ${hr}/${stippled_hr} as a Horizontal Line, text-oriented nodes |
| ${cpu} (incl. per-core), ${memperc}, ${fs_used_perc}, ${upspeed}/${downspeed}, ${uptime}, ${nodename}, ${kernel}, ${processes}, ${battery_percent}, ${time}, … | Native source nodes, wired into visuals when possible |
| ${execi} / ${exec} / ${execbar} | Known scripts — by filename or by content (e.g. an oddly-named script that calls nvidia-smi or sensors -u) — → family sources; otherwise Custom Script nodes |
| Cairo .lua from lua_load | Custom Lua node(s): helpers + draw body; surface boilerplate adjusted toward Studio's cr / W / H |
| Click regions in Lua | Clickable markers with commands when detected |
| Shell scripts in the tree | Custom Script nodes (or known mappings by name/content), including scripts only referenced from Lua |
Warnings listed after import call out approximations. Read them.
- Import the theme folder.
- Fix missing wires, Canvas size, and alignment (window type & transparency should already be closer to right).
- Re-add images / icons / album art manually if they did not appear as first-class visual nodes.
- Use Live Preview; same pipeline as export.
-
Build & Install and test from Manager with
start.sh.
After import, the project is a normal Studio graph: edit, preview, and export like anything created from scratch.
- Themes that are almost entirely one large hand-written Cairo file
- Themes that depend on external binaries and absolute paths not present on your machine
- Compositor-specific hacks that only worked on the author's setup
- Custom sensor/data scripts whose purpose isn't guessable from a handful of known command signatures
Those still benefit from landing in Custom Lua + sources you can rewire, but the last mile is manual.