<Mark> is a simple component that instantiates different SVG elements depending on the markType but also other attributes sent. So, for example, a markType of rect will usually result in an SVG rectangle but if you set renderMode="sketchy" it will return two SVG paths. All display elements are wrapped in a <g> and Mark does have a limited drag-and-drop context. This will probably eventually be its own library in the future. You would pass a Mark any of the native SVG properties you would expect of the markType you intend to render, and Mark will adjust those if the final product is not an element that supports it (such as "r" when the actual rendered element is a path). By default Marks will try to make an animated transition from one state to another, using flubber.js if they are SVG paths in their initial and end state.

import { Mark } from 'semiotic-mark';

<Mark
   markType="circle"
   renderMode="painty"
   r={5}
   cx={150}
   cy={150}
   style={{ fill: "red" }}
/>

A required property that sets the SVG equivalent element that this mark will represent, which accepts all SVG standard elements except ellipse and polygon as well as pseudo markTypes like horizontalBar and verticalBar which are easier to place that top-left rects that are drawn down.

<Mark markType="rect" ... />

If set to true, then forceUpdate will cause an element to change to any new state without a transition. This is useful in cases where there is no decent way to transition or to skip animated transitions for performance purposes.

<Mark forceUpdate={true} ... />

Marks currently ship with two kinds of renderMode, sketchy and painty. If set to sketchy you'll get a jittered outline and a fill made of individual lines, which doesn't work great for very complex shapes. If set to painty you'll get a gooey, painty sort of fill that uses SVG filters. Marks with either of these modes will not experience automatic transitions.

<Mark renderMode="sketchy" ... />

Only has effect if the mark is instantiated inside a <MarkContext /> which decorates Marks with a rudimentary ui state that is automatically updated and checked as you drag and drop Marks.

If set to true, you can click on this mark and move it around visually. It will stay in its new visual position unless resetAfter is set to true.

<Mark draggable={true} ... />

Setting dropFunction enables a simple drag-and-drop context that tracks the Mark you're dragging and the cursor position. If the cursor is over another Mark, it will fire the dropFunction with {source, target} passed.

<Mark dropFunction={d => {mergeThesePieces(d)}}} ... />

If resetAfter is set to true, then the Mark will snap back to its original position after dragging. This is useful for when you want to use drag-and-drop to combine elements, rather than visual repositioning.

<Mark resetAfter={true} ... />

If freezeX is set to true, then the Mark will only drag along the y-axis.

<Mark freezeX={true} ... />

If freezeY is set to true, then the Mark will only drag along the x-axis.

<Mark freezeY={true} ... />

An object passed to Marks, typically via <MarkContext /> that keeps track of ui context for interactivity.

A function passed to Marks, typically via <MarkContext /> that changes the values in the sent context object.