@umriss-ui/schedule 0.3.3 → 0.3.5

package/CHANGELOG.md

@@ -15,6 +15,24 @@ moves from here under the rule above.
 
 ---
 
+## 0.3.5 – Found by search (Sep. 2026)
+
+### Fixed
+
+- **The package's description and keywords say what it is in the words a
+  search uses**, and the demo it links to addresses every page by a path
+  (`…/schedule/<page>/`) instead of a hash, with the page's text readable before
+  the demo starts. Old `#/<page>` links still land. Nothing in the package's
+  code changed.
+
+---
+
+## 0.3.4 – Core 0.14.0 (Sep. 2026)
+
+Needs `@umriss-ui/core` 0.14; the peer range moves to `^0.14.0`. Nothing else changes for a caller.
+
+---
+
 ## 0.3.3 – What you are working with (Sep. 2026)
 
 ### Changed

package/README.md

@@ -1,6 +1,6 @@
 # @umriss-ui/schedule
 
-Work planned over time: **subtasks** on **lanes** — people, vehicles, rooms or
+A React Gantt-style schedule for data-dense applications — work planned over time: **subtasks** on **lanes** — people, vehicles, rooms or
 machines. One task runs across several lanes in a fixed order, each stop has a
 main time with a lead-in before it and a lead-out after it, between the stops
 lie **dependencies** with lags of their own, and a lane can be **blocked** for

package/docs/llms-full.md

@@ -1,6 +1,6 @@
-# @umriss-ui/schedule 0.3.3
+# @umriss-ui/schedule 0.3.5
 
-> The umriss schedule for data-dense applications - work on lanes over time, with dependencies, blocked time, findings and controlled editing.
+> React Gantt-style schedule for data-dense applications - work on lanes over time, with dependencies, blocked time, findings and controlled editing.
 
 Install with `pnpm add @umriss-ui/schedule`. This text is generated from the package's demo (https://romanhaendler.github.io/umriss-ui/schedule/): every page with its import line, its examples - the source exactly as it runs, with the package name where the demo imports its own source - its props tables generated from the code, and what it deliberately does not do. The pages index stands in https://romanhaendler.github.io/umriss-ui/schedule/llms.txt.
 
@@ -560,7 +560,7 @@ Install the schedule with its two peers and hand it plain data: lanes, tasks, su
 import { Schedule, Lane, Subtasks, Dependencies } from "@umriss-ui/schedule";
 ```
 
-Demo page: https://romanhaendler.github.io/umriss-ui/schedule/#/installation
+Demo page: https://romanhaendler.github.io/umriss-ui/schedule/installation/
 
 Install it with its peers: `pnpm add @umriss-ui/schedule @umriss-ui/core @umriss-ui/charts`, with React 18 or 19. The stylesheets load themselves - each package's script imports its own, so there is nothing to import by hand; `@umriss-ui/schedule/styles.css` stays exported for setups that link stylesheets themselves.
 
@@ -614,7 +614,7 @@ Work on lanes over time, with a day band above and time ticks that follow the zo
 import { Schedule, Lane, Subtasks, Dependencies } from "@umriss-ui/schedule";
 ```
 
-Demo page: https://romanhaendler.github.io/umriss-ui/schedule/#/schedule
+Demo page: https://romanhaendler.github.io/umriss-ui/schedule/schedule/
 
 Lanes stand in the order they are declared; a subtask on a lane that is not declared is not drawn. Declare `Dependencies` before `Subtasks` and its lines run beneath the bars.
 
@@ -815,7 +815,7 @@ One row per person, vehicle or room, named by its header and kept in the order i
 import { Lane } from "@umriss-ui/schedule";
 ```
 
-Demo page: https://romanhaendler.github.io/umriss-ui/schedule/#/lane
+Demo page: https://romanhaendler.github.io/umriss-ui/schedule/lane/
 
 A lane is declared by its id, the one subtasks name, and a label. The label is content, not a string: a name with a plate number, a status beside it. It is real text, read by a screen reader, and it stays at the left edge while the plot pans.
 
@@ -942,7 +942,7 @@ Teams, depots or regions over the lanes, to any depth, folded into one row when
 import { LaneGroup, Lane } from "@umriss-ui/schedule";
 ```
 
-Demo page: https://romanhaendler.github.io/umriss-ui/schedule/#/lane-groups
+Demo page: https://romanhaendler.github.io/umriss-ui/schedule/lane-groups/
 
 A group is structure, never a lane: nothing sits on it, no finding is reported for it and no intent names it (ADR-0025). The lanes keep the order they were declared in, whatever group they are in.
 
