Release note and uniformization

dazoulay-simplicite · dazoulay-simplicite · commit 7dadb1feeb43 · 2026-01-09T12:19:50.000+01:00
diff --git a/docs/docs/front/icons.md b/docs/docs/front/icons.md
@@ -47,7 +47,7 @@ It is possible to override the default icon sets, which can be useful if you are
 
 In this case, use the **Icons set** field of the Theme to specify your resource. Call it `IMAGES_COLOR` if you want to override the color set.
 
-Javascript API
+JavaScript API
 --------------
 
 To use an icon in your JS code, use the following API:
diff --git a/docs/docs/front/javascript-dev.md b/docs/docs/front/javascript-dev.md
@@ -1,9 +1,9 @@
 ---
 sidebar_position: 30
-title: Javascript Development
+title: JavaScript Development
 ---
 
-Javascript Development
+JavaScript Development
 ======================
 
 :::warning
@@ -178,7 +178,7 @@ Explore examples for different environments:
 - **React Native**: [Mobile demo](https://github.com/simplicitesoftware/react-native-demo)
 - **Within Simplicité**: [Demo module](https://github.com/simplicitesoftware/module-demo-jslib)
 
-Core Javascript usage
+Core JavaScript usage
 ---------------------
 
 ### External Objects (Embedded Widgets)
diff --git a/docs/docs/integration/webservices/git-repositories.md b/docs/docs/integration/webservices/git-repositories.md
@@ -229,7 +229,7 @@ If required, you can specify additional settings to change the ESLint&reg; confi
 
 ```json
 {
-  "eslintConfig": "<default|<Javascript resource name>>"
+  "eslintConfig": "<default|<JavaScript resource name>>"
 }
 ```
 
diff --git a/docs/make/userinterface/externalobjects/basic.md b/docs/make/userinterface/externalobjects/basic.md
@@ -52,7 +52,7 @@ All **External Objects** are organized as web elements, thus are composed of 3 [
 
 - **HTML** is the resource containing the _HTML_ code of your object that defines its core structure and organization.
 - **STYLES** is the resource containing the stylesheet (_CSS_ or _LESS_) associated with your object's _HTML_.
-- **CLASS** is the resource with the Javascript logic inside of which you will code the behaviors and interactions for your External Object.
+- **CLASS** is the resource with the JavaScript logic inside of which you will code the behaviors and interactions for your External Object.
 
 And in addition, all external objects works with a **Java Class** that ensures both their proper setup, and the rendering of the web resources.
 
@@ -115,7 +115,7 @@ How to create
        @Override
        public Object display(Parameters params) {
            try {
-               // Call the render Javascript method implemented in the SCRIPT resource
+               // Call the render JavaScript method implemented in the SCRIPT resource
                // ctn is the "div.extern-content" to fill on UI
                return javascript(getName() + ".render(ctn);");
            }
@@ -148,7 +148,7 @@ Read More
 
 **Tips & Advices**:
 
-- [Javascript Development](/docs/front/javascript-dev).
+- [JavaScript Development](/docs/front/javascript-dev).
 - [Ajax Library](/docs/front/lib-ajax).
 
 **Details & Specificities**:
diff --git a/docs/make/userinterface/externalobjects/staticsite.md b/docs/make/userinterface/externalobjects/staticsite.md
@@ -12,13 +12,13 @@ What is a Static Web Site?
 Simplicité's [External Objects](/make/userinterface/externalobjects/basic) allow you to create **Static Web Site** objects;
 standalone web pages used to display elements without necessarily being logged nor necessarily interacting with any feature from Simplicité's backend.
 
-In other terms it is a static site that you create using either the native web stack (HTML, CSS, Javascript)
+In other terms it is a static site that you create using either the native web stack (HTML, CSS, JavaScript)
 or any popular web frameworks (Vue.js, React Angular, etc.).
 
 :::tip
 
 If the static site interacts with Simplicité's backend it is **highly** recommended
-to use [our simplified Javascript client lib](https://www.npmjs.com/package/simplicite) especially if it is based on a web framework.
+to use [our simplified JavaScript client lib](https://www.npmjs.com/package/simplicite) especially if it is based on a web framework.
 
 :::
 
@@ -86,7 +86,7 @@ Specific use case and code examples can be found in the following pages:
 
 **CLASS**:
 
-- Javascript where you declare all of your component's behavior and interactions.
+- JavaScript where you declare all of your component's behavior and interactions.
 - Most happens in the `async render(){ ... }` method.
 - Access your HTML using `const $content = this.ctn;` and then `$content.html(...)`.
   > You can also use more classic ways to access your elements like `document.getElementById()` or `$(<element-identifier>)`.
diff --git a/docs/make/userinterface/externalobjects/uicomponent.md b/docs/make/userinterface/externalobjects/uicomponent.md
@@ -100,7 +100,7 @@ There are 2 different categories for your external object's implementation:
    - `com.simplicite.webapp.web.ResponsiveExternalObject` by default
    - Can be overridden by a java code extending `ResponsiveExternalObject` or at least `ExternalObject` (the main parent class).
 
-2. The _workflow_ and _behavior_ that is done using the _Javascript Resource_.
+2. The _workflow_ and _behavior_ that is done using the _JavaScript Resource_.
    - JS class extending `Simplicite.UI.ExternalObject`
    - Implementing the `render()` method to handle the DOM-related instantiations.
    - Declaring any other custom behaviors or features.
@@ -426,7 +426,7 @@ The key concepts and understanding that you need are:
 You may need to implement some behaviors and features specifically on the _server-side_ (though in the java code).
 Such workflow is required when you don't want to share information with the front (public) or you just want the calculations to be done by the backend.
 
-1. **Javascript:** make a call to the [service](https://platform.simplicite.io/current/jsdoc/Simplicite.UI.ExternalObject.html#service) hook,
+1. **JavaScript:** make a call to the [service](https://platform.simplicite.io/current/jsdoc/Simplicite.UI.ExternalObject.html#service) hook,
    and pass the  and data needed as arguments.
 
    ```javascript
@@ -632,5 +632,5 @@ Read More
 
 **JS Dev**:
 
-- [Javascript Development](/docs/front/javascript-dev).
+- [JavaScript Development](/docs/front/javascript-dev).
 - [Ajax Library](/docs/front/lib-ajax).
diff --git a/docs/make/userinterface/externalobjects/webpage.md b/docs/make/userinterface/externalobjects/webpage.md
@@ -79,7 +79,7 @@ public class _ extends com.simplicite.webapp.web.WebPageExternalObject { // repl
     @Override
     public String displayBody(Parameters params) {
         try {
-            // Call the render Javascript function implemented in the SCRIPT resource
+            // Call the render JavaScript function implemented in the SCRIPT resource
             return javascript(getName() + ".render();");
         }
         catch (Exception e) {
@@ -162,5 +162,5 @@ Read More
 
 **JS Dev**:
 
-- [Javascript Development](/docs/front/javascript-dev).
+- [JavaScript Development](/docs/front/javascript-dev).
 - [Ajax Library](/docs/front/lib-ajax).
diff --git a/docs/make/userinterface/resources.md b/docs/make/userinterface/resources.md
@@ -21,7 +21,7 @@ Resource types
 | Image       | Image file that can be used in a publication                      |
 | Style CSS   | CSS stylesheet for customizing the UI                             |
 | Object icon | Icon set                                                          |
-| Javascript  | Javascript file for front-end customization                       |
+| JavaScript  | JavaScript file for front-end customization                       |
 | HTML        | Used for the content of a publication                             |
 | Markdown    | Store a Markdown file                                             |
 | PDF         | Store a PDF file in the application for use in business process   |
diff --git a/docs/versions/release-notes/v5-0.md b/docs/versions/release-notes/v5-0.md
@@ -30,7 +30,7 @@ This means the recommended JVM to run the platform is still an **up to date JVM*
 Rhino
 -----
 
-Implementing server side logic (hooks) using the Rhino (server-side Javascript) is now considered **deprecated**,
+Implementing server side logic (hooks) using the Rhino (server-side JavaScript) is now considered **deprecated**,
 this possibility will be removed in next major version (v6), then only Java server logic will be possible.
 
 Converting your existing Rhino scripts to Java class is thus highly recommended.
diff --git a/docs/versions/release-notes/v6-1.md b/docs/versions/release-notes/v6-1.md
@@ -283,7 +283,7 @@ Post-release
 - Backported improvements on the counters widget
 - Allowed `ObjectContext` message with suggestion
 - Backported the permission merge action on list to merge same permissions on several groups
-- Backported possibility to implement external object script as a Javascript class
+- Backported possibility to implement external object script as a JavaScript class
   extending `Simplicite.UI.ExternalObject` (and overriding the `render` class function)
 - Fixed notepad fields losing their current content in case of validation error of the form
 
diff --git a/docs/versions/release-notes/v6-2.md b/docs/versions/release-notes/v6-2.md
@@ -270,8 +270,8 @@ UI changes
 - For example, if the user changes a field twice and returns to its original value,
   the dialog "quit without saving" will no longer appear.
 
-- It is now possible - and recommended - to implement a `ResponsiveExternalObject` Javascript script
-  as a **Javascript class** extending `Simplicite.UI.ExternalObject`
+- It is now possible - and recommended - to implement a `ResponsiveExternalObject` JavaScript script
+  as a **JavaScript class** extending `Simplicite.UI.ExternalObject`
   with an override of the `render` class function, e.g.:
 
 ```javascript
@@ -586,7 +586,7 @@ Post-release
 - Fixed issue where the list ordering preference was shown even when the object's configuration wasn't relevant (i.e. no field areas visible on the list)
 - Backported [from v6.3](v6-3#new-helper-methods) new `Tool.before/after` date comparison shorthand methods
 - Fixed missing standard packages/classes in the public Java API (e.g. the annotations package)
-- Fixed resource name of generated external object's Javascript resource (`CLASS` instead of legacy `SCRIPT`)
+- Fixed resource name of generated external object's JavaScript resource (`CLASS` instead of legacy `SCRIPT`)
 
 ### 6.2.18 (2025-10-31) {#version-6.2.18}
 
diff --git a/docs/versions/release-notes/v6-3.md b/docs/versions/release-notes/v6-3.md
@@ -600,7 +600,7 @@ Note: compilation warnings are non-blocking but should be resolved rather than i
 The list of possible compiler options are described
 [in the Eclipse documentation](https://help.eclipse.org/latest/index.jsp?topic=%2Forg.eclipse.jdt.doc.user%2Ftasks%2Ftask-using_batch_compiler.htm).
 
-### Javascript console tool
+### JavaScript console tool
 
 New global variable `$console`, by default:
 
@@ -1130,7 +1130,7 @@ Post-release
 
 ### 6.3.0-RC5 (UNRELEASED) - release candidate 5 {#version-6.3.0-beta-RC5}
 
-- Upgraded Java libs
+- Upgraded Java and JavaScript libs
 - Fixed "Readonly form" contextual helps not displaying
 - Added parameter `USE_SSE` to disable the server-side-event services when not available/usable
 - Added the stylistic stylelint plugin and associated rules to lint the module's custom CSS/LESS resources
diff --git a/docs/versions/release-notes/v7-0.md b/docs/versions/release-notes/v7-0.md
@@ -246,7 +246,7 @@ to reflect not only the actual content of these files but also the needs of curr
 :::warning
 
 The case of `.stylelint-configuration` is more than just an additional extension to the file name,
-the content of the configuration was using the legacy JSON syntax, now it uses the modern Javascript syntax.
+the content of the configuration was using the legacy JSON syntax, now it uses the modern JavaScript syntax.
 
 :::
 
@@ -255,7 +255,7 @@ To migrate your existing module linting configurations (depending on your module
 - **Rename** your Checkstyle configuration if present (e.g. `mv .checkstyle-configuration .checkstyle-configuration.xml`)
 - **Rename** your JSHint configuration if present (e.g. `mv .jshint-configuration .jshint-configuration.json`)
 - **Rename** your ESLint configuration if present (e.g. `mv .eslint-configuration .eslint-configuration.mjs`)
-- **Refactor** as Javascript your StyleLint configuration if present (e.g. `mv .stylelint-configuration .stylelint-configuration.mjs`)
+- **Refactor** as JavaScript your StyleLint configuration if present (e.g. `mv .stylelint-configuration .stylelint-configuration.mjs`)
 
 **Alternatively** you can just commit your module so as the new configuration files are generated and compare your existing configuration files
 to the newly generated ones (which also contains new rules). Once merged you can remove the old configuration files.
diff --git a/src/components/PlatformBlock/index.js b/src/components/PlatformBlock/index.js
@@ -170,7 +170,7 @@ export default function PlatformBlock({
             </div>
             <div className={styles.bodyRight}>
               <div className={styles.subBlock}>
-                <h3>Javascript</h3>
+                <h3>JavaScript</h3>
                 <div className={styles.blockItems}>
                   {jsResources.base.map((r,i) => (
                       <div key={`js-${i}`} className={styles.blockItem}>

Original file line number	Diff line number	Diff line change
`@@ -229,7 +229,7 @@ If required, you can specify additional settings to change the ESLint® confi`
`229`	`229`
`230`	`230`	```json
`231`	`231`	`{`
`232`		`- "eslintConfig": "<default\|<Javascript resource name>>"`
	`232`	`+ "eslintConfig": "<default\|<JavaScript resource name>>"`
`233`	`233`	`}`
`234`	`234`	```
`235`	`235`