4d
diff --git a/‎crowdin.yml‎
Lines changed: 2 additions & 2 deletions b/‎crowdin.yml‎
Lines changed: 2 additions & 2 deletions
diff --git a/‎docs/API/ClassStoreClass.md‎
Lines changed: 58 additions & 0 deletions b/‎docs/API/ClassStoreClass.md‎
Lines changed: 58 additions & 0 deletions
diff --git a/‎docs/API/DataStoreClass.md‎
Lines changed: 1 addition & 1 deletion b/‎docs/API/DataStoreClass.md‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎docs/API/EmailObjectClass.md‎
Lines changed: 1 addition & 1 deletion b/‎docs/API/EmailObjectClass.md‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎docs/API/IMAPTransporterClass.md‎
Lines changed: 10 additions & 0 deletions b/‎docs/API/IMAPTransporterClass.md‎
Lines changed: 10 additions & 0 deletions
diff --git a/‎docs/Concepts/classes.md‎
Lines changed: 4 additions & 4 deletions b/‎docs/Concepts/classes.md‎
Lines changed: 4 additions & 4 deletions
diff --git a/‎docs/FormEditor/forms.md‎
Lines changed: 13 additions & 12 deletions b/‎docs/FormEditor/forms.md‎
Lines changed: 13 additions & 12 deletions
diff --git a/‎docs/ORDA/orda-events.md‎
Lines changed: 1 addition & 1 deletion b/‎docs/ORDA/orda-events.md‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎docs/Project/components.md‎
Lines changed: 2 additions & 2 deletions b/‎docs/Project/components.md‎
Lines changed: 2 additions & 2 deletions
diff --git a/‎docs/language-legacy/4D Environment/get-database-parameter.md‎
Lines changed: 1 addition & 1 deletion b/‎docs/language-legacy/4D Environment/get-database-parameter.md‎
Lines changed: 1 addition & 1 deletion
@@ -1,5 +1,5 @@
-commit_message: %original_file_name% %language%
-append_commit_message: false
+commit_message: '%original_file_name% %language%'
+append_commit_message: 
 files:
   - source: /docs/**/*
     ignore:
 
