@itwin/hypermodeling-frontend 4.0.0-dev.90 → 4.0.0-dev.91

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (1) hide show
  1. package/package.json +14 -15
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@itwin/hypermodeling-frontend",
3
- "version": "4.0.0-dev.90",
3
+ "version": "4.0.0-dev.91",
4
4
  "description": "iTwin.js hypermodeling package",
5
5
  "main": "lib/cjs/hypermodeling-frontend.js",
6
6
  "module": "lib/esm/hypermodeling-frontend.js",
@@ -22,18 +22,12 @@
22
22
  "url": "http://www.bentley.com"
23
23
  },
24
24
  "peerDependencies": {
25
- "@itwin/core-bentley": "^4.0.0-dev.90",
26
- "@itwin/core-common": "^4.0.0-dev.90",
27
- "@itwin/core-frontend": "^4.0.0-dev.90",
28
- "@itwin/core-geometry": "^4.0.0-dev.90"
25
+ "@itwin/core-bentley": "^4.0.0-dev.91",
26
+ "@itwin/core-common": "^4.0.0-dev.91",
27
+ "@itwin/core-frontend": "^4.0.0-dev.91",
28
+ "@itwin/core-geometry": "^4.0.0-dev.91"
29
29
  },
30
30
  "devDependencies": {
31
- "@itwin/build-tools": "4.0.0-dev.90",
32
- "@itwin/core-bentley": "4.0.0-dev.90",
33
- "@itwin/core-common": "4.0.0-dev.90",
34
- "@itwin/core-frontend": "4.0.0-dev.90",
35
- "@itwin/core-geometry": "4.0.0-dev.90",
36
- "@itwin/certa": "4.0.0-dev.90",
37
31
  "@itwin/eslint-plugin": "^4.0.0-dev.33",
38
32
  "@types/chai": "4.3.1",
39
33
  "@types/mocha": "^8.2.2",
@@ -49,10 +43,16 @@
49
43
  "rimraf": "^3.0.2",
50
44
  "source-map-loader": "^4.0.0",
51
45
  "typescript": "~5.0.2",
52
- "webpack": "^5.76.0"
46
+ "webpack": "^5.76.0",
47
+ "@itwin/build-tools": "4.0.0-dev.91",
48
+ "@itwin/core-common": "4.0.0-dev.91",
49
+ "@itwin/core-frontend": "4.0.0-dev.91",
50
+ "@itwin/core-bentley": "4.0.0-dev.91",
51
+ "@itwin/core-geometry": "4.0.0-dev.91",
52
+ "@itwin/certa": "4.0.0-dev.91"
53
53
  },
54
54
  "dependencies": {
55
- "@itwin/appui-abstract": "4.0.0-dev.90"
55
+ "@itwin/appui-abstract": "4.0.0-dev.91"
56
56
  },
57
57
  "nyc": {
58
58
  "extends": "./node_modules/@itwin/build-tools/.nycrc"
@@ -77,6 +77,5 @@
77
77
  "test": "npm run -s webpackTests && certa -r chrome",
78
78
  "test:debug": "certa -r chrome --debug",
79
79
  "webpackTests": "webpack --config ./src/test/utils/webpack.config.js 1>&2"
80
- },
81
- "readme": "# Hypermodeling Extension\r\n\r\nCopyright © Bentley Systems, Incorporated. All rights reserved. See LICENSE.md for license terms and full copyright notice.\r\n\r\nThis package enables a feature called \"hyper-modeling\". iModels often contain 2d views of spatial model(s) intended to serve as documentation, called \"section drawings\". These views are produced by applying a section (clip) volume to the spatial geometry and projecting the section cut geometry onto the plane to generate a 2d view. A spatial element called a \"section drawing location\" is positioned at the section cut plane, with a link to the 2d section view. Hyper-modeling allows the 2d graphics to be displayed in situ with the spatial models at the section drawing location.\r\n\r\n## Usage\r\n\r\nBefore any of the package's APIs are used, the application must call and await the result of `HyperModeling.initialize()`. Typically this will be done when the app starts up. For example:\r\n\r\n```ts\r\n await IModelApp.startup();\r\n await HyperModeling.initialize();\r\n```\r\n\r\nThe API entry point is `HyperModeling`. Use `HyperModeling.startOrStop()` to toggle hypermodeling features for a `Viewport`. When enabled, a marker is displayed in the viewport for each section drawing location. Clicking the marker applies the section clip and displays the graphics from the section drawing, along with any sheet annotations, in situ with the spatial model(s). Hovering over a marker opens a mini-toolbar with additional interactions:\r\n * Apply Section: Applies the section clip and displays the section graphics and sheet annotations.\r\n * Open Section: Navigate to the 2d section drawing view.\r\n * Open Sheet: If the section drawing was placed onto a sheet, navigate to the corresponding view attachment.\r\n\r\n## Key-ins\r\n\r\nThe package exposes the following key-in commands:\r\n\r\n* `hypermodeling [toggle]`: Enables or disables hypermodeling for the active viewport. Arguments:\r\n * `toggle`: \"ON\" to enable hypermodeling, \"OFF\" to disable, or \"TOGGLE\" to invert the current state. Default: \"TOGGLE\".\r\n* `hypermodeling marker config [category] [model] [hiddenSectionTypes]`: Changes aspects of the marker display configuration for the active viewport. If no arguments are supplied, all settings are reset to defaults. Arguments:\r\n * `category=0|1`: If 1, only markers belonging to visible categories are displayed; if 0, markers on all categories are displayed.\r\n * `model=0|1`: If 1, only markers belonging to visible models are displayed; if 0, markers in all models are displayed.\r\n * `hiddenSectionTypes=p|e|s|d`: Specifies types of markers that should not be displayed - (p)lan, (e)levation, (d)etail, and (s)ection. Multiple types can be specified - e.g., `hiddenSectionTypes=pd` indicates plan and detail section markers should be hidden.\r\n* `hypermodeling merker default config`: Changes aspects of the global marker display configuration used for any subsequently creted HyperModelingDecorators. The arguments are the same as for `hypermodeling marker config`.\r\n* `hypermodeling graphics config [drawing] [sheet] [clip] [boundaries]`: Changes aspects of the global configuration affecting how section graphics are displayed. Each argument is of the form `name=0|1` where 0 indicates the option should be disabled and 1 indicates it should be enabled. Arguments:\r\n * `drawing=0|1`: Whether to display the section drawing graphics.\r\n * `sheet=0|1`: Whether to draw the sheet annotations.\r\n * `clip=0|1`: Whether to apply clip volumes to the 2d graphics.\r\n * `boundaries=0|1`: Whether to visualize 2d clip volumes as boundary shapes for debugging.\r\n\r\n## Contributing\r\n\r\n[Contributing to iTwin.js](https://github.com/iTwin/itwinjs-core/blob/master/CONTRIBUTING.md)\r\n"
80
+ }
82
81
  }