@itwin/editor-frontend 4.0.0-dev.90 → 4.0.0-dev.92

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@itwin/editor-frontend",
-  "version": "4.0.0-dev.90",
+  "version": "4.0.0-dev.92",
   "description": "iTwin.js frontend components",
   "main": "lib/cjs/editor-frontend.js",
   "module": "lib/esm/editor-frontend.js",
@@ -23,36 +23,36 @@
     "url": "http://www.bentley.com"
   },
   "peerDependencies": {
-    "@itwin/appui-abstract": "^4.0.0-dev.90",
-    "@itwin/core-bentley": "^4.0.0-dev.90",
-    "@itwin/core-common": "^4.0.0-dev.90",
-    "@itwin/core-frontend": "^4.0.0-dev.90",
-    "@itwin/core-geometry": "^4.0.0-dev.90"
+    "@itwin/appui-abstract": "^4.0.0-dev.92",
+    "@itwin/core-bentley": "^4.0.0-dev.92",
+    "@itwin/core-common": "^4.0.0-dev.92",
+    "@itwin/core-frontend": "^4.0.0-dev.92",
+    "@itwin/core-geometry": "^4.0.0-dev.92"
   },
   "//devDependencies": [
     "NOTE: All peerDependencies should also be listed as devDependencies since peerDependencies are not considered by npm install",
     "NOTE: All tools used by scripts in this package must be listed as devDependencies"
   ],
   "devDependencies": {
-    "@itwin/appui-abstract": "4.0.0-dev.90",
-    "@itwin/build-tools": "4.0.0-dev.90",
-    "@itwin/certa": "4.0.0-dev.90",
-    "@itwin/core-bentley": "4.0.0-dev.90",
-    "@itwin/core-common": "4.0.0-dev.90",
-    "@itwin/core-frontend": "4.0.0-dev.90",
-    "@itwin/core-geometry": "4.0.0-dev.90",
     "@itwin/eslint-plugin": "^4.0.0-dev.33",
     "cpx2": "^3.0.0",
     "eslint": "^8.36.0",
     "rimraf": "^3.0.2",
-    "typescript": "~5.0.2"
+    "typescript": "~5.0.2",
+    "@itwin/appui-abstract": "4.0.0-dev.92",
+    "@itwin/build-tools": "4.0.0-dev.92",
+    "@itwin/core-bentley": "4.0.0-dev.92",
+    "@itwin/certa": "4.0.0-dev.92",
+    "@itwin/core-common": "4.0.0-dev.92",
+    "@itwin/core-frontend": "4.0.0-dev.92",
+    "@itwin/core-geometry": "4.0.0-dev.92"
   },
   "//dependencies": [
     "NOTE: these dependencies should be only for things that DO NOT APPEAR IN THE API",
     "NOTE: editor-frontend should remain UI technology agnostic, so no react/angular dependencies are allowed"
   ],
   "dependencies": {
-    "@itwin/editor-common": "4.0.0-dev.90"
+    "@itwin/editor-common": "4.0.0-dev.92"
   },
   "eslintConfig": {
     "plugins": [
@@ -72,6 +72,5 @@
     "pseudolocalize": "betools pseudolocalize --englishDir ./src/public/locales/en --out ./public/locales/en-PSEUDO",
     "test": "",
     "cover": ""
-  },
-  "readme": "# @itwin/editor-frontend\r\n\r\nCopyright © Bentley Systems, Incorporated. All rights reserved. See LICENSE.md for license terms and full copyright notice.\r\n\r\n## Description\r\n\r\nThe __@itwin/editor-frontend__ package contains frontend classes for editing iModels.\r\n\r\n## Documentation\r\n\r\nSee the [iTwin.js](https://www.itwinjs.org) documentation for more information.\r\n\r\n## Key-ins\r\n\r\nThe following key-ins are available for this package.\r\n\r\n###### Enabled by `EditorOptions.registerUndoRedoTools`\r\n\r\n* `editor undo all` - Undo all changes to elements.\r\n* `editor undo single` - Undo last change to elements.\r\n* `editor redo` - Redo last undone change to elements.\r\n\r\n###### Enabled by `EditorOptions.registerBasicManipulationTools`\r\n\r\n* `editor delete elements` - Delete selected elements.\r\n* `editor move elements` - Move selected elements.\r\n* `editor rotate elements` - Rotate selected elements. Accepts 0-3 arguments:\r\n  * `method=0|1` How rotate angle will be specified. 0 for by 3 points, 1 for by specified angle.\r\n  * `about=0|1|2` Location to rotate about. 0 for point, 1 for placement origin, and 2 for center of range.\r\n  * `angle=number` Rotation angle in degrees when not defining angle by points.\r\n\r\n###### Enabled by `EditorOptions.registerSketchTools`\r\n\r\n* `editor create arc` - Create a new arc element or add an arc to an existing open path. Accepts 0-3 arguments:\r\n  * `method=0|1|2|3` How arc will be defined. 0 for center/start, 1 for start/center, 2 for start/mid/end, and 3 for start/end/mid.\r\n  * `radius=number` Arc radius for start/center or center/start, 0 to define by points.\r\n  * `sweep=number` Arc sweep angle in degrees for start/center or center/start, 0 to define by points.\r\n* `editor create linestring` - Create a new linestring element or add a linestring to an existing path.\r\n\r\n###### Enabled by `EditorOptions.registerProjectLocationTools`\r\n\r\n* `editor project location show` - Show the decoration for editing the iModel's project extents and geolocation.\r\n* `editor project location hide` - Hide the decoration preserving unsaved changes (call show to redisplay).\r\n* `editor project location cancel` - Clear the decoration and abandon unsaved changes.\r\n* `editor project location save` - Save the modified project extents or geolocation.\r\n\r\n* `editor project geolocation point` - Enter latitude, longitude, altitude, and north angle for a known location. Accepts 0-4 arguments:\r\n  * `latitude=number` Latitude of accept point in degrees.\r\n  * `longitude=number` Longitude of accept point in degrees.\r\n  * `altitude=number` Height above ellipsoid of accept point.\r\n  * `north=number` North direction in degrees of accept point.\r\n* `editor project geolocation north` - Define north direction by two points.\r\n* `editor project geolocation move` - Tweak geolocation by defining a translation from two points.\r\n\r\n## Project Extents and Geolocation\r\n\r\n### Usage\r\n\r\nRunning the `editor project location show` command, with a spatial view active, enables the display of the project extents and geolocation controls.\r\n\r\n![decoration example](https://raw.githubusercontent.com/iTwin/itwinjs-core/master/editor/frontend/docs/images/pl_decoration.png \"Example of decoration for a geolocated imodel\")\r\n\r\n1. A clip volume representing the current project extents.\r\n    * The current size is shown in locate tooltip using the active distance formatting.\r\n2. Control to define the ECEF origin.\r\n    * Click to run the `editor project geolocation point` command.\r\n    * This control is not displayed when the imodel has a valid GCS defined.\r\n3. Control to define the north direction.\r\n    * Click to run the `editor project geolocation north` command.\r\n    * This control is not displayed when the imodel isn't geolocated.\r\n    * When a GCS is defined, the current north direction is displayed for information purposes but can't be modified.\r\n4. Controls to define the project extents.\r\n    * Click an arrow control to resize.\r\n\r\n> The decorations and controls are expected to be selectable and modifiable by the default tool.\r\n\r\n#### Changing the project extents\r\n\r\nUse the arrow controls (#4) to resize the project extents.\r\n\r\n> If making the project extents larger, it is helpful to have the background map displayed to avoid decoration clipping.\r\n\r\nWhile there isn't hard limit imposed on the size of the project extents, when any dimension exceeds the recommend maximum a warning symbol is displayed.\r\n\r\nFor the project extents height, the recommended maximum is 2 km.\r\n\r\n![max z extents](https://raw.githubusercontent.com/iTwin/itwinjs-core/master/editor/frontend/docs/images/pl_extent_z.png \"Example of z extents larger than recommended\")\r\n\r\nFor the project extents length and width, the recommended maximum when a GCS is defined is 350 km, and 20 km for imodels that aren't map projections (only ECEF transform defined). In addition to the warning symbols near the arrow controls, a red transparent fill is also displayed to help indicate the xy extents may be too large.\r\n\r\n![max xy extents](https://raw.githubusercontent.com/iTwin/itwinjs-core/master/editor/frontend/docs/images/pl_extent_xy.png \"Example of z extents larger than recommended\")\r\n\r\n#### Adding or Updating Geolocation\r\n\r\nIf an imodel is not currently geolocated, or is incorrectly geolocated without a valid GCS defined, the geolocation control (#2) will be displayed. Clicking on this control runs the `editor project geolocation point` command, and after snapping to a known coordinate you will be prompted to enter new values for latitude, longitude, altitude, and north angle.\r\n\r\nIf the imodel is already geolocated, the tool settings is populated with the current values for the snapped coordinate. If you don't know the north direction angle, not to worry, this can be defined interactively with another control once the model has an ECEF origin defined.\r\n\r\n![define geolocation](https://raw.githubusercontent.com/iTwin/itwinjs-core/master/editor/frontend/docs/images/pl_geolocate.png \"Example of defining ECEF origin\")\r\n\r\n##### Interactively Defining North Direction\r\n\r\nThe north direction can set interactively by 2 points, click on the north direction control (#3) to run the  `editor project geolocation north` command.\r\n\r\n![define north](https://raw.githubusercontent.com/iTwin/itwinjs-core/master/editor/frontend/docs/images/pl_north_1.png \"Example of defining north direction by 2 points\")\r\n\r\nAfter zooming out far enough, only the north direction control will be displayed in the view. This may be helpful for seeing where the project is located on the globe or visually confirming the proper north direction.\r\n\r\n![north decoration](https://raw.githubusercontent.com/iTwin/itwinjs-core/master/editor/frontend/docs/images/pl_north_2.png \"Example of north decoration when zoomed out\")\r\n\r\n> The north direction control is only displayed *after* an imodel has been geolocated.\r\n\r\n##### Interactively Tweaking Lat/Long/Altitude\r\n\r\nIf the geolocation is *almost* correct, the latitude, longitude, and altitude can be interactively adjusted by defining a translation by 2 points.\r\n\r\nFor example, running the `editor project geolocation move` command can be used to correct an incorrect altitude for the building below that is half buried in the terrain.\r\n\r\n![incorrect altitude](https://raw.githubusercontent.com/iTwin/itwinjs-core/master/editor/frontend/docs/images/pl_move_1.png \"Example of incorrect altitude\")\r\n\r\nFirst identify a point on the building to move from, it can be helpful turning off map locate for this point if it's below the terrain. For the second point, with map locate re-enabled and the active snap mode set to nearest, identify a point on the terrain to complete the adjustment.\r\n\r\n> AccuDraw can be very helpful when adjusting altitude. Use the T/F/S shortcuts to orient the AccuDraw compass, use Enter (smartlock) to lock an axis to snap the 2nd point. For this example F and Enter were used to lock the up direction before changing to nearest snap for the 2nd point.\r\n\r\n![adjusting altitude](https://raw.githubusercontent.com/iTwin/itwinjs-core/master/editor/frontend/docs/images/pl_move_2.png \"Example of interactively adjusting altitude\")\r\n\r\nNow we can see the building correctly adjusted for the terrain.\r\n\r\n![corrected altitude](https://raw.githubusercontent.com/iTwin/itwinjs-core/master/editor/frontend/docs/images/pl_move_3.png \"Example of corrected altitude\")\r\n\r\n#### Saving And Abandoning Changes\r\n\r\nTo abandon changes to the project extents or geolocation currently being previewed, run the `editor project location cancel` command.\r\n\r\nTo turn off the display of decorations while preserving unsaved changes, run the `editor project location hide` command. Use `editor project location show` to restore preview of unsaved changes.\r\n\r\nTo save the changes being previewed, run the `editor project location save` command.\r\n"
+  }
 }