\n\n\n\n\n[](https://github.com/dwyl/esta/issues)\n\n
\n\nThis package allows you to create a complex grid and distort it, taking the concept of a [Coons patch](https://en.wikipedia.org/wiki/Coons_patch) and applying it to a grid system, meaning the grid is not bounded by four straight lines, but by four cubic Bézier curves. This allows you to create some very strange and interesting grids that would be very difficult to generate with traditional graphics software.\n\nThere is an [editor](https://warp-grid.undistraction.com) which allows you to generate and manipulate a grid, giving access to all the configuration available.\n\nThe package provides a set of powerful configuration options to define the grid including variable- or fixed-width/height columns and gutters, control over distribution of rows and columns using Bézier easing, and access to different types of interpolation, as well as the option to provide your own interpolation.\n\nIts API gives you access to information about the grid's metrics: its bounds, rows, columns, gutters and cells. It is designed to be recursive, so that the metrics for an individual grid-cell can be used as bounds for a completely different grid, allowing for nested grids.\n\nThis package does not handle any rendering itself, but provides you with all the information about the grid that you need to render the grid using SVG, Canvas or anything else you like.\n\nIf you just want to generate a coons-patch, you can use the lower level package [coons-patch](https://github.com/Undistraction/coons-patch).\n\n## Install package\n\n```bash\npnpm add warp-grid\n# or\nnpm add warp-grid\n# or\nyarn add warp-grid\n```\n\n[Package Documentation](http://warp-grid-docs.undistraction.com/) (TypeDoc generated).\n\nThis package is written in TypeScript and exports its types.\n\n## Quick-start\n\nThe basic workflow is that you supply bounds representing the edges of boundaries of your grid, and a grid configuration object describing the grid you'd like to map onto those bounds. In return you receive an object with information about the grid, and an API to allow you to get information about the grid. This means no expensive calculations are done up front, and calculations are only performed as and when you need them.\n\n```typeScript\nimport { warpGrid } from 'warp-grid'\n\n// Define bounding (cubic Bézier) curves for the patch\nconst boundingCurves = {\n top: {\n startPoint: { x: 0, y: 0 },\n endPoint: { x: 100, y: 0 },\n controlPoint1: { x: 10, y: -10 },\n controlPoint2: { x: 90, y: -10 },\n },\n bottom: {\n startPoint: { x: 0, y: 100 },\n endPoint: { x: 100, y: 100 },\n controlPoint1: { x: -10, y: 110 },\n controlPoint2: { x: 110, y: 110 },\n },\n left: {\n startPoint: { x: 0, y: 0 },\n endPoint: { x: 0, y: 100 },\n controlPoint1: { x: -10, y: -10 },\n controlPoint2: { x: -10, y: 110 },\n },\n right: {\n startPoint: { x: 100, y: 0 },\n endPoint: { x: 100, y: 100 },\n controlPoint1: { x: 110, y: -10 },\n controlPoint2: { x: 110, y: 110 },\n },\n}\n\n// Define a 10 x 5 grid with gutters\nconst gridDefinition = {\n columns: 10,\n rows: 5,\n gutter: 2\n}\n\nconst grid = warpGrid(\n boundingCurves,\n gridDefinition\n)\n\n// Get a point on the patch at the provided horizontal and vertical ratios (0–1 inclusive)\nconst point = grid.getPoint({ u: 0.5, v: 0.75 })\n\n// Get an Array containing all the curves along the x-axis.\nconst curvesXAxis = grid.getLinesXAxis()\n\n// Get an Array containing all the curves along the y-axis.\nconst curvesYAxis = grid.getLinesYAxis()\n\n// Get an Array containing all the curves along the both the x- and y-axis.\nconst curves = grid.getLines()\n\n// Get an array of points representing every point on the grid where lines intersect.\nconst intersections = grid.getIntersections()\n\n// Get the bounds for the grid-square at the supplied coordinates (columnIdx, rowIdx)\nconst bounds = grid.getCellBounds(3, 2)\n\n// Get an array containing the bounds for every grid-square\nconst allBounds = grid.getAllCellBounds()\n```\n\n## Usage\n\n### Primitives\n\nThere are a number of data types that are used by the package to describe aspects of the grid:\n\nPoints look like this:\n\n```typeScript\nconst point = {\n x: 34,\n y: 44\n}\n```\n\nAll curves are represented by cubic Bézier curves:\n\n```typeScript\nconst curve = {\n startPoint: {\n x: 0,\n y: 0\n },\n controlPoint1: {\n x: 0,\n y: 33\n },\n controlPoint2: {\n x: 0,\n y: 66\n },\n endPoint: {\n x: 0,\n y: 100\n }\n}\n```\n\nBounding curves look like this, where each item is curve.\n\n```typeScript\nconst boundingCurves = {\n top: { … },\n bottom: { … },\n left: { … },\n right: { … }\n}\n```\n\n### Bounding curves\n\nTo generate a grid you must provide a set of four **bounding curves** (`top`, `left`, `bottom` and `right`) in the form of four cubic Bézier curves. A cubic Bézier curve describes a straight-line or curve using a start point (`startPoint`), an end point (`endPoint`) and two other control points(`controlPoint1` and `controlPoint2`). Each point has an `x` and `y` coordinate.\n\nAt minimum you must supply start and end points for each curve. If you do not supply `controlPoint1` it will be set to the same coordinates as the start point, and if you do not supply `controlPoint2` it will be set to the same coordinates as the end point. Setting both control points to the same values as the start and end point will result in a straight line. You also need to ensure that the four curves meet at the corners.\n\nYou will probably be expecting the end of each curve to be the start of the next, however in keeping with the math involved in generating a coons-patch this is not the case. The `top` and `bottom` curves run left to right, and `left` and `right` curves run top to bottom, so this means that:\n\n- the `startPoint` of the `top` curve must share the same coordinates with the `startPoint` of the `left` curve.\n- the `endPoint` of the `top` curve must share the same coordinates with the `startPoint` of the `right` curve.\n- the `startPoint` of the `bottom` curve must share the same coordinates with the end point of the `left` curve.\n- the `endPoint` of the `bottom` curve must share the same coordinates with the `endPoint` of the `right` curve.\n\n```\n top\n -------->\nleft | | right\n ↓ ------> ↓\n bottom\n```\n\nNote that when you are getting cell bounds back from the API, both `getCellBounds` and `getAllCellBounds` accept a config object which has a `makeBoundsCurvesSequential` key. If this is set to true, the order of the bounding curves is made sequential:\n\n```\n top\n ↑ ------->\nleft | | right\n <------- ↓\n bottom\n```\n\n## Grid definition\n\nThe grid definition is an object describing the grid you are modelling. It will be merged with a set of defaults.\n\nBefore going any further it is important to understand how the grid handles columns, rows and gutters. Individual step values can either be numbers, in which case the values are treated as relative values to each other, or absolute values (in the form of pixel-strings with the format '{number}px', for example '48px'). The grid calculations will favour gutters, rows and columns with absolute values, with steps and gutters with relative values sharing the remaining available space. It is important to remember that the length of each side of the grid is independent. The grid will first calculate the length of each side, allow space for all the steps and gutters with absolute values, then share out the remaining space amongst the other steps and gutters. This allows for some pretty interesting layouts.\n\nUnder the hood, gutters are just steps with `isGutter` set to `true`. By using objects for step values you can control individual gutter sizes (see below),\n\n### Columns and Rows\n\n`columns` and `rows` define the number of columns and rows in the grid. A grid has a minimum of one row and one column. The generic name for columns and rows used in the following docs and in the codebase is _steps_.\n\nThese fields can be one of the following:\n\n1. **An integer**, in which case that integer will represent the number of columns or rows. For example `columns: 2`, will result in a grid with two columns.\n\n2. **An array of integers or pixel strings or objects**, in which case the steps will each have those absolute or relative value, or if objects will have the absolute or relative value provided by the object's `value` property. To tell the grid to treat an item as a gutter, set `isGutter` to `true`. You can mix integers, string and objects.\n\n```typeScript\n{\n columns: [\n 2,\n `30px`,\n 1\n ],\n rows: [\n 1,\n `10px`,\n {\n value: 2,\n isGutter: true,\n },\n 5,\n 5\n ],\n …\n}\n```\n\n### Gutters\n\n`gutter` describes the width of horizontal gutters and the height of vertical gutters. Gutters are the spaces between the grid cells. If `gutter` is a number, it describes both horizontal and vertical gutters. If it is an array of two numbers, the first number describes the horizontal gutter and the second number describes the vertical gutter. Like columns and rows, gutters can either be relative or absolute pixel-numbers, for example: `3`, or `3px`.\n\nAs outlined above, there is an additional way to add gutters without using the gutters property. You can add them to the `rows` or `columns` arrays, using an object with a `value` property, but also adding an `isGutter` property set to `true`: (`{ value: 2, isGutter: true}`). This allows you to define gutters of different widths/heights in the same way you can define columns or rows of different widths/heights.\n\n```typeScript\n{\n gutter: [\n 2,\n `10px`\n ],\n …\n}\n```\n\nYou can add multiple steps with `isGutter` set to `true`, and you can have these beside one-another if you want. If you use steps with `isGutter` set to `true` alongside the `gutter` property, the `gutter` property will act as a default, and gutters of that value will be added between any steps that do not already have at least one gutter between them. They will have no effect on steps with `isGutter` set to `true`.\n\n### Interpolations\n\nA lot of the work done by the package involves interpolation. The grid also supports configuration params that change how it performs these interpolations.\n\n#### interpolationStrategy\n\n`interpolationStrategy` changes the algorithm used to interpolate the position of points along a curve. These algorithms are used in calculating the location of points within the bounds. This value can be either a string, a function, or a tuple of two functions.\n\nIf it's a string it can be either `even` (the default) or `linear`. `linear` is a simple form of interpolation that results in a distribution that is affected by the amount of curvature of the bounds. `even` uses a more complex approach and usually results in more evenly distributed results. However this comes at the cost of performance.\n\nAlternatively a single factory function, or a tuple of two factory functions (one for each axis) can be supplied.\n\n```typeScript\n{\n interpolationStrategy: `even`,\n …\n}\n```\n\nThese functions comprise of a factory function that accepts a configuration object and returns an interpolation function. The factory function is called internally using config from the grid definition object.\n\nFactory functions for both linear and even interpolation are exported by this package:\n\n- `interpolatePointOnCurveEvenlySpacedFactory`\n- `interpolatePointOnCurveLinearFactory`\n\nIf you use your own interpolation factory function it should have the following signature.\n\n```typeScript\n(config: {precision: number, bezierEasing: BézierEasing}) => (t: number, curve: Curve): Point\n```\n\n##### Factory\n\n- `config` is an object with a `precision` key that can be used to control the precision of interpolation, and `bezierEasing` which is an object with bezierEasing values for modifying distribution for each axis. If your interpolation function doesn't require any configuration you can just use an empty function.\n\n##### Interpolation function\n\n- `t` is the ratio along the axis (0–1 inclusive).\n- `curve` is a cubic Bézier curve along which the interpolation will be used.\n\n#### lineStrategy\n\n`lineStrategy` controls how the grid lines are interpolated and can either be `straightLines` or `curves`. The lines returned from `getLines`, `getLinesXAxis` and `getLinesYAxis`, and the bounds returned from `getCellBounds` and `getAllCellBounds` are always represented by cubic Bézier curves, however if the `lineStrategy` is `straightLines` (the default), the calculations are significantly simplified and all lines will be straight (`controlPoint1` will be the same as the `startPoint`, and `controlPoint2` will be the same as `endPoint`) For more accurate calculations choose `curves` which will draw curved cubic Bézier curves at the expense of performance.\n\n```typeScript\n{\n lineStrategy: `curves`,\n …\n}\n\n```\n\n#### precision\n\nIf you choose to use an interpolation strategy of `even`, this parameter controls how precise the interpolation is. Higher values are more memory-intensive but more accurate. The default value is `20`. With `linear` this will have no effect.\n\n```typeScript\n{\n precision: 5\n …\n}\n```\n\n### bezierEasing\n\nThe grid provides a very powerful way of controlling the distribution of lines along each access using bezierEasing. Bézier easing is widely used for animation as a way of providing easing to a changing value. Instead of applying easing to an animation, here it is applied to the interpolation of points along an axis. `bezierEasing` is implemented internally by first creating an easing function, and then passing a value (in the range of 0–1) to it. The easing function requires four values (each from 0–1). The first two values represent the position of the first control point (x, y) and the last two values represent the position of the second control point. So the value for `bezierEasing` will look like this:\n\n```typeScript\n{\n bezierEasing: {\n xAxis: [0, 0, 1, 1],\n yAxis: [0, 0, 1, 1],\n }\n …\n}\n\n```\n\nThe easiest way to understand what effect the different values have is to play with the [editor](https://warp-grid.undistraction.com).\n\nHere is a full example of a grid definition:\n\n```typeScript\n{\n columns: 8,\n rows: [10, 5, 20, 5, 10],\n gutter: [5, 3],\n interpolationStrategy: `even`,\n lineStrategy: 'curves',\n precision: 30,\n bezierEasing: {\n xAxis: [0, 0.5, 1, 1],\n yAxis: [0, 0, 0.3, 1],\n }\n}\n```\n\n## Return value\n\nThe return value is a `warp grid` object representing the grid and providing an API to interrogate it.\n\n```typeScript\n{\n model: {\n columns,\n rows,\n columnsNonGutter,\n rowsNonGutter,\n boundingCurves\n },\n getPoint,\n getLinesXAxis,\n getLinesYAxis,\n getLines,\n getIntersections,\n getCellBounds,\n getAllCellBounds,\n}\n```\n\n### Model object\n\n`model` provides access to the resolved configuration data that was used to generate the patch. The configuration data is not the same as the data you passed in, but is instead the internal representation of that data.\n\n- `columns` contains an array of column values. This will always be made up of objects, regardless of how you supplied them.\n- `rows` contains an array of row values. This will always be made up of objects, regardless of how you supplied them.\n- `boundingCurves` contains the bounding curves object that was passed in.\n\n### API\n\n#### Important note\n\nOne of the powerful features of this package is that a grid cell can itself be used as bounds for another grid. To achieve this, the bounding curves returned from `getCellBounds` and `getAllCellBounds` follow the same pattern as the bounding curves used to define the grid, meaning the top and bottom curves run left-to-right and the left and right curves run top-to-bottom.\n\n- `getPoint({ u, v })` returns the point on the grid at the supplied `u` and `v` ratios. Both `u` and `v` should be a number from `0–1` inclusive. For example, a `u` of `0` and a `v` of `0` would return a point in the top left corner. A `u` of `1` and a `v` of `1` would return a point in the bottom right corner (remember that the top and bottom boundary curves run from left-to-right and the left and right boundary curves run from top to bottom).\n\n- `getLinesXAxis()` returns an array representing all the curves for each step along the x-axis. This includes curves for all left and right edges.\n\n- `getLinesYAxis()` returns an array representing all the curves for each step along the y-axis. This includes curves for all top and bottom edges.\n\n- `getLines()` returns an object with `xAxis` and `yAxis` keys, each of which contains an array representing all the curves for each step along that axis.\n\n- `getIntersections()` returns an array of points, one for every point at which an x-axis line intersects with a y-axis line.\n\n- `getCellBounds(columnIdx, rowIdx)` returns a set of bounding curves for the cell at the supplied column and row. Column and row are zero-based. You can pass an optional config object as the third argument. See the docs for more information.\n\n- `getAllCellBounds()` returns an array of bounding curves for all the cells in the grid. See the docs for additional config parameters. You can pass an optional config object as the third argument. See the docs for more information.\n\n## Dependencies\n\nThis project has five dependencies:\n\n- [coons-patch](https://www.npmjs.com/package/coons-patch) to calculate points on a surface defined by Bézier curves.\n- [bezier-js](https://www.npmjs.com/package/bezier-js) for Bézier curve math.\n- [fast-memoize](https://www.npmjs.com/package/fast-memoize) for memoization.\n- [bezier-easing](https://www.npmjs.com/package/bezier-easing) for creating Bézier-easing functions.\n- [ml-matrix](https://www.npmjs.com/package/ml-matrix) for matrix math\n\n## Thanks\n\nThanks to pomax for his help (and code) for curve fitting (which is much more complex than it might seem). His [A Primer on Bézier Curves](https://pomax.github.io/bezierinfo/) is a thing of wonder.\n\n## Maintenance\n\n### Install\n\n```bash\npnpm install\n```\n\n### Build\n\n```bash\npnpm run build # Build once\npnpm run build-watch # Build and watch for changes\n```\n\n### Preview build\n\n```bash\npnpm run preview\n```\n\n### Generate docs\n\n```bash\npnpm run docs\n```\n\n### View the generated docs\n\n```bash\npnpm run docs-view\n```\n\n### Run unit tests\n\nUnit tests use vitest. Note that some of the tests are written in JS instead of TS. Those tests are related to validation of types at runtime. Any validations that validate things that cannot be caught by TS are written in TS.\n\n```bash\npnpm run test # Run tests once\npnpm run test-watch # Run tests and watch for changes\npnpm run test-coverage # Run tests and output a coverage report\npnpm run test-snapshot # Regenerate snapshots\n```\n\n### Lint\n\n```bash\npnpm run lint-prettier\npnpm run lint-eslint\n```\n\n### Linking\n\nTo link into the local version of `coons-patch` for local testing run:\n\n```\npnpm run link\n```\n\nTo unlink (and install the package from npm):\n\n```\npnpm run unlink\n```\n\n### Release\n\nReleases are via semantic-release and executed on CI via Github actions.\n\nThe following steps are run as part of the actions pipeline\n\n- Code is linted\n- Unit tests are run\n- TypeScript is compiled to JavaScript\n- Package is released (if previous stages all pass)\n","readmeFilename":"README.md"}