@sakuzu/maplibre-gl-draw-ui 1.0.0 → 1.2.0

package/CHANGELOG.md

@@ -7,6 +7,194 @@ follows semantic versioning.
 
 ## [Unreleased]
 
+## [1.2.0] - 2026-10-02
+
+The narrow screen and the stage, from the visual review: the map's
+padding and its controls follow the panes kata's Shell reports, the
+actions card stands above the attribution and fits the map, the
+inspector takes the width of its sheet and keeps its tabs in the head,
+Delete has one place, maplibre-gl's controls follow the theme, and every
+dataset is dragged among the layers. It reads kata 1.6.0.
+
+### Added in 1.2.0
+
+- maplibre-gl's controls in the map's container, those of the
+  application too, follow the theme of `createDrawUI` (#10). The control
+  container (`.maplibregl-control-container`) has `data-mgd-ui-controls`,
+  to which the build moves kata's tokens as it does to `.mgd-ui`, and
+  the `data-color-mode` of the root, following `setTheme` and the
+  system; `destroy()` removes both. The groups of buttons, the lines
+  between them, the attribution and the scale are painted with the
+  tokens, and maplibre-gl's icons are inverted in the dark look.
+
+### Changed in 1.2.0
+
+- Every dataset is dragged among the layers in the layer panel (#6). A
+  dataset of `above-store` or `below-store` dropped among the layers is
+  moved to `layer-order` (`datasets.move`) and placed with
+  `layers.reorder`; when the reorder is refused, it goes back to its
+  own order. `LayerPanelDraw` needs `datasets.move`.
+- The map's padding follows the inset of kata's Shell (`onlayout`)
+  (#8): at the left, the room the left pane takes, beside the map or
+  floating over it with its gap; at the bottom, the height of the
+  sheets. The right pane, which opens with the selection, and the
+  toolbar are no longer padding, so the view does not jump on a
+  selection.
+- The controls of the bottom right of the map (not the attribution)
+  move to the left of the right pane, gap-md apart, while they would be
+  under it, and the bottom left corner (the scale) rises above the
+  attribution's box where that box reaches it across, as the two-line
+  attribution of a narrow map does (#8). The attribution is only read;
+  its compact form stays maplibre-gl's own.
+- The actions card stands above the higher of the scale and the
+  attribution's box where that box reaches the card across (#7). Its
+  height is capped to the map above its place, less gap-md at the top
+  and the button that opens the layer panel again while it shows, and
+  the whole card scrolls.
+- In a sheet, on a narrow map, the inspector takes the width of the
+  sheet instead of the width of a panel (#9). The inspector of a feature
+  passes its tabs to kata's InspectorFrame, so they stay in the head
+  while the content scrolls; its measurements are under the head, and
+  its description starts the content of each tab.
+- Delete is in the lead of the foot for several features, layers or
+  groups, as for one feature, instead of among the operations (#11).
+- kata 1.6.0: the Footer of an inspector stacks only when its row does
+  not fit, a sheet's half stage is the content's height, a narrow map
+  opens one side sheet at a time, and the actions of a row of the layer
+  panel that show on hover take no room until the row is hovered.
+
+## [1.1.0] - 2026-10-01
+
+The basemaps as the back of the stack in the layer panel, the datasets
+as rows of the stack, a limit on the features the panel lists, the
+snapping settings on the magnet, the actions of the application in a
+card, the inspector on the first tab of its options, and the layer panel
+without a pencil, in-place renaming and row counts. The word
+`activeLayer` leaves the `Messages` type (a locale that still sets it is
+ignored at runtime).
+
+### Added in 1.1.0
+
+- The datasets are rows of the layer panel, in their place in
+  the stack: those of `above-store` in front of every layer, those of
+  `layer-order` where `layers.getOrder()` places them among the layers,
+  and those of `below-store` behind every layer. A row shows the ID of
+  the dataset with a database mark, and the eye shows and hides it with
+  `setVisible`. It has no lock, and a press
+  on it leaves the selection as it is. A
+  `layer-order` dataset is dragged among the layers (`layers.reorder`
+  with its ID); the others stay. The rows follow `dataset.added`,
+  `dataset.removed`, `dataset.reordered` and the `changed` event of each
+  dataset. The option `datasets: false` (`LayerPanelOptions`) leaves
+  them out. New word: `datasets`.
+- The basemaps of the layer panel, `basemaps` (`{ id, label,
+  style, preview }`), `basemap` and `onbasemap`, in the options of
+  `createDrawUI` and of `createLayerPanel` (`LayerPanelOptions`). With
+  two or more, the basemap row opens them on the right, in the place of
+  the inspector: a list of their labels, each with its `preview` (a
+  value of CSS `background`; a neutral square without one) and a check
+  on the current one. Opening it clears the selection; a selection made
+  on the map or in the tree, its close button and Escape close it.
+  Choosing one replaces the map's style, calls `onbasemap` and leaves
+  the list open; `basemap` names the current one at the start, and
+  `ui.setBasemap(id)` and `ui.getBasemap()` change and read it. The
+  drawing is drawn again on top of the new style. The layer panel put
+  alone opens the list in the place of its sections.
+- The legend lists the style rules of the datasets as well as
+  those of the layers, in the order of the stack: a block for each
+  dataset with a rule (`Dataset.getStyleRule()` of core), titled with
+  its ID, with the rows `deriveLegend` gives and swatches shaped after
+  the types of its first rows. It follows `dataset.added`,
+  `dataset.removed`, `dataset.reordered` and the `changed` event of each
+  dataset (the reasons `style` and `rows`). The word `noLegend` now says
+  that no layer or dataset has a style rule. It needs core with
+  `Dataset.getStyleRule()`.
+- The actions of the application, rows of a card at the bottom
+  left of the map, above maplibre-gl's scale: `ui.actions` (`add`,
+  `remove`, `list`, `refresh`) and the options `actions` and
+  `actionsTitle` of `createDrawUI`. An action (`ActionSpec`) is a switch
+  (`kind: 'toggle'`), which shows what `checked` returns, or a button
+  (`kind: 'action'`), and its `shortcut` is a key of the interface,
+  listed with `?` under the title of the card. `run` is called by a
+  press and by the key; `checked` and `disabled` are read again after
+  each run and on `refresh()`, and `hint` is a caption under the row. A
+  key the interface or another action uses is refused with an error, and
+  `tools.add` refuses the key of an action. The card folds into one
+  button from its head, starts folded on a map narrower than 48rem, and
+  stands above the toolbar where it would reach it across; the layer
+  panel floating at the left ends above it. New word: `actions`.
+  `actionsOpen: false` starts the card folded.
+
+### Changed in 1.1.0
+
+- The layer panel lists up to 1,000 features in a layer, those
+  of its groups included. A layer that holds more lists none of them and
+  none of its groups: its one child is a row with their number and a
+  hint, "12,345 features. Select them on the map.", which is not
+  pressed, hidden, locked or dragged. The row of the layer works as
+  before. Each row of the panel costs about a third of a millisecond to
+  draw, so a layer of 20,000 features took seconds. `features`
+  (`LayerPanelOptions`) is now `boolean | number`: `true` (the default)
+  for the limit of 1,000, a number for another limit, `false` for no
+  features; a number less than 0 throws. New word: `manyFeatures` (with
+  `{count}`).
+- The layer panel is a stack of two sections, as in the
+  reference layout. The first, Stack (the new word `stack`), is the
+  tree with the add menu in its head; the second, Basemap, holds one
+  row with a globe mark and the name of the basemap the map shows: the
+  label of the current one of `basemaps`, else the `name` of the map's
+  style, else the word `basemap`. The panel lists the stack from the
+  front, and the basemap is its back. The row is not a node of the tree:
+  it is not dragged, hidden, locked or selected. Before the release, the
+  menu of the basemaps was a button at the top right of the map, beside
+  the theme button, and then a menu under the tree; both are gone.
+- The inspector of a feature opens on the first tab of
+  `inspector.tabs`, so `['attributes', 'style']` opens on Attributes.
+  The default stays `['style', 'attributes']`, which opens on Style. Once
+  a tab is chosen, it is kept from one feature to the next as before.
+- The magnet of the toolbar opens the snapping settings above
+  the toolbar instead of switching snapping: snapping, the kinds of
+  target under it (vertices, edges, intersections and guides, off while
+  snapping is off), snapping to datasets, tracing edges and moving shared
+  vertices together, and the key that pauses snapping. Each switch writes
+  `draw.options.update` and follows `options.changed`. The magnet stays
+  pressed while snapping is on. New words: `snapVertex`, `snapEdge`,
+  `snapIntersection`, `snapGuide`, `snapDatasets`, `traceEdges`,
+  `sharedVertexDrag` and `snapPauseKey` (with `{key}`).
+
+### Removed in 1.1.0
+
+- Renaming in place in the layer panel (F2 or a double click on
+  a row), as in the reference layout. The names of layers, groups and
+  features are changed in the head of the inspector, which also ends a
+  defect: a locked row could still be renamed in the tree.
+- The pencil that marked the active layer (the layer drawn
+  features go into) in the layer panel, as in the reference layout: the
+  row of a layer looks the same whether it is active or not. Pressing a
+  layer still makes it active (`layers.setActive`). The word
+  `activeLayer` is gone with it; at run time a locale that still gives
+  it is accepted and the word is ignored.
+
+### Fixed in 1.1.0
+
+- In the inspector of a feature, what a tab shows first is spaced
+  from the line of the tabs as the content of a panel is from its head
+  (pad-md to the first field, pad-lg to a section title). The panel of
+  the tab is now a Stack of its own under the tabs, so kata's spacing of
+  a first group applies; before, the title of the first section touched
+  the line.
+- The fields of the style have no "Style" title any more: they
+  sit straight under the Style tab, and the sections of the application
+  and Operations keep their titles. The reset of the style, which was an
+  icon button in that title, is a "Reset the style" text action after
+  the fields. In the same way, the shared fields of a selection, the
+  fields of a group and the fields of a layer have no title repeating
+  what the head says; the style rule of a layer keeps its title.
+- The page without a bundler in the README names
+  `@sakuzu/maplibre-gl-draw/geometry` in its import map, which the
+  single-file build imports. The README also shows the package from
+  React and from Vue, and a page that loads it from a CDN.
+
 ## [1.0.0] - 2026-10-01
 
 The first release of the standard user interface of