fix versions 21 pages switch

.github/workflows/workflow-build.yml

@@ -55,6 +55,10 @@ jobs:
         run: |
           cd build
           echo "google-site-verification: google1a6263055b2bea44.html" >> google1a6263055b2bea44.html
+      - name: Fix version-dropdown links
+        uses: doc4d/doc_postprocessing@v1
+        with:
+          path: ./build
       - uses: actions/upload-artifact@v4
         with:
           path: ./build

README.md

@@ -203,6 +203,7 @@ Aller dans l'interface Algolia et lancer un reindex de la doc
 3. faire git rebase upstream/main -X ours (remettre tout dans Tempo et en cas de conflit prendre la preprod)
 4. git push (fait une PR auto et pas de conflit)
 
+5. En cas de conflits résolus: sur la preprod sur github, cliquer sur **Sync Fork**.
 
 ## Building new architecture for sorted themes
 ### Edit the sidebars.js file
@@ -405,3 +406,7 @@ Translate commit (apply + commit) — pour appliquer et committer
 | 164 (¤) | a_contient_keyword |
 | default | (assert) |
 
+## Fix pour le switch de version entre 21.x et 21 R+ (changement de structure)
+un swizzle :
+https://github.com/doc4d/docs/commit/c20dca17cde1993756ceb632253e0b8144ed7529
+

crowdin.yml

@@ -1,3 +1,5 @@
+commit_message: New Crowdin updates
+append_commit_message: false
 files:
   - source: /docs/**/*
     ignore:

docs/API/IMAPTransporterClass.md

