aurea-eden 1.25.1

package/.gitattributes

@@ -0,0 +1,2 @@
+# Auto detect text files and perform LF normalization
+* text=auto

package/.github/workflows/static.yml

@@ -0,0 +1,43 @@
+# Simple workflow for deploying static content to GitHub Pages
+name: Deploy static content to Pages
+
+on:
+  # Runs on pushes targeting the default branch
+  push:
+    branches: ["main"]
+
+  # Allows you to run this workflow manually from the Actions tab
+  workflow_dispatch:
+
+# Sets permissions of the GITHUB_TOKEN to allow deployment to GitHub Pages
+permissions:
+  contents: read
+  pages: write
+  id-token: write
+
+# Allow only one concurrent deployment, skipping runs queued between the run in-progress and latest queued.
+# However, do NOT cancel in-progress runs as we want to allow these production deployments to complete.
+concurrency:
+  group: "pages"
+  cancel-in-progress: false
+
+jobs:
+  # Single deploy job since we're just deploying
+  deploy:
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+      - name: Setup Pages
+        uses: actions/configure-pages@v5
+      - name: Upload artifact
+        uses: actions/upload-pages-artifact@v3
+        with:
+          # Upload entire repository
+          path: '.'
+      - name: Deploy to GitHub Pages
+        id: deployment
+        uses: actions/deploy-pages@v4

package/CHANGELOG.md

