@algorisys/tinyfly 0.110.0 → 0.111.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -54,7 +54,7 @@ A lightweight, API-driven animation engine and visual editor for creating high-p
54
54
  - **Code-drawn targets** - A `custom` canvas target draws with code (characters, charts, props) while the timeline animates its position, opacity and its own `props`, so drawing stays code and timing stays JSON
55
55
  - **Immediate mode too** - A scene's `background` and `draw(ctx, { time })` functions paint each frame directly, Cairo/Processing-style, and mix freely with timeline targets
56
56
  - **Timing from narration** - `planNarration()` lays spoken lines out from their clip lengths (lead, gap, tail) into cues, scene spans and markers; `voiceNarration()` measures recorded clips with ffmpeg and writes the sample-aligned narration WAV
57
- - **Cricket stories** - Public `@algorisys/tinyfly/sports` builders create an organic adult/child cast, standard pitch, full fielding side, wickets and boundary. Sixteen authored plays cover deliveries, strokes, running, boundaries, catches, fielding, throws, dismissals, no-balls and wides for Test, ODI and T20. Exact contact keys, captions and results are JSON; eight camera views include a 360° ground orbit and ball follow, with 25%–400% review zoom and reset. Fielders watch the bowler, track the incoming delivery through its bounce, then follow the struck ball. Body turns stay continuous from strokes into batter runs, into collection runs and while following return throws. A side-on right-handed stance and Adults/Men/Children/Mixed casts reuse the organic rig. Keeper-bound misses clear the native legs and intact stumps before palm collection. Public `CRICKET_FIELDING_POSITIONS` labels name all eleven stock fielders, including Extra cover; the Teams and field positions guide explains the two on-field batters, nine waiting teammates and mid-on/long-on. Playback, scrubbing and camera controls sit beside the scene (above it on phones). Try [Cricket Stories](https://tinyfly.app/examples/live-cricket-story), download its scene/action/camera JSON, or render the headless example. See [the cricket guide](docs/cricket.md).
57
+ - **Cricket stories** - Public `@algorisys/tinyfly/sports` builders create an organic adult/child cast, standard pitch, full fielding side, wickets and boundary. Sixteen authored plays cover deliveries, strokes, running, boundaries, catches, fielding, throws, dismissals, no-balls and wides for Test, ODI and T20. Exact contact keys, captions and results are JSON; eight camera views include a 360° ground orbit and ball follow, with 25%–400% review zoom and reset. Select MCC, ICC men or ICC women field markings. ICC ODI/T20 restriction areas use wicket-centred capsule outlines; optional public setup markers classify the field. Fielders watch the bowler, track the incoming delivery through its bounce, then follow the struck ball. Body turns stay continuous from strokes into batter runs, into collection runs and while following return throws. A side-on right-handed stance and Adults/Men/Children/Mixed casts reuse the organic rig. Keeper-bound misses clear the native legs and intact stumps before palm collection. Public `CRICKET_FIELDING_POSITIONS` labels name all eleven stock fielders, including Extra cover; the Teams and field positions guide explains the two on-field batters, nine waiting teammates and mid-on/long-on. Playback, scrubbing and camera controls sit beside the scene (above it on phones). Try [Cricket Stories](https://tinyfly.app/examples/live-cricket-story), download its scene/action/camera JSON, or render the headless example. See [the cricket guide](docs/cricket.md).
58
58
  Wide camera clipping scales for boundaries up to 250 m, and ball-follow generation reads only ball channels. Local full-page previews include add-ons before publication; copied pages keep their versioned CDN bundles.
59
59
  Defensive blocks meet the blade with both hands on the bat. Keeper-bound deliveries pass outside the off stump with clearance for the displayed ball before collection.
60
60
 
@@ -233,7 +233,7 @@ for what you import:
233
233
  | `@algorisys/tinyfly/maps` | Animated maps: OpenStreetMap tiles or an offline world outline, places, routes that draw on, a camera that flies (`mapTarget`, `mapFlyTracks`, `fitView`, `WORLD_CITIES`) | Anywhere with a Canvas 2D context (tiles need a network) |
234
234
  | `@algorisys/tinyfly/characters` | Poseable stick figure: `stickFigureTarget`, `poseTracks`, `POSES`, `blendPose`, `walkPose`, `drawStickFigure`; `stickFigureJoints` and `layers` for costumes, hair and props; `turn`, `sit` and ground contact; an organic look by default (`classic` keeps the old one); **characters v2**: `character()` / `characterTarget()`, turnarounds front to back, contact, reaching, clean / pencil / silhouette looks; `hair`, `facialHair`, `glasses`, `hat`, `ears`, `face`, `feet`, `build`, `outfit` as data, `castMember()`, `HUMAN_EXPRESSIONS` with face marks; `embrace`, `helpUp`, `scenery` | Anywhere with a Canvas 2D context |
235
235
  | `@algorisys/tinyfly/headless` | `renderVideo`, `renderStills`, `FrameRenderer`: render a scene to MP4 or PNGs (see [Rendering Video from Code](docs/video-rendering.md)) | Node (`@napi-rs/canvas` optional peer, ffmpeg) |
236
- | `@algorisys/tinyfly/sports` | `cricketPlayer`, `cricketField`, `cricketAction`, `cricketClip`, `cricketCameraTracks`, `cricketEventAt`, shared `ballFlightTracks`; authored organic cricket stories and a 360° ground camera | Browser, Worker, Node; scene rendering through adapters |
236
+ | `@algorisys/tinyfly/sports` | `cricketPlayer`, `cricketField`, `cricketAction`, `cricketClip`, `cricketCameraTracks`, `cricketEventAt`, field marking profiles/classification/overlays, shared `ballFlightTracks`; authored organic cricket stories and a 360° ground camera | Browser, Worker, Node; scene rendering through adapters |
237
237
  | `@algorisys/tinyfly/browser` | One script-tag bundle (`tinyfly.iife.js`): the engine, player, drivers, interaction, the GSAP-style `live` / `tf` facades, teaching-embed controls and mounting, and the `characters` stick figure. Not included: `export`, `adapters`, `teach`, the framework hooks, `headless` | Browser |
238
238
 
239
239
  ```js
@@ -280,7 +280,7 @@ GSAP-shaped functions at the top level. Teaching embeds are included: add
280
280
  itself.
281
281
 
282
282
  ```html
283
- <script src="https://cdn.jsdelivr.net/gh/algorisys-oss/tinyfly@v0.110.0/cdn/tinyfly.iife.js"></script>
283
+ <script src="https://cdn.jsdelivr.net/gh/algorisys-oss/tinyfly@v0.111.0/cdn/tinyfly.iife.js"></script>
284
284
  <script>
285
285
  tinyfly.to('.box', { x: 200, rotate: 90, duration: 1, ease: 'power2.out' })
286
286
 
@@ -316,7 +316,7 @@ A teaching figure needs no code at all:
316
316
  <script type="application/json" data-tinyfly-timeline>{ …timeline JSON with markers… }</script>
317
317
  <figcaption>Appending to a full slice</figcaption>
318
318
  </figure>
319
- <script src="https://cdn.jsdelivr.net/gh/algorisys-oss/tinyfly@v0.110.0/cdn/tinyfly.iife.js" data-tinyfly-auto></script>
319
+ <script src="https://cdn.jsdelivr.net/gh/algorisys-oss/tinyfly@v0.111.0/cdn/tinyfly.iife.js" data-tinyfly-auto></script>
320
320
  ```
321
321
 
322
322
  See [Teaching Animations](docs/teaching.md).
@@ -415,7 +415,7 @@ Without a build step, the player bundle puts the same functions on a `tinyfly` g
415
415
  <div data-tinyfly="box" style="width: 60px; height: 60px; background: #4a9eff;"></div>
416
416
  </div>
417
417
 
418
- <script src="https://cdn.jsdelivr.net/gh/algorisys-oss/tinyfly@v0.110.0/cdn/tinyfly-player.iife.js"></script>
418
+ <script src="https://cdn.jsdelivr.net/gh/algorisys-oss/tinyfly@v0.111.0/cdn/tinyfly-player.iife.js"></script>
419
419
  <script>
420
420
  tinyfly.play('#animation', './animation.json', { loop: -1 })
421
421
  </script>
@@ -524,7 +524,7 @@ Or skip the code entirely with declarative embeds (see [Teaching Animations](doc
524
524
  <svg viewBox="0 0 720 200">…</svg>
525
525
  <script type="application/json" data-tinyfly-timeline>{ …timeline JSON… }</script>
526
526
  </figure>
527
- <script src="https://cdn.jsdelivr.net/gh/algorisys-oss/tinyfly@v0.110.0/cdn/tinyfly-embed.iife.js" data-tinyfly-auto></script>
527
+ <script src="https://cdn.jsdelivr.net/gh/algorisys-oss/tinyfly@v0.111.0/cdn/tinyfly-embed.iife.js" data-tinyfly-auto></script>
528
528
  ```
529
529
 
530
530
  ### Audio / Video Sync
package/docs/cricket.md CHANGED
@@ -34,10 +34,13 @@ See [getting started](getting-started.md) for the versioned CDN URLs.
34
34
  | API | Result |
35
35
  | --- | --- |
36
36
  | `cricketPlayer({ id, role, preset?, format?, height?, position?, color?, headwear?, appearance? })` | An owned JSON `character` scene object. Roles: batter, bowler, keeper, fielder, umpire. Presets include youngMan, youngWoman, childBoy, childGirl. |
37
- | `cricketField({ id?, format?, cast?, boundaryRadius?, battingColor?, fieldingColor? })` | `scene`, `format`, `boundaryRadius`, `landmarks`; stock fielders have human-readable JSON `name` labels. A 20.12 × 3.05 metre pitch, standard creases, wickets/bails, two bats, ball, boundary, eleven fielding players, two batters and two umpires. |
37
+ | `cricketField({ id?, format?, cast?, boundaryRadius?, markingProfile?, battingColor?, fieldingColor? })` | `scene`, `format`, `boundaryRadius`, `landmarks`, `markingProfile`, `fieldingArea`; stock fielders have human-readable JSON `name` labels. A 20.12 × 3.05 metre pitch, standard creases, wickets/bails, two bats, ball, boundary, eleven fielding players, two batters and two umpires. |
38
+ | `cricketFieldingAreaContains(field, point)` | `true` inside/on the ideal restriction-area capsule, `false` outside, `null` without region metadata. Uses x/z; point height is ignored. |
39
+ | `cricketFieldingPositions(field)` | Owned setup-position data for stock fielders: `id`, `name`, `position`, `inside`. |
40
+ | `cricketFieldingOverlay(field)` | Optional static JSON line markers, green inside/orange outside. Append to scene objects without changing motion. |
38
41
  | `cricketAction(field, { action?, duration?, every? })` | A JSON timeline, timed events/captions and declared example result. Does not modify the field. |
39
42
  | `cricketClip(options)` | Combines field and action; default T20, adult cast, pace bowling, 6000 ms. |
40
- | `cricketCameraTracks(clip, { view?, yaw?, every? })` | Ordinary scene camera tracks. Merge these with the action tracks. |
43
+ | `cricketCameraTracks(clip, { view?, yaw?, zoom?, every? })` | Ordinary scene camera tracks. Merge these with the action tracks. |
41
44
  | `cricketEventAt(events, time)` | Most recent event at that time, including when seeking backward. |
42
45
  | `ballFlightPoint(options, time)`, `ballFlightTracks(options)` | Shared sampled arcs for other sports too. `from`, `to`, `arc`, `curve`, `start`, `end`, `target`; exact endpoints. |
43
46
 
@@ -93,6 +96,63 @@ before the ball arrives. Their native head poses aim at world targets,
93
96
  independently of their body yaw and camera selection. The live example's
94
97
  **Teams and field positions** disclosure uses the scene's JSON labels.
95
98
 
99
+ ## Field marking profiles
100
+
101
+ `markingProfile` is `icc-men` (default), `icc-women` or `mcc`, independent of
102
+ `cast`. `CRICKET_MARKING_PROFILES` exports their names, dimensions and summaries.
103
+ These select field markings only; venue boundaries, player eligibility,
104
+ powerplay phases and the rest of a competition's conditions require separate
105
+ checks. A caller-selected small boundary remains an illustrative venue.
106
+
107
+ | Profile | Popping crease painted on each side | ODI/T20 restriction area |
108
+ | --- | --- | --- |
109
+ | `icc-men` | 7.5 m | Wicket-centred semicircles of radius 27.43 m, joined by straight sides |
110
+ | `icc-women` | 7.5 m | Wicket-centred semicircles of radius 23 m, joined by straight sides |
111
+ | `mcc` | 1.83 m minimum | None prescribed by the base Laws |
112
+
113
+ Test has no restriction-area line for any profile. All profiles retain the
114
+ 20.12 m pitch, the 1.22 m popping-crease offset and the return-crease positions.
115
+ The painted popping crease is a finite visual mark; the actual crease is
116
+ considered unlimited in length. The existing object ID `fielding-circle` is
117
+ retained for the corrected capsule outline. For ICC men its extrema are
118
+ x = ±27.43 m and z = ±37.49 m; the two arc centres are z = ±10.06 m.
119
+
120
+ The dimensions follow MCC 2026 Law 7.3 and ICC October 2026 clauses 7.3/28.7.
121
+ Sources: [MCC Laws](https://www.lords.org/getmedia/a4ef9f77-2a25-4f5b-a286-4601f08e6334/Laws-of-Cricket-2017-Code-4th-Edition-%282026%29_5.pdf),
122
+ [ICC men Test](https://images.icc-cricket.com/image/upload/prd/a8114zro5tkioifz0jqg.pdf),
123
+ [ODI](https://images.icc-cricket.com/image/upload/prd/bxkzkcyvfn6tvi70zh0w.pdf),
124
+ [T20I](https://images.icc-cricket.com/image/upload/prd/bsxcho7ufe2pjban0wjp.pdf),
125
+ [ICC women Test](https://images.icc-cricket.com/image/upload/prd/hbwwi78pugzpdwft0v4v.pdf),
126
+ [ODI](https://images.icc-cricket.com/image/upload/prd/qunpw1kfh3ibxlz58jlw.pdf) and
127
+ [T20I](https://images.icc-cricket.com/image/upload/prd/o3vhm0zw7pppoxpgopke.pdf).
128
+
129
+ ```ts
130
+ import { cricketField, cricketFieldingAreaContains, cricketFieldingPositions,
131
+ cricketFieldingOverlay } from '@algorisys/tinyfly/sports'
132
+
133
+ const field = cricketField({ format: 't20', markingProfile: 'icc-women' })
134
+ const inside = cricketFieldingAreaContains(field, [0, 0, 30]) // true
135
+ const setup = cricketFieldingPositions(field)
136
+ const outside = setup.filter(player => player.inside === false)
137
+ const sceneWithMarkers = { ...field.scene,
138
+ objects: [...field.scene.objects, ...cricketFieldingOverlay(field)] }
139
+ ```
140
+
141
+ Classification uses the ideal capsule rather than a midpoint circle. Points on
142
+ its boundary count as inside, with a 1 nm numeric tolerance. `null` distinguishes
143
+ an absent area from an outside point, including older/custom JSON fields with
144
+ no `fieldingArea` metadata. The query accepts world-ground x/z reference points;
145
+ it does not judge whole-player/foot placement or whether a field is legal.
146
+ The setup helpers read the stock players' unparented scene positions. Markers
147
+ stay there during playback. Both ICC stock layouts have nine reference points
148
+ inside and two outside (Fine leg and Third man), useful for a powerplay placement
149
+ illustration; this is not automatic umpiring.
150
+
151
+ Select **Markings** and **Setup field markers** in the example, then choose an
152
+ overhead/whole-ground camera. Profile and overlay changes preserve current
153
+ story time and playback; selected zoom is retained. Downloaded JSON includes
154
+ the profile, analytic region metadata, corrected line and optional markers.
155
+
96
156
  ## Review zoom
97
157
 
98
158
  Pass `zoom` to `cricketCameraTracks(clip, { view: 'batter', zoom: 2 })` for
@@ -1143,7 +1143,7 @@ The dialog shows the generated HTML/JavaScript code with a **Copy Code** button.
1143
1143
  **Steps to embed:**
1144
1144
  1. Build the player: `npm run build:player`
1145
1145
  2. Copy `lib/player/tinyfly-player.iife.js` to your project (or load
1146
- `https://cdn.jsdelivr.net/gh/algorisys-oss/tinyfly@v0.110.0/cdn/tinyfly-player.iife.js`
1146
+ `https://cdn.jsdelivr.net/gh/algorisys-oss/tinyfly@v0.111.0/cdn/tinyfly-player.iife.js`
1147
1147
  instead; see [Deployment](DEPLOYMENT.md))
1148
1148
  3. Copy the generated code into your HTML
1149
1149
  4. Adjust the script `src` path if needed
package/docs/examples.md CHANGED
@@ -743,7 +743,7 @@ For simple website embedding without a build system.
743
743
  </html>
744
744
  ```
745
745
 
746
- Build the player with `npm run build:player` to generate `lib/player/tinyfly-player.iife.js`, or load it from the CDN: `https://cdn.jsdelivr.net/gh/algorisys-oss/tinyfly@v0.110.0/cdn/tinyfly-player.iife.js`.
746
+ Build the player with `npm run build:player` to generate `lib/player/tinyfly-player.iife.js`, or load it from the CDN: `https://cdn.jsdelivr.net/gh/algorisys-oss/tinyfly@v0.111.0/cdn/tinyfly-player.iife.js`.
747
747
 
748
748
  ---
749
749
 
@@ -185,7 +185,7 @@ with a GSAP-style call (durations are in seconds here):
185
185
  ```html
186
186
  <div class="box" style="width:60px;height:60px;background:#4a9eff"></div>
187
187
 
188
- <script src="https://cdn.jsdelivr.net/gh/algorisys-oss/tinyfly@v0.110.0/cdn/tinyfly.iife.js"></script>
188
+ <script src="https://cdn.jsdelivr.net/gh/algorisys-oss/tinyfly@v0.111.0/cdn/tinyfly.iife.js"></script>
189
189
  <script>
190
190
  tinyfly.to('.box', { x: 200, duration: 1 })
191
191
  </script>
@@ -74,7 +74,7 @@ Without a build step, the all-in-one bundle exposes the same functions on a
74
74
  global — `tinyfly.to()`, `tinyfly.timeline()` and so on:
75
75
 
76
76
  ```html
77
- <script src="https://cdn.jsdelivr.net/gh/algorisys-oss/tinyfly@v0.110.0/cdn/tinyfly.iife.js"></script>
77
+ <script src="https://cdn.jsdelivr.net/gh/algorisys-oss/tinyfly@v0.111.0/cdn/tinyfly.iife.js"></script>
78
78
  <script>
79
79
  tinyfly.to('.box', { x: 200, duration: 1 })
80
80
  </script>
package/docs/llm-guide.md CHANGED
@@ -100,6 +100,16 @@ demonstrations, not collision-based umpiring or an innings simulator. Do not
100
100
  infer new outcomes from the illustrative arcs. See `docs/cricket.md` and
101
101
  `examples/headless-video/cricket-story.mjs`; `/examples/live-cricket-story`
102
102
  has event seeking and downloadable scene/action/camera JSON.
103
+ Choose `markingProfile: 'icc-men' | 'icc-women' | 'mcc'` explicitly when
104
+ teaching field geography; default ICC men is independent of cast. These are
105
+ marking dimensions, not full competition profiles. ODI/T20 ICC areas are
106
+ wicket-centred capsules (27.43/23 m radii); Test/MCC have no restriction line.
107
+ ICC popping-crease marks extend 7.5 m on either side; MCC minimum is 1.83 m.
108
+ `cricketFieldingAreaContains(field, point)` returns true/false/null, with null
109
+ for absent metadata/areas. `cricketFieldingPositions`/`cricketFieldingOverlay`
110
+ provide owned static setup markers. Do not count null as outside or interpret
111
+ point classification as legal whole-player placement. Markers stay at setup
112
+ positions; append them to the scene and preserve them in exported JSON.
103
113
  `CRICKET_FIELDING_POSITIONS` maps the eleven stock fielding IDs to public labels;
104
114
  scene objects carry them in `name`. `fielder` is Extra cover. Keep eleven fielders,
105
115
  two on-field batters and two umpires; nine batting teammates wait off-field.
package/docs/maps.md CHANGED
@@ -14,8 +14,8 @@ On a page with no build step, load the maps add-on after the browser bundle; it
14
14
  adds to the same `tinyfly` global:
15
15
 
16
16
  ```html
17
- <script src="https://cdn.jsdelivr.net/gh/algorisys-oss/tinyfly@v0.110.0/cdn/tinyfly.iife.js"></script>
18
- <script src="https://cdn.jsdelivr.net/gh/algorisys-oss/tinyfly@v0.110.0/cdn/tinyfly-maps.iife.js"></script>
17
+ <script src="https://cdn.jsdelivr.net/gh/algorisys-oss/tinyfly@v0.111.0/cdn/tinyfly.iife.js"></script>
18
+ <script src="https://cdn.jsdelivr.net/gh/algorisys-oss/tinyfly@v0.111.0/cdn/tinyfly-maps.iife.js"></script>
19
19
  ```
20
20
 
21
21
  It is a separate script because the offline world map it carries adds about
package/docs/teaching.md CHANGED
@@ -25,7 +25,7 @@ path for all of that:
25
25
  </figure>
26
26
 
27
27
  <!-- once, anywhere on the page (a site-wide footer is fine) -->
28
- <script src="https://cdn.jsdelivr.net/gh/algorisys-oss/tinyfly@v0.110.0/cdn/tinyfly-embed.iife.js" data-tinyfly-auto></script>
28
+ <script src="https://cdn.jsdelivr.net/gh/algorisys-oss/tinyfly@v0.111.0/cdn/tinyfly-embed.iife.js" data-tinyfly-auto></script>
29
29
  ```
30
30
 
31
31
  Every `[data-tinyfly-embed]` mounts when the page is ready, with no per-post