A folder load checked each .wasm path and then opened it with a blocking
open. When a named pipe replaced the file between the two, the open held
the load until something wrote to the pipe, and with it startup or a
prefs.set of the folder. On Unix the file is now opened
without waiting and without making a terminal the controlling terminal,
and the opened file is checked again: anything that is not a regular file,
or is over the module limit, is refused and listed in the folder report.
A folder load still reads at most 1,000 .wasm files, the first by file
name, and now holds only those paths while it lists the folder. The
files past the first 1,000 were dropped and not reported; plugin.reload
and plugin.list now return their count as leftOut. An error while the
folder is listed fails the load, as an error opening the folder does,
instead of dropping the entries after it.
* refactor(cdr): depend on shared craft-cdr from craft-libs (#1665)
Replaces the local crates/cdr (vectorcraft-cdr) crate with craft-cdr
from storytold/craft-libs#2697 (storytold/craft-libs#778), keeping
VectorCraft's document/artboard/layer/shape mapping in crates/engine.
Co-authored-by: dotCooCoo <[email protected]>
* build(cdr): pin craft-cdr to craft-libs main (75d179f8df)
* build(cdr): pin craft-cdr to craft-libs main (9b28b56bc7)
* docs(cdr): point CDR/CMX provenance and test paths to craft-cdr
---------
Co-authored-by: dotCooCoo <[email protected]>
Plugin::load now validates each module with wasmparser and a fixed list
of WebAssembly features before wasmi reads it: mutable globals, sign
extension, saturating conversions, multi-value, bulk memory, reference
types, tail calls, extended constant expressions and floats. A module
that uses any other feature is refused, so a wasmi upgrade, a change to
its defaults or one of its crate features turned on elsewhere in the
build does not change what a plug-in may use. wasmi's Config is set to
the same list for every setter it has in this build.
The list is the set wasmi accepted before, without multi-memory. A
second memory was already refused by the one-memory limit; its error
now says "multiple memories". No module that loaded before is refused.
wasmparser 0.228.0 is the version wasmi 2.0.0 already uses.
A new test loads a plug-in that uses each listed feature and checks
that modules using SIMD, relaxed SIMD, memory64, a second memory,
custom page sizes, wide arithmetic, threads, exceptions, legacy
exceptions, function references or garbage collection are refused with
an error that names the feature.
docs/plugins.md lists the whole set; it named only four of the allowed
features before.
The gate's one job builds all 106 test binaries on a 4-CPU, 16 GB runner,
and it is often stopped with exit code 143 ("The runner has received a
shutdown signal") during that build. ci.yml now runs the gate as five
legs:
- Shards 1 to 4 run `cargo xtask ci shard`, which builds and runs the
tests and doctests of its own crates: ui-egui, engine, the apps with
mcp and xtask, and every other crate.
- Shard 5 runs the other `cargo xtask ci` steps.
- On pushes to main, a `cache warm` leg runs `cargo xtask ci warm`,
which builds what every shard builds and saves the dependency cache.
`gate (ubuntu-24.04)` passes only when all five legs passed.
`cargo xtask ci` with no argument runs every step, as before.
`cargo xtask shards` lists each shard's crates. It fails when a crate
named in xtask/src/shards.rs is not a workspace member or is named
twice, and when a crate builds with other features in its shard than in
`cargo test --workspace`. Every shard runs it first. vectorcraft-affinity
and vectorcraft-pdf now turn on `synth` and `read-count` in their own
dev-dependencies, which vectorcraft-engine's dev-dependencies turned on
before. Without that, 39 tests of affinity's `it` binary do not build in
a shard without the engine.
The gate also sets dev-debug "0" and dev-strip: true, so the workspace
crates build without line tables and the test binaries without debug
info or symbols.
* eps: delegate scene-writer shading, image stream, and line style syntax to craft-ps
* chore(eps): repin craft-ps to merged craft-libs main (cfcc86242)
Every storytold/craft-libs git dependency, the hayro, krilla and
linesweeper patches and the web app's craft-web-api now use one
revision, 64b181977a, so Cargo.lock holds one copy of each craft-libs
crate. craft-ui's docking Monitor has a new work_area field; the
monitors VectorCraft lists set it to None, as winit reports no work
area.
craft-image-codecs moves from a499742a93 to 3af718585c on craft-libs main.
It brings in storytold/craft-libs#1758: a deep EXR file with more than one
part now finds each part's chunks after every part's offset table, and an
offset table that runs past the end of the file is an error.
The move also brings in the other merged changes to craft-image-codecs and
the craft-jpeg, craft-metadata and craft-tiff copies it uses: #1646, #1686,
#1837, #1838, #1867 and #1889. #1774 moves DDS reading and writing into the
new craft-dds crate, which adds BC4 and BC5 textures. The other craft-libs
crates stay at their current revisions. craft-svg keeps its own
craft-image-codecs at 431f704478, which it only uses for PNG, JPEG, GIF and
WebP images.
A Russian or Bulgarian word written with a combining breve (`и` + U+0306
for `й`) failed the Cyrillic script check and stayed whole; the check now
reads the composed word, so it breaks at the same characters as `чайник`.
A stress mark, which composes with nothing, still keeps the word whole.
The all-capitals guard skipped a decomposed capital such as `O` + U+0308,
since a combining mark has no case, so `ÖĞRENCİ` spelled that way was
hyphenated in Turkish; the guard now counts only the letters.
The XML declaration, DOCTYPE entity subset and root <svg> open now go
through SvgWriter. Mapping and the rest of the document stay in the app.
Width and height stay unitless in one place so #7105 can rebase.
Object › Plug-ins › Packaging Tools › Check Fold Lines, and the Fold Lines
panel's Check button, check the fold lines of the selection, or of the
document while nothing is selected (`addon.packaging.check`).
- Cut lines bound the material: each connected piece that encloses an
area is one blank, its largest closed cut line is the outline, and a
closed cut line inside it is a hole. A slot drawn as a rectangle across
the outline leaves the same material as a notch drawn in it, and an
outline drawn as several open cut lines works too.
- Creases, partial cuts and perforations divide a blank into panels; the
pieces between the same two panels form one hinge.
- 15 issue codes, errors and warnings, each naming its lines; cut line
ends within a tolerance (0.1 pt, 0.01 to 10) are joined and reported as
a gap. With `select`, the lines the issues name are selected.
- The panel lists the issues in the interface language, with a summary
line; clicking an issue or its Select button selects its lines. The
list is kept until the document changes.
`vectorcraft_pathops::adjacency` maps paths as live_paint does and keeps,
for each edge, every input it lies on and the faces on both sides; the
blank model is `vectorcraft_three_d::fold::blanks`. The engine now depends
on vectorcraft-three-d directly.
Docs: docs/mcp.md (Check Fold Lines), crates/pathops/README.md, ROADMAP.