.meb standard changelog
Format follows Keep a Changelog. Versioning:
05-versioning.md.
[3.0.0] — 2026-11-19
A tree as in a design program — step 1 of version 3.0 (the mebCAD document tree one to one). Further 3.x elements (authored drawings with point addresses, panel embedding, linear elements, movable states) will be added as MINOR changes.
Changed (breaking)
- A cabinet is a group with a role — the
type: "cabinet"node is removed; a cabinet is{ "type": "group", "role": "cabinet" }. The role says what the group is for production and rules; no role means a plain group: a drawer, a subassembly, a set, a room. See §7.3–§7.4. - Panel, hardware item and solid are nodes in
children—cabinet.panels[],cabinet.hardware[]andcabinet.solids[]are removed; a panel hastype: "panel", a hardware itemtype: "hardware", a solidtype: "solid". They stand in any group and in the root — a worktop over a set of cabinets does not need an artificial cabinet, and a drawer is a group in a cabinet with its own panels. See §7.1, §8, §12. - Every group has a front —
cabinet.frontbecomesgroup.front(default"-Y", editable). See §7.3, §14.2. - The identifier of every node is unique in the file, including a hardware item without a position, and every node has a name.
Added
- Tree rules §15.10 — only a group has children, there is no cabinet inside a cabinet at any depth, every node except a hardware item without a position has
positionandrotation. - A number once assigned stays (§7.5) — a program writing an object read from a file keeps its
production_id. - Rotation angles in the range (−180°, 180°] (§7.2) — a recommendation, one notation for the same angle.
- Appendix B — reading 2.x files: a 2.x cabinet → a group with a role, cabinet lists → children; one path for readers.
- Glossary: entries Group role and Group front; updated Node, Group, Cabinet, Solid, Panel, Hardware item, Hardware instance.
Compatibility
- A breaking change (MAJOR). A 3.0 file is not a valid 2.x file, and a 2.x implementation MUST reject it (
05-versioning.md§3). - Migration path: Appendix B of the specification — the mapping of every 2.x → 3.0 change; the
docs/examples/examples are rewritten to 3.0. - Version 2.6.0 is the last 2.x version; implementations reading 3.0 MAY read 2.x through the mapping in Appendix B.
- Schema:
https://meb.org.pl/schema/3.0.0/meb.schema.json.
[2.6.0] — 2026-11-19
Added
grain_group.rows[]— row alignment. Each row of a block has its own alignment (align):"start"— to the start edge (the left one with vertical grain, the bottom one with horizontal grain),"center"— to the center,"end"— to the end edge. The remaining width of a row narrower than the widest one lies on the other side; with center, half on each side. A row without an entry is aligned to the start. See §13.2.- Position-in-block notation
#B.RA.P— e.g.#1.2S.1: block 1, row 2 aligned to the center (lettersP— start,S— center,K— end, the same for both grain directions), panel 1. A program without grain groups uses it to carry the block in panel names, and a converter creates groups from it; a program that displays a block uses it to write the panel's position. See §13.3. - Validation rule §15.4 item 6: a
rows[]entry points to an existing row of the group, each row at most once. - Glossary: entries Face of a grain group panel, Row alignment and Position-in-block notation; updated Grain group, Grain relative to the front and Order in a grain group.
- Example
09-ciaglosc-sloja.meb— a display cabinet group: two 600 drawer fronts above a 900 door aligned to the center.
Clarified
- The face of a group panel is the side visible from outside the furniture (§13.1) — a block is described in the view of the panels' faces, and it is the face one looks at when assessing grain continuity; machining operations from the inside (hinge cups) lie on the back. The source program MUST describe a group panel with its face outwards — a panel described with its face inwards would be a mirror image of itself in the block and would get its machining operations on the wrong side of the grain. Version 2.5.0 said “in the view of the face, as the panels lie in the front of the furniture”, without tying the face to the visible side.
- Start edge instead of alignment edge — positions (
order) are counted from the left edge (with horizontal grain, from the bottom edge) regardless of the row alignment; in 2.5.0 this edge was also the only alignment.
Compatibility
- A backward-compatible change (MINOR) — a new optional field. A group without
rowsmeans the same as in 2.5.0: all rows aligned to the start edge. - A 2.5.0 implementation ignores
rowsin accordance with §1.3 and reads the block with rows aligned to the start — it will read the rows and positions of the panels correctly; only the location of the remaining row width will differ. - Schema:
https://meb.org.pl/schema/2.6.0/meb.schema.json.
[2.5.0] — 2026-11-16
Added
- Grain continuity group as a block of rows. A group (
grain_groups[]) is no longer only a strip of panels cut one after another: it is a block of rows laid one after another along the grain, and a row is panels side by side across the grain, all with the same dimension along the grain. The grain passes between rows of panels of different widths (“staggered”) — e.g. a row of three 500 fronts above a row of two 750 fronts. A strip is a block in which each row has one panel. See §13. grain_group.orientation— grain relative to the front (optional,"vertical"— the default — or"horizontal"). With vertical grain the rows are horizontal strips, row 1 is at the top, and positions are counted from the left edge; with horizontal grain the rows are columns, row 1 is on the left, and positions are counted from the bottom edge. This edge is the alignment edge — all rows are aligned to it. See §13.1.grain_group.members[].row— row number along the grain (optional, integer ≥ 1, rows consecutively 1…n).orderis now the position in the row (1…m in each row), counted from the alignment edge in the view of the face.- Validation rules §15.4: rows consecutively 1…n and positions in a row consecutively 1…m without repetitions (in place of the
ordersequence 1…n), the same dimension along the grain within a row, the block fits on the sheet along the grain (the sum of the rows with kerfs) and across it (the widest row with kerfs) — in place of the sum of the strip's panels. - Glossary: entries Grain relative to the front and Row in a grain group; updated Grain group, Order in a grain group (position in the row) and Kerf.
- Example
09-ciaglosc-sloja.meb— a block with vertical grain (the example with 500 and 750 fronts), a block with horizontal grain and a strip withoutrow.
Compatibility
- A backward-compatible change (MINOR) — only new optional fields. A member without
rowis a separate row: row number = itsorder, position = 1, so groups from 2.4.0 and older files keep exactly their meaning (a strip of panels, each in a separate row), and their validation gives the same result as before. An implementation reading 2.5.0 MUST accept members withoutrowin this meaning. A group withoutorientationhas vertical grain. - A 2.4.0 implementation ignores
rowandorientationin accordance with §1.3, so it will not read a group with rows: theorderpositions repeat between rows in it, which is an error under its rule §15.4 item 3. It reads files with groups withoutrowunchanged. production_id: the location of a panel in a group is now the row and the position (row+order) — unchanged in a group withoutrow.- Schema:
https://meb.org.pl/schema/2.5.0/meb.schema.json.
Clarified
- Sheet dimension along the grain (§15.4) — it is determined by the material grain (
material.grain), and the panel dimension along the grain bypanel.grain. The earlier wording “whenalong_length” did not say which field it referred to.
[2.4.0] — 2026-11-06
Added
- Polyhedron (
geometry.type: "polyhedron") — a solid made of planar polygonal faces. Vertices (vertices:id,x,y,z), edges (edges:id,start,end, optionallyfold— a fold edge) and faces (faces:id,loops— the outline, then the holes). A face is any polygon with holes, so a wall with a through window, a sloped ceiling and a room with a floor and walls in one solid are stored exactly, without triangles. Every element has anidthat the program keeps between edits — the solid returns from the file to the program without loss. A polyhedron may be open and consist of several pieces. See §7.6.2. - Validation rules §15.9 items 8–10 (edges, loops and planarity of the polyhedron's faces), uniqueness of the
idof polyhedron elements (§15.1) and references to its vertices (§15.2). - Glossary: entry Polyhedron; updated Solid geometry.
- Example
08-bryla-swobodna.meb— a wall with a through window and a floor without thickness in one polyhedron.
Compatibility
- A backward-compatible change (MINOR) — a new enum value
geometry.type: polyhedronand new geometry fields; all 2.3.0 files are valid in 2.4.0. An implementation that does not know the polyhedron skips a solid with such geometry in accordance with05-versioning.md§4. production_idunchanged: solids do not affect the production number.- Schema:
https://meb.org.pl/schema/2.4.0/meb.schema.json.
[2.3.0] — 2026-10-25
Added
- Solid (
type: "solid") — any geometry with a material. A new node type for everything that is not a cabinet: a wall, floor, ceiling, column, furniture massing, household appliance, decoration. Fieldsmaterial_refandgeometry; the node is a leaf and is grouped like any other. The standard does not distinguish kinds of solids — the name is a free label. A solid does not go to production. See §7.6. geometry— an outline with thickness or a mesh.type: extrusion: a closedoutline(apathobject from §10), optionalholesandthickness— the same geometry as a panel (a wall with a window, a sloped ceiling).type: mesh:mesh_reftomeshes_catalog. See §7.6.1 and §14.5.cabinet.solids[]— built-in appliances. The cabinet's solids (an oven, a sink) lie in its coordinate system and move together with it; the cabinet still contains no child nodes. See §7.4.meshes_catalog— triangle meshes (positions,triangles) embedded in the file and shared by solids and hardware. A.mebfile is complete: without references to external files and catalogs. See §11.7.material.furniture— furniture material (bool, defaulttrue). A production implementation skips panels with a non-furniture material (glass pane, mirror, sheet metal) — the panel stays in the file for the installer; a preview allows hiding, with one command, everything that has a non-furniture material. See §11.1.1.material.category: "surface"— appearance only (plaster, steel, glass, plastic) with acolorfield (#RRGGBB), without thickness and sheet; alwaysfurniture: false.- Hardware with a position.
hardware_instancegains optionalid,position,rotation,material_refandgeometry— a single piece in its place in the cabinet, withquantity: 1. The geometry is appearance only; the hardware item is still counted throughhardware_ref. Hardware without a position remains a list item with a quantity. See §12. - Hardware machining operations —
drilling.hardware_instance_ref,routing.hardware_instance_ref. A machining operation points to the positioned hardware item it results from — also in another cabinet; removing or moving the hardware item takes its machining operations with it. Fasteners (confirmat screw, cam lock, dowel) are described the same way. See §12.1. - Validation rules §15.9 (solids and hardware) and new items in §15.1–§15.3.
- Glossary: entries Solid, Solid geometry, Mesh catalog, Furniture material, Hardware machining operation; updated Hardware item and Hardware instance.
Compatibility
- A backward-compatible change (MINOR) — new optional fields and new enum values (
node.type: solid,material.category: surface); all 2.2.0 files are valid in 2.3.0, and a material without thefurniturefield remains a furniture material. An implementation that does not support solids skips thesolidnode in accordance with05-versioning.md§4 and ignores the new fields in accordance with §1.3. production_idunchanged: solids and the position and geometry of hardware do not affect the production number; a cabinet's hardware is compared byhardware_refand total quantity.- Schema:
https://meb.org.pl/schema/2.3.0/meb.schema.json.
Clarified
- Origin of the cabinet coordinate system (§14.2) — the bottom left front corner of the cabinet outline (outer). The earlier wording “inner corner” contradicted the standard's examples, in which the left side starts at
x = 0. Only the description changes; files and their meaning remain unchanged.
[2.2.0] — 2026-10-15
Added
panel.edge_finish— edge finish without edge banding. A new optional panel field with side keysxL/x0/yW/y0(likeedging). Each edge isnullor an object{ sanded, chamfer }:sanded— sanded edge,chamfer— the size of a 45° chamfer on both corners of the edge (at the face and at the back),0= no chamfer. Typical case: HPL compact boards — sanding + 1×1 mm chamfer. The field describes the appearance of the finished edge, not the machine, tool or process. No field = the file says nothing about the finish (the reader may apply its own default setting); an edge that isnullor omitted = no finish. See §8.5.1.routing.edge_finish(type: outline/hole) — finish of the cut walls{ walls, sanded, chamfer };wallsmeans the same asrouting.edging.walls("all"or base sides and/or segmentids). The field is not allowed inslot,pocketandbiscuit. See §9.3.2.- Validation rules §15.8: an edge does not have both
edgingandedge_finish; an outline wall does not appear in bothedging.wallsandedge_finish.walls;2 × chamfer < dimensions.thickness. - Glossary: entry “Edge finish” — distinguishes
edge_finishfrom surface finishes (finishes[]) and bevels (bevels[]).
Compatibility
- A backward-compatible change (MINOR) — only new optional fields; all 2.1.0 files are valid in 2.2.0. An implementation that does not support edge finish ignores the field in accordance with §1.3.
- Schema:
https://meb.org.pl/schema/2.2.0/meb.schema.json. Thewallsdefinition is now shared byrouting.edgingandrouting.edge_finish($defs/routing_walls) — without a change in meaning.
[2.1.0] — 2026-06-27
Added
routing.edgingin array form — per‑segment edge banding with different materials. Theedgingfield (type: outline/hole) now accepts — besides a single object{ ref, walls, pre_trim }— an array of such objects. Each entry bands its ownwallslist (base sides and/or segmentids) with its ownrefmaterial, which makes it possible to band different walls of one outline with different edge bands (e.g. each slanted segment with a different one). It delivers the return of edge banding on a milled outline announced in 2.0.0 (“contour operations”). The same wall MUST NOT appear in more than one entry.
Compatibility
- A backward-compatible change (MINOR). The object form (a single entry) remains valid and equivalent to a one-element array; all 2.0.0 files are valid in 2.1.0. Implementations reading
edgingMUST support both forms (object and array). - Schema:
https://meb.org.pl/schema/2.1.0/meb.schema.json.
[2.0.0] — 2026-06-24
Changed (breaking)
- Unified vertical L/W/T panel convention (right-handed).
panel.dimensionschanged from{w, h, d}to{length, width, thickness};materials_catalog[].sheetfrom{w, h}to{length, width}(trimunchanged). Canonical 2D view convention: length (length) vertical, width (width) horizontal, thickness (thickness) along the Z axis. Operation coordinates:xalong the length,yalong the width (increasing to the left); origin = bottom-right corner. The origin in the bottom-right corner makes the coordinate system right-handed and consistent with the 3D scene (three.js) — the 2D face view is no longer a mirror image of the 3D view. edge_sidenames anchored in the coordinate. The valuesleft/right/top/bottomare replaced byy0/yW/xL/x0:y0=y=0,yW=y=W(length edges),xL=x=L,x0=x=0(width edges). This applies to drillings, bevels, edge millings, biscuits, edge banding keys (edging),wallsand thefinish.surfacevalues (edge_xL/edge_x0/edge_yW/edge_y0). The names are independent of the view orientation. The local 3D frame remainslength → X, width → Y, thickness → Z(y0→Y−,yW→Y+,xL→X+,x0→X−) — theposition/rotationexamples in07-geometry-explained.mdhave no numerical changes.edging.sequenceas an edge pair. The field changed from an array of sides to the string"width_first"|"length_first"(default"width_first").width_first= widths first (xL/x0), then lengths (y0/yW);length_firstthe other way round. The pair banded later covers the corners. The model reflects the physical order on the edge bander (opposite edges banded in pairs) and is consistent with the rozkrojex model; an arbitrary order of individual sides is no longer representable.- Removed
pre_trimandafter_routing. The edge banding edge object (panel.edging.{side}andbevel.edging) now contains onlyref. The dimensions indimensionsare always final after edge banding (they include the edge banding); the standard does not describe a raw dimension — the reduction by the edge banding thickness is done by the edge bander.after_routing(edge banding on a milled outline) will return with the topic of contour operations. pocketwithout edge banding.routing.edging(edge banding on milled walls) now applies only tooutlineandhole. A pocket does not haveedging(norwall_profile— see “Routings rework” below).outline/hole: newrouting.edging.pre_trim. A flag (bool, defaultfalse) specifying whether the edge bander pre-mills the edge by the edge banding thickness before banding.pre_trim: trueis allowed only fortype: outlinewith a single straightmachinedsegment — the edge bander does not pre-mill a curved edge; forholealwaysfalse.outline:machinedsegment marker.outlineremains a closed outline (closed: true) describing the finished shape (winding = material side, CAD convention). The new, optional fieldsegments[].machined: truemarks a segment that is a real cut — the difference of the outline relative to the base rectangledimensions. When there is no explicit flag, machining is determined geometrically (a segment outside the rectangle boundary). It allows the postprocessor (XCS) andpre_trim/edgingto operate only on the actual cut, without processing the whole outline.- Edge drillings and biscuits: a dedicated
zaxis + a unifiedx/ysystem. Fortype: edge(androutingtype: biscuitin the edge variant) the depth of the hole/axis within the thickness is now in thezfield — measured from the face (face: top),z ∈ [0, thickness], defaultthickness/2— instead of being encoded in the “free” face-plane axis.xalways means the position along the length,yalong the width; no axis changes its meaning between edges any more. Base side: you give the axis running along the edge (y0/yW→x,xL/x0→y) +z, the perpendicular axis is implied byedge_side. See §9.2.1.
Added
- Drilling / biscuit in the edge of a through outline (
on_segment+s). An operation in a non-axis-aligned wall created by a through cut — a slanted/arc segment of the outline (outline) or a hole wall (hole) — addressed parametrically:on_segment(a reference to theidof anoutline/holesegment) +s(the distance along the segment from its start, arc length) +z([0, thickness]). Thex/yposition and the drilling direction are determined from the segment geometry and the material side (winding:outline— material inside,hole— outside). Inholeevery segment is a wall (themachinedflag does not apply).pocketis not supported (not through). Theon_segmentandedge_sidemodes are mutually exclusive. See §9.2.2. path.segments[].id(string, optional) — path segment identifier; required when the segment is the target ofon_segment; unique withinpath.drilling.z/routing(biscuit).z— depth of the edge axis from the face (defaultthickness/2).routing.edging.wallsaddresses segments byid. Thewallsarray can now contain — besides base sides (y0/yW/xL/x0) — path segmentids (segments[].id). It allows banding a single non-axis-aligned wall (e.g. a specific slantedoutlinesegment or a selectedholewall) that cannot be addressed by a base side."all"unchanged.
Clarified
- Profile coordinate system (
type: slot, section: profiled): one frame for slotsurface((0,0)on thepathaxis) andedge((0,0)at the cornerface ∩ edge_side/on_segment);Y=0= entry surface, the profile is open and anchored on it,Y+into the thickness (§11.5.2). - Glossary: removed the dead entries
path_reference(inner_edge/outer_edge) and the mention ofthrough: truein a pocket — fields removed in 1.1.0, absent from the 2.0.0 schema.
Routings rework — slot, profiles, on_segment
type: sweep→type: slot. A unified slot/extrusion primitive. Two orthogonal axes: placement (surfacewithpath/edgewithedge_sideoron_segment) and an explicitsectionfield (simple= awidth×depthrectangle + optionaloffset;profiled= a fullprofile_ref). Inprofiledthe profile defines the whole cut geometry (depth = the profile's reach into the material); nooffset— positioning is baked into the profile.profiles[].start(object{x, y}, optional, default{0, 0}) — the start point of the cross-section; allows positioning/centering the profile (e.g. a slot centered on thepathaxis withstart.x = −width/2).wall_profileremoved completely (outline, hole, pocket). Cut walls are straight by default; profiling/chamfering a through wall is done with a slot or a bevel viaon_segment. A profiled pocket wall (not through) = a separateslotplacement: surfacewithpathalong the edge.pocketsimplified to{ face, depth, path }(flat bottom, straight walls).on_segmentuniversal for edge operations —slotandbevelare added (besidesdrilling/biscuit/edging.walls).bevel.on_segmentis allowed only forlinesegments (a bevel = a straight cut); a curve is chamfered with a profiled slot.bevel:edge_sideXORon_segment, always the whole edge (withoutstart/end).- Segment
idunique within the panel (previously: withinpath) —on_segmentis a pure ref without specifying the path.
Migration 1.x → 2.0.0
- Change the keys
dimensions.w/h/d→length/width/thicknessandsheet.w/h→length/width— values unchanged. - Remove
edgingfromtype: pocketoperations (wall edge banding not supported); if a wall is to be banded, usetype: outline/hole. outlinewithout structural changes (still a closed outline); optionally mark real-cut segments with themachinedflag.holeunchanged.- Remap
edge_sideand theedging/walls/finish.surfacekeys to names anchored in the coordinate: edgey=0→y0,y=W→yW,x=L→xL,x=0→x0(likewiseedge_*infinish.surface). The panel origin is now bottom-right (y=0on the right) — the numerical values of the operation coordinates (x,y) remain unchanged; only the edge naming and the 2D view orientation change (the width increases to the left, no mirroring relative to 3D). - Edge drillings and biscuits: move the depth within the thickness from the face-plane axis to
z(from the face). For length edges (y0/yW) keepx(position along the length) and removey; for width edges (xL/x0) keepy(position along the width) and removex. Example:{edge_side:"xL", x:9, y:150}→{edge_side:"xL", y:150, z:9}. Omittedz=thickness/2. - Replace the
edging.sequencearray with a string: if the first listed edge was a width edge (xL/x0) →"width_first", if a length edge (y0/yW) →"length_first"; missing/empty field →"width_first". - Remove the
pre_trimandafter_routingfields from theedging.{side}andbevel.edgingobjects — thedimensionsvalues remain unchanged (they are already final). type: "sweep"→type: "slot"+ add the requiredsection:simple(when there waswidth+depth) orprofiled(when there wasprofile_ref). Edge sweepoffset(along the thickness): withprofiledbake it into the profile (start/geometry), withsimpleit stays asoffset.- Remove
wall_profilefromoutline/hole/pocket. If a wall had a profile: for through cuts model it with anon_segmentslot/bevel, for a pocket wall — with aplacement: surfaceslot along that edge. - Ensure the uniqueness of segment
ids within the whole panel (not only the path). - Schema:
https://meb.org.pl/schema/2.0.0/meb.schema.json.
[1.2.1] — 2026-06-15
Clarified
- Grain (
grain) hierarchy between material and panel.material.grainis the only source of the existence and the base direction of the grain;panel.grainis subordinate — it has meaning only whenmaterial.grain ≠ "none". The valuepanel.grain = "none"means that the panel does not respect the grain (rotation allowed, texture not drawn). Whenmaterial.grain ≠ "none"andpanel.grain ≠ "none", the panel respects the grain in thepanel.graindirection. The rotation rule (§15.5) remains unchanged. - The clarification does not change the file structure or the JSON Schema — all 1.2.0 files remain valid; only the interpretation of the dependency between the two fields changes (previously left unstated).
Fixed
- Viewer (2D and 3D): the grain texture is now drawn only when
material.grain ≠ "none"andpanel.grain ≠ "none", in thepanel.graindirection. Removed the earlier fallbackpanel.grain || material.grain, which showed the texture also for a material without grain.
[1.2.0] — 2026-05-22
Added
project.has_3d(boolean, optional) — a flag indicating whether the file contains 3D position data of panels and scene nodes. Whenfalse, implementations MUST NOT attempt to render a 3D preview and SHOULD display an appropriate message. When the field is absent, an implementation SHOULD treat it astrue(backward compatibility with 1.1.0 and older files).
Changed
node.positionandnode.rotation— changed from required to optional. When absent, the node is spatially undefined; theproject.has_3d = falseflag should signal this at the level of the whole project.panel.positionandpanel.rotation— changed from required to optional. Production data (dimensions, material, edge banding, drillings) remain complete without these fields.
[1.1.0] — 2026-05-16
Changed
- Milling typology extended with two new geometric types:
outlineandhole, which replace the oldpocketwiththrough: true. type: "outline"— through milling changing the outer outline of a rectangular panel; the path touches the boundary of thedimensionsrectangle; noface,depth,throughfields.type: "hole"— through milling inside the panel (a closed cut-out); the path lies entirely inside the rectangle; noface,depth,throughfields.type: "pocket"— only a non-through recess to the depthdepth;facestill required; the semantics do not depend on whether the path touches the boundary.- Removed the
path_referencefield (inner_edge/outer_edge) — it was a CAM domain concept, inadequate for a geometric description of milling. - Removed the
throughfield frompocket— the operation type encodes this information directly. - Viewer 2D:
faceContourPathdetermined fromtype: outline;throughPocketCutoutsdetermined fromtype: hole;contourEdgeSpansfilteroutline. - Viewer 3D:
panelContourRoutinglooks fortype: outline;throughPocketRoutingslooks fortype: hole.
Removed
type: "pocket"withthrough: true— replaced bytype: "outline"(when it touches the boundary) ortype: "hole"(when inside).- The
path_referencefield — removed completely from the standard. - The
throughfield on routing — removed completely.
[1.0.0] — 2026-05-16
The first stable version of the standard.
Changed
- The milling model redesigned to a geometric approach — the standard describes the resulting cut geometry, not the tool or CAM parameters.
- Routing types changed from
contour/pocket/edgeto three geometric primitives:sweep/pocket/biscuit. type: sweepreplaces bothtype: edge(sweep along an edge) and axis operations on the face (sweep over the surface); it always requiresprofile_refor the pairwidth+depth.type: pocketkeeps the semantics of a pocket with a closed outline; it also covers the formertype: contour(through pocket = outline cut-out); removedpath_reference: axis.path_referencefor pockets limited to"inner_edge"|"outer_edge"(removed"axis").- Profile coordinate system unified: zero point
(0, 0)= theface ∩ edge_sidecorner;X+= into the material from the edge,Y+= into the thickness from the face.
Removed
type: contour— replaced bytype: pocketwiththrough: true.type: edge— replaced bytype: sweepwith theedge_sidefield.edge_profilesin the routing operation — the outline edge profile was a special case of sweep; replaced by sweep along an edge.path_reference: axis— axis operations are nowtype: sweepwithwidth+depth.depthandtilt_anglefrom edge routings (formertype: edge) — the geometry is fully defined byprofile_ref.
Added
type: sweep— an extrusion primitive; supports slots on the face (sweep/surface withpath) and slots/profiles on the edge (sweep/edge withedge_side).type: biscuit— a point primitive for biscuit (lamella) joints; requires a reference tobiscuit_catalog.- The
wall_profilefield intype: pocket— an optional profile of the pocket wall/bottom. - The
offsetfield in sweep along an edge — the offset of the profile zero point from the corner along the thickness. - The
widthfield in routing — the slot width for a rectangular sweep (without a profile). biscuit_catalogin the file root — an optional biscuit catalog with the fieldsid,name,code,length,width,thickness.- The
x,yposition fortype: biscuitmeans the biscuit axis;thicknessis distributed symmetrically on both sides of the axis. - A biscuit in the edge is described by
edge_side; a biscuit in the face byface.