bimplus-renderer 1.8.30-jquery-update2-01 → 1.8.30-textures-01

package/MOMENT_TIMEZONE_INTEGRATION.md

@@ -1,38 +1,38 @@
-# Moment Timezone Integration
-
-The `setSunPosition` function now supports optional moment-timezone integration. Here are the different ways to use it:
-
-## Inject programmatically
-
-```javascript
-import { injectMomentTimezone, hasMomentTimezone } from 'bimplus-renderer';
-
-// If you have moment-timezone available in your application
-import moment from 'moment-timezone';
-
-// You can check if moment-timezone is available before calling the function:
-if (!hasMomentTimezone()) {
-  console.log('Injecting moment-timezone for sun positioning features');
-  injectMomentTimezone(moment);
-}
-
-// Now you can use setSunPosition
-viewport3D.setSunPosition({
-  northDirection: 0,
-  year: 2024,
-  month: 6,
-  day: 21,
-  hours: 12,
-  minutes: 0,
-  timezone: 'Europe/Berlin',
-  latitude: 52.5200,
-  longitude: 13.4050,
-  showSky: true
-});
-```
-
-This approach allows:
-- Backward compatibility for existing users who have moment-timezone
-- Forward compatibility for new users who don't want the dependency
-- Clear error messages when the functionality is used without the required library
+# Moment Timezone Integration
+
+The `setSunPosition` function now supports optional moment-timezone integration. Here are the different ways to use it:
+
+## Inject programmatically
+
+```javascript
+import { injectMomentTimezone, hasMomentTimezone } from 'bimplus-renderer';
+
+// If you have moment-timezone available in your application
+import moment from 'moment-timezone';
+
+// You can check if moment-timezone is available before calling the function:
+if (!hasMomentTimezone()) {
+  console.log('Injecting moment-timezone for sun positioning features');
+  injectMomentTimezone(moment);
+}
+
+// Now you can use setSunPosition
+viewport3D.setSunPosition({
+  northDirection: 0,
+  year: 2024,
+  month: 6,
+  day: 21,
+  hours: 12,
+  minutes: 0,
+  timezone: 'Europe/Berlin',
+  latitude: 52.5200,
+  longitude: 13.4050,
+  showSky: true
+});
+```
+
+This approach allows:
+- Backward compatibility for existing users who have moment-timezone
+- Forward compatibility for new users who don't want the dependency
+- Clear error messages when the functionality is used without the required library
 - Flexibility in how the library is provided (npm, CDN, injection)

package/MOMENT_TIMEZONE_INTEGRATION_FOR_TEST.md