@@ -0,0 +1,58 @@
+---
+id: ClassStoreClass
+title: ClassStore
+---
+
+
+`4D.ClassStore` properties are available classes and class stores. 
+
+4D exposes two [class stores](../Concepts/classes.md#class-stores):
+
+- [`cs`](../commands/cs) for user classes and component class stores
+- [`4D`](../commands/4d) for built-in classes
+
+
+### Summary
+
+
+||
+|---|
+|[<!-- INCLUDE ClassStoreClass.classClassName.Syntax -->](#classclassname)<br/><!-- INCLUDE ClassStoreClass.classClassName.Summary -->|
+|[<!-- INCLUDE ClassStoreClass.classStoreName.Syntax -->](#classstorename)<br/><!-- INCLUDE ClassStoreClass.classStoreName.Summary -->|
+
+
+## *.classClassName*
+
+
+<!-- REF ClassStoreClass.classClassName.Syntax -->***.classClassName*** : 4D.Class<!-- END REF -->
+
+#### Description
+
+Each <!-- REF ClassStoreClass.classClassName.Summary -->exposed [`4D.Class`](./ClassClass.md) class in the class store<!-- END REF --> is available as a property of the class store.
+
+#### Example
+
+```4d
+var $myclass:=cs.EmployeeEntity
+	//$myclass is a class from the cs class store
+
+```
+
+
+## *.classStoreName*
+
+
+<!-- REF ClassStoreClass.classStoreName.Syntax -->***.classStoreName*** : 4D.ClassStore<!-- END REF -->
+
+#### Description
+
+Each <!-- REF ClassStoreClass.classStoreName.Summary -->`4D.ClassStore` published by a component<!-- END REF --> is available as a property of the class store.
+
+The name of the class store exposed by a component is the component namespace as [declared in the component's Settings page](../Extensions/develop-components.md#declaring-the-component-namespace).
+
+#### Example
+
+```4d
+var $classtore:=cs.AiKit
+	//$classtore is the class store of the 4D AIKit component
+```
@@ -53,7 +53,7 @@ A [Datastore](ORDA/dsMapping.md#datastore) is the interface object provided by O
 
 #### Description
 
-Each dataclass in a datastore is available as a property of the [DataStore object](ORDA/dsMapping.md#datastore)data. The returned object <!-- REF DataStoreClass.dataclassName.Summary -->contains a description of the dataclass<!-- END REF -->.
+Each dataclass in a datastore is available as a property of the [DataStore object](ORDA/dsMapping.md#datastore) data. The returned object <!-- REF DataStoreClass.dataclassName.Summary -->contains a description of the dataclass<!-- END REF -->.
 
 #### Example
 
 
@@ -27,7 +27,7 @@ This class is [**streamable**](../Concepts/dt_object.md#binary-streaming-variabl
 
 Email objects provide the following properties:
 
-> 4D follows the [JMAP specification](https://jmap.io/spec-mail.html) to format the Email object.
+> 4D follows the [JMAP specification](https://jmap.io/spec/rfc8621/) to format the Email object.
 
 ||
 |---|
 
@@ -158,6 +158,16 @@ $flags["$seen"]:=True
 $status:=$transporter.addFlags(IMAP all;$flags)
 ```
 
+#### See also
+
+[`.removeFlags()`](#removeflags) 
+
+
+#### See also
+
+[`.removeFlags()`](#removeflags) 
+
+
 <!-- END REF -->
 
 <!-- REF IMAPTransporterClass.append().Desc -->
 
@@ -52,8 +52,8 @@ You can also remove the .4dm class file from the "Classes" folder on your disk.
 
 Available classes are accessible from their class stores. Two class stores are available:
 
-- [`cs`](../commands/cs) for user class store
-- [`4D`](../commands/4d) for built-in class store
+- [`cs`](../commands/cs) for user classes and component class stores
+- [`4D`](../commands/4d) for built-in classes
 
 
 #### `cs`
@@ -67,7 +67,7 @@ Available classes are accessible from their class stores. Two class stores are a
 
 |Parameter|Type||Description|
 |---|---|---|---|
-|classStore|Object|&#8592;|User class store for the project or component|
+|classStore|[4D.ClassStore](../API/ClassStoreClass.md)|&#8592;|User class store for the project or component|
 </div>
 <!-- END REF -->
 
@@ -90,7 +90,7 @@ $instance:=cs.myClass.new()
 
 |Parameter|Type||Description|
 |---|---|---|---|
-|classStore|Object|&#8592;|4D class store|
+|classStore|[4D.ClassStore](../API/ClassStoreClass.md)|&#8592;|4D class store|
 </div>
 <!-- END REF -->
 
 
@@ -67,6 +67,16 @@ You can add or modify 4D forms using the following elements:
 }
 ```
 
+### Project form and Table form
+
+There are two categories of forms:
+
+- **Project forms** - Independent forms that are not attached to any table. They are intended more particularly for creating interface dialog boxes as well as components. Project forms can be used to create interfaces that easily comply with OS standards.
+
+- **Table forms** - Attached to specific tables and thus benefit from automatic functions useful for developing applications based on databases. Typically, a table has separate input and output forms.
+
+Typically, you select the form category when you create the form, but you can change it afterwards.
+
 
 ## Using forms
 
@@ -82,12 +92,12 @@ Forms are called using specific commands of the 4D Language. In your 4D desktop
 
 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)).
+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 draws an 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](../Develop/async.md#event-listening). When you call this command without asterisk (\*), the dialog will stay on screen and the code execution is frozen until an event occurs.
 3. (optional) Use the [`Form`](../commands/form) command from within the form context to access form data. 
 
 
-::note Compatibility
+:::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. 
 
@@ -246,15 +256,6 @@ There are several other ways to use forms in the 4D applications, including:
 - 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:
-
-- **Project forms** - Independent forms that are not attached to any table. They are intended more particularly for creating interface dialog boxes as well as components. Project forms can be used to create interfaces that easily comply with OS standards.
-
-- **Table forms** - Attached to specific tables and thus benefit from automatic functions useful for developing applications based on databases. Typically, a table has separate input and output forms.
-
-Typically, you select the form category when you create the form, but you can change it afterwards.
 
 ## Form pages
 
 
@@ -155,7 +155,7 @@ This event is triggered each time a value is modified in the entity.
 
 This event is triggered as soon as the 4D Server / 4D engine can detect a modification of attribute value which can be due to the following actions:
 
-- in **client/server with the [`local` keyword](../ORDA/ordaClasses.md#local-functions)** or in **4D single-user**:
+- in **client/server with the [`local` keyword](../Concepts/classes.md#local)** or in **4D single-user**:
     - the user sets a value on a 4D form,
     - the 4D code makes an assignment with the `:=` operator. The event is also triggered in case of self-assignment (`$entity.attribute:=$entity.attribute`).
 - in **client/server without the `local` keyword**: some 4D code that makes an assignment with the `:=` operator is [executed on the server](../commands/execute-on-server).
 
@@ -335,7 +335,7 @@ The Dependency manager checks periodically if component updates are available on
 
 #### Naming conventions for 4D version tags
 
-If you want to use the [**Follow 4D Version**](#defining-a-github-dependency-version-range) dependency rule, the tags for component releases must comply with specific conventions. 
+If you want to use the [**Follow 4D Version**](#defining-a-dependency-version-range) dependency rule, the tags for component releases must comply with specific conventions. 
 
 - **LTS versions**: `x.y.p` pattern, where `x.y` corresponds to the main 4D version to follow and `p` (optional) can be used for patch versions or additional updates. When a project specifies that it follows the 4D version for *x.y* LTS version, the Dependency Manager will resolve it as "the latest version x.*" if available or "version below x". If no such version exists, the user will be notified. For example, "20.4" will be resolved by the Dependency manager as "the latest component version 20.\* or version below 20". 
 
@@ -459,7 +459,7 @@ The following status labels are available:
 - **Duplicated**: The dependency is not loaded because another dependency with the same name exists at the same location (and is loaded). 
 - **Available after restart**: The dependency reference has just been added or updated [using the interface](#monitoring-project-dependencies), it will be loaded once the application restarts.  
 - **Unloaded after restart**: The dependency reference has just been removed [using the interface](#removing-a-dependency), it will be unloaded once the application restarts.   
-- **Update available \<version\>**: A new version of the dependency matching your [component version configuration](#defining-a-github-dependency-version-range) has been detected.   
+- **Update available \<version\>**: A new version of the dependency matching your [component version configuration](#defining-a-dependency-version-range) has been detected.   
 - **Refreshed after restart**: The [component version configuration](#defining-a-dependency-version-range) of the dependency has been modified, it will be adjusted at the next startup.   
 - **Recent update**: A new version of the dependency has been loaded at startup.  
 
 
@@ -1436,7 +1436,7 @@ In previous releases, time values were converted and stored as number of millise
 
 **Possible values:** 0 = legacy print rendering disabled, 1 = legacy print rendering enabled
 
-**Description:** Sets or gets the current status of the [legacy print renderer](../../FormEditor/forms.md#legacy-print-rendering) on macOS or Windows. When the legacy print renderer is *disabled*, 4D’s [modern print rendering engine](../../FormEditor/forms.md) is used. Note that when forms are rendered under Liquid Glass (macOS) or Fluent UI (Windows) interfaces, this selector is ignored (in such contexts forms are always printed using the modern print renderer, see [this section](../../FormEditor/forms.md#legacy-print-rendering)). In converted projects, this parameter can also be set permanently using a [compatibility setting](../../settings/compatibility.md). 
+**Description:** Sets or gets the current status of the [legacy print renderer](../../FormEditor/forms.md#legacy-print-renderer) on macOS or Windows. When the legacy print renderer is *disabled*, 4D’s [modern print rendering engine](../../FormEditor/forms.md) is used. Note that when forms are rendered under Liquid Glass (macOS) or Fluent UI (Windows) interfaces, this selector is ignored (in such contexts forms are always printed using the modern print renderer, see [this section](../../FormEditor/forms.md#legacy-print-renderer)). In converted projects, this parameter can also be set permanently using a [compatibility setting](../../settings/compatibility.md).
Original file line number	Diff line number	Diff line change
`@@ -1436,7 +1436,7 @@ In previous releases, time values were converted and stored as number of millise`
`1436`	`1436`
`1437`	`1437`	`Possible values: 0 = legacy print rendering disabled, 1 = legacy print rendering enabled`
`1438`	`1438`
`1439`		-Description: Sets or gets the current status of the [legacy print renderer](../../FormEditor/forms.md#legacy-print-rendering) on macOS or Windows. When the legacy print renderer is disabled, 4D’s [modern print rendering engine](../../FormEditor/forms.md) is used. Note that when forms are rendered under Liquid Glass (macOS) or Fluent UI (Windows) interfaces, this selector is ignored (in such contexts forms are always printed using the modern print renderer, see [this section](../../FormEditor/forms.md#legacy-print-rendering)). In converted projects, this parameter can also be set permanently using a [compatibility setting](../../settings/compatibility.md).
	`1439`	+Description: Sets or gets the current status of the [legacy print renderer](../../FormEditor/forms.md#legacy-print-renderer) on macOS or Windows. When the legacy print renderer is disabled, 4D’s [modern print rendering engine](../../FormEditor/forms.md) is used. Note that when forms are rendered under Liquid Glass (macOS) or Fluent UI (Windows) interfaces, this selector is ignored (in such contexts forms are always printed using the modern print renderer, see [this section](../../FormEditor/forms.md#legacy-print-renderer)). In converted projects, this parameter can also be set permanently using a [compatibility setting](../../settings/compatibility.md).
`1440`	`1440`
`1441`	`1441`
`1442`	`1442`