@@ -0,0 +1,60 @@
+# Changelog
+
+All notable changes to this project will be documented in this file. See [standard-version](https://github.com/conventional-changelog/standard-version) for commit guidelines.
+
+### [1.25.1](https://gitlab.tecna.pl/waszkowski_r/three-diagram/compare/v1.25.0...v1.25.1) (2025-04-30)
+
+## [1.25.0](https://gitlab.tecna.pl/waszkowski_r/three-diagram/compare/v1.24.0...v1.25.0) (2025-04-30)
+
+## [1.24.0] - 2025-04-30
+### Added
+- Complete JSDoc documentation for main module and components
+
+## [1.1.0] - 2025-04-26
+### Added
+- New sample diagrams for demonstration
+- Spot light functionality for better 3D visualization
+### Changed
+- Enhanced diagram display modes
+
+## [1.0.0] - 2025-03-16
+### Added
+- Complete BPMN notation support
+- BPMN elements and icons
+- Icon placeholders system
+- Text wrapping functionality
+### Changed
+- Improved icon shape handling
+
+## [0.3.0] - 2025-02-28
+### Added
+- BPMN parser functionality
+- Connector system for diagram elements
+### Changed
+- Major project reorganization
+- API improvements
+
+## [0.2.0] - 2025-02-16
+### Added
+- Bar visualization with random heights and colors
+- Text support for elements
+- Analysis mode with TWEEN animations
+### Changed
+- Controls system with map and orbit controls
+- Project files organization refactor
+
+## [0.1.0] - 2025-01-23
+### Added
+- Basic BPMN shapes and elements
+- Diagram modes (EDIT, VIEW)
+- Camera controls and adjustments
+- Map controls for EDIT mode
+- Window resize handling
+- Favicon support
+
+## [0.0.1] - 2025-01-13
+### Added
+- Initial project setup
+- Basic Three.js integration
+- Project structure
+- License

package/LICENSE

@@ -0,0 +1,17 @@
+GNU GENERAL PUBLIC LICENSE
+                       Version 3, 29 June 2007
+
+ Copyright (C) 2025 Robert Waszkowski
+
+ This program is free software: you can redistribute it and/or modify
+ it under the terms of the GNU General Public License as published by
+ the Free Software Foundation, either version 3 of the License, or
+ (at your option) any later version.
+
+ This program is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+ GNU General Public License for more details.
+
+ You should have received a copy of the GNU General Public License
+ along with this program.  If not, see <https://www.gnu.org/licenses/>.

package/README.md

@@ -0,0 +1,171 @@
+# Aurea EDEN
+
+![Aurea EDEN Logo](assets/aurea-eden-logo.jpeg)
+
+A flexible Three.js-based framework for creating custom diagramming notations in 3D, featuring built-in BPMN support while enabling developers to define and extend their own visual languages with parameter-driven transformations.
+
+## Table of Contents
+
+- [Installation](#installation)
+- [Quick Start](#quick-start)
+- [Features](#features)
+- [Core Components](#core-components)
+- [Advanced Usage](#advanced-usage)
+- [API Reference](#api-reference)
+- [Contributing](#contributing)
+- [License](#license)
+
+## Installation
+
+```bash
+npm install aurea-eden-lib
+```
+
+## Quick Start
+
+```javascript
+import { BpmnDiagram } from 'aurea-eden-lib';
+
+// Create new diagram
+const diagram = new BpmnDiagram(container);
+
+// Add elements
+diagram.addStartEvent('e1')
+    .addTask('t1')
+    .positionRightOf('e1')
+    .addWrappedText('Handle Task')
+    .connectFrom('e1')
+    .setValue(75)
+    .addValueBar();
+
+// Arrange and display
+diagram.arrange();
+diagram.fitScreen();
+```
+
+## Features
+
+- **3D Visualization**: Extend 2D notations into 3D space
+- **Parameter Visualization**: Show quantitative data through value bars
+- **Custom Notations**: Create your own visual languages
+- **Interactive Controls**: Pan, zoom, and rotate diagrams
+- **Multiple View Modes**: Switch between VIEW and ANALYZE modes
+- **Fluid API**: Method chaining for intuitive diagram creation
+- **Built-in BPMN Support**: Ready-to-use BPMN elements
+
+## Core Components
+
+### Diagram Class
+
+The main container for all diagram elements:
+
+```javascript
+const diagram = new BpmnDiagram(container);
+diagram.setMode('ANALYZE');    // Switch to analysis mode
+diagram.fitScreen();          // Adjust view
+```
+
+### Elements
+
+Available BPMN elements:
+- StartEvent
+- EndEvent
+- Task
+- UserTask
+- Gateway
+- Connector
+
+### Materials
+
+Three material types:
+```javascript
+import { DiagramMaterial, BarMaterial, EditMaterial } from 'aurea-eden-lib';
+
+// Standard element material
+new DiagramMaterial({ 
+    color: 0x00ff00,
+    shininess: 60 
+});
+
+// Value bar material
+new BarMaterial({ 
+    color: 0xff0000,
+    opacity: 0.5 
+});
+```
+
+## Advanced Usage
+
+### Creating Custom Elements
+
+```javascript
+import { DiagramElement, Shape } from 'aurea-eden-lib';
+
+class CustomElement extends DiagramElement {
+    constructor(diagram, id) {
+        super(diagram, id);
+        this.shape = new CustomShape();
+        this.add(this.shape);
+    }
+}
+```
+
+### Custom Connectors
+
+```javascript
+const waypoints = [
+    element1.getNorthPoint(),
+    { x: 100, y: 200, z: 0 },
+    element2.getSouthPoint()
+];
+
+diagram.addFlowConnector('connector1', waypoints);
+```
+
+## API Reference
+
+### BpmnDiagram Methods
+
+#### Element Creation
+- `addStartEvent(id)`
+- `addEndEvent(id)`
+- `addTask(id)`
+- `addUserTask(id)`
+- `addGateway(id)`
+
+#### Element Positioning
+- `positionRightOf(elementId)`
+- `positionBelow(elementId)`
+- `positionUpRightOf(elementId)`
+- `positionDownRightOf(elementId)`
+
+#### View Control
+- `center()`
+- `fitScreen()`
+- `rotate(angle)`
+- `setMode(mode)`
+
+## Contributing
+
+1. Fork the repository
+2. Create your feature branch (`git checkout -b feature/AmazingFeature`)
+3. Commit your changes (`git commit -m 'Add some AmazingFeature'`)
+4. Push to the branch (`git push origin feature/AmazingFeature`)
+5. Open a Pull Request
+
+## License
+
+This project is licensed under the GNU General Public License v3.0 - see the [LICENSE](LICENSE) file for details.
+
+## Dependencies
+
+- Three.js: 3D graphics library
+- Tween.js: Animation library
+
+## Author
+
+Robert Waszkowski
+
+---
+
+For more examples and detailed API documentation, visit our [GitHub Wiki](https://github.com/your-repo/aurea-eden/wiki).

package/README_.md

@@ -0,0 +1,174 @@
+# Aurea EDEN
+
+![Three Diagram Logo](assets/3diagram_logo.png)
+
+## Libraries used
+
+```
+npm install --save three
+npm install @tweenjs/tween.js
+npm install --save-dev vite
+
+```
+
+## Run
+### Vite
+```
+npx vite
+```
+and open the local site: [http://localhost:5173/](http://localhost:5173/)
+
+
+### Build and run
+```
+npm run build
+npx vite
+```
+and open the local site [http://localhost:5173/use-lib.html](http://localhost:5173/use-lib.html)
+
+## Getting started
+
+To make it easy for you to get started with GitLab, here's a list of recommended next steps.
+
+Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
+
+## Add your files
+
+- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
+- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
+
+```
+cd existing_repo
+git remote add origin https://gitlab.tecna.pl/waszkowski_r/three-diagram.git
+git branch -M master
+git push -uf origin master
+```
+
+## Git configuration
+
+You can view all of your settings and where they are coming from using:
+
+```
+$ git config --list --show-origin
+```
+
+Your Identity
+The first thing you should do when you install Git is to set your user name and email address. This is important because every Git commit uses this information, and it’s immutably baked into the commits you start creating:
+
+```
+$ git config --global user.name "John Doe"
+$ git config --global user.email johndoe@example.com
+```
+
+### Avoid Repeated Credential Prompts
+
+If you want VS Code to stop asking for credentials every time you push your changes to GitLab, follow this step:
+
+```
+git config credential.helper store
+```
+
+## Integrate with your tools
+
+- [ ] [Set up project integrations](https://gitlab.tecna.pl/waszkowski_r/three-diagram/-/settings/integrations)
+
+## Collaborate with your team
+
+- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
+- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
+- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
+- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
+- [ ] [Set auto-merge](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
+
+## Test and Deploy
+
+Use the built-in continuous integration in GitLab.
+
+- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
+- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
+- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
+- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
+- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
+
+***
+
+# Editing this README
+
+When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.
+
+## Suggestions for a good README
+
+Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
+
+## Name
+Choose a self-explaining name for your project.
+
+## Description
+Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
+
+## Badges
+On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
+
+## Visuals
+Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
+
+## Installation
+Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
+
+## Usage
+Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
+
+## Support
+Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
+
+## Roadmap
+If you have ideas for releases in the future, it is a good idea to list them in the README.
+
+## Contributing
+State if you are open to contributions and what your requirements are for accepting them.
+
+For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
+
+You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
+
+## Authors and acknowledgment
+Show your appreciation to those who have contributed to the project.
+
+## License
+This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.
+
+## Project status
+If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
+
+# Acknowledgment
+The library structure and behavior are inspired by Sameer Kumar's sample JavaScript Vite library. For more details, visit the [GitHub repository](https://github.com/sameer1612/ninja-lib) and the [preparation guide](https://betterprogramming.pub/the-pragmatic-guide-to-your-first-javascript-library-516a7b08c677).
+
+Useful Three.js Tutorial [here](https://sbcode.net/threejs/)
+(i.e. [OrbitControls](https://sbcode.net/threejs/orbit-controls/)).
+
+Drawing technology flow chart [orthogonal connection algorithm](https://pubuzhixing.medium.com/drawing-technology-flow-chart-orthogonal-connection-algorithm-fe23215f5ada).
+Routing [Orthogonal Diagram Connectors in JavaScript](https://medium.com/swlh/routing-orthogonal-diagram-connectors-in-javascript-191dc2c5ff70).
+Orthogonal Connector Routing example [here](https://orthogonal.jose.page/).
+
+
+
+For testing 
+
+$ npm install --save dat.gui
+
+https://github.com/dataarts/dat.gui
+
+
+**Adding automated versioning**
+
+https://muetsch.io/mastering-software-versioning-in-javascript-projects.html
+
+Install:
+```terminal
+npm i --save-dev standard-version
+```
+
+Set a new version:
+```terminal
+npm run release
+```

package/assets/favicon/about.txt

@@ -0,0 +1,6 @@
+This favicon was generated using the following graphics from Twitter Twemoji:
+
+- Graphics Title: 2197.svg
+- Graphics Author: Copyright 2020 Twitter, Inc and other contributors (https://github.com/twitter/twemoji)
+- Graphics Source: https://github.com/twitter/twemoji/blob/master/assets/svg/2197.svg
+- Graphics License: CC-BY 4.0 (https://creativecommons.org/licenses/by/4.0/)

package/assets/favicon/site.webmanifest

@@ -0,0 +1 @@
+{"name":"","short_name":"","icons":[{"src":"/android-chrome-192x192.png","sizes":"192x192","type":"image/png"},{"src":"/android-chrome-512x512.png","sizes":"512x512","type":"image/png"}],"theme_color":"#ffffff","background_color":"#ffffff","display":"standalone"}