@@ -1211,7 +1211,7 @@ The bars: a main time with an optional lead-in before it and lead-out after it,
 import { Subtasks } from "@umriss-ui/schedule";
 ```
 
-Demo page: https://romanhaendler.github.io/umriss-ui/schedule/#/subtasks
+Demo page: https://romanhaendler.github.io/umriss-ui/schedule/subtasks/
 
 Lead-in and lead-out are durations beside the main time, not times of their own: moving the subtask takes them along. They are drawn faint in the task's colour, so preparation reads as belonging to the work and as not being it, and they occupy the lane as the main time does.
 
@@ -1355,7 +1355,7 @@ A line of text inside each bar: cut off where the bar is too narrow, left out wh
 import { Schedule } from "@umriss-ui/schedule";
 ```
 
-Demo page: https://romanhaendler.github.io/umriss-ui/schedule/#/bar-labels
+Demo page: https://romanhaendler.github.io/umriss-ui/schedule/bar-labels/
 
 The text lies on the main time, not on the lead-in. Its colour follows the bar: light text on a dark bar, dark text on a pale one, measured by contrast in either theme.
 
@@ -1421,7 +1421,7 @@ What a bar says besides its colour: provisional, fixed, muted, running on past t
 import { Subtasks, resolveAppearance } from "@umriss-ui/schedule";
 ```
 
-Demo page: https://romanhaendler.github.io/umriss-ui/schedule/#/appearances
+Demo page: https://romanhaendler.github.io/umriss-ui/schedule/appearances/
 
 `"provisional"` owns the fill (none at all), `"fixed"` the ends (a cap inside each), `"muted"` the saturation, `"open"` a fade at the edge of the view, and `progress` a rail inside the main time. The faint, outlined fill belongs to a lead-in and a lead-out and to nothing else.
 
@@ -1664,7 +1664,7 @@ Two subtasks claiming one lane at the same time (also called a double booking or
 import { Subtasks } from "@umriss-ui/schedule";
 ```
 
-Demo page: https://romanhaendler.github.io/umriss-ui/schedule/#/overlap
+Demo page: https://romanhaendler.github.io/umriss-ui/schedule/overlap/
 
 The later bar is offset a few pixels and edged, and the shared time is marked across the lane. Lead-in and lead-out occupy the lane too, so a lead-out meeting the next lead-in is an overlap. The offset stops at three levels and never leaks into the lane below.
 
@@ -1785,7 +1785,7 @@ Lines from one subtask's end to the next one's start within a task, with the lag
 import { Dependencies } from "@umriss-ui/schedule";
 ```
 
-Demo page: https://romanhaendler.github.io/umriss-ui/schedule/#/dependencies
+Demo page: https://romanhaendler.github.io/umriss-ui/schedule/dependencies/
 
 `leaves` and `arrives` say what a dependency connects - the main time, or the outer edge of the lead-out and the lead-in - and so decide whether it is violated. `attach`, `ends` and `route` only change how the line is drawn.
 
@@ -2066,7 +2066,7 @@ The shape of a dependency's line: a curve that leaves and arrives forwards, a st
 import { Dependencies } from "@umriss-ui/schedule";
 ```
 
-Demo page: https://romanhaendler.github.io/umriss-ui/schedule/#/routes
+Demo page: https://romanhaendler.github.io/umriss-ui/schedule/routes/
 
 #### Examples
 
@@ -2239,7 +2239,7 @@ A day band that names the days and a time band whose ticks follow the zoom, from
 import { Schedule } from "@umriss-ui/schedule";
 ```
 
-Demo page: https://romanhaendler.github.io/umriss-ui/schedule/#/time-axis
+Demo page: https://romanhaendler.github.io/umriss-ui/schedule/time-axis/
 
 The calendar is a list of intervals in which time counts, nothing more; deriving it from opening hours and holidays is the application's business. A dotted line marks each seam, and a drag that would end in removed time stops at the seam where time counts again.
 
@@ -2375,7 +2375,7 @@ Leave, maintenance and other time a lane is not available: hatched behind the wo
 import { BlockedTimes, findings } from "@umriss-ui/schedule";
 ```
 
-Demo page: https://romanhaendler.github.io/umriss-ui/schedule/#/blocked-time
+Demo page: https://romanhaendler.github.io/umriss-ui/schedule/blocked-time/
 
 Blocked time is data beside the work: one list, each interval naming its lane, as a leave table or a maintenance plan holds it. `findings` takes the same list as its third argument.
 
@@ -2591,7 +2591,7 @@ A line across the lanes at the present moment, so that whatever should have happ
 import { Schedule } from "@umriss-ui/schedule";
 ```
 
-Demo page: https://romanhaendler.github.io/umriss-ui/schedule/#/now-line
+Demo page: https://romanhaendler.github.io/umriss-ui/schedule/now-line/
 
 #### Examples
 
@@ -2683,7 +2683,7 @@ Moving through a plan with the gestures of any scrolling surface: drag, wheel, C
 import { Schedule } from "@umriss-ui/schedule";
 ```
 
