Différences

Ci-dessous, les différences entre deux révisions de la page.

--- en:editeur:presentation [2026/10/09 23:47] – Documentation 4.16 : generation et mises a jour de l'editeur cyrilfiesta
+++ en:editeur:presentation [2026/10/20 22:06] (Version actuelle) – Mod?les sur_place, port?e des encadr?s et objets 4.17 cyrilfiesta
@@ Ligne 9: / Ligne 9: @@
   * **Web**: the //Editor// button in the site header.
   * **Desktop**: the //Editor// button in the application.
-The scenario stays on your machine until you export it.
 ===== Main interface =====
@@ Ligne 18: / Ligne 16: @@
   * **Graph** (centre) - a visual map of every room and their connections
   * **Inspector** (right panel) - detailed editing of the selected room
-  * **Globals panel** (⚙️ icon) - variables, global events, permanent timers, aliases
+  * **Globals panel** - variables, global events, permanent timers, aliases
   * **Toolbar** (top) - Test, Linter, Export, Undo/Redo and Save buttons
@@ Ligne 28: / Ligne 26: @@
 ===== Editor profiles =====
-The button in the top right corner decides what the inspector shows:
+**View > Open Editor Profile** selects the fields shown in the inspector:
-  * **Simplified** - hides the advanced fields, ideal to start with
+  * **Simplified** - hides the advanced fields, for a first scenario
   * **Essential** - the common features, without the rare settings
   * **Expert** - every field visible, for complex scenarios
@@ Ligne 52: / Ligne 50: @@
 ===== Generate rooms =====
-**Tools → Generate rooms…** prepares a route using one of six structures. The result opens in a separate tab: fill in the text, test, then import the rooms you want into your scenario. See [[en:editeur:generation|Room generation]] for settings, directions, numbered choices and optional models.
+**Tools > Generate rooms...** prepares a route using one of six structures. The result opens in a separate tab: fill in the text, test, then import the rooms you want into your scenario. See [[en:editeur:generation|Room generation]] for settings, directions, numbered choices and optional models.
 ===== File formats =====
@@ Ligne 58: / Ligne 56: @@
 The editor works with the ''.jdrproj'' format (internal JSON). It can:
-  * **Import** an existing ''.yaml'' file (''File → Import YAML'')
+  * **Import** an existing ''.yaml'' file (''File > Import YAML'')
-  * **Export** to ''.yaml'' (''File → Export YAML'')
+  * **Export** to ''.yaml'' (''File > Export YAML'')
   * **Export** to standalone HTML5 or to a PDF gamebook
@@ Ligne 72: / Ligne 70: @@
 ===== Palettes and visual styles (v4.10) =====
-The game interface and the editor come with **palettes** (colours) and **styles** (layout), freely combinable.
+The game interface and the editor come with **palettes** (colors) and **styles** (layout), freely combinable.
 ^ Palette ^ Description ^
 | ''sombre'' | Dark background, high contrast (default) |
-| ''neutre'' | Neutral grey, with no colour cast |
+| ''neutre'' | Neutral grey, with no color cast |
 | ''clair'' | Light background, for daytime reading |
-| ''bonbons'' | Colourful and soft, meant for children and sensitive eyes |
+| ''bonbons'' | Colorful and soft, meant for children and sensitive eyes |
 | ''reverie'' | Calm pastel blue, mint and pink, a soothing mood |
@@ Ligne 89: / Ligne 87: @@
 | ''reverie-s'' | Soft and airy gamebook |
-Palettes carry the colours, styles carry the layout: they combine freely.
+Palettes carry the colors, styles carry the layout: they combine freely.
 ===== Room groups (v4.10) =====
@@ Ligne 95: / Ligne 93: @@
 Groups organise the rooms visually inside the graph, with no effect on the exported YAML.
-  * View menu → **Manage groups…** lists every group with its number of rooms
+  * View menu > **Manage groups...** lists every group with its number of rooms
   * Renaming a group to an existing name offers to **merge** the two
   * Groups are purely visual: no impact on gameplay or on the export
@@ Ligne 101: / Ligne 99: @@
 ===== Room order and numbering (v4.10) =====
-  * The room list shows the **exported number** next to the identifier (''1 - start'', ''2 - corridor''…)
+  * The room list shows the **exported number** next to the identifier (''1 - start'', ''2 - corridor''...)
   * **Drag and drop** in the list changes the YAML export order
   * Typing a number in the Position field moves the room and renumbers the others consistently
+===== Data and controls (4.17) =====
+Web/Desktop forms support [[en:yaml:listes-boucles|lists, collections and loops]] and [[en:yaml:raccourcis|keyboard, mouse and gamepad shortcuts]]. Large projects use pagination and search to limit the number of displayed fields.
+During a test, **Test data** opens current values in a separate window. Diagnostics open the relevant field: see [[en:editeur:linter-export|Linter and author tests]].
+===== Models, objects and HUD panels =====
+In a [[en:yaml:modeles|model]] definition, insertion into the calling room corresponds to ''inline: true'' and requires one internal room. Each generic collection can also provide defaults for missing properties.
+In [[en:yaml:objets|objects]], **Display name** is folded when empty. **Secret item**, near the location, simplifies the form while retaining furniture description and button. Hidden fields keep their values. **Rename an item**, in the Objects effect family, has separate object and new display-name fields; an empty value restores the identifier.
+Every [[en:yaml:hud|HUD panel]] offers **Clear when leaving the room**, unchecked by default. It exports ''scope: room''; omitting scope preserves the historical persistent behaviour. These settings support undo/redo and FR/EN YAML import/export.
+[[en:yaml:listes-boucles|Structured data]] supports descriptions at every level and tags on roots. Names, values and descriptions remain grouped in the same form.