@@ -46,7 +46,7 @@ IMAP Transporter objects are instantiated with the [IMAP New transporter](../com
 
 ## 4D.IMAPTransporter.new()
 
-<!-- REF #4D.IMAPTransporter.new().Syntax -->**4D.IMAPTransporter.new**( *server* : Object ) : 4D.IMAPTransporter<!-- END REF -->
+<!-- REF #4D.IMAPTransporter.new().Syntax -->**4D.IMAPTransporter.new**( *parameter* : Object ) : 4D.IMAPTransporter<!-- END REF -->
 
 
 <!-- REF #4D.IMAPTransporter.new().Params -->

docs/Develop/async.md

@@ -63,7 +63,7 @@ The calling process posts a message then the worker executes it. The worker can
 
 ### Event listening
 
-In event-driven development, it is obvious that some code must be able to listen for incoming events. Events can be generated by the user interface (such as a mouse click on an object or a keyboard key pressed) or by any other interaction such as an http request or the end of another action. For example, when a form is displayed using the `DIALOG` command, user actions can trigger events that your code can process. A click on a button will trigger the code associated to the button. 
+In event-driven development, it is obvious that some code must be able to listen for incoming events. Events can be generated by the user interface (such as a mouse click on an object or a keyboard key pressed) or by any other interaction such as an http request or the end of another action. For example, when a form is displayed using the [`DIALOG`](../commands/dialog) command, user actions can trigger events that your code can process. A click on a button will trigger the code associated to the button. 
 
 In the context of asynchronous execution, the following features place your code in listening mode:
 

docs/FormEditor/forms.md

@@ -67,6 +67,185 @@ You can add or modify 4D forms using the following elements:
 }
 ```
 
+
+## Using forms
+
+Forms are called using specific commands of the 4D Language. In your 4D desktop applications, forms can be used in various ways, depending on their status within your interface needs. A form can be:
+
+- used in its own window for data viewing, processing, editing, or to display on-screen information to the user,
+- used embedded in another form (subform),
+- used as template for printing,
+- or called by specific features like the Label editor. 
+
+
+### Using a project form in a window
+
+When you want to use a form as on-screen dialog, you need to (1) create a window and (2) load the form within the window, along with an event loop to process user actions. The straighforward steps to display a form on screen are:
+
+1. Call the [`Open form window`](../commands/open-form-window) command to create and preconfigure a window tailored for your form. Note that the command only draw aan empty window, it does not display anything.
+2. In the same method, call the [`DIALOG`](../commands/dialog) command to actually load the form in the opened form window, ready for user interaction. [`DIALOG`](../commands/dialog) loads form data and places your code in listening mode to user events. When you call this command without asterisk (\*), the dialog will stay on screen and the code execution is frozen until an event occurs (see also ["Event listening" paragraph](../Develop/async.md#event-listening)).
+3. (optional) Use the [`Form`](../commands/form) command from within the form context to access form data. 
+
+
+::note Compatibility
+
+All-in-one commands such as [`ADD RECORD`](../commands/add-record) or [`MODIFY RECORD`](../commands/add-record) merge all steps in a single call. These legacy commands can still be used for prototyping or basic developments but are not adapted to modern, fully controlled interfaces. They directly rely on the 4D database and legacy features such as [table forms](#project-form-and-table-form) and do not benefit from the power and flexibility of [ORDA features](../ORDA/overview.md). Unless specific needs, it is recommended to use project forms for your 4D desktop application interfaces. 
+
+:::
+
+
+#### Simple example
+
+You create the following basic form in the [Form editor](./formEditor.md):
+
+![](../assets/en/FormEditor/example-form-1.png)
+
+The form is [associated with a "myForm" class](./properties_FormProperties.md#form-class), defined as follow:
+
+```4d
+    //cs.myForm
+property name : Text
+property age : Integer
+
+Class constructor
+  This.name:=""
+  This.age:=0
+```
+
+The form class is automatically instantiated by 4D once the form is loaded. If you execute the following project method:
+
+```4d
+    // Instantiate a form object that will host form data and UI logic
+var $formObject:=cs.myForm.new()
+
+    //Prepare default value within the form object
+$formObject.name:="Smith"
+$formObject.age:=42
+
+    // Create an empty window with ad-hoc settings that fits the desired form dimensions, resizing properties,
+    // and window type (this does not render the form)
+var $win:=Open form window("myForm"; Movable form dialog box; Horizontally centered; Vertically centered)
+
+    //Render the form, and provide $formObject's data. Dialog also activates the form event loop
+DIALOG("myForm"; $formObject)
+
+    //Without asterisk to Dialog statement, the form waits for a closing action from the user 
+    //before executing the rest of the code. Calling Close window is just a good practice 
+CLOSE WINDOW($win) //releases reference
+
+    //Display data modified by the user, if any/
+ALERT($formObject.name+" is "+String($formObject.age)+" years old!")
+
+```
+
+4D displays:
+
+![](../assets/en/FormEditor/example-form-2.png)
+
+
+### Using forms as subforms
+
+A form can be embedded within another form, in which case it becomes a [subform object](../FormObjects/subform_overview.md) which follows specific rules. A subform is automatically used when its parent form is [displayed in a window](#using-a-project-form-in-a-window).
+
+In the same way that you pass an object to a form with the [`DIALOG`](../commands/dialog) command, you can also pass an object to a subform area using the property list. Then, you can use it in the subform with the [`Form`](../commands/form) command. In this example, the "InvoiceAddress" object is bound to the subform:
+
+![](../assets/en/FormEditor/subform-example.png)
+
+
+
+### Using forms to be printed
+
+In 4D desktop applications, forms can be printed using the various [commands of the **Printing** theme](../commands/theme/Printing). 
+
+#### Examples
+
+You can use forms to print data, either as page or as list. 
+
+- To simply print some part of a form, use the [`Print form`](../commands/print-form) command. For example:
+
+```4d
+var $formData:={}
+$formData.lastname:="Smith"
+$formData.firstname:="john"
+$formData.request:="I need more COFFEE"
+var $h:=Print form("Request_var";$formData;Form detail)
+```
+
+- To print a form within a printing job to process data during printing, use [`FORM LOAD`](../commands/form-load) and [`Print object`](../commands/print-object) commands. For example:
+
+```4d
+ var $formData : Object
+ var $over : Boolean
+ var $full : Boolean
+
+ OPEN PRINTING JOB
+ $formData:={}
+ $formData.LBcollection:=[]
+ ... //fill the collection with data
+
+ FORM LOAD("GlobalForm";$formData) 
+ $over:=False
+ Repeat
+    $full:=Print object(*;"LB") // the datasource of this "LB" listbox is Form.LBcollection
+    LISTBOX GET PRINT INFORMATION(*;"LB";lk printing is over;$over)
+    If(Not($over))
+       PAGE BREAK
+    End if
+ Until($over)
+ FORM UNLOAD
+ CLOSE PRINTING JOB
+ ```
+
+
+#### Print rendering engine
+
+4D uses a dedicated print rendering engine to generate outputs with a design adapted for printing. It includes the following main features:
+
+- Interactive widgets such as buttons, toggles, dropdowns, etc. and modern UI effects such as glass, blur, transparency, or shadow effects are converted into adapted static representations and flattened into printable styles, so that the document remains readable and professional once printed.
+- Layout structure, spacing, and alignment, are preserved so that the printed document reflects the logical structure of the on-screen form.
+- The same output is produced, whether the form is printed from macOS or Windows.
+
+For example, the following form:
+
+![](../assets/en/FormEditor/screen_rendering.png)
+
+... will be printed with this rendering:
+
+![](../assets/en/FormEditor/print_rendering.png)
+
+
+:::tip Related blog post
+
+[Printing Modern Interfaces with Clean, Consistent Output](https://blog.4d.com/printing-modern-interfaces-with-clean-consistent-output)
+
+:::
+
+#### Legacy print renderer
+
+In releases prior to 4D 21 R3, another print renderer was used. This legacy renderer simply draws widgets as they appear on the screen. For compatibility, the legacy renderer is **enabled by default** in projects or databases converted from versions prior to 4D 21 R3, so that forms designed with this renderer continue to be printed as expected. 
+
+You can however enable the modern print rendering engine at any moment by:
+
+- unchecking the **Use legacy print rendering** option in the [Compatibility page of the Settings dialog box](../settings/compatibility.md) (permanent setting),
+- or executing [`SET DATABASE PARAMETER`](../commands/set-database-parameter) command with `Use legacy print rendering` selector set to 1 (volatile setting).
+
+:::warning Limitation
+
+For technical reasons, the legacy print renderer is not available with forms displayed with [Fluent UI](#fluent-ui-rendering) on Windows or [Liquid Glass](../Notes/updates.md#support-of-liquid-glass-on-macos) on macOS. In these contexts, forms are **always printed with the modern print rendering engine**, whatever the compatibility option. 
+
+:::
+
+
+
+### Other form usages
+
+There are several other ways to use forms in the 4D applications, including:
+
+- a form can be [inherited](#inherited-forms) from another form,
+- a form can be [associated to a listbox](../FormObjects/properties_ListBox.md#detail-form-name) in response to a user action to display a row using an edit button or a double-click,
+- the [label editor can use a form](../Desktop/labels.md#form-to-use) as template to print labels.
+
+
 ## Project form and Table form
 
 There are two categories of forms:
@@ -79,7 +258,7 @@ Typically, you select the form category when you create the form, but you can ch
 
 ## Form pages
 
-Each form has is made of at least two pages:
+Each form is made of at least two pages:
 
 - a page 1: a main page, displayed by default
 - a page 0: a background page, whose contents is displayed on every other page.
@@ -98,6 +277,8 @@ There are no restrictions on the number of pages a form can have. The same field
 A multi-page form has both a background page and several display pages. Objects that are placed on the background page may be visible on all display pages, but can be selected and edited only on the background page. In multi-page forms, you should put your button palette on the background page. You also need to include one or more objects on the background page that provide page navigation tools for the user.
 
 
+
+
 ## Fluent UI rendering
 
 :::caution Developer Preview

docs/FormEditor/properties_Print.md

@@ -8,7 +8,7 @@ title: Print
 
 Allows defining specific print settings for the form. This feature is useful to view printing page limits in the form editor. 
 
-> **Compatibility:** Even if these settings are taken into account when the form is printed in Application mode, it is discouraged to rely on this feature to store print settings for the form, due to limitations regarding the platform and driver dependency. It is highly recommended to use the 4D commands `Print settings to BLOB`/`BLOB to print settings` which are more powerful. 
+> **Compatibility:** Even if these settings are taken into account when the form is printed in Application mode, it is discouraged to rely on this feature to store print settings for the form, due to limitations regarding the platform and driver dependency. It is highly recommended to use the 4D commands [`Print settings to BLOB`](../commands/print-settings-to-blob)/[`BLOB to print settings`](../commands/blob-to-print-settings) which are more powerful. 
 
 You can modify the following print settings: 
 

docs/Notes/updates.md

@@ -18,6 +18,7 @@ Read [**What’s new in 4D 21 R3**](https://blog.4d.com/whats-new-in-4d-21-r3/),
 - New [**AI** page in Settings](../settings/ai.md), allowing to configure [Provider model aliases](../aikit/provider-model-aliases.md) that can be called in the code using 4D AIKit component. 
 - 4D AIKit component: new [Providers](../aikit/Classes/OpenAIProviders.md) class to instantiate and handle [Provider and model aliases](../aikit/provider-model-aliases.md). 
 - Support of [`server` keyword](../Concepts/classes.md#server) for ORDA data model functions and shared/session singleton functions. 
+- New [printing renderer](../FormEditor/forms.md#print-rendering-engine) for forms on Liquid glass and Fluent UI interfaces. New compatibility options to [enable the renderer on Classic interfaces](../FormEditor/forms.md#legacy-print-renderer). 
 - Dependencies: support of [components stored on GitLab repositories](../Project/components.md#configuring-a-gitlab-repository).
 - [**Fixed bug list**](https://bugs.4d.fr/fixedbugslist?version=21_R3): list of all bugs that have been fixed in 4D 21 R3.
 
@@ -74,7 +75,7 @@ Read [**What’s new in 4D 21 R2**](https://blog.4d.com/whats-new-in-4d-21-r2/),
 
 |Library|Current version|Updated in 4D|Comment|
 |---|---|---|----|
-|BoringSSL|9b86817|21|Used for QUIC|
+|BoringSSL|664a985|**21 R4**|Used for QUIC|
 |CEF|7258|21|Chromium 139|
 |Hunspell|1.7.2|20|Used for spell checking in 4D forms and 4D Write Pro|
 |ICU|77.1|21|This upgrade forces an automatic rebuild of alphanumeric, text and object indexes.|
@@ -84,7 +85,7 @@ Read [**What’s new in 4D 21 R2**](https://blog.4d.com/whats-new-in-4d-21-r2/),
 |Libuv |1.51.0|21|Used for QUIC|
 |libZip|1.11.4|21|Used by zip class, 4D Write Pro, svg and serverNet components|
 |LZMA|5.8.1|21||
-|ngtcp2|1.18.0|21|Used for QUIC|
+|ngtcp2|1.22.1|**21 R4**|Used for QUIC|
 |OpenSSL|3.5.2|21||
 |PDFWriter|4.7.0|21|Used for [`WP Export document`](../WritePro/commands/wp-export-document.md) and [`WP Export variable`](../WritePro/commands/wp-export-variable.md) |
 |SpreadJS|18.2.0|21 R2|See [this blog post](https://blog.4d.com/4d-view-pro-whats-new-in-4d-21-r2/) for an overview of the new features|

docs/WritePro/user/user-new.md

@@ -38,7 +38,7 @@ When the list is created using [the WP SET ATTRIBUTE command](../commands-legacy
 
 ### Multi-level lists
 
-Multi-level lists are based on [hierarchical list style sheets](stylesheets.md#hierarchical-list-style-sheets). Multi-level lists contain a root-level style sheet and one or more sub-level style sheet(s). Each level is attached to a hierarchical list style sheet and represents a depth in the list (level 1, level 2, level 3, etc.). 
+Multi-level lists are based on [hierarchical list style sheets](../user-legacy/stylesheets.md#hierarchical-list-style-sheets). Multi-level lists contain a root-level style sheet and one or more sub-level style sheet(s). Each level is attached to a hierarchical list style sheet and represents a depth in the list (level 1, level 2, level 3, etc.). 
 
 When a new sub-level is created, the level numbering restarts at 1. When you add or remove an element in your multi-level list, the numbers are automatically adjusted.
 
@@ -48,7 +48,7 @@ Multi-level lists are created with command [WP New style sheet](../commands/wp-n
 
 Multi-level lists can be managed using:
 
-* paragraph [style sheet attributes](../commands/4d-write-pro-attributes.md#style-sheets) (such as `wk list level index`, `wk list level count`, and `wk list concat string format`)
+* paragraph [style sheet attributes](../commands-legacy/4d-write-pro-attributes.md#style-sheets) (such as `wk list level index`, `wk list level count`, and `wk list concat string format`)
 * dedicated [standard actions](../user-legacy/standard-actions.md) for level management (`listLevelAppend`, `listLevelInc`, `listLevelDec`)
 * dedicated standard actions for numbering marker management (`listConcatStringFormat`, `listNumberFormat`).
 
@@ -64,11 +64,11 @@ Multi-level lists can be managed using:
 
 ## Hierarchical list style sheets
 
-Hierarchical list style sheets are used to create [multi-level lists](using-a-4d-write-pro-area.md#multi-level-lists).
+Hierarchical list style sheets are used to create [multi-level lists](../user-legacy/using-a-4d-write-pro-area.md#multi-level-lists).
 
 To create a hierarchical list style sheet, use [WP New style sheet](../commands/wp-new-style-sheet.md) and pass in *listLevelCount* the desired number of levels. You then define a hierarchy of related paragraph style sheets: one **root-level** style sheet and one or more **sub-level** style sheets linked to it. Each level represents a depth in the list (level 1, level 2, level 3, etc.) and is automatically named "root-level name + lvl + index", for example "Mylist lvl 2".
 
-To customize hierarchical list styles, the paragraph style sheet object can be customized using [style sheet attributes](../commands/4d-write-pro-attributes.md#style-sheets).
+To customize hierarchical list styles, the paragraph style sheet object can be customized using [style sheet attributes](../commands-legacy/4d-write-pro-attributes.md#style-sheets).
 
 Hierarchical list style sheets are fully supported by the following commands: [`WP Get style sheet`](../commands/wp-get-style-sheet.md), [`WP SET ATTRIBUTES`](../commands/wp-set-attributes.md), [`WP DELETE STYLE SHEET`](../commands/wp-delete-style-sheet.md).