-Demo page: https://romanhaendler.github.io/umriss-ui/schedule/#/pan-and-zoom
+Demo page: https://romanhaendler.github.io/umriss-ui/schedule/pan-and-zoom/
 
 Dragging the background pans through time and through the lanes. The wheel scrolls the lanes and hands the scroll back to the page at their end; Shift with the wheel pans through time; Ctrl or ⌘ with the wheel, or a pinch, zooms around the pointer.
 
@@ -2752,7 +2752,7 @@ A click on a bar selects its whole task on every lane, so a planner sees every p
 import { Schedule } from "@umriss-ui/schedule";
 ```
 
-Demo page: https://romanhaendler.github.io/umriss-ui/schedule/#/selection
+Demo page: https://romanhaendler.github.io/umriss-ui/schedule/selection/
 
 The schedule keeps the selection itself unless you pass `selectedTask`; then your state holds it and every change is reported. The report also names the subtask that was clicked, the one the editing grips belong to.
 
@@ -2908,7 +2908,7 @@ Reports what the pointer does on the plan - hover, click, right-click - with wha
 import { Schedule } from "@umriss-ui/schedule";
 ```
 
-Demo page: https://romanhaendler.github.io/umriss-ui/schedule/#/interactions
+Demo page: https://romanhaendler.github.io/umriss-ui/schedule/interactions/
 
 A hit names a subtask together with the part of it (lead-in, main time, lead-out), a dependency, a lane, or nothing.
 
@@ -3084,7 +3084,7 @@ Names what the pointer rests on - a subtask with its times and findings, a depen
 import { Schedule } from "@umriss-ui/schedule";
 ```
 
-Demo page: https://romanhaendler.github.io/umriss-ui/schedule/#/tooltip
+Demo page: https://romanhaendler.github.io/umriss-ui/schedule/tooltip/
 
 Its words come from the wording of @umriss-ui/core and its numbers from its formats, so a provider switches it with everything else. It steps aside while a drag is in flight and is placed where it has room.
 
@@ -3308,7 +3308,7 @@ Keeps two schedules on the same hours: pan or zoom one and the other follows (al
 import { Schedule } from "@umriss-ui/schedule";
 ```
 
-Demo page: https://romanhaendler.github.io/umriss-ui/schedule/#/linked-schedules
+Demo page: https://romanhaendler.github.io/umriss-ui/schedule/linked-schedules/
 
 `onDomainChange` reports the visible span after a pan or zoom, at most once per frame. A span handed in as `initialDomain` is not reported back, so two schedules never feed each other.
 
@@ -3470,7 +3470,7 @@ Converts between a point on the screen and a time on a lane, so marks of your ow
 import { Schedule } from "@umriss-ui/schedule";
 ```
 
-Demo page: https://romanhaendler.github.io/umriss-ui/schedule/#/handle
+Demo page: https://romanhaendler.github.io/umriss-ui/schedule/handle/
 
 The handle holds three functions and nothing else: `clientPointOf(time, lane?)`, `positionAt(clientX, clientY)` and `visibleDomain()`. Everything else the schedule does is props.
 
@@ -3579,7 +3579,7 @@ Drag a bar to a new time or onto another lane (also called drag-and-drop resched
 import { Schedule, applyIntent } from "@umriss-ui/schedule";
 ```
 
-Demo page: https://romanhaendler.github.io/umriss-ui/schedule/#/move-and-lane
+Demo page: https://romanhaendler.github.io/umriss-ui/schedule/move-and-lane/
 
 Each name in `intents` enables one gesture. Without `intents` the schedule is read-only, and pressing a bar pans the plot.
 
@@ -3786,7 +3786,7 @@ Change how long work takes, or how long its preparation and its wrap-up take, by
 import { Schedule, applyIntent } from "@umriss-ui/schedule";
 ```
 
-Demo page: https://romanhaendler.github.io/umriss-ui/schedule/#/stretch
+Demo page: https://romanhaendler.github.io/umriss-ui/schedule/stretch/
 
 `stretch` enables the two edges of the main time. `leadIn` and `leadOut` add a grip at the outer edge of each; the grips show on the selected subtask only, so click a bar first.
 
@@ -3889,7 +3889,7 @@ Makes a drag land on a raster - the axis' own step, a fixed duration, or a patte
 import { Schedule, snapTime } from "@umriss-ui/schedule";
 ```
 
