75 Commits

  • Shell: the tray, Lucid's own pointer, the clock engine, network drives and the bar's content size
    - Tray: both looks rebuilt in Material You, every app in a slot of its own or
      three stacked with a count; a click opens the tray, each app a row with its
      menu opening in place
    - Pointer: Bibata Modern's shapes drawn from source in the palette's colours,
      fading with it, the tilt card, and the shell drawing the pointer itself in drags
    - Clock's engine in the shell (Alarms, ClockLink): alarms ring with the app
      closed and always post Snooze and Stop
    - Lumen: network drives (Connect to server, shares, Nearby); Lens: videos
    - Bar: Content size, notch edges as quarter ellipses up to 64 px, frosted and lit
      on hover; fixes across the dock, desktop, widgets, LucidShot and Settings
    
    Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
  • Merge pull request #109 from ciroenrique4-eng/pr/lyrics
    # Conflicts:
    #	lucidui/SymbolPaths.js
  • Lyrics: a page in the media panel and a desktop widget
    The words of what is playing come from lrclib.net, looked up only while
    something shows them and kept in ~/.cache/lucid/lyrics (of a search, only
    the record chosen is kept). lucidui/Lyrics.js reads lrclib's answers:
    word timing from its lyricsfile when a track has word sync, LRC line
    timing otherwise, with the words spread over the line by length.
    LyricsSource follows a player's position between its reports.
    
    The media panel gets a Lyrics page beside Identify (also `qs ipc call
    media lyrics`): the song scrolling by, the line being sung lit, a click
    on a line seeks to it.
    
    The new Lyrics widget follows the song in three looks:
    - Word by word: each word pops in as it is sung, a few at a time, like
      short-video captions; now and then one word is drawn hollow (option)
    - Karaoke: the line fills letter by letter, the next one under it. Time
      a word has beyond a sung pace is held on its last vowel, so a
      stretched note stalls the fill there
    - Classic: the whole song scrolling by, the current line in the middle
    Options: card behind the words, hide without lyrics.
  • Launcher: a full bottom bar draws it, as one piece of glass with the strip
    Drawn by the dock, a surface of its own, the launcher standing on the bar
    never frosted like the strip under it: a layer drawn later frosts what the
    earlier ones painted, so there was always a join. On a full bottom bar the
    dock now lends its launcher face to a LauncherPanel the bar draws, centred
    on the strip it grows out of, in the same blur pass as the strip: in the rig
    the glass runs from the launcher into the strip with no step at all, the
    wide wallpaper picker too. The bar's modules stay where they are under it.
    Search, results and modes stay the dock's own launcher, the face being lent,
    not copied (the dock's barLauncher / launcherHost / menuInDock machinery from
    45f4148 is back). Start and Apps do not morph. Elsewhere, and with the bar
    on top, the dock keeps its launcher.
    
    Undone with it, at the user's word: f444cf5 (denser glass for the launcher
    and panels) and 5ec077b (the bar lifted over the dock's launcher), which the
    bar drawing it makes moot.
    
    Rig-checked: open/close/reopen, click inside stays open, click away, Escape
    and Start close it, the face returns to the dock, the search takes the
    keyboard (typing reached it as reliably as the dock's own launcher).
    
    Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
  • Launcher and bar panels: denser glass, so they read as the bar does
    The launcher and the bar were the same glass, but the launcher is big and
    see-through, so over a bright sky it showed as a pale slab beside a bar
    lying over dark ground. Big glass (the launcher, a bar panel on the full
    bar) now takes Theme.bgDense, letting a sixth as much through as the bar
    does at the same Glass level (0.92 opaque at 0.5, solid at 0). Where it
    meets the strip it starts at the strip's glass and thickens over
    Theme.glassRamp, so the join shows no line: the launcher's foot standing on
    the bar, a panel's body, the gaps between merged panels, the corners at a
    panel's feet and the fillets. Over the sky in the rig the launcher went
    from 56,70,85 to 30,47,54 against a bar at 22-25,35-38,40-44. The dock
    itself keeps the bar's glass.
    
    Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
  • Bar: drawn over the launcher standing on it, so the two frost alike
    Hyprland blurs each layer from what is already painted under it. The
    launcher standing on a bottom bar was drawn after the bar, so its glass
    frosted the bar's bright icons and its foot sat a clear step off the strip
    (19-21 levels in the rig). Now the dock stays on the overlay layer while
    the bar holds the bottom edge, and the bar goes up to the overlay as the
    launcher opens, landing above it: the launcher frosts the windows behind
    it, the bar frosts the launcher's edge, which is the same glass. The step
    drops to 4-11. Hyprland's layer fades do not touch the bar on the switch
    (85 frames flat with the user's animations); over a fullscreen window
    nothing changes.
    
    Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
  • Bar: its edge blends are frosted like the rest of the bar
    The concave corners the bar draws (an open panel's feet on the full bar's
    strip, the strip's ends at the screen sides, notch blends, a cover strip's
    ends, the hang plan's fillets) were painted but in no blur region, so they
    tinted the wallpaper without frosting it and stood out against the strip and
    the panel they join. FlareRegion gives each one its square less the circle
    its curve is drawn from, a pixel wider, as the dock's edge blends have it,
    mirrored for a bottom bar; ModuleRegion adds a module's own, FilletRegions
    the fillets. The panel flare's size moved to bar.panelFlareSize so the
    drawing and the blur read one number.
    
    A panel's feet now butt against it instead of reaching half a pixel over
    its edge, which gave that column a second coat: a light line down the
    corner.
    
    Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
  • Start and Apps: no more morph into the launcher
    Put on hold for now: Start opens the dock's launcher again, as before the
    link, and Apps stays as it is while it is open. Gone with it: the dock
    lending its launcher face to Start (menuInDock, launcherHost, faceLent),
    Start's launcher panel, Apps folding into it and standing at its height
    (BarPill matchHeight, closeAlong), and joined islands merging open panels.
    
    Kept: Start's Launcher look and press squash, the calmer hovers (linked to
    Apps, Start still lights as the first icon of its row), Apps' dock-style
    indicators and tooltip, panels standing over the bar and over fullscreen
    windows, the bar clearing for a panel too wide for its place, the bridge
    fixes, and the slower panel close.
    
    Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
  • Bar: the launcher opens out of Start and Apps without a cut
    Modules an open panel covers fade out where they stood, but still sat in the
    row the merge walks: once Start's panel slid left past them, one sorted
    between Start and Apps and parted them, and a dark gap ran down between the
    two for a few frames. Covered modules no longer count.
    
    Apps folded into Start's launcher counted as covered too once it was zero
    wide, so it unfolded on the close while fading back in, see-through beside
    the panel. It never fades while it is part of that shape.
    
    Bridges cover whole pixels out to both panels, and a zero-wide panel grows
    no flares.
    
    Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
  • Open the control centre over IPC
    qs ipc call controlcentre toggle | open | close, reaching the main bar's
    System pill the way the clock, media and workspaces targets do. Closes #107.
  • Bar: a panel too wide for its place clears the whole bar
    Once an open panel stands over any other module (the launcher's wallpaper
    picker in the Start module, say), every module steps aside while it is open,
    not only the ones under it, and all come back as it shuts. Workspaces too.
    
    Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
  • Bar: the linked island morphs whole, open panels stand over the bar, and over fullscreen
    The launcher grew out of the Start button alone on the full bar. Now the
    folding Apps module stands at Start's height frame by frame (BarPill
    matchHeight) while its width folds away, and the bar merges the two side by
    side, so the panel rises out of the whole linked island from its first
    frame. Joined pairs merge on islands too: one island stays one shape.
    
    An open panel now stands above the other modules (z), and those it stands
    over fade out until it shuts instead of showing cut off at its edge or
    drawing over it, as the bar did over the wide wallpaper picker.
    
    Over a fullscreen window, which hides the bar's layer, the bar goes up to
    the overlay while one of its panels is open and as it shuts: every module,
    and the launcher in Start, opens over videos and fullscreen apps.
    
    Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
  • Start: linked to Apps it becomes the launcher; Apps and Start feel like the dock
    With Start and Apps linked, the launcher opens out of the Start module: the
    module grows into it as a bar panel, and the dock lends it the launcher's own
    face (one face, so search, selection and modes are the same launcher) until
    the panel has shut. Every way in opens it there except the dock's own button,
    which still grows the dock into it. The dock follows the launcher with
    menuInDock where it draws or takes input, menuOpen where the launcher itself
    is meant. The link counts on the full bar too, which draws no joins.
    
    Apps: icons swell and lift off the bar on hover, squash under a press and
    spring back, kick as an app launches, and new ones grow in. The indicator is
    the dock's: a segment a window, longer in focus, red and breathing when a
    window wants attention, and a breathing dot until a launched app's first
    window comes. The tooltip slides out from the bar. Start squashes under a
    press; the Distro look no longer loads its icon off the main thread.
    
    A panel now closes as long as it opens, slow at first and soft at the end:
    the exit curve finished at 90 px a frame and read as too quick.
    
    Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
  • Bar: notches light up whole, and edit mode outlines their edge blends
    Hovering a notch module that is not joined lit its edge blends (BarFlare
    tints them) but not the module, and the module grew sideways into its own
    blends. A notch now lights up in place with them, as a joined module does.
    
    In edit mode a notch's outline was a box along the pill. It now runs as the
    dock's does: open along the screen's edges, out along the blends into the
    top edge, and down a screen side where Meet the screen sides curves a module
    into it. A blend deeper than the straight side is met where the bottom
    corner starts. The bar works out the blend sizes in notchFlareOf() for both,
    and planHangs() notes where each screen-side curve starts (meets).
    
    Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
  • Bar: #91-#100 fitted to this version
    - Open panels side by side always merge into one shape on the full bar
      and on notches (#92), with no switch for it. The gaps it fills join the
      input mask and the blur (BridgeRegion), so they frost like the panels.
    - Apps (#99): its icons load on the main thread; an icon theme image
      loaded asynchronously took Quickshell down at startup. They are the
      dock's own now, Lucid's tonal tiles where there is one (BarAppIcon),
      and a dragged icon carries a drawn pointer with it (HeldPointer).
    - OSD over a bottom bar: #22's last three commits, left out when #22 came
      in, are back. The notch rises out of a full bottom bar only; over islands
      or notches it would stand on nothing past a module's ends, so it floats
      as a card. Over a fullscreen window it keeps to the screen edge.
    - LucidShot's toolbar and recording pill keep clear of a bottom bar as
      they do of the dock.
    - Theme loads its font from the shell's folder, so the installer's tree
      and lucidbar/Theme.qml (synced) both find it.
    - The control centre studio's rise starts where the panel really is: the
      bar window's margin is counted, on either edge.
    - Settings search finds the bar's Position under bottom, position, edge.
    
    Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
  • Merge pull request #100 from ciroenrique4-eng/pr/bar-position
    # Conflicts:
    #	luciddocks/Dock.qml
    #	lucidedit/EditLayer.qml
  • Bar: a bar that hides comes out of the screen edge
    A bar set to hide kept its margin outside its window, so the strip that
    reveals it sat that far from the screen edge: pushing the pointer against
    the edge did nothing, on either edge. A hiding bar now reaches the edge
    itself, with its margin inside, and leaves the zones of other surfaces
    alone. Once out, its whole band keeps it there, so crossing the margin or
    a gap between islands does not send it away.
  • Bar: it slides over to the new edge
    On a change of position the bar slides out of the edge it is on, picking
    up speed, moves while out of sight, and slides in at the other edge. The
    edge the bar is drawn on lags the one asked for by that slide; the first
    load takes the saved edge as it is.
  • Bar: a Position setting puts the bar on the bottom edge
    The bottom bar is the top bar mirrored: the window hangs from the bottom
    edge and its content is turned upside down, so every shape, notch, flare,
    join and panel keeps its maths, and each module turns its own content back
    the right way up. Input and blur regions are mirrored by hand, since the
    window works in its own coordinates. Desktop icons, new widgets, the
    workspace overview and the previews in Settings follow the bar. What a
    module lays over the screen goes up from it: the system module's tooltip,
    the tray's menus, and the stack of notifications, newest nearest the bar.
    
    The bottom edge then belongs to the bar, and the dock steps aside while
    it is there: making the two share the edge took a case for every
    combination, and every one of them was a dock dodging the bar. dockEnabled
    is left as it was, so the dock is back once the bar returns to the top.
    The launcher stays, standing on the bar: on a notch or a full bar it
    rises out of the bar's top, curving into it, and the bar puts out a strip
    to its width where it is wider than the bar; over islands it floats the
    pop-up distance above and fades as it goes. Its window ends on the bar's
    top, so it sinks into the bar rather than stopping short of it. A panel
    and the launcher shut each other, as they now open in the same place.
    
    The dock's apps can come along on the bar's Apps module. Settings says
    so under Position, and the Dock page opens on a card that tells why the
    dock is not there, with a button that turns the Apps module on, or opens
    its card once it is, and one that moves the bar back up; the dock's
    settings stay open to change meanwhile.
  • Bar: an Apps module, the dock's apps on the bar
    The dock's apps can sit on the bar as a module: the pinned ones in the
    dock's order, then any other app with a window open. A dot marks the open
    ones, stretched into a bar in the accent for the one in focus, and after a
    beat a tooltip gives the app's name and how many windows it has. A click
    opens an app, or brings its window up without moving the pointer,
    whatever the warp setting; with several windows, one on another
    workspace, or on a right click, a panel grows out of the module with a
    live preview of each window, as the dock's, and New window, Pin or Unpin
    and Close. A middle click opens a new window, and the wheel goes through
    an app's windows.
    
    The icons drag as on the dock: a pin along the bar to another pin's place,
    an open app in among the pins to pin it there, and a pin pulled off the
    bar to unpin it.
    
    The icons take about half the bar's height. The module takes a third of
    the bar at most: past that its last slot reads "+N" and opens the rest in
    a grid, the open apps keeping their place on the bar and the pins giving
    way.
    
    It reads the pins the dock keeps, and changes them through the dock, so
    both show the same ones in the same order, and the windows from
    Hyprland's toplevels, as the active window module does. Its card in
    Settings has the dock's own switches that make sense on the bar, the same
    settings, so they cannot drift apart: running apps, the running
    indicator, tooltips and icon tiles. Off by default; it lives in the
    centre group.
  • OSD: the dock steps down for the notch
    The notch kept clear of the dock's reserved strip, so with the dock up it
    sat on top of it with its corners in the air. It now goes under the strip
    to the edge itself, and the dock slides down while it shows and comes
    back after. A dock held up by a menu or a drag keeps the edge; the card
    floats above it then.
  • OSD: a notch style, lock keys as toasts, and the keyboard light
    Three additions, all off or invisible by default:
    
    - OSD style: the island as it is, or a notch - the card sits flush on the
      bottom edge, rises out of it instead of popping, and hangs the dock's
      concave corners off its sides. One vertical anchor in both styles (the
      notch reaches the edge through the offset), since swapping anchors lets
      the anchor engine write the height and drop its binding.
    - Caps Lock, Num Lock and the microphone can be a toast instead of a card,
      for a machine where the OSD is in the way. The detection stays in the OSD,
      which reports through a signal; ToastEvents shows it.
    - The keyboard backlight. Its key is handled in firmware: the led moves and
      nothing writes the file, so inotify never fires. kbd-backlight-watch.py
      sits in poll() on brightness_hw_changed and reports the level; the file
      watch stays for a level something does write, rereading after 200 ms
      because the driver applies the write out of line. The helper treats
      ENODATA (no key pressed since boot) as "no level yet", arms
      PR_SET_PDEATHSIG so it dies with the shell, and leaves if the led goes.
      A few whole steps draw as one block per step, the steps that are on in
      full and the rest as a thin rail, with the count as the readout; a
      fine-grained level keeps the level track. It is news only, so the card
      takes no pointer for it.
    
    Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
  • Blur: a surface sliding off its layer no longer frosts the whole of it
    Hyprland clips the blur to the region's overlap with the surface, and an empty clip means no clip, so a region wholly outside it frosts everything. A hidden bar's pills sat there, covering the screen for as long as it stayed hidden, and the jelly pushed a hidden dock's last row off the edge in brief flashes. The blur regions are now clipped to the surface, so such a region arrives empty and nothing is frosted.
    
    Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
  • Notches: open panels side by side merge into one shape too
    The merge of open panels now covers notches as well as the full bar. Two
    modules of one notch with their panels open fill the gap between them and
    round the shorter one into the side of the taller, with the notch's flare
    for the curve. The fill runs the whole height, a notch having no strip under
    the gap, and joining a screen side stays with the full bar. A hanging
    panel's flare against the island is left out on a side merged into its
    neighbour.
  • Full bar: open panels side by side merge into one shape
    A new switch under Settings > Bar (Merge open panels, off by default). With it
    on, two open panels next to each other on the full bar - a notification toast
    beside the system panel, say - fill the gap between them, and the shorter
    one's shared corner becomes a fillet against the taller one's side.
  • Updates: install a new release from inside Lucid, and a beta channel
    When a release is out, Update on the About page (and on the notification)
    warns, asks for the password, and shows a pop-up with a progress bar while
    lucidupdate/updater.py downloads the release's source and runs its own
    install.sh in a pty. The installer's yes/no questions and any sudo prompt
    are asked in the pop-up; at the end it offers Restart now, Remind me later
    (an hour) or Cancel. The runner lives outside the shell and writes its
    events to a file, so a reload reattaches where it was. The password goes
    into sudo once; a keep-alive loop holds the credential for the install.
    
    Beta updates (off by default, with a critical warning on the switch) offer
    the newest commit on main the same way. install.sh leaves the restart to
    the updater when LUCID_UPDATER is set.
    
    Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
  • Bar: a start button
    The launcher from the bar, a click to open it or put it away, at the start
    of the left group. Five looks: Lucid's mark as on the dock, a grid of nine
    dots, the distribution's logo (the one os-release names, in the accent;
    Lucid's mark where there is none), the account picture, or the word Start
    on a chip. It lights up while the launcher is open.
    
    A module new to the arrangement goes to the end of its home group; this one
    is marked "first" in the registry and goes to the start of it. It has
    nothing to unfold, so BarPill gains opensOnHover for a pill that is only a
    button. Off by default.
  • Sound: play through several outputs at once
    Settings > Sound gains a checklist of outputs. Ticking two or more adds a
    Combined output, a pipewire-pulse combine-sink kept by the Audio service:
    remade at login, rebuilt when the ticked set changes, and left alone when
    one of its devices drops away, since it rejoins by itself. Its per-device
    feed streams are hidden from the Applications list.
  • Screenshot: say why the region overlay didn't open
    When grim cannot freeze the screen the overlay stayed shut without a word.
    It now shows a "Couldn't capture the screen" toast and logs grim's own error,
    and `qs ipc call snap status` reports what the overlay thinks it is doing
    (open, freezing, settling, the last freeze's exit and error, its display), so a
    region capture that does nothing can be diagnosed from a bug report.
    
    Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
  • Release v1.20.1
    Desktop icons, bar islands and a full bar, live wallpapers and four picker
    styles, files over Bluetooth with a pairing agent, a Startup page, fingerprint
    unlock on the lock and login screens, five new widgets, metric or imperial
    units, the Steam open/close loop fixed, and the right graphics drivers for
    Steam. Fifteen pull requests from Ciro Rivera and one from SKetU-l. The full
    notes are in CHANGELOG.md.
    
    Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
  • Settings: a Storage page
    Settings > Storage, in the System group: an overview of every drive, a
    usage map to zoom through (Home or the whole disk) with what fills it,
    what could go (package caches, old trash, duplicates and large files in
    your own folders) with a confirm for each, and the drives themselves with
    their health. storagetool.py does the scanning and the cleaning; the
    Storage singleton keeps the scans and warns when space runs low
    (storageLowWarn, storageLowPercent) and empties trash older than
    storageTrashDays (0, never, to begin with).
    
    The bar's disk card and the System widget measure free space as df
    does: against used plus available, leaving the root reserve out.
    
    Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
  • Merge #14: Displays: a bar on every display
    Settings > Displays > The bar on its own gains Every display (or
    qs ipc call -- displays bar all). On 1.20's shell.qml: the bar is a
    Variants with one instance unless that is picked, each bar places itself
    on its own display, and the dock, the screenshot windows and the capture
    preview move out of the bar window, where their own bindings already
    placed them.
    
    One bar speaks for the shell: the one on the shell's display, or the one
    in use. Only it turns into notification popups, raises the privacy
    toast, and writes which modules are away. The clock, media and
    workspaces ipc targets live in shell.qml and reach that bar, since every
    bar would otherwise register them; the overview and the dock menu still
    close each other, per bar.
    
    Checked on a headless wayfire with one and with two outputs: a bar on
    each, the popup on one, and the ipc reaching the main bar.
    
    Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
  • ...
  • Merge #44, #50: arrange the bar's modules, and three new modules
    Settings > Bar takes Ciro's arrangement editor and module cards, and the
    bar's layout is his barLayout plus the show* switches, which is also
    what a 1.10.5 install already has. The bar itself keeps 1.20's placement:
    barHas, barZones and barKeysOf now read barLayout, so the eased
    reordering and the slot a leaving pill keeps work as before.
    
    The six modules keep their 1.20 looks: their looks and look options are
    left out of barModules, the card and the defaults. Privacy, Power and
    Active window come in as they are, off by default. The placement fixes
    from #44 (the notification stack and the tray menu on either side, a
    right click to the module's card) are applied to the 1.20 modules.
  • Merge #46, #47: Windows and Input pages for Hyprland
    # Conflicts:
    #	Prefs.qml
    #	README.md
    #	lucidprefs/NavGlyph.qml
    #	lucidprefs/Settings.qml
  • Merge #53: Night light: warm the screen through hyprsunset, by hand or on a schedule
    # Conflicts:
    #	README.md
    #	lucidbar/System.qml
    #	shell.qml