@@ -1,64 +1,64 @@
-# Test-Only Moment-Timezone Integration
-
-## Overview
-
-This solution successfully implements moment-timezone dependency injection specifically for tests while keeping the production code completely free of the dependency.
-
-## Implementation
-
-### 1. Production Code (Optional Dependency)
-- **[src/viewport3d.js](src/viewport3d.js)**: Contains optional moment-timezone detection
-- **[src/utils/momentTimezoneInjector.js](src/utils/momentTimezoneInjector.js)**: Utility for external injection (for BimExplorer app)
-- Production builds work without moment-timezone installed
-- Runtime errors provide clear instructions when moment-timezone features are needed
-
-### 2. Test-Only Injection
-- **[test/setup/momentTimezoneInjector.js](test/setup/momentTimezoneInjector.js)**: Test setup that injects moment-timezone globally
-- **package.json**: moment-timezone installed as `devDependency` only
-- **karma-files-config.js**: Loads injector before any test files
-
-### 3. Test Configuration
-```javascript
-// In karma-files-config.js
-files: [
-  "src/**/*.js",
-  // Load test environment setup (inject moment-timezone for tests)
-  "test/setup/momentTimezoneInjector.js",
-  // Load custom assertions first
-  "test/customAsserts.js",
-  // Load test files
-  "test/**/*.js",
-],
-```
-
-## How It Works
-
-### For Tests
-1. Karma loads the moment-timezone injector first
-2. The injector imports moment-timezone (available as dev dependency)
-3. Injects it into global scope (`window.moment`)
-4. All tests run with moment-timezone available
-5. Sun calculation tests pass with accurate timezone handling
-
-### For Production
-1. Production code uses optional detection: `getMomentTZ()`
-2. If moment-timezone isn't found, production code either:
-   - Throws descriptive error for features requiring it (`setSunPosition`)
-3. Build process excludes moment-timezone from production bundle
-4. Users can inject moment-timezone via BimExplorer app if needed
-
-## File Changes
-
-### New Files
-- `test/setup/momentTimezoneInjector.js` - Test environment setup
-
-### Modified Files  
-- `karma-files-config.js` - Added test setup loader
-- `package.json` - Added moment-timezone as devDependency
-
-### Existing Files (Unchanged)
-- `src/viewport3d.js` - Already has optional moment-timezone detection
-- `src/utils/momentTimezoneInjector.js` - Already provides injection utilities
-- All test files - Work seamlessly with injected moment-timezone
-
+# Test-Only Moment-Timezone Integration
+
+## Overview
+
+This solution successfully implements moment-timezone dependency injection specifically for tests while keeping the production code completely free of the dependency.
+
+## Implementation
+
+### 1. Production Code (Optional Dependency)
+- **[src/viewport3d.js](src/viewport3d.js)**: Contains optional moment-timezone detection
+- **[src/utils/momentTimezoneInjector.js](src/utils/momentTimezoneInjector.js)**: Utility for external injection (for BimExplorer app)
+- Production builds work without moment-timezone installed
+- Runtime errors provide clear instructions when moment-timezone features are needed
+
+### 2. Test-Only Injection
+- **[test/setup/momentTimezoneInjector.js](test/setup/momentTimezoneInjector.js)**: Test setup that injects moment-timezone globally
+- **package.json**: moment-timezone installed as `devDependency` only
+- **karma-files-config.js**: Loads injector before any test files
+
+### 3. Test Configuration
+```javascript
+// In karma-files-config.js
+files: [
+  "src/**/*.js",
+  // Load test environment setup (inject moment-timezone for tests)
+  "test/setup/momentTimezoneInjector.js",
+  // Load custom assertions first
+  "test/customAsserts.js",
+  // Load test files
+  "test/**/*.js",
+],
+```
+
+## How It Works
+
+### For Tests
+1. Karma loads the moment-timezone injector first
+2. The injector imports moment-timezone (available as dev dependency)
+3. Injects it into global scope (`window.moment`)
+4. All tests run with moment-timezone available
+5. Sun calculation tests pass with accurate timezone handling
+
+### For Production
+1. Production code uses optional detection: `getMomentTZ()`
+2. If moment-timezone isn't found, production code either:
+   - Throws descriptive error for features requiring it (`setSunPosition`)
+3. Build process excludes moment-timezone from production bundle
+4. Users can inject moment-timezone via BimExplorer app if needed
+
+## File Changes
+
+### New Files
+- `test/setup/momentTimezoneInjector.js` - Test environment setup
+
+### Modified Files  
+- `karma-files-config.js` - Added test setup loader
+- `package.json` - Added moment-timezone as devDependency
+
+### Existing Files (Unchanged)
+- `src/viewport3d.js` - Already has optional moment-timezone detection
+- `src/utils/momentTimezoneInjector.js` - Already provides injection utilities
+- All test files - Work seamlessly with injected moment-timezone
+
 This solution provides the best of both worlds: comprehensive test coverage with accurate timezone calculations, while maintaining a lean production build without unnecessary dependencies.

package/README.md