-Demo page: https://romanhaendler.github.io/umriss-ui/schedule/#/snapping
+Demo page: https://romanhaendler.github.io/umriss-ui/schedule/snapping/
 
 Without `snap` a drag lands on the fine band's step, which follows the zoom. A number is a step in milliseconds; `{ step, offset }` counts from local midnight; `false` places to the minute.
 
@@ -4045,7 +4045,7 @@ Drag work that is not on the plan yet - from a backlog or a list of unassigned j
 import { Schedule, subtaskFromPlace } from "@umriss-ui/schedule";
 ```
 
-Demo page: https://romanhaendler.github.io/umriss-ui/schedule/#/placing
+Demo page: https://romanhaendler.github.io/umriss-ui/schedule/placing/
 
 The browser hands over dragged data only on the drop, so declare what is being dragged in `placing` on your `dragstart` and clear it on `dragend`. The schedule then shows the ghost at the snapped time, with the findings the drop would create.
 
@@ -4168,7 +4168,7 @@ Marks the lanes and times a piece of work may not go to as soon as a drag begins
 import { Schedule, BlockedTimes } from "@umriss-ui/schedule";
 ```
 
-Demo page: https://romanhaendler.github.io/umriss-ui/schedule/#/where-it-may-go
+Demo page: https://romanhaendler.github.io/umriss-ui/schedule/where-it-may-go/
 
 `canMoveTo(subtask, lane)` is asked once per lane when a drag takes hold, and again at the drop. Refused lanes are drawn back and hatched; over one, the ghost stays on the last lane allowed, tied to the pointer by a line.
 
@@ -4406,7 +4406,7 @@ Works out which later work has to move when one piece moves: every successor who
 import { ripple, shiftTask, applyIntent } from "@umriss-ui/schedule";
 ```
 
-Demo page: https://romanhaendler.github.io/umriss-ui/schedule/#/ripple
+Demo page: https://romanhaendler.github.io/umriss-ui/schedule/ripple/
 
 `ripple(subtasks, dependencies, intent)` returns move intents down the whole chain, in the order they were pushed. A successor keeps its length and is never pulled earlier: room that opens up is the planner's.
 
@@ -4612,7 +4612,7 @@ Lists what is wrong with a plan - double bookings on a lane, dependencies that d
 import { findings, overlaps, violatedDependencies, inBlockedTime } from "@umriss-ui/schedule";
 ```
 
-Demo page: https://romanhaendler.github.io/umriss-ui/schedule/#/findings
+Demo page: https://romanhaendler.github.io/umriss-ui/schedule/findings/
 
 `findings(subtasks, dependencies, blocked)` returns all three kinds; `overlaps`, `violatedDependencies` and `inBlockedTime` return one each. They are pure functions: run them wherever the data changes, with or without a schedule on screen.
 

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@umriss-ui/schedule",
-  "version": "0.3.3",
-  "description": "The umriss schedule for data-dense applications - work on lanes over time, with dependencies, blocked time, findings and controlled editing.",
+  "version": "0.3.5",
+  "description": "React Gantt-style schedule for data-dense applications - work on lanes over time, with dependencies, blocked time, findings and controlled editing.",
   "license": "MIT",
   "author": "Roman Händler",
   "homepage": "https://romanhaendler.github.io/umriss-ui/schedule/",
@@ -15,11 +15,16 @@
   },
   "keywords": [
     "react",
-    "components",
-    "ui",
-    "umriss",
+    "gantt",
+    "gantt-chart",
+    "scheduler",
     "schedule",
-    "canvas"
+    "timeline",
+    "planning",
+    "resource-planning",
+    "canvas",
+    "typescript",
+    "umriss"
   ],
   "type": "module",
   "files": [
@@ -45,8 +50,8 @@
   "peerDependencies": {
     "react": ">=18",
     "react-dom": ">=18",
-    "@umriss-ui/charts": "^0.8.0",
-    "@umriss-ui/core": "^0.13.1"
+    "@umriss-ui/charts": "^0.8.1",
+    "@umriss-ui/core": "^0.14.1"
   },
   "devDependencies": {
     "@fontsource/geist-mono": "^5.3.0",
@@ -60,9 +65,9 @@
     "typescript": "^5.6.3",
     "vite": "^6.0.0",
     "vite-plugin-dts": "^4.3.0",
-    "@umriss-ui/charts": "0.8.0",
     "@umriss-ui/demo": "0.0.0",
-    "@umriss-ui/core": "0.13.1"
+    "@umriss-ui/charts": "0.8.1",
+    "@umriss-ui/core": "0.14.1"
   },
   "scripts": {
     "props": "node --disable-warning=ExperimentalWarning --experimental-strip-types demo/props.ts",