Feature/frontal solver (#43)

Author: nikoscham

CONTRIBUTING.md

@@ -2,105 +2,112 @@
 
 Thank you for your interest in contributing! FEAScript is in early development, with continuous additions of new features and improvements. To ensure a smooth and collaborative development process, please review and follow the guidelines below.
 
-## Contribution Guidelines
-
-1. **Development Tools:**  
-   We recommend using [Visual Studio Code](https://code.visualstudio.com/) with the [Prettier plugin](https://marketplace.visualstudio.com/items?itemName=esbenp.prettier-vscode) for automatic code formatting. Additionally, use a **110-character line width** to maintain consistent formatting.
-
-2. **Coding Style:**  
-   Observe the code near your intended changes and aim to preserve that style in your modifications.
-
-3. **Variable Naming:**  
-   Use [camelCase](https://en.wikipedia.org/wiki/Camel_case) formatting for variable names throughout the code.
-
-4. **File Naming:**  
-   All JavaScript source files in FEAScript end with the suffix `Script` before the `.js` extension (e.g., `loggingScript.js`, `meshGenerationScript.js`, `newtonRaphsonScript.js`). This is an explicit, project‑level stylistic choice to:
-
-   - Visually distinguish internal FEAScript modules from third‑party or external library files.
-   - Keep historical and stylistic consistency across the codebase.
-
-   Exceptions:
-
-   - Public entry file: `index.js` (standard entry point convention).
-   - Core model file: `FEAScript.js` (matches the library name; appending "Script" would be redundant).
-
-5. **File Structure:**  
-   All files in the FEAScript-core codebase should follow this structure:
-
-   1. **Banner**: All files start with the FEAScript ASCII art banner.
-   2. **Imports**:
-      - External imports (from npm packages) first, alphabetically ordered.
-      - Internal imports next, grouped by module/folder.
-   3. **Classes/Functions**: Implementation with proper JSDoc comments.
-
-   Example:
-
-   ```javascript
-   //   ______ ______           _____           _       _     //
-   //  |  ____|  ____|   /\    / ____|         (_)     | |    //
-   //  | |__  | |__     /  \  | (___   ___ ____ _ ____ | |_   //
-   //  |  __| |  __|   / /\ \  \___ \ / __|  __| |  _ \| __|  //
-   //  | |    | |____ / ____ \ ____) | (__| |  | | |_) | |    //
-   //  |_|    |______/_/    \_\_____/ \___|_|  |_|  __/| |    //
-   //                                            | |   | |    //
-   //                                            |_|   | |_   //
-   //       Website: https://feascript.com/             \__|  //
-
-   // External imports
-   import { mathLibrary } from "math-package";
-
-   // Internal imports
-   import { relatedFunction } from "../utilities/helperScript.js";
-
-   /**
-    * Class to handle specific functionality
-    */
-   export class MyClass {
-     /**
-      * Constructor to initialize the class
-      * @param {object} options - Configuration options
-      */
-     constructor(options) {
-       // Implementation
-     }
-
-     /**
-      * Function to perform a specific action
-      * @param {number} input - Input value
-      * @returns {number} Processed result
-      */
-     doSomething(input) {
-       // Implementation
-       return input * DEFAULT_VALUE;
-     }
-   }
-   ```
-
-6. **Branching & Workflow:**  
-   To contribute a new feature or fix:
-
-   - Do not commit directly to `main`.
-   - Instead, create a short‑lived branch:
-     - `feature/<topic>` for new functionality
-     - `fix/<issue>` for bug fixes
-
-   External contributors:
-
-   1. Fork the repo.  
-   2. Branch from `main` in your fork.  
-   3. Push and open a PR from your fork’s branch into `main`.
-
-7. **Local Testing:**  
-   Before submitting a pull request, test your modifications by running the FEAScript library from a local directory. For example, you can load the library in your HTML file as follows:
-
-   ```javascript
-   import { FEAScriptModel, plotSolution, printVersion } from "[USER_DIRECTORY]/FEAScript-core/src/index.js";
-   ```
-
-   FEAScript can be run on a local server. To start a local server, you can use [Python HTTP Server](https://docs.python.org/3/library/http.server.html):
-
-   ```bash
-   python -m http.server
-   ```
-
-   where the server will be available at `http://127.0.0.1:8000/`. Static file server npm packages like [serve](https://github.com/vercel/serve#readme) and [Vite](https://vite.dev/) can also be used.
+## Contents
+
+- [Development Environment & Coding Style](#development-environment--coding-style)
+- [Variable & File Naming](#variable--file-naming)
+- [File Structure](#file-structure)
+- [Branching & Workflow](#branching--workflow)
+- [Local Testing](#local-testing)
+
+## Development Environment & Coding Style
+
+- Use [Visual Studio Code](https://code.visualstudio.com/) with the [Prettier plugin](https://marketplace.visualstudio.com/items?itemName=esbenp.prettier-vscode) for automatic code formatting
+- Use a **110-character line width** to maintain consistent formatting
+- Observe the code near your intended changes and aim to preserve that style in your modifications
+
+## Variable & File Naming
+
+- Use [camelCase](https://en.wikipedia.org/wiki/Camel_case) formatting for variable names throughout the code
+- All JavaScript source files in FEAScript end with the suffix `Script` before the `.js` extension (e.g., `loggingScript.js`, `meshGenerationScript.js`, `newtonRaphsonScript.js`). This is an explicit, project‑level stylistic choice to:
+  - Visually distinguish internal FEAScript modules from third‑party or external library files
+  - Keep historical and stylistic consistency across the codebase
+
+### Exceptions
+
+- Public entry file: `index.js` (standard entry point convention)
+- Core model file: `FEAScript.js` (matches the library name; appending "Script" would be redundant)
+
+## File Structure
+
+All files in the FEAScript-core codebase should follow this structure:
+
+1.  Banner: All files start with the FEAScript ASCII art banner
+2.  Imports:
+    - External imports first, alphabetically ordered
+    - Internal imports next, grouped by module/folder
+3.  Classes/Functions: Implementation with proper JSDoc comments
+
+Example:
+
+```javascript
+//   ______ ______           _____           _       _     //
+//  |  ____|  ____|   /\    / ____|         (_)     | |    //
+//  | |__  | |__     /  \  | (___   ___ ____ _ ____ | |_   //
+//  |  __| |  __|   / /\ \  \___ \ / __|  __| |  _ \| __|  //
+//  | |    | |____ / ____ \ ____) | (__| |  | | |_) | |    //
+//  |_|    |______/_/    \_\_____/ \___|_|  |_|  __/| |    //
+//                                            | |   | |    //
+//                                            |_|   | |_   //
+//       Website: https://feascript.com/             \__|  //
+
+// External imports
+import { mathLibrary } from "math-package";
+
+// Internal imports
+import { relatedFunction } from "../utilities/helperScript.js";
+
+/**
+ * Class to handle specific functionality
+ */
+export class MyClass {
+  /**
+   * Constructor to initialize the class
+   * @param {object} options - Configuration options
+   */
+  constructor(options) {
+    // Implementation
+  }
+
+  /**
+   * Function to perform a specific action
+   * @param {number} input - Input value
+   * @returns {number} Processed result
+   */
+  doSomething(input) {
+    // Implementation
+    return input * DEFAULT_VALUE;
+  }
+}
+```
+
+## Branching & Workflow
+
+To contribute a new feature or fix:
+
+- Do not commit directly to `main`
+- Instead, create a short‑lived branch:
+  - `feature/<topic>` for new functionality
+  - `fix/<issue>` for bug fixes
+
+External contributors:
+
+1.  Fork the repo
+2.  Branch from `main` in your fork
+3.  Push and open a PR from your fork’s branch into `main`
+
+## Local Testing
+
+Before submitting a pull request, test your modifications by running the FEAScript library from a local directory. For example, you can load the library in your HTML file as follows:
+
+```javascript
+import { FEAScriptModel, plotSolution, printVersion } from "[USER_DIRECTORY]/FEAScript-core/src/index.js";
+```
+
+FEAScript can be run on a local server. Ensure you start the server from the workspace root directory, where both `FEAScript-core` and `FEAScript-website` folders are located, to correctly resolve relative paths in the HTML files. To start a local server, you can use [Python HTTP Server](https://docs.python.org/3/library/http.server.html):
+
+```bash
+python -m http.server
+```
+
+where the server will be available at `http://127.0.0.1:8000/`. Static file server npm packages like [serve](https://github.com/vercel/serve#readme) and [Vite](https://vite.dev/) can also be used.

README.md

@@ -6,7 +6,7 @@
 
 <!-- [![liberapay](https://img.shields.io/liberapay/receives/FEAScript.svg?logo=liberapay)](https://liberapay.com/FEAScript/) -->
 
-[FEAScript](https://feascript.com/) is a lightweight finite element simulation library built in JavaScript. It empowers users to create and execute simulations for physics and engineering applications in both browser-based and server-side environments. This is the core library of the FEAScript project.
+[FEAScript](https://feascript.com/) is a lightweight finite element simulation library written in JavaScript. It empowers users to create and execute simulations for physics and engineering applications in both browser-based and server-side environments. This is the core library of the FEAScript project.
 
 > 🚧 **FEAScript is currently under heavy development.** Its functionality and interfaces may change rapidly as new features and enhancements are introduced.
 
@@ -99,9 +99,9 @@ FEAScript also works well in interactive JavaScript notebook environments where
 
 For users who prefer a visual approach to creating simulations, we offer the [FEAScript Platform](https://platform.feascript.com/) - a browser-based visual editor built on the [Blockly](https://developers.google.com/blockly) library. This no-code interface allows you to:
 
-- Build and run finite element simulations directly in your browser by connecting visual blocks together
-- Create complex simulations without writing any JavaScript code
-- Save and load projects in XML format for easy sharing and reuse
+- Build and run finite element simulations directly in your browser by connecting visual blocks together.
+- Create complex simulations without writing any JavaScript code.
+- Save and load projects in XML format for easy sharing and reuse.
 
 While FEAScript's JavaScript API offers full programmatic control for advanced customization, the FEAScript Platform provides an accessible entry point for users without coding experience.
 

dist/feascript.cjs.js

@@ -13,7 +13,7 @@ import * as math from "mathjs";
 global.math = math;
 
 // Import FEAScript library
-import { FEAScriptModel, logSystem, VERSION } from "feascript";
+import { FEAScriptModel, VERSION } from "feascript";
 
 console.log("FEAScript Version:", VERSION);
 

dist/feascript.cjs.js.map

@@ -13,7 +13,7 @@ import * as math from "mathjs";
 global.math = math;
 
 // Import FEAScript library
-import { FEAScriptModel, logSystem, VERSION } from "feascript";
+import { FEAScriptModel, VERSION } from "feascript";
 
 console.log("FEAScript Version:", VERSION);