@@ -1,124 +1,124 @@
-bim+ renderer
-=========
-
-bim+ renderer is a javascript renderer core based on three js.
-
-Quick Links
------------
-
-https://nemetschekprime.atlassian.net/wiki/spaces/bimpluspublic/pages/1090127443/Bimplus+Renderer+Reference
-
-How to build
-------------
-
-### Install nodejs
-[http://www.nodejs.org/](http://www.nodejs.org/)
-
-### Install local npm modules
-Open up a normal command line (admin is not needed) and go to the renderer folder
-
-    npm install
-
-(whenever package.json has changed, you might to do this again)
-
-### Install emscripten SDK
-[https://emscripten.org/](https://emscripten.org/)
-Install the emscripten toolchain to cross compile the performance critical parts written
-in c/c++ to web assembly
-
-### Build renderer
-Library building process is using UMD (Universal Module Definition) output format so
-it's compatible with both cjs and amd module formats. The same library can be use in the
-client or on the server. Build process is using babel so it's possible to use new ES2015
-code in source codes.
-
-Library can be build in several ways as a dev or prod version.
-To run a dev build with source maps run:
-
-    npm run build
-
-To build a prod version - uglified, minified run:
-    
-    npm run build-prod
-
-Pulish new release to npm (Hint: Before doing this npm login needs to be done and the package version adjusted) :
-    
-    npm run npm-publish
-
-Check content of npm package (result is bimplus-renderer@(version).tar.gz)
-    
-    npm run npm-pack
-
-### Develop/Debug renderer
-goto your renderer folder
-
-    npm link
-
-goto your application folder which uses the renderer
-
-    npm link bimplus-renderer
-
-Do you changes in the renderer and build
-
-    npm run build
-
-or
-
-  grunt run build-prod
-
-Your app will automatically get the changes done in the renderer
-
-After developing it might be wise to unlink:
-goto your renderer folder
-
-  npm unlink
-
-goto your application folder which uses the renderer
-
-  npm unlink bimplus-renderer
-  npm install
-
-### Unit testing
-With every build output is copied also to the test folder.
-To run the unit tests go to the test subfolder and run
-
-    npm install
-    npm run test
-
-### Documentation
-Bimplus WebSDK uses npm documentation plugin for easy documentation generation.
-To generate a documentation please install documentation plugin via npm :
-
-npm install -g documentation
-
-To create documentation in html format go to your renderer folder and run :
-
-  npm run build-doc
-
-Documentation output will be in renderer/documentation folder
-
-To create documentation in markdown format go to your renderer folder and run :
-
-  npm run build-docMd
-
-Documentation output will be in renderer/documentation/Bimplus_Renderer_doc.md file.
-
-To create a markdown suitable for Confluence run script:
-
-    npm run build-docConf
-
-Please note that python must be installed !!
-This script will convert generated markdown into Confluence format. See console
-output for converted file name. Default place is in ./documentation in file :
-Bimplus_Renderer_doc_confluence.md
-
-
-Content of the confluence file can be inserted into Confluence page :
-- start confluence page editation mode
-- choose Insert more content  / {} Markup option from toolbar
-- in popup window choose to Insert Markdown format
-- copy content of the converted confluence markdown file into the field in Confluence
-- save it (Please note that page links doesn't work in page preview mode)
-
-### Typescript definitions
-- typescript definition file is located in subfolder 'types'
+bim+ renderer
+=========
+
+bim+ renderer is a javascript renderer core based on three js.
+
+Quick Links
+-----------
+
+https://nemetschekprime.atlassian.net/wiki/spaces/bimpluspublic/pages/1090127443/Bimplus+Renderer+Reference
+
+How to build
+------------
+
+### Install nodejs
+[http://www.nodejs.org/](http://www.nodejs.org/)
+
+### Install local npm modules
+Open up a normal command line (admin is not needed) and go to the renderer folder
+
+    npm install
+
+(whenever package.json has changed, you might to do this again)
+
+### Install emscripten SDK
+[https://emscripten.org/](https://emscripten.org/)
+Install the emscripten toolchain to cross compile the performance critical parts written
+in c/c++ to web assembly
+
+### Build renderer
+Library building process is using UMD (Universal Module Definition) output format so
+it's compatible with both cjs and amd module formats. The same library can be use in the
+client or on the server. Build process is using babel so it's possible to use new ES2015
+code in source codes.
+
+Library can be build in several ways as a dev or prod version.
+To run a dev build with source maps run:
+
+    npm run build
+
+To build a prod version - uglified, minified run:
+    
+    npm run build-prod
+
+Pulish new release to npm (Hint: Before doing this npm login needs to be done and the package version adjusted) :
+    
+    npm run npm-publish
+
+Check content of npm package (result is bimplus-renderer@(version).tar.gz)
+    
+    npm run npm-pack
+
+### Develop/Debug renderer
+goto your renderer folder
+
+    npm link
+
+goto your application folder which uses the renderer
+
+    npm link bimplus-renderer
+
+Do you changes in the renderer and build
+
+    npm run build
+
+or
+
+  grunt run build-prod
+
+Your app will automatically get the changes done in the renderer
+
+After developing it might be wise to unlink:
+goto your renderer folder
+
+  npm unlink
+
+goto your application folder which uses the renderer
+
+  npm unlink bimplus-renderer
+  npm install
+
+### Unit testing
+With every build output is copied also to the test folder.
+To run the unit tests go to the test subfolder and run
+
+    npm install
+    npm run test
+
+### Documentation
+Bimplus WebSDK uses npm documentation plugin for easy documentation generation.
+To generate a documentation please install documentation plugin via npm :
+
+npm install -g documentation
+
+To create documentation in html format go to your renderer folder and run :
+
+  npm run build-doc
+
+Documentation output will be in renderer/documentation folder
+
+To create documentation in markdown format go to your renderer folder and run :
+
+  npm run build-docMd
+
+Documentation output will be in renderer/documentation/Bimplus_Renderer_doc.md file.
+
+To create a markdown suitable for Confluence run script:
+
+    npm run build-docConf
+
+Please note that python must be installed !!
+This script will convert generated markdown into Confluence format. See console
+output for converted file name. Default place is in ./documentation in file :
+Bimplus_Renderer_doc_confluence.md
+
+
+Content of the confluence file can be inserted into Confluence page :
+- start confluence page editation mode
+- choose Insert more content  / {} Markup option from toolbar
+- in popup window choose to Insert Markdown format
+- copy content of the converted confluence markdown file into the field in Confluence
+- save it (Please note that page links doesn't work in page preview mode)
+
+### Typescript definitions
+- typescript definition file is located in subfolder 'types'

package/bin/README.emcc.md

@@ -1,41 +1,41 @@
-emcc for webassemblies
-======================
-
-Python installation
--------------------
-Installation of python. On windows the best way is to open a powershell and type python. When python isn't installed a window is opened and python can be installed from webstore
-
-After finished installation check installed python version in cmd or powershell
-
-    PS H:\> python --version
-    Python 3.8.6
-
-Installation Emscripten
------------------------
-Install the emcc sdk.
-Good description could be found here
-
-    https://www.tutorialspoint.com/webassembly/webassembly_installation.htm
-
-Create some folder like C:\wa or C:\wa-emcc and clone the sdk inside this folder
-
-Building Bimplus-Render
------------------------
- Add path information to systemvariables (Used installation folder for emcc like D:\wa-emcc\)
-
-    D:\wa-emcc\emsdk
-    D:\wa-emcc\emsdk\upstream\emscripten
-    D:\wa-emcc\emsdk\node\12.18.1_64bit\bin
-    D:\wa-emcc\emsdk\python\3.7.4-pywin32_64bit
-    D:\wa-emcc\emsdk\java\8.152_64bit\bin;
-
-### Output of emcc is generated in bin folder
-The 
-
-    bin\
-
-folder is needed for 
-
-    npm run build
-
-so we have excluded this file from .gitignore
+emcc for webassemblies
+======================
+
+Python installation
+-------------------
+Installation of python. On windows the best way is to open a powershell and type python. When python isn't installed a window is opened and python can be installed from webstore
+
+After finished installation check installed python version in cmd or powershell
+
+    PS H:\> python --version
+    Python 3.8.6
+
+Installation Emscripten
+-----------------------
+Install the emcc sdk.
+Good description could be found here
+
+    https://www.tutorialspoint.com/webassembly/webassembly_installation.htm
+
+Create some folder like C:\wa or C:\wa-emcc and clone the sdk inside this folder
+
+Building Bimplus-Render
+-----------------------
+ Add path information to systemvariables (Used installation folder for emcc like D:\wa-emcc\)
+
+    D:\wa-emcc\emsdk
+    D:\wa-emcc\emsdk\upstream\emscripten
+    D:\wa-emcc\emsdk\node\12.18.1_64bit\bin
+    D:\wa-emcc\emsdk\python\3.7.4-pywin32_64bit
+    D:\wa-emcc\emsdk\java\8.152_64bit\bin;
+
+### Output of emcc is generated in bin folder
+The 
+
+    bin\
+
+folder is needed for 
+
+    npm run build
+
+so we have excluded this file from .gitignore