cell/merge | Paragraph, Cell | Used with paragraphs: merges paragraphs. Used with cells: merges the selected cells. | +| minHeight | {paragraph \| image/}minHeight?value=
cell/split | Paragraph, Cell | Used with paragraph: splits paragraph. Used with cells: splits the selected cells (only cells that have been already merged may be split). | +| styleSheet | {paragraph \| image/}styleSheet?value={1<=number<=number of target style sheets} | Paragraph, Image, Submenu, showDialog | Applies Nth stylesheet to the selected target elements. With dialog, new stylesheet will use current attributes from the first selected target. (default target is paragraph) Ex: styleSheet?value=1 //apply first paragraph style sheet to the selected paragraphs and set it as paragraph stylesheets. | +| styleSheets | {paragraph \| image/}styleSheets | Paragraph, Image, Submenu | Default submenu for editing target stylesheets. | +| tabDecimalSeparator | tabDecimalSeparator?value={point \| comma \| pointOrComma \| system} | Document, Submenu | Defines the character used as decimal separator by decimal tabulations. | +| tableAlign | tableAlign?value={left \| center \| right}
or
table/tableAlign?value={left \| center \| right} | Table, Submenu | Specifies horizontal alignment for a table. | +| table/avoidPageBreakInside | table/avoidPageBreakInside | Table | Allows/disallows page breaks inside tables. Disabled if: the current selection does not contain at least one table the table is in a header or a footer | +| table/bottomCarryOverRow | table/bottomCarryOverRow | Table | Toggles between display/not display of carry-over rows (see Carry-over rows). | +| textAlign | textAlign?value={left \| right \| center \| justify \| initial} | Paragraph | Paragraph text alignment (initial=use right for rtl or left for ltr direction). | +| textBox | textBox | Submenu | Submenu with all actions available for the focused/selected text box | +| textBox/remove | textBox/remove | TextBox | Removes the selected text box | +| textIndent | textIndent?value=
| Data row | 1 | yes | The datasource formula must return iterable elements | If the table does not have header rows and/or break row(s), the data row is the first row of the table - otherwise, it is the first row following either the header or the break row(s). It is usually filled with expressions using **This** (e.g. *This.item.value*) that give access to processed data when the document is in *Display values* mode and the row is duplicated. | +| 
| Sort break rows | up to 5 | \- | The datasource formula must return iterable elements | The row(s) appearing before or after the data row. See *Break rows* | +| 
| Bottom carry-over row | 1 | \- | The datasource formula must return iterable elements | The first row following the data row or the break row(s). See *Carry-over rows* | +|  | Placeholder row | 1 | \- | The datasource must be defined | placeholder row is to be displayed instead of the data row and the break rows (if any) when the datasource is empty and the "Show placeholder row" attribute is set on the table via the standard action *emptyDatasource*or the constant *wk empty datasource*. The placeholder row comes immediately before the other rows. | +| | Other rows | unlimited | \- | \- | Standard rows (not duplicated) | | + +Example (*Show references* mode): + + + +When the formulas are computed, the data row is automatically duplicated as needed to match all entities or collection items returned by the datasource formula: + + + +In any cases, the following statement returns the actual number of rows: + +```4d + WP GET ATTRIBUTES($table;wk row count;$vcount) //31 for the example above +``` + +### Carry-over rows + +Tables based on datasources support **bottom carry-over rows** that are automatically displayed at the bottom of each page/column when the table is split over more than one page/column. A carry-over row can display extra information based on previously displayed/printed items, thanks to the **This.previousItems** expression (see *Expressions with This*). This feature allows you, for example, to add subtotal rows. + + + +Carry-over rows are displayed: + +* when a datasource table does not fit in a single page (or column) +* at the bottom of the table +* on the first page (or first column) and all other ones except on the last one. + +**Important:** Carry-over rows are only available on tables filled by a datasource formula returning a non-empty collection or entity selection and in display values mode. In all other cases or when the datasource formula has not been computed, a carry-over row is displayed as a regular row. + +To create carry-over rows: + +1. In the table template, add a row just after the data row or the break row(s) and insert any necessary formulas inside, using for example **This.previousItems**. +2. Enable the carry-over row feature for your document. You can: +\- use the *bottomCarryOverRow* standard action (see *Using 4D Write Pro standard actions*), or +\- use the [WP SET ATTRIBUTES](../commands/wp-set-attributes) command with the wk bottom carry over row *Tables* attribute selector. + +**Note:** Page breaks inside rows are not allowed when the carry-over row feature is enabled (see *Table pagination*). Corresponding options, if set, are ignored. + +### Break rows + +Tables based on datasources support one or several **Sort Break Rows** that can be displayed either before or after the data row. S**ort Break Rows** help you to visually divide your already sorted datasource items in your table into different parts based on a computed formula value. + + + +Each time the formula value changes, a new break row is inserted. Therefore, for tables to be rendered correctly, the entity selection (or collection) used as table datasource **must be sorted accordingly**. For example, if breaks by countries and cities are wanted, then the datasource must be sorted as follows: *ds.people.all().orderBy("country asc, city asc")* + +The break value is defined through the *wk break formula* attribute. Value is usually a formula based on an item property like "This.item.name'', otherwise the computed value may never change which makes the break formula useless. The *wk break formula* attribute is ignored if the table has no datasource or if the row is a header. A break row must be adjacent to the data row (either before or after), or to another break row, otherwise it is ignored. + +```4d + WP SET ATTRIBUTES($row_2;wk break formula;Formula(This.item.country)) +``` + +Thanks to the **This.breakItems** expression you can use this feature, for example, to display the total average of the data rows within one break row. breakItems is an evaluated subset of the table datasource, either an entity selection if the table datasource is an entity selection, or a collection if the datasource is a collection. So, inside a break row, you can type: *This.breakItems.sum("salary")* + +To create break rows: + +1. Order the datasource with the levels corresponding to the breaks you want to display, for example, *ds.People.all().orderBy("continent asc, country asc, city asc")* +2. Draw the break row(s) in the table template. If the breaks are located after the data row, they must match the **opposite sort order** as the datasource, and if they are located before the data row, they must match **the same sort order** as the datasource. +3. Set the attribute *wk break formula* to the selected row(s): + +```4d + $row:=WP Table get rows($table;2;1) //select the second row as break + WP SET ATTRIBUTES($row_2;wk break formula;Formula(This.item.country)) +``` + +### Expressions with This + +When used in a formula within the table, the **This** keyword gives access to different data according to the context: + +| **Context** | **Expression** | **Type** | **Returns** | +| --------------------------------------------------------------------------------------------------- | ---------------------------------------- | -------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Anywhere | This.table | Object | Current table | +| | This.row | Object | Current table row element | | +| | This.rowIndex | Number | Index of the current row, starting from 1 | | +| When a datasource has been defined for the table | This.table.dataSource | Object (formula) | Datasource as a formula | +| | This.tableData | Collection or Entity selection (usually) | Evaluated table.dataSource | | +| In each data row when a table datasource returns a collection or an entity selection | This.item.xxx | Any | Mapped to each item of the table datasource collection or entity selection, for example **This.item.firstName** if the associated entity has the *firstName* attribute | +| | This.itemIndex | Number | Index of the current item in the collection or entity selection, starting from 0 | | +| In any row (except header rows) when a table datasource returns a collection or an entity selection | This.previousItems | Collection or Entity selection | Items displayed on the pages before the bottom carry over row (if any) or before the row of the expression, including the page where is displayed the row containing the expression.
This expression returns the same type of value as the **This.tableData** expression. | +| In a break row | This.breakItems | Collection or Entity selection | Items of the collection or entity selection displayed in the rows between: the current break row and the previous break row of the same level (or the start of the table) if the break row(s) are displayed after the data row. the current break and the next break row of the same level (or the end of the table) if the break row(s) are displayed before the data row. | + +In any other contexts, these expressions will return *undefined*. + +**Note:** For more information about formula insertion, see [WP INSERT FORMULA](../commands/wp-insert-formula). + +### Working with a table datasource + +When a table is filled from a datasource, rows are automatically created when references are computed. You can insert or delete rows, edit cell contents, change the style, etc.: + + + +However, keep in mind that if the table datasource is recomputed, any modifications made on computed rows (except on the first row) are lost. On the other hand, since the first row is the data row, any modification made to this row will be propagated to all rows if the table datasource is recomputed. Same thing goes for break rows, any modifications made on computed break rows are lost, except for the template break rows (which can be located either at the end or the beginning of the table). + +For example: + + + +After recomputing expressions: + + + +When the cursor is inserted in a cell of a table filled with a datasource, a warning icon is displayed on the left side along with a tip that displays information: + + + +When formulas are displayed as references or when you save the document, only the first row is displayed/saved as template (if formulas are not frozen). + +When the formulas are frozen, the table becomes a standard table and the table datasource is reset. + +**Note:** *freezeExpressions* standard action does not recompute formulas. \ No newline at end of file diff --git a/docs/WritePro/user-legacy/importing-4d-write-documents.md b/docs/WritePro/user-legacy/importing-4d-write-documents.md new file mode 100644 index 00000000000000..82bc824e7dddb9 --- /dev/null +++ b/docs/WritePro/user-legacy/importing-4d-write-documents.md @@ -0,0 +1,225 @@ +--- +id: importing-4d-write-documents +title: Importing 4D Write documents +displayed_sidebar: docs +--- + +One of the main features of the new 4D Write Pro object is the ability to import and convert existing 4D Write documents. This will allow you to migrate applications that currently rely on the 4D Write plug-in. + +**Compatibility notes:** + +* Only 4D Write documents of the last generation ("4D Write v7") are supported. +* Copying-pasting from a 4D Write document to a 4D Write Pro area is not supported for the moment. A 4D Write document can only be imported using 4D Write Pro language commands. +* Carriage returns (CR) in formulas behave differently in 4D Write and 4D Write Pro. In 4D Write, they are always interpreted as paragraph breaks, whereas in 4D Write Pro they are interpreted as line breaks by default. To maintain CR in formulas as paragraph breaks in imported 4D Write documents, after conversion use: +```4d + WP SET ATTRIBUTES(wp;wk break paragraphs in formulas;wk true) +``` + +For more information, see *Managing formulas*. + +## How to import a 4D Write document + +4D Write Pro objects offer two ways to import 4D Write documents: + +* For 4D Write files stored on disk, you use the [WP Import document](../commands/wp-import-document) command, +* For 4D Write areas stored in BLOB fields, you use the [WP New](../commands/wp-new) command. + +For more information, please refer to the description of these commands. + +## Which properties will be recovered from 4D Write? + +To facilitate your migration from the 4D Write plug-in to 4D Write Pro, we want to support as many 4D Write features as possible in 4D Write Pro objects. + +This paragraph lists the 4D Write plug-in properties that are currently recovered in a 4D Write Pro area after an import using the [WP Import document](../commands/wp-import-document) or [WP New](../commands/wp-new) commands. + +Note however that a few differences can be seen, which are not considered as bugs. This is due, for example, to the default font used in 4D Write Pro for bullets, or small conversions in the Underline type. + +### Document info + +| **4D Write plug-in** | **4D Write Pro** | +| ------------------------ | --------------------------------------------- | +| Creation date & time | Available | +| Modification date & time | Available | +| Locked | Not available (use read-only object property) | +| Title | Available | +| Subject | Available (only plain text) | +| Author | Available | +| Company | Available | +| Notes | Available | + +### Document view parameters + +| **4D Write plug-in** | **4D Write Pro** | +| ------------------------- | ------------------------------------------------------------------ | +| View page mode | Not imported (use Document/Page view mode in the context menu) | +| View rulers | Not imported (use object property) | +| View frames | Not imported (use object property) | +| View header | Not imported (use object property) | +| View footer | Not imported (use object property) | +| View first page header | Not available | +| View first page footer | Not available | +| View pictures | Not available | +| View HScrollbar | Not imported (use hor. scrollbar object property) | +| View VScrollbar | Not imported (use vert. scrollbar object property) | +| View invisible characters | Not imported (use object property) | +| View references | Not imported (use [ST SET OPTIONS](../../commands/st-set-options)) | +| View column separators | Available (starting with v17) | +| View H Splitter | Not available | +| View V Splitter | Not available | +| View Wysiwyg | Not available | +| View zoom | Not imported (use Document/Zoom in the context menu) | + +### Document parameters + +| **4D Write plug-in** | **4D Write Pro** | +| -------------------- | ---------------------------------------------------------------- | +| Unit | Not imported (use Document/Measurement unit in the context menu) | +| Language | Not available | +| Count of columns | Available (starting with v17) | +| Column spacing | Available (starting with v17) | +| Widows & orphans | Available | +| Default tab | Available | +| Leading tab | Available | +| URL color | Not available | +| URL visited color | Not available | + +**Note:** The system separator (as returned by [GET SYSTEM FORMAT](../../commands/get-system-format)) is used as decimal separator for decimal tabs. You can change this parameter using the [WP SET ATTRIBUTES](../commands/wp-set-attributes) command. + +### Document pagination parameters + +| **4D Write plug-in** | **4D Write Pro** | +| ----------------------------------------------- | ---------------- | +| Page width | Available | +| Page height | Available | +| First page number | Available | +| First page header & footer are different | Available | +| Left & right page header & footer are different | Available | +| Page binding | Available | +| Opposite pages | Available | +| Page margins | Available | +| Header top margin | Available | +| Header bottom margin | Available | +| Footer top margin | Available | +| Footer bottom margin | Available | +| First page top margin | Available | +| First page bottom margin | Available | +| Header first page top margin | Available | +| Header first page bottom margin | Available | +| Footer first page top margin | Available | +| Footer first page bottom margin | Available | +| First page is right | Available | + +### Document printing parameters + +| **4D Write plug-in** | **4D Write Pro** | +| -------------------- | ---------------- | +| Kind of paper | Not available | +| Landscape | Not available | +| Width | Not available | +| Height | Not available | +| User margins | Not available | +| Scale | Not available | +| X resolution | Not available | +| Y resolution | Not available | + +### Images + +**Compatibility notes:** + +* Picture display modes are automatically imported as of 4D Write Pro v19 R2, using [WP Import document](../commands/wp-import-document). You can restore the previous behavior (all images are scaled to fit) using the *importDisplayMode* attribute. +* On Windows, images having the Mac OS PICT format are imported but cannot be rendered in 4D Write Pro. If you import a document containing images of this type, you need to convert them to another format. Support of PICT format has been removed since 4D v18 and can no longer be used. + +| **4D Write plug-in** | **4D Write Pro** | +| ---------------------------------- | ---------------------------------------------------- | +| X (left) | (& position :absolute) (for images in page only) | +| Y (top) | (& position :absolute) (for images in page only) | +| Width | Available | +| Height | Available | +| Page number | Available (starting with v16 R6) | +| Behind | Available (starting with v16 R6) | +| Not in first page | Available (starting with v16 R6) | +| Viewport mode (scale to fit, etc.) | Available | +| Is expression | Available for inline pictures (starting with v16 R5) | +| Keep size | Not imported (automatic in 4D Write Pro) | + +### Character properties + +| **4D Write plug-in** | **4D Write Pro (span properties)** | +| ------------------------------------------- | ---------------------------------- | +| Italic | Available | +| Bold | Available | +| Strikeout | Available | +| Underline | Available | +| Shadow | Available | +| Exponent (superscript or subscript) | Available | +| Capitals (uppercase or small uppercase) | Available | +| Font Family | Available | +| Font Size | Available | +| Text Color | Available | +| Text Back Color | Available | +| Underline Color | Available | +| Strikeout Color | Available | +| Shadow color | Available | +| User property | Not available | +| Spell checking (syntax & grammar on or off) | Not imported (area property) | +| Appearance | Not available | +| Style sheet | Available (starting with 4D v18) | + +### Paragraph properties + +| **4D Write plug-in** | **4D Write Pro** | +| ------------------------------------ | ---------------- | +| Justification | Available | +| Interline | Available | +| Bullet | Available | +| Left margin | Available | +| Right margin | Available | +| Text indent | Available | +| Border line style | Available | +| Border line color | Available | +| Border back color | Available | +| Left border | Available | +| Right border | Available | +| Top border & top inside border | Available | +| Bottom border & bottom inside border | Available | +| Border spacing | Available | +| Style Sheet | Available | +| Tabulations | Available | + +### Hyperlinks + +| **4D Write plug-in** | **4D Write Pro** | +| -------------------- | ----------------------------------------- | +| URL link | Available (\*) | +| 4D method link | Available (\*\*) (starting with v17 R5) | +| Open document link | Available (converted to a local file URL) | + +* (\*) Starting with 4D v16 R4, URL links are converted to editable attributes. For more information, please refer to *Link commands*. +* (\*\*) You need to adapt parameters received within the called methods: + +| **Parameters** | **4D Write plug-in**| **4D Write Pro**| +| -------------- | ------------------- | --------------- | +| $1 | Longint - 4D Write area reference | Text - 4D Write Pro area name | +| $2 | Text - Link label | Object - Link description:.method - Link's method name. Must be be allowed with the [SET ALLOWED METHODS](../../commands/set-allowed-methods) command. .parameter - User parameter value passed to the method (if used).range - Range of the link's label. See *Range handling commands* | +| $3 | Longint - User parameter (methodRef) | \- | + +### 4D expressions + +| **4D Write plug-in** | **4D Write Pro** | +| -------------------- | ----------------- | +| 4D expression | Available\* | +| Date & Time | Available | +| HTML expression | Not available\*\* | +| RTF expression | Not available | + +\*Use the [WP SET ATTRIBUTES](../commands/wp-set-attributes) command with the wk break paragraphs in formulas attribute to transform CR returned by formulas into paragraph breaks in the imported document (line breaks by default). (See *Managing formulas*) + +\*\*can be imported as text between **##htmlBegin##** and **##htmlEnd##** tags if you use the wk import html expressions as text constant. + +### Text data + +| **4D Write plug-in** | **4D Write Pro** | +| -------------------- | ---------------- | +| Main text data | Available | +| Header text data | Available | +| Footer text data | Available | \ No newline at end of file diff --git a/docs/WritePro/user-legacy/importing-and-exporting-in-docx-format.md b/docs/WritePro/user-legacy/importing-and-exporting-in-docx-format.md new file mode 100644 index 00000000000000..bcdc273b549821 --- /dev/null +++ b/docs/WritePro/user-legacy/importing-and-exporting-in-docx-format.md @@ -0,0 +1,191 @@ +--- +id: importing-and-exporting-in-docx-format +title: Importing and Exporting in docx format +displayed_sidebar: docs +--- + +4D Write Pro can both import and export documents in the .docx format. This format is supported by word processing applications such as Microsoft Word. + +**Compatibility note**: Support for 4D Write Pro documents imported or exported in .docx format is only certified for Microsoft Word 2010 and newer. Older versions, particularly Microsoft Word 2007, may not be able to open the documents. + +## How to import .docx format + +Documents in .docx format can be imported into 4D Write Pro with the [WP Import document](../commands/wp-import-document) command. For more information, please refer to the description of this command. + +### Behavioral changes + +While the majority of .docx settings are preserved, some settings are known to be either unsupported or behave differently in 4D Write Pro. These are: + +#### Alignment / Layout + +| **Setting** | **Description**| +| -------- |----------- | +| Anchored text areas | Anchored text areas are imported as text boxes by default (they can also be ignored or imported as inline text, see [WP Import document](../commands/wp-import-document) command option). Only simple text areas can be imported. Inline text areas are imported as anchored in the front layer. Text areas anchored with text around are imported with their text wrapping properties (exception: the .docx wrapping option "tight" is imported as wrap square). | +| Paragraph layout | Only Western text layouts are supported. Distributed, Thai and Asian paragraph styles are not supported.| +| Page Size | Different page sizes per section are not supported. Only the page size from the first section is imported. | + +#### Background + +| **Setting** | **Description** | +| ----------- | --------------- | +| Watermark | Not supported | + +#### Expressions + +| **Setting** | **Description** | +| ----------------- | ------------------------------------ | +| MS Word equations | Not supported. Data is not imported. | +| MS Word charts | Not supported. Data is not imported. | + +#### Lists + +| **Setting** | **Description**| +| ----------- |--------------- | +| Hierarchical lists | Multi-level lists are not supported. Multi-level lists are converted to a single level lists so list appearance and/or numbering may be different | | + +#### Pictures / Images + +| **Setting** | **Description**| +| ----------- |--------------- | +| DrawingML shapes | Only simple DrawingML images (inline or anchored) are imported. Complex DrawingML shapes are not supported. | +| VML shapes or images | Not supported. VML is obsolete in MS Word and should not be used in documents created with MS Word 2010 or older. | +| 3D models | Not supported, however the last rendered 2D image of the 3D model may be imported if present in the .docx. | +| SmartArt | Not supported. | + +#### References / Review + +| **Setting** | **Description** | +| ----------- | --------------------------------------- | +| Comments | Not supported. Content is not imported. | +| Footnotes | Not supported. Content is not imported. | + +#### Spacing + +| **Setting**| **Description**| +| ----------- |--------------- | +| "At least" line spacing | Not supported. "At least" line spacing is converted to fixed (single) line spacing. | +| Fit text | Not supported. The normal 4D Write Pro style is used. | + +#### Tables + +| **Setting** | **Description** | +| ----------- | --------------------------------------------- | +| Tables | Contiguous tables do not merge automatically. | + +#### Text + +| **Setting**| **Description**| +| ----------- |--------------- | +| Themes | Text themes are not imported. If a color or font definition references a color or font in a theme, the last computed color or font will be used. Otherwise, the | +| color or font defined in the theme is used. | | + +### Import log + +When importing .docx format into 4D Write Pro, a log object is created and included within the imported document object. This object can be retrieved through the "importLog" custom attribute (or wk import log constant): + +```4d + $myDoc:=WP Import document("test.docx") + if($myDoc#Null) + var $log : Object + $log:=$myDoc[wk import log] + End if +``` + +The import log object contains the following properties: + +| Constant | Comment | +| ----------- |--------------- | +| wk import log | Log object containing information about the .docx import operation. Properties are read-only and cannot be set:
| **Property** | **Type** | **Description** | |
| status | Text | Import status: successful - the document is imported into 4D Write Pro failed - an empty 4D Write Pro document is returned | |
| developer | Collection | Collection of message object(s) for 4D Write Pro developers. | |
| \[ \].type | Text | The kind of message logged: info warning error | |
| \[ \].message | Text | Message about the import operation. | |
| user | Collection | Collection of message object(s) for 4D Write Pro users. | |
| \[ \].type | Text | The kind of message logged: info warning | |
| \[ \].messageShort | Text | Brief message about the import operation. | |
| \[ \].messageLong | Text | Extended message about the import operation. |
Range end offset, or section/subsection text end index in the document body (for subsection, text end index of the parent section).
**Value type**: Longint | +| `wk owner` | `owner` | *(Read-only attribute)*
Owner of the range/object/section/subsection (reference to the document for section/subsection).
**Value type**: Object | +| `wk start` | `start` | *(Read-only attribute)*
Range start offset, or section/subsection text start index in the document body (for subsection, text start index of the parent section).
**Value type**: Longint | +| `wk type` | `type` | *(Read-only attribute)* Type of 4D Write Pro object. Possible values:
- `wk type default`: Range or section with not defined type
- `wk type paragraph`: Paragraph type range
- `wk type image`: Image (anchored and inline)
- `wk type container`: Header or footer, for instance
- `wk type table`: Table reference
For ranges of cells, columns and rows only:
- `wk type table row`: Table row reference
- `wk type table cell`: Table cell reference
- `wk type table column`: Table column reference
For subsections only:
- `wk first page`: First page subsection
- `wk right page`: Right page subsection
- `wk left page`: Left page subsection | + +The ranges of rows, columns and cells of [tables](./handling-tables.md) have specific, private attributes allowing to define them: + +| Constant | Value | Comment | +|----------------------|------------------|---------| +| `wk cell count` | `cellCount` | Total number of cells in the row.
**Value type**: Longint *(value for `wk type table row`)* | +| `wk column count` | `columnCount` | *(Available for tables, documents and sections)* Number of columns.
**Value type**: Longint
For a table: read-only attribute
For a document or a section: read-write attribute. Default value = 1 (single column). Maximum value = 20 | +| `wk first column` | `firstColumn` | *(Read-only attribute)* Number of the first table column included in the range.
**Value type**: Longint | +| `wk first row` | `firstRow` | *(Read-only attribute)* Number of the first table row included in the range.
**Value type**: Longint | +| `wk header row count`| `headerRowCount` | *(Read/Write)* Number of rows of the table with the attribute `wk header` set to `True`.
Maximum value is 5. If you pass a value above 5, `wk header` is set to `True` for the first five rows only *(see [Repeated headers](./handling-tables.md#repeated-headers))*. | +| `wk row count` | `rowCount` | *(Read-only attribute)* Total number of rows.
**Value type**: Longint | +| `wk table` | `table` | *(Read-only attribute)* The parent table.
**Value type**: Object | +| `wk table ID` | `tableID` | *(Read-only attribute)* ID of the parent table.
**Value type**: String | + + + +Several commands allow you to define document ranges: +- [WP Text range](../commands-legacy/wp-text-range.md) returns a new range corresponding to boundaries you passed as parameters. +- [WP Selection range](../commands-legacy/wp-selection-range) returns a new range corresponding to the current user selection. +- [WP Picture range](../commands-legacy/wp-picture-range) returns a new range containing only the pictures. +- [WP Paragraph range](../commands-legacy/wp-paragraph-range) returns a new range containing only the paragraphs. +- [WP Table range](../commands-legacy/wp-table-range) returns a new range containing only the tables. + +You can get information about the position of a range in a document (page number, column number...) using the [`WP Get position`](../commands-legacy/wp-get-position) command. + + diff --git a/docs/WritePro/user-legacy/storing-4d-write-pro-documents-in-4d-object-fields.md b/docs/WritePro/user-legacy/storing-4d-write-pro-documents-in-4d-object-fields.md new file mode 100644 index 00000000000000..0d7a3fa05edff7 --- /dev/null +++ b/docs/WritePro/user-legacy/storing-4d-write-pro-documents-in-4d-object-fields.md @@ -0,0 +1,181 @@ +--- +id: 4d-write-pro-documents +title: 4D Write Pro documents +displayed_sidebar: docs +--- + + +## .4wp document format + +You can save and re-open 4D Write Pro documents to and from disk without any loss using the native **.4wp** format. + +The **.4wp** format consists of a zip folder whose name is the document title and whose contents are HTML text and images: + +* HTML text combines regular HTML with 4D expressions (which are not computed) as well as 4D-specific tags, +* images are stored in a folder with the same name as the document title, next to the HTML file. + +Since .4wp documents are based on HTML, they can be imported or opened in any external application supporting HTML. + +The 4D Write Pro internal document format is a proprietary HTML extension, compatible with HTML5/XHTML5, but which supports its own subset of HTML/CSS attributes and tags. As a result, only HTML documents exported by 4D Write Pro can be opened by 4D Write Pro without any risk of data loss. Importing HTML documents that were created externally could produce errors. + +For more information, you can [**download the list of 4D Write pro attributes with associated definition as CSS style or XHTML tag**](https://download.4d.com/Documents/Products%5FDocumentation/LastVersions/Line%5F19/4DWP-attributes-and-xhtml.pdf) in the 4D Write Pro XHTML. + +### Backward compatibility + +You can always reopen a .4wp document with a previous version of 4D Write Pro. If it contains attributes that were added in more recent versions, these attributes are just ignored. However, if you save the document, the attributes are removed from the document and will be lost. + + +## Storing 4D Write Pro documents in 4D Object fields + +You can store your 4D Write Pro documents automatically in the 4D data file. If you created a 4D Write Pro area on a form and created an Object field to store the area’s contents, any text entered in the area is saved automatically with each record when the record is validated. You can then use the [QUERY BY ATTRIBUTE](../../commands/query-by-attribute) command in order to select records based on the value of their internal attributes. You can also add and query your own attributes with 4D Write Pro areas. + +This section describes the following features: + +* Binding a 4D Object field to a 4D Write Pro area in a form +* Setting, getting, and querying custom attributes of stored 4D Write Pro documents using the [OB SET](../../commands/ob-set), [OB Get](../../commands/ob-get) standard object commands, and [QUERY BY ATTRIBUTE](../../commands/query-by-attribute). + +### Assigning a 4D Object field to a 4D Write Pro area + +To bind a 4D Write Pro area with a 4D Object field, you just need to reference the field in the Variable Name property of the area. + +### Creating the Object field in the Structure + +In your database structure, any 4D Object field can be used to store 4D Write Pro documents. As with any Object field, you just have to define its standard properties, according to your needs: + +* the field name, +* its attributes, such as "Expose as REST resource," as well as its index, +* its storage option. + + + +### Assigning the Object field to the 4D Write Pro area + +Once you have defined an Object field to store your 4D Write Pro document, you just need to reference it in the form containing the area. You can use any table or a project form. +In the Form editor, enter the field name using the standard "\[Table\]Field" notation in the **Variable or Expression** area of the Property list for the 4D Write Pro area: + + + +Your 4D Write Pro area is then associated with the field, ensuring that its contents will be saved automatically with each record. Note that if you do not use the 4D standard action buttons, you will have to save the area manually using 4D commands. + +### Using custom attributes + +When 4D Write Pro areas are stored in Object fields, you can save and read any custom attributes with the 4D Write Pro document, such as, for example, the writer's name, the document category, or any additional information you may find useful. You can then query your custom attributes to select records matching the criteria. + +Custom attributes will be exported with the [WP EXPORT DOCUMENT](../commands/wp-export-document) or [WP EXPORT VARIABLE](../commands/wp-export-variable) commands. They will be exported as well when converting a 4D Write Pro Object field to JSON using the [JSON Stringify](../../commands/json-stringify) command (along with the 4D Write Pro main document attributes). + +To set or get custom attributes, you just need to use object notation or the [OB Get](../../commands/ob-get) and [OB SET](../../commands/ob-set) commands. + +For example, in the form method, you can write: + +```4d + If(Form event code=On Validate) + [MyDocuments]My4DWP["myatt_Last edition by"]:=Current user + [MyDocuments]My4DWP.myatt_Category:="Memo" + [MyDocuments]My4DWP:=[MyDocuments]My4DWP //to record the edit + End if +``` + +or: + +```4d + If(Form event code=On Validate) + OB SET([MyDocuments]My4DWP;"myatt_Last edition by";Current user) + OB SET([MyDocuments]My4DWP;"myatt_Category";"Memo") + End if +``` + +You can also read custom attributes of the documents: + +```4d + vAttrib:=[MyDocuments]My4DWP.myatt_Category +``` + +or: + +```4d + vAttrib:=OB Get([MyDocuments]My4DWP;"myatt_Category") +``` + +If you have saved custom 4D Write Pro attributes in your data file, you can query these attributes to create a selection of records containing the appropriate attribute value. In the following example, you query the table containing the Object field to select records: + +```4d + QUERY BY ATTRIBUTE([MyDocuments];[MyDocuments]My4DWP;"myatt_Category";=;"Memo") + //selects all records in MyDocuments whose "myatt_Category" custom attribute has the value "Memo" + //in the My4DWP Object field (bound to a 4D Write Pro area) +``` + +:::warning About custom attribute names + +Since custom attributes share the same naming space as 4D Write Pro internal attributes, we strongly recommend that you use prefixes when defining your own attribute names in order to avoid any conflicts between internal and custom attributes. Non-prefixed names are reserved for 4D Write Pro internal attributes. You can use any custom prefix (for instance, we used "myatt\_" as a prefix in the above example). + +::: + +**Note:** Custom attributes cannot be handled by the [WP SET ATTRIBUTES](../commands/wp-set-attributes), [WP GET ATTRIBUTES](../commands/wp-get-attributes), and [WP RESET ATTRIBUTES](../commands/wp-reset-attributes) commands (they only support 4D Write Pro internal attributes). + + + + + +## Opening and exporting documents + +In 4D applications, 4D Write Pro documents are created, imported, and exported by means of specific commands found in the **4D Write Pro** theme ([WP EXPORT DOCUMENT](../commands/wp-export-document), [WP EXPORT VARIABLE](../commands/wp-export-variable), [WP Import document](../commands/wp-import-document), [WP New](../commands/wp-new)). + +You can also [associate a 4D Write Pro area with an Object field](../user-legacy/defining-a-4d-write-pro-area.md#storing-4d-write-pro-documents-in-4d-object-fields) of the database. This way, each 4D Write Pro document is automatically saved with the record and stored in the database's data. + + +## Printing 4D Write Pro documents + +4D Write Pro documents can be printed in two ways: + +* As parts of 4D forms +* As independent documents + +### Printing documents in 4D forms + +You can print 4D Write Pro embedded objects as part of any kind of [4D form](../../FormEditor/forms.md) (project, table, input, or output) using standard 4D printing commands such as [PRINT SELECTION](../../commands/print-selection) or [PRINT RECORD](../../commands/print-record). + +The standard *Print Variable Frame* option is also supported(\*) for 4D Write Pro areas, allowing you to manage size during printing. When this option is checked, the margins (outside and inside) and top border are only applied to the first page, and the margins (outside and inside) and bottom border are only applied to the last page. Pagination properties of the document are ignored: widow and orphan control is disabled and page breaks are not applied (these properties are only used for page rendering on screen, or for standalone printing of the document). When the **Print Variable Frame** option is selected, only objects located above the form area are printed. For more information about this option, refer to "*Print Variable Frame*" in the Design Reference manual. + +(\*) The [Print object](../../commands/print-object) and [Print form](../../commands/print-form) commands are not compatible with this option. + +#### View mode for printing + +Regardless of the **View mode** set for the 4D Write Pro area (see *Configuring View properties*), it is always printed as in the **Embedded** mode when you use a 4D printing command such as [Print form](../../commands/print-form). In this case, the following Appearance settings are not taken into account for the 4D Write Pro form objects: Page view mode (always "Embedded"), Show headers, Show footers, Show page frame (always "No"), Show hidden characters (always "No"). + +#### Example + +The following example shows the effect of the **Print Variable Frame** option on a 4D Write Pro area embedded in the default output form. The following code is executed: + +```4d + ALL RECORDS([Movies]) + ORDER BY([Movies]Title) + PRINT SELECTION([Movies]) +``` + +* Here is the result with the Print Variable Frame option **unchecked** (off): + +* Here is the result with the Print Variable Frame option **checked** (on): + + +*(Sample text source: Wikipedia)* + +### Printing independent documents + +Starting with 4D v15 R5, 4D Write Pro includes printing features allowing you to print independent 4D Write Pro documents as well as to control standard printing options such as the format, orientation, or page numbers. + +#### 4D Write Pro commands + +Basically, two commands handle the 4D Write Pro printing features: **WP PRINT** and **WP USE PAGE SETUP**. + +* [WP PRINT](../commands/wp-print) launches a print job for a 4D Write Pro document or adds the document to a current print job. +* [WP USE PAGE SETUP](../commands/wp-use-page-setup) modifies the current printer page settings based on the 4D Write Pro document attributes for page size and orientation. + +**Note:** On machines with Windows 7 or Windows Server 2008 R2, make sure that the *Platform Update for Windows 7* has been installed so that the printing features are supported. + +#### Regular 4D commands + +The following 4D commands support 4D Write Pro printing features: + +* [SET PRINT OPTION](../../commands/set-print-option) and [GET PRINT OPTION](../../commands/get-print-option): All options are supported for 4D Write Pro documents printed by [WP PRINT](../commands/wp-print). For Paper option and Orientation option, you may find it more efficient to call [WP USE PAGE SETUP](../commands/wp-use-page-setup) in order to easily synchronize these attributes with the 4D Write Pro document settings. The Page range option (15) allows you to specify the page range to print. +* [PRINT SETTINGS](../../commands/print-settings): Defines print settings for the current printer; if [WP PRINT](../commands/wp-print) is called afterwards, it takes any print settings modified by means of the Print Settings dialog boxes into account (except for margins, which are always based on the 4D Write Pro document). +* [OPEN PRINTING JOB](../../commands/open-printing-job) and [CLOSE PRINTING JOB](../../commands/close-printing-job): [WP PRINT](../commands/wp-print) can be called between these commands in order to insert one or more 4D Write Pro documents into a single print job. \ No newline at end of file diff --git a/docs/WritePro/user-legacy/stylesheets.md b/docs/WritePro/user-legacy/stylesheets.md new file mode 100644 index 00000000000000..c01538f2296cce --- /dev/null +++ b/docs/WritePro/user-legacy/stylesheets.md @@ -0,0 +1,141 @@ +--- +id: stylesheets +title: Style sheets +displayed_sidebar: docs +slug: /WritePro/user/stylesheets +--- + + +A style sheet is an object of defined set of attribute settings used to control the appearance of your 4D Write Pro documents. These settings can be applied to paragraphs and characters, such as the font to display, as well as the font's size, color, and weight. Once a style sheet is defined, it is saved as an object in the 4D Write Pro document so it can easily be reused. Style sheets let you give your documents a distinctive and unique appearance, while saving you time and effort. + + +## Default style + +All 4D Write Pro documents have a default paragraph style sheet, "Normal". New style sheets (created with the [WP New style sheet](../commands-legacy/wp-new-style-sheet) command) automatically inherit from the Normal style. Attributes modified by a style sheet effect only the paragraphs they are applied to, the rest of the document retains the default Normal settings. If a style sheet is removed, the modified attributes will revert to the Normal style. + +The Normal style defines a default value for every style sheet attribute in a 4D Write Pro document and can be retrieved with the [WP Get style sheet](../commands-legacy/wp-get-style-sheet) command. The Normal style sheet can be modified (but not renamed) with the [WP SET ATTRIBUTES](../commands/wp-set-attributes) command. While style sheets created with the [WP New style sheet](../commands-legacy/wp-new-style-sheet) command can be deleted with the [WP DELETE STYLE SHEET](../commands-legacy/wp-delete-style-sheet) command, the Normal style sheet can not be deleted. + +## Paragraph and character style sheet attributes + +Style sheets allow you to define the attributes of entire paragraphs or specific characters: + +- **Paragraph** - The vast majority of the attributes which can be modified apply only to paragraphs. Paragraph style sheets include character style settings, as well as formatting attributes that can only be applied at the paragraph level (e.g. margins, borders, tabs, etc.). +- **Character** - Character style sheets use only the attributes appropriate for distinquishing text (one or more characters) from the paragraph style (e.g., headers, titles, underlined text, etc.). + +Note that paragraph styles apply to whole paragraphs. To apply a style only to a specific part of a paragraph, you must use a character style sheet. + +## Style sheet precedence + +Multiple paragraph and character style sheets can be combined within the same 4D Write Pro document. It's important to note style sheet precedence is determined by the order they are applied. + +- If you apply a paragraph style sheet and then apply a character style sheet, the character style sheet will take precedence over the paragraph style sheet. For example, you could apply a paragraph style sheet to the body of your document, then you could create a "bold" character style sheet and apply it to specific words. The paragraph style sheet will still apply to the rest of the text, however the character style sheet will be prioritized for the designated words. +- If you apply a character style sheet and then apply a paragraph style sheet, the paragraph style sheet will be applied to all of the text and any character styles from the character style sheet will be removed. + + +## Applying style sheets + +Style sheets are applied with the [WP SET ATTRIBUTES](../commands/wp-set-attributes) command using the `wk style sheet` or `wk new line style sheet` constants (or using object notation). + +## Retrieving style sheets + +The [WP Get style sheets](../commands-legacy/wp-get-style-sheets) command lets you retrieve all style sheets in a document according to their specific type. The [WP Get style sheet](../commands-legacy/wp-get-style-sheet) command lets you retrieve a single style sheet by its name. + +## Importing and exporting style sheets + +Because style sheets are stored as objects, they can easily be imported into other 4D Write Pro documents or maintained when exported in multiple formats. + +- **Import** - You can get all of the style sheet objects from a designated 4D Write Pro document and use them in a new document with the [WP IMPORT STYLE SHEETS](../commands-legacy/wp-import-style-sheets) command. +- **Export** - The [WP EXPORT DOCUMENT](../commands/wp-export-document) or [WP EXPORT VARIABLE](../commands/wp-export-variable.md) commands export your documents with their style sheets. + + +## Style sheet attributes + +The following paragraph and character style sheet attributes can be modified with the [WP SET ATTRIBUTES](../commands/wp-set-attributes) and [WP RESET ATTRIBUTES](../commands/wp-reset-attributes) commands, or retrieved with the [WP GET ATTRIBUTES](../commands/wp-get-attributes) command. + +:::note + +Some attributes are linked together. Therefore when adding only one of these attributes, the other linked attributes will also be created with the default values. For linked attributes, the default value can be different than the value defined in the Normal style sheet. For example, if you define only a red left border, the other borders will be black (default value) even if the borders in the Normal style sheet were previously defined as purple. + +::: + + +| Attribute | Paragraph | Character | Linked With | +|----------------------------------|-----------|-----------|-------------| +| `wk avoid widows and orphans` | X | | | +| `wk background clip` | X | | | +| `wk background color` | X | X | | +| `wk background height` | X | | `wk background width` | +| `wk background image` | X | | | +| `wk background image url` | X | | | +| `wk background origin` | X | | | +| `wk background position horizontal` | X | | `wk background position vertical` | +| `wk background position vertical` | X | | `wk background position horizontal` | +| `wk background repeat` | X | | | +| `wk background width` | X | | `wk background height` | +| `wk border color` | X | | `wk border color bottom`, `wk border color left`, `wk border color right`, `wk border color top` | +| `wk border color bottom` | X | | `wk border color`, `wk border color left`, `wk border color right`, `wk border color top` | +| `wk border color left` | X | | `wk border color`, `wk border color bottom`, `wk border color right`, `wk border color top` | +| `wk border color right` | X | | `wk border color`, `wk border color bottom`, `wk border color left`, `wk border color top` | +| `wk border color top` | X | | `wk border color`, `wk border color bottom`, `wk border color left`, `wk border color right` | +| `wk border radius` | X | | | +| `wk border style` | X | | `wk border style bottom`, `wk border style left`, `wk border style right`, `wk border style top` | +| `wk border style bottom` | X | | `wk border style`, `wk border style left`, `wk border style right`, `wk border style top` | +| `wk border style left` | X | | `wk border style`, `wk border style bottom`, `wk border style right`, `wk border style top` | +| `wk border style right` | X | | `wk border style`, `wk border style bottom`, `wk border style left`, `wk border style top` | +| `wk border style top` | X | | `wk border style`, `wk border style bottom`, `wk border style left` | +| `wk border width` | X | | `wk border width bottom`, `wk border width left`, `wk border width right`, `wk border width top` | +| `wk border width bottom` | X | | `wk border width`, `wk border width left`, `wk border width right`, `wk border width top` | +| `wk border width left` | X | | `wk border width`, `wk border width bottom`, `wk border width right`, `wk border width top` | +| `wk border width right` | X | | `wk border width`, `wk border width bottom`, `wk border width left`, `wk border width top` | +| `wk border width top` | X | | `wk border width`, `wk border width bottom`, `wk border width left`, `wk border width right` | +| `wk direction` | X | | | +| `wk font` | X | X | `wk font bold`, `wk font italic`, `wk font size` | +| `wk font bold` | X | X | `wk font`, `wk font family`, `wk font italic`, `wk font size` | +| `wk font family` | X | X | `wk font`, `wk font bold`, `wk font italic`, `wk font size` | +| `wk font italic` | X | X | `wk font`, `wk font bold`, `wk font family`, `wk font size` | +| `wk font size` | X | X | `wk font`, `wk font bold`, `wk font family`, `wk font italic` | +| `wk line height` | X | | | +| `wk list font` | X | | | +| `wk list string format LTR` | X | | | +| `wk list string format RTL` | X | | | +| `wk list style image` | X | | | +| `wk list style image height` | X | | | +| `wk list style image url` | X | | | +| `wk list style type` | X | | | +| `wk margin` | X | | `wk margin bottom`, `wk margin left`, `wk margin right`, `wk margin top` | +| `wk margin bottom` | X | | `wk margin`, `wk margin left`, `wk margin right`, `wk margin top` | +| `wk margin left` | X | | `wk margin`, `wk margin bottom`, `wk margin right`, `wk margin top` | +| `wk margin right` | X | | `wk margin`, `wk margin bottom`, `wk margin left`, `wk margin top` | +| `wk margin top` | X | | `wk margin`, `wk margin bottom`, `wk margin left`, `wk margin right` | +| `wk min height` | X | | | +| `wk min width` | X | | | +| `wk name` | X | X | | +| `wk new line style sheet` | X | | | +| `wk owner` | X | X | | +| `wk padding` | X | | `wk padding bottom`, `wk padding left`, `wk padding right`, `wk padding top` | +| `wk padding bottom` | X | | `wk padding`, `wk padding left`, `wk padding right`, `wk padding top` | +| `wk padding box` | X | | | +| `wk padding left` | X | | `wk padding`, `wk padding bottom`, `wk padding right`, `wk padding top` | +| `wk padding right` | X | | `wk padding`, `wk padding bottom`, `wk padding left`, `wk padding top` | +| `wk padding top` | X | | `wk padding`, `wk padding bottom`, `wk padding left`, `wk padding right` | +| `_o_wk page break inside` | X | | | +| `wk tab default` | X | | `wk tabs`, `wk tab stop offsets`, `wk tab stop types`, `wk tab stop leadings` | +| `wk tabs` | X | | `wk tab default`, `wk tab stop offsets`, `wk tab stop types`, `wk tab stop leadings` | +| `wk tab stop offsets` | X | | `wk tabs`, `wk tab default`, `wk tab stop types`, `wk tab stop leadings` | +| `wk tab stop types` | X | | `wk tabs`, `wk tab default`, `wk tab stop offsets`, `wk tab stop leadings` | +| `wk tab stop leadings` | X | | `wk tabs`, `wk tab default`, `wk tab stop offsets`, `wk tab stop types` | +| `wk text align` | X | | | +| `wk text color` | X | X | | +| `wk text indent` | X | | | +| `wk text linethrough color` | X | X | | +| `wk text linethrough style` | X | X | `wk text underline style` | +| `wk text shadow color` | X | X | `wk text shadow offset` | +| `wk text shadow offset` | X | X | `wk text shadow color` | +| `wk text transform` | X | X | | +| `wk text underline color` | X | X | | +| `wk text underline style` | X | X | `wk text linethrough style` | +| `wk type` | X (read only) | X (read only) | | +| `wk vertical align` | X | X | | +| `wk width` | X | | | + + diff --git a/docs/WritePro/user-legacy/text-boxes.md b/docs/WritePro/user-legacy/text-boxes.md new file mode 100644 index 00000000000000..574e6de144c935 --- /dev/null +++ b/docs/WritePro/user-legacy/text-boxes.md @@ -0,0 +1,56 @@ +--- +id: text-boxes +title: Text boxes +displayed_sidebar: docs +slug: /WritePro/user/text-boxes +--- + + + +Text boxes are areas that are anchored to a page or a section and can be filled with text, inline pictures, or tables. Text boxes can be positioned anywhere on the page and meet specific needs, for example to insert a company’s name or logo or an address area. + + + +**Note:** A text box cannot contain headers, footers, columns, anchored images, or other text boxes. + +Text boxes are added with an absolute position, in front of/behind text, as well as anchored to a page or specific parts of a document in Page mode: header, footer, a section, all sections, or a subsection. Text boxes can also be used in embedded mode (anchored to the layer box). + +Adding a text box to a 4D Write Pro document can be accomplished in the following ways: + +* using the [`WP New text box`](../commands-legacy/wp-new-text-box.md) command, +* using the *insertTextBox* [standard action](./defining-a-4d-write-pro-area.md#standard-actions) + +To select a text box, the user has to click on it (**Ctrl/Cmd+click** if the text box is on the background layer). Once selected, the text box can be moved or resized using the mouse or arrow keys. + +To remove a selected text box, you can hit the **Delete** or **Backspace** key, use the **textBox/remove** standard action, or execute the [`WP DELETE TEXT BOX`](../commands-legacy/wp-delete-text-box.md) command. + +Text box attributes are handled with the [WP SET ATTRIBUTES](../commands/wp-set-attributes) command or [standard actions](./defining-a-4d-write-pro-area.md#standard-actions). The following attributes and actions are available: + +| **Property (constant)** | **Standard action** | **Comments** | +| ----------------------- | ------------------------- | --------------------------------------------------------------------------- | +| wk width | textBox/width | If set to "auto", width converted to 8cm as text box width cannot be "auto" | +| wk height | textBox/height | If set to "auto", height is adjusted to fit the contents | +| wk padding | textBox/padding | | +| wk border \[...\] | textBox/border\[...\] | | +| wk background \[...\] | textBox/background\[...\] | | +| wk vertical align | textBox/verticalAlign | | +| wk id | \- | cannot be empty for a text box | +| wk anchor \[...\] | textBox/anchor\[...\] | | +| wk owner | \- | read-only | +| wk protected | \- | | +| wk style sheet | \- | read-only and always "" (no style sheet) | + +Text boxes support automatic text wrapping when anchored to a document with options like on the left, right, largest side, above and below, or all around provided through the property wk anchor layout or the standard action **anchorLayout**. Check this [blog post](https://blog.4d.com/4d-write-pro-more-display-options-for-anchored-pictures-and-text-boxes/) for more details. + + + +Text boxes with text wrapping anchored to the body of the page do not affect the header or the footer (the text box is displayed in front of the header or the footer); on the contrary, text boxes anchored to the header and footer affect the body of the page if they overlap it. + +**Note**: If you want to anchor a text box with text wrapping to the header or footer, you must also set the vertical alignment of the text box to the top. + +Text boxes are not displayed if: + +* the view mode is Draft; +* they are centered or anchored to sections and the **Show HTML WYSIWYG** option is checked; +* the "visible background" option is not enabled. + diff --git a/docs/WritePro/user-legacy/using-a-4d-write-pro-area.md b/docs/WritePro/user-legacy/using-a-4d-write-pro-area.md new file mode 100644 index 00000000000000..badcb5bddd716d --- /dev/null +++ b/docs/WritePro/user-legacy/using-a-4d-write-pro-area.md @@ -0,0 +1,418 @@ +--- +id: using-a-4d-write-pro-area +title: Properties & Layout +displayed_sidebar: docs +slug: /WritePro/user/properties +--- + + + +## Basics + +When the document is in [**Page** view mode](./defining-a-4d-write-pro-area.md#selecting-the-view-mode), the following document properties are available for the user: + +* Page outlines to represent printing limits +* Page width and Page height (default: 21x29.7 cm) +* Page orientation (default: Portrait) +* Page margin (default: 2.5 cm) + +You can also use additional commands such as **Document.../Page size** or **Document.../Page orientation**. + +**Note:** When a document is in **Embedded** or **Draft** view mode, page properties can be set, even if their effect is not visible. In **Draft** view mode, the following paragraph property effects are visible: + +* Page height limitation (lines drawn) +* Columns +* Avoid page break inside property +* Widow and orphan control. + +## Paragraph breaks + +When displayed in Page or Draft mode (or in the context of a document printing), 4D Write Pro paragraphs can break: + +* automatically, if the paragraph height is greater than the available page height, +* depending on paragraph breaks set by programming or by the user. + +Breaks can be added by programming or by the user. Available actions include: + +* [WP INSERT BREAK](../commands/wp-insert-break) command +* *insertPageBreak* standard action +* **Insert page break** option of the default contextual menu + +### Controlling automatic breaks + +You can control automatic breaks in paragraphs using the following features: + +* **Widow and orphan control**: When this option is set for a paragraph, 4D Write Pro does not allow widows (last line of a paragraph isolated at the top of a page) or orphans (first line of a paragraph isolated at the bottom of a page) in the document. In the first case, the previous line of the paragraph is added to the top of the page so that two lines are displayed there. In the second case, the single first line is moved onto the next page. +* **Avoid page break inside**: When this option is set for a paragraph, 4D Write Pro prevents this paragraph from being broken into parts on two or more pages. +* **Keep with next:** When this option is set for a paragraph, that paragraph cannot be separated from the one that follows it by an automatic break. See `wk keep with next` and the corresponding *keepWithNext* [standard action](./defining-a-4d-write-pro-area.md#standard-actions). + +These options can be set using the context menu, or [attributes](../commands-legacy/4d-write-pro-attributes.md) (`wk avoid widows and orphans`, `wk page break inside paragraph`, or *widowAndOrphanControlEnabled* and *avoidPageBreakInside* [standard actions](./defining-a-4d-write-pro-area.md#standard-actions). + +## Background + +The background of 4D Write Pro documents and document elements (tables, paragraphs, sections, headers/footers, etc.) can be set with the following effects: + +* colors +* borders +* images +* origin, horizontal and vertical positioning +* painting area +* repeat + +These [attributes](../commands-legacy/4d-write-pro-attributes.md) can be defined programmatically for either individual elements on a page and/or entire document backgrounds with the [WP SET ATTRIBUTES](../commands/wp-set-attributes) command or by [standard actions](./defining-a-4d-write-pro-area.md#standard-actions). + +Users can modify background attributes via the contextual menu as shown below: + +  + +For an example of adding a full-sized image as a background, see the *How Do I* (HDI) demo [here](http://download.4d.com/Demos/4D%5Fv16%5FR5/HDI%5F4DWP%5FBackImagePaperBox.zip). + +## Headers, footers, and sections + +4D Write Pro documents support headers and footers. These headers and footers are related to sections. + +A section is a part of a document which is defined by a page range and can have its own paging and common attributes. A document can contain any number of sections (from just one, up to the total number of pages). Each page can only belong to one section, except pages with continuous section breaks (see below). + +4D Write Pro documents can contain: + +- one or more sections (one section by default) +- for each section, up to three subsections: + - first page subsection + - left page(s) subsection + - right page(s) subsection + +You can define a set of headers and footers for each section. + +### Defining a section + +A section is a subset of continuous pages in a 4D Write Pro document. A document can contain one or more sections. A section can contain any number of pages, from a single page to the total number of pages in the document. A section page can contain a single column or up to 20 column(s). + +By default, a document contains a single section, named **Section 1**. The 4D Write Pro contextual menu displays this section number wherever you click in the document: + + + +You create a new section by adding a section break in the text flow: + + + +When a section break has been added, the contextual menu displays an incremented number for each section. You can, however, rename any section: + + + +The name you entered is then used as the section name everywhere in the document: + +  + +Note that if you have defined a different first page or different left/right pages for a section, the page type is also displayed in the menu (see below). + +### Inserting a continuous section break + +A continuous section break creates a new section on the same page. This allows you to create pages with sections that have different numbers of columns (see *Creating a page with multiple-column and single column sections*). + +Sections created with continuous section breaks are counted in the document (they have section numbers), but unlike sections created with regular section breaks, their headers, footers, anchored images, etc. are only taken into account when a physical page break has occurred. + +**Note:** If you change the page orientation for the new section after you insert a continuous section break, it turns into a regular section break. + +### Section attributes + +Sections inherit attributes from the document. However, common document attributes, including headers and footers, can be modified separately for each section. The contextual pop-up menu displays the properties and attributes available at the section level: + + + +* **Page orientation**: allows you to set a specific page orientation (Portrait or Landscape) per section. +* **Different first page**: allows you to set different attributes for the first page of the section; this feature can be used to create flyleaves, for example. When this attribute is checked, the first page of the section is handled as a subsection itself and can have its own attributes. + + +* **Different left and right pages**: allows you to set different attributes for left and right pages of the section. When this attribute is checked, left and right pages of the section are handled as subsections and can have their own attributes. + + +* **Columns** commands: allow to define the number and properties of columns for the section. These options are detailed below. +* **Header** and **Footer** commands: these options allow you to define separate headers and footers. These options are detailed below. +* **Margins** / **Paddings** / **Borders** / **Background**: these attributes can be defined separately for each section. For more information on these attributes, please refer the *4D Write Pro Attributes* article. + +### Inserting headers and footers + +Each section can have specific header and footer. Headers and footers are displayed only when the document page view mode is **Page**. + + Within a section, you can define up to three different headers and footers, depending on the enabled options: + +* first page, +* left page(s), +* right page(s). + +To create a header or a footer: + +1. Make sure the document is in **Page** view mode. +2. Double-click in the header or footer area of the desired section and page to switch to editing mode. + * The header area is at the top of the page: +  + * The footer area is at the bottom of the page: +  + +You can then enter any static contents, which will be repeated automatically on each page of the section (except for the first page, if enabled). + + + +You can insert dynamic contents such as the page number or the page count using the [ST INSERT EXPRESSION](../../commands/st-insert-expression) command (for more information, please refer to the *Inserting document and page expressions* paragraph). + +**Note:** You can also handle footers and headers by programming using specific commands such as [WP Get header](../commands/wp-get-header) and [WP Get footer](../commands/wp-get-footer). + +Once a header or a footer has been defined for a section, you can configure its common attributes using the contextual menu: + + + +For more information on **Margins**, **Paddings**, **Borders**, and **Background** attributes, please refer the *4D Write Pro Attributes* section. + +You can remove the entire definition of a header or a footer (contents and attributes) by selecting the **Remove header** or **Remove footer** command in the contextual menu. + +### Compatibility + +4D Write Pro handles headers and footers of documents converted from the 4D Write plug-in with a fixed height. + +The following expressions and properties are also supported and converted from the 4D Write plug-in headers and footers: + +* page number and page count variables +* distinct first page +* distinct left/right pages + + +## Rulers + +Horizontal rulers are available in every viewing mode of 4D Write Pro and have the following characteristics: + +* Graduations in cm, mm, inches or pt according to current layout unit defined in the 4D Write Pro document. You can change measurement units using the context menu or by modifying the wk layout unit attribute. +* First line indent symbol +* Left paragraph margin symbol +* Right paragraph margin symbol +* Tabs displayed along lower edge of ruler +* Visible color contrast representing left and right page margins + +Vertical rulers are available in Page mode only and have the following characteristics: + +* Graduations in cm, mm, inches or pt according to current layout unit defined in the 4D Write Pro document. You can change measurement units using the context menu or by modifying the wk layout unit attribute. +* Visible color contrast representing top and bottom page margins + +You can change the display status of the rulers via standard actions (see *Using 4D Write Pro standard actions*) or by checking or unchecking the **Show horizontal ruler** or **Show vertical ruler** item in the context menu of the 4D Write Pro area: + + + +**Note:** A specific 4D Write Pro area property allows defining the default display for the rulers (see *Configuring View properties* section). + +### Adjusting text margins and indents + +#### Horizontal ruler + +You can modify the left and right margins, indents and tab positions by clicking and dragging the corresponding symbols on the horizontal ruler: + + + +When you hover the mouse over one of these symbols, the cursor changes to indicate that it can be moved, and a vertical guide line appears while you drag it: + + + +When multiple paragraphs are selected, dragging margin or indent symbols applies these margins or indents to all selected paragraphs. Holding down the **Shift** key while dragging these symbols maintains existing intervals between indents or margins in the selected paragraphs. + +#### Vertical ruler + +You can modify the top and bottom margins with the vertical ruler. When you hover the mouse over the margin limit, the cursor changes to indicate that it can be moved, and a horizontal guide line appears while you drag it: + + + +This action can be used to modify the spacing between the top and bottom of the page and the body and the header and footer of a document. + +### Managing tabs + +You can use the horizontal ruler's context menu to create, modify or delete tabs: + + + +To create a tab, just right-click directly on the horizontal ruler and choose its type from the context menu; a single left click automatically creates a default left tab. You can also right-click on existing tabs to modify their type using the context menu. + +**Remove tab** is only available when you right-click directly on an existing tab; you can also remove tabs by dragging them outside the horizontal ruler area. + +:::note Notes + +* Tabs can also be defined programmatically with the [WP SET ATTRIBUTES](../commands/wp-set-attributes), [WP GET ATTRIBUTES](../commands/wp-get-attributes), and [WP RESET ATTRIBUTES](../commands/wp-reset-attributes) commands with the `wk tab default` and `wk tabs` selectors. +* For decimal tabs, 4D Write Pro considers the first dot or comma character from the right as the decimal separator; this default setting can be modified with the `wk tab decimal separator` selector. + +::: + +#### Define leading characters + +The characters preceeding tabs (leading characters) can be defined by selecting from five predefined characters or by designating a specific character to use. The predefined characters are: + +* None (no characters are displayed - *default*) +* .... (dots) +* \--- (dashes) +* \_\_ (underscores) +* \*\*\* (asterisks) + +Leading characters always appear before the tab and follows the text direction (left to right or right to left). They can be defined programmatically with the [WP SET ATTRIBUTES](../commands/wp-set-attributes), [WP GET ATTRIBUTES](../commands/wp-get-attributes), and [WP RESET ATTRIBUTES](../commands/wp-reset-attributes) commands using `wk leading` with the `wk tab default` or `wk tabs` selectors, or via the horizontal ruler's contextual menu (as shown below). + + + +When **Other...** is selected, a dialog is displayed where a custom leading character can be defined. + +### Multi-column rulers + +When two or more columns are defined for the document or the section, the horizontal ruler displays a specific area for each column: + + + +**Note:** Multi-column feature is not available in **Embedded** view mode. + +### On After Edit event + +An [`On After Edit`](../../Events/onAfterEdit.md) form event is triggered for a 4D Write Pro area form object whenever any of the tab or margin controls are moved, added or deleted, whether by dragging them or using the context menu. + +## Columns + +4D Write Pro allows you to manage columns in your documents. Columns are chained from the left-most column to the right-most column. In other words, when entering text, the text flow will start filling the left column and continue with the column directly to the right until it reaches the end of the page. Once the end of the page is reached, the text flow cycles through the next page. In order to be able to balance the page settings, 4D Write Pro allows you to insert column breaks. + + + +Columns can be defined at the document level (they are displayed in the whole document) and/or at the section level (each section can have its own column configuration). + +**Note:** Columns are supported in **Page view** mode and **Draft view** mode only (they are not displayed in **Embedded** view mode), and they are exported to .docx using [WP EXPORT DOCUMENT](../commands/wp-export-document) but not to HTML and MIME HTML formats (wk web page complete format). + +Columns can be set using: + +* the **Columns** submenu of the 4D Write Pro area context menu, +* 4D Write Pro [attributes](../commands-legacy/4d-write-pro-attributes.md), +* 4D Write Pro [standard actions](./defining-a-4d-write-pro-area.md#standard-actions). + +You can set or get the following properties and actions for columns: + +| **Property** | **Description** | **Document attributes**| **Standard actions** | +| ----------- | -------- | ------- | --------------- | +| Number of columns | You can define up to 20 columns for the document/section | wk column count | *columnCount* | +| Column spacing | Space between columns in pts, inches, or cm. Note that all columns will have the same size. Each column width is automatically calculated by 4D Write Pro according to the number of columns, the page width, and the spacing | wk column spacing | *columnSpacing* | +| Column width | (read-only attribute) Current width for each column, i.e. computed width | wk column width | \- | +| Column rule style, color, and width | You can add a vertical separator (a decorative line) between columns. These options let you design the separator style, color and width. To remove the vertical separator, select **None** as a style. | wk column rule style, wk column rule color, wk column rule width | *columnRuleStyle*, *columnRuleColor*, *columnRuleWidth* | +| Insert break | Insert a column break | wk column break, see also [WP INSERT BREAK](../commands/wp-insert-break) | *insertColumnBreak* | +| Columns menu | Create a Columns sub-menu | \- | *columns* | + +### Creating a page with multiple-column and single column sections + +*Inserting a continuous section break* in your document allows you to have multiple-column sections and single column sections on the same page. + +For example: + + + +You can insert a continuous section break and change the number of columns to two for the first section: + + + + +## Bookmarks + +4D Write Pro allows you to create and work with dynamic references to parts of your documents, called **bookmarks**. A bookmark is a named reference attached to a specific [range](./ranges.md) in a 4D Write Pro document. + +Bookmarks are dynamic, which means that if the user moves, adds or removes text belonging to the bookmark, the associated range will be updated automatically and the bookmark will continue to reference the same content within the document. For example: + +- You create a bookmark named "MyBM" that references the "Hello world" text on page 20 of your document. +- Then you insert 50 pages at the beginning of the document. +- You will still be able to access the same "Hello world" text automatically, now on page 70 of the document, by means of the "MyBM" bookmark. + +A document can contain an unlimited number of bookmarks. Several bookmarks can reference the same range, and bookmark ranges can be interleaved. However, each bookmark name must be unique in the document. Bookmarks are not imported when using the [WP INSERT DOCUMENT BODY](../commands/wp-insert-document-body) command (bookmarks in the destination document cannot be overwritten). + +Once created, a bookmark is stored within the document. It is saved with the document, and can be handled by several different commands. It can also be used to reference parts of a template document. These parts can then be assembled automatically with data from the database to produce dynamic output documents such as invoices or catalogs. + +Several commands allow you to create, remove, and use bookmarks: + +[WP NEW BOOKMARK](../commands-legacy/wp-new-bookmark.md) to create a new bookmark from a range, +[WP GET BOOKMARKS](../commands-legacy/wp-get-bookmarks.md) to get all bookmarks defined in a document, +[WP Bookmark range](../commands-legacy/wp-bookmark-range.md) to retrieve a range from an existing bookmark, +[WP DELETE BOOKMARK](../commands-legacy/wp-delete-bookmark.md) to delete a bookmark. + +## Links + +4D Write Pro allows you to assign hyperlinks to any target object of your document, including ranges (text, picture, etc.), elements (table, body, footer, etc.), or the whole document. For example, you can set a URL hyperlink to a picture range; if the 4D Write Pro document is exported to HTML, users can click the picture to open a page at a specified address. + +Hyperlinks can also be activated from within 4D Write Pro documents using the **Ctrl+click** (Windows) or **Cmd+click** (macOS) shortcut. In a non-enterable 4D Write Pro document, a link can be activated using a simple click. + +4D Write Pro supports links of the following types: + +| Link Type | Description | +|-----------|-------------| +| `url` | Links to web pages or to any document, opens the associated application when activated (\*). Activating a URL link to a 4D Write Pro document (`.4wp`, `.4w7`) replaces the current document in the 4D Write Pro area.
(\*) Just like the [OPEN URL](../../commands-legacy/open-url.md) command. | +| `bookmark`| Links to bookmarks in the document | +| `method` | Activating a link to a 4D method executes the method (provided it is registered by the [SET ALLOWED METHODS](../../commands/set-allowed-methods.md) method). | + +Hyperlinks are managed through the following commands: + +- [WP SET LINK](../commands-legacy/wp-set-link.md) to insert a link using a target object +- [WP Get links](../commands-legacy/wp-get-links.md) to get the collection of all links in a target object. + + +:::note + +Links are handled as attributes, thus they can be set or get using the [WP SET ATTRIBUTES](../commands/wp-set-attributes) and [WP GET ATTRIBUTES](../commands/wp-get-attributes) commands along with the `wk link url` constant. However, we recommended using [WP SET LINK](../commands-legacy/wp-set-link.md) and [WP Get links](../commands-legacy/wp-get-links.md) because they automatically encode/decode hyperlinks as URLs. When reading links using the [WP GET ATTRIBUTES](../commands/wp-get-attributes) command, if the target object contains several links, the command returns the first link string. + +::: + +For example, if you want to transform the text selected by the user into a URL link to a web site: + + + + +You can write: + +```4d + $range:=WP Get selection(*;"WParea") + WP SET LINK($range;New object("url";"http://www.4d.com")) +``` + + + +To remove a link from a target object, you can write either: + +```4d + WP RESET ATTRIBUTES($range;wk link url) +``` +or + +```4d + WP SET ATTRIBUTES($range;wk link url;"") +``` + +**Note:** If *$range* does not include the whole link, the link is truncated but not entirely removed. + + +## Using commands from the Objects (Forms) theme + +The following 4D commands from the [Objects (Forms)](../../commands/theme/Objects_Forms.md) theme support 4D Write Pro form objects: + + + +| Command | Comments | +|------------------------------------------------------|----------| +| `OBJECT DUPLICATE` | | +| `OBJECT Get auto spellcheck` / `OBJECT SET AUTO SPELLCHECK` | | +| `OBJECT Get border style` / `OBJECT SET BORDER STYLE` | | +| `OBJECT Get context menu` / `OBJECT SET CONTEXT MENU` | | +| `OBJECT GET COORDINATES` / `OBJECT SET COORDINATES` | | +| `OBJECT Get data source` / `OBJECT SET DATA SOURCE` | | +| `OBJECT GET DRAG AND DROP OPTIONS` / `OBJECT SET DRAG AND DROP OPTIONS` | | +| `OBJECT Get enabled` / `OBJECT SET ENABLED` | | +| `OBJECT Get enterable` / `OBJECT SET ENTERABLE` | | +| `OBJECT GET EVENTS` / `OBJECT SET EVENTS` | | +| `OBJECT Get focus rectangle invisible` / `OBJECT SET FOCUS RECTANGLE INVISIBLE` | | +| `OBJECT Get font` / `OBJECT SET FONT` | Applied to current selection (if any) | +| `OBJECT Get font size` / `OBJECT SET FONT SIZE` | Applied to current selection (if any) | +| `OBJECT Get font style` / `OBJECT SET FONT STYLE` | Applied to current selection (if any) | +| `OBJECT Get horizontal alignment` / `OBJECT SET HORIZONTAL ALIGNMENT` | Applied to current selection (if any). Support of the `wk justify` constant for 4D Write Pro areas | +| `OBJECT GET RESIZING OPTIONS` / `OBJECT SET RESIZING OPTIONS` | | +| `OBJECT GET RGB COLORS` / `OBJECT SET RGB COLORS` | Applied to current selection (if any) | +| `OBJECT Get type` | | +| `OBJECT Get vertical alignment` / `OBJECT SET VERTICAL ALIGNMENT` | Vertical alignment of paragraphs: only has an effect when paragraph height is greater than paragraph text height | +| `OBJECT Get visible` / `OBJECT SET VISIBLE` | | +| `OBJECT Is styled text` | Returns true | +| `OBJECT MOVE` | | +| `OBJECT GET SUBFORM CONTAINER SIZE` | | +| `OBJECT Get name` | | +| `OBJECT Get pointer` | | + +Any OBJECT commands not listed above are not applicable to 4D Write Pro areas. + diff --git a/docs/assets/en/WritePro/ak_400.png b/docs/assets/en/WritePro/ak_400.png new file mode 100644 index 00000000000000..03ddd799fa0a3a Binary files /dev/null and b/docs/assets/en/WritePro/ak_400.png differ diff --git a/docs/assets/en/WritePro/ak_700.png b/docs/assets/en/WritePro/ak_700.png new file mode 100644 index 00000000000000..67de2c6ccbeac1 Binary files /dev/null and b/docs/assets/en/WritePro/ak_700.png differ diff --git a/docs/assets/en/WritePro/comment.png b/docs/assets/en/WritePro/comment.png new file mode 100644 index 00000000000000..7bc9233ea63c89 Binary files /dev/null and b/docs/assets/en/WritePro/comment.png differ diff --git a/docs/assets/en/WritePro/header_title_olv.png b/docs/assets/en/WritePro/header_title_olv.png new file mode 100644 index 00000000000000..96e9102ce17d7b Binary files /dev/null and b/docs/assets/en/WritePro/header_title_olv.png differ diff --git a/docs/assets/en/WritePro/link1.png b/docs/assets/en/WritePro/link1.png new file mode 100644 index 00000000000000..37389843e8f050 Binary files /dev/null and b/docs/assets/en/WritePro/link1.png differ diff --git a/docs/assets/en/WritePro/link2.png b/docs/assets/en/WritePro/link2.png new file mode 100644 index 00000000000000..a49860493ce8e7 Binary files /dev/null and b/docs/assets/en/WritePro/link2.png differ diff --git a/docs/assets/en/WritePro/pict2584929.en.png b/docs/assets/en/WritePro/pict2584929.en.png new file mode 100644 index 00000000000000..819f7c287ddaa5 Binary files /dev/null and b/docs/assets/en/WritePro/pict2584929.en.png differ diff --git a/docs/assets/en/WritePro/pict2584938.en.png b/docs/assets/en/WritePro/pict2584938.en.png new file mode 100644 index 00000000000000..411355746e0391 Binary files /dev/null and b/docs/assets/en/WritePro/pict2584938.en.png differ diff --git a/docs/assets/en/WritePro/pict2646292.en.png b/docs/assets/en/WritePro/pict2646292.en.png new file mode 100644 index 00000000000000..2f6dd9ff7667f9 Binary files /dev/null and b/docs/assets/en/WritePro/pict2646292.en.png differ diff --git a/docs/assets/en/WritePro/pict2646294.en.png b/docs/assets/en/WritePro/pict2646294.en.png new file mode 100644 index 00000000000000..c5706f5b23244e Binary files /dev/null and b/docs/assets/en/WritePro/pict2646294.en.png differ diff --git a/docs/assets/en/WritePro/pict2994900.en.png b/docs/assets/en/WritePro/pict2994900.en.png new file mode 100644 index 00000000000000..cae8f054a00ad2 Binary files /dev/null and b/docs/assets/en/WritePro/pict2994900.en.png differ diff --git a/docs/assets/en/WritePro/pict2994904.en.png b/docs/assets/en/WritePro/pict2994904.en.png new file mode 100644 index 00000000000000..cd70790beb1915 Binary files /dev/null and b/docs/assets/en/WritePro/pict2994904.en.png differ diff --git a/docs/assets/en/WritePro/pict2994907.en.png b/docs/assets/en/WritePro/pict2994907.en.png new file mode 100644 index 00000000000000..2623c1d996e42d Binary files /dev/null and b/docs/assets/en/WritePro/pict2994907.en.png differ diff --git a/docs/assets/en/WritePro/pict2994910.en.png b/docs/assets/en/WritePro/pict2994910.en.png new file mode 100644 index 00000000000000..320ddf239ac86c Binary files /dev/null and b/docs/assets/en/WritePro/pict2994910.en.png differ diff --git a/docs/assets/en/WritePro/pict2994913.en.png b/docs/assets/en/WritePro/pict2994913.en.png new file mode 100644 index 00000000000000..61613bf845f8c9 Binary files /dev/null and b/docs/assets/en/WritePro/pict2994913.en.png differ diff --git a/docs/assets/en/WritePro/pict2994942.en.png b/docs/assets/en/WritePro/pict2994942.en.png new file mode 100644 index 00000000000000..01f531e6cb591c Binary files /dev/null and b/docs/assets/en/WritePro/pict2994942.en.png differ diff --git a/docs/assets/en/WritePro/pict2994945.en.png b/docs/assets/en/WritePro/pict2994945.en.png new file mode 100644 index 00000000000000..07c3f9f10eb2d5 Binary files /dev/null and b/docs/assets/en/WritePro/pict2994945.en.png differ diff --git a/docs/assets/en/WritePro/pict2994956.en.png b/docs/assets/en/WritePro/pict2994956.en.png new file mode 100644 index 00000000000000..78bbcbb797cc5c Binary files /dev/null and b/docs/assets/en/WritePro/pict2994956.en.png differ diff --git a/docs/assets/en/WritePro/pict2994958.en.png b/docs/assets/en/WritePro/pict2994958.en.png new file mode 100644 index 00000000000000..75d6dd97fc625c Binary files /dev/null and b/docs/assets/en/WritePro/pict2994958.en.png differ diff --git a/docs/assets/en/WritePro/pict2994965.en.png b/docs/assets/en/WritePro/pict2994965.en.png new file mode 100644 index 00000000000000..276bf3df53d508 Binary files /dev/null and b/docs/assets/en/WritePro/pict2994965.en.png differ diff --git a/docs/assets/en/WritePro/pict2995027.en.png b/docs/assets/en/WritePro/pict2995027.en.png new file mode 100644 index 00000000000000..1aa8745413d65b Binary files /dev/null and b/docs/assets/en/WritePro/pict2995027.en.png differ diff --git a/docs/assets/en/WritePro/pict3033006.en.png b/docs/assets/en/WritePro/pict3033006.en.png new file mode 100644 index 00000000000000..ad7e034e246705 Binary files /dev/null and b/docs/assets/en/WritePro/pict3033006.en.png differ diff --git a/docs/assets/en/WritePro/pict3033008.en.png b/docs/assets/en/WritePro/pict3033008.en.png new file mode 100644 index 00000000000000..51f1aa5c128b59 Binary files /dev/null and b/docs/assets/en/WritePro/pict3033008.en.png differ diff --git a/docs/assets/en/WritePro/pict3053372.en.png b/docs/assets/en/WritePro/pict3053372.en.png new file mode 100644 index 00000000000000..91b126ea0f2350 Binary files /dev/null and b/docs/assets/en/WritePro/pict3053372.en.png differ diff --git a/docs/assets/en/WritePro/pict3071271.en.png b/docs/assets/en/WritePro/pict3071271.en.png new file mode 100644 index 00000000000000..e7f020cc979f5e Binary files /dev/null and b/docs/assets/en/WritePro/pict3071271.en.png differ diff --git a/docs/assets/en/WritePro/pict3307937.en.png b/docs/assets/en/WritePro/pict3307937.en.png new file mode 100644 index 00000000000000..fb12b681bed355 Binary files /dev/null and b/docs/assets/en/WritePro/pict3307937.en.png differ diff --git a/docs/assets/en/WritePro/pict3307941.en.png b/docs/assets/en/WritePro/pict3307941.en.png new file mode 100644 index 00000000000000..0016bc2e11049d Binary files /dev/null and b/docs/assets/en/WritePro/pict3307941.en.png differ diff --git a/docs/assets/en/WritePro/pict3308424.en.png b/docs/assets/en/WritePro/pict3308424.en.png new file mode 100644 index 00000000000000..17c545dcd5e7cc Binary files /dev/null and b/docs/assets/en/WritePro/pict3308424.en.png differ diff --git a/docs/assets/en/WritePro/pict3513503.en.png b/docs/assets/en/WritePro/pict3513503.en.png new file mode 100644 index 00000000000000..eddf97544e0575 Binary files /dev/null and b/docs/assets/en/WritePro/pict3513503.en.png differ diff --git a/docs/assets/en/WritePro/pict3513505.en.png b/docs/assets/en/WritePro/pict3513505.en.png new file mode 100644 index 00000000000000..5e8669f5c2aace Binary files /dev/null and b/docs/assets/en/WritePro/pict3513505.en.png differ diff --git a/docs/assets/en/WritePro/pict3514201.en.png b/docs/assets/en/WritePro/pict3514201.en.png new file mode 100644 index 00000000000000..cfcd01019f70bb Binary files /dev/null and b/docs/assets/en/WritePro/pict3514201.en.png differ diff --git a/docs/assets/en/WritePro/pict3541581.en.png b/docs/assets/en/WritePro/pict3541581.en.png new file mode 100644 index 00000000000000..8d2321c8b19748 Binary files /dev/null and b/docs/assets/en/WritePro/pict3541581.en.png differ diff --git a/docs/assets/en/WritePro/pict3626363.en.png b/docs/assets/en/WritePro/pict3626363.en.png new file mode 100644 index 00000000000000..823fcf7c97fbcb Binary files /dev/null and b/docs/assets/en/WritePro/pict3626363.en.png differ diff --git a/docs/assets/en/WritePro/pict3751849.en.png b/docs/assets/en/WritePro/pict3751849.en.png new file mode 100644 index 00000000000000..df240b64e8c0c9 Binary files /dev/null and b/docs/assets/en/WritePro/pict3751849.en.png differ diff --git a/docs/assets/en/WritePro/pict3752166.en.png b/docs/assets/en/WritePro/pict3752166.en.png new file mode 100644 index 00000000000000..40ec61e14638df Binary files /dev/null and b/docs/assets/en/WritePro/pict3752166.en.png differ diff --git a/docs/assets/en/WritePro/pict3752176.en.png b/docs/assets/en/WritePro/pict3752176.en.png new file mode 100644 index 00000000000000..1b09211ea8ac30 Binary files /dev/null and b/docs/assets/en/WritePro/pict3752176.en.png differ diff --git a/docs/assets/en/WritePro/pict3893246.en.png b/docs/assets/en/WritePro/pict3893246.en.png new file mode 100644 index 00000000000000..84c289b866e8e6 Binary files /dev/null and b/docs/assets/en/WritePro/pict3893246.en.png differ diff --git a/docs/assets/en/WritePro/pict3893248.en.png b/docs/assets/en/WritePro/pict3893248.en.png new file mode 100644 index 00000000000000..c21d5b60eeb195 Binary files /dev/null and b/docs/assets/en/WritePro/pict3893248.en.png differ diff --git a/docs/assets/en/WritePro/pict4101161.en.png b/docs/assets/en/WritePro/pict4101161.en.png new file mode 100644 index 00000000000000..661c944356118b Binary files /dev/null and b/docs/assets/en/WritePro/pict4101161.en.png differ diff --git a/docs/assets/en/WritePro/pict4101210.en.png b/docs/assets/en/WritePro/pict4101210.en.png new file mode 100644 index 00000000000000..52d6d286b37274 Binary files /dev/null and b/docs/assets/en/WritePro/pict4101210.en.png differ diff --git a/docs/assets/en/WritePro/pict4101242.en.png b/docs/assets/en/WritePro/pict4101242.en.png new file mode 100644 index 00000000000000..b72796fcb066a9 Binary files /dev/null and b/docs/assets/en/WritePro/pict4101242.en.png differ diff --git a/docs/assets/en/WritePro/pict4101252.en.png b/docs/assets/en/WritePro/pict4101252.en.png new file mode 100644 index 00000000000000..ca86037a8d4a3a Binary files /dev/null and b/docs/assets/en/WritePro/pict4101252.en.png differ diff --git a/docs/assets/en/WritePro/pict4101267.en.png b/docs/assets/en/WritePro/pict4101267.en.png new file mode 100644 index 00000000000000..0d3e10a91e6847 Binary files /dev/null and b/docs/assets/en/WritePro/pict4101267.en.png differ diff --git a/docs/assets/en/WritePro/pict4619596.en.png b/docs/assets/en/WritePro/pict4619596.en.png new file mode 100644 index 00000000000000..0c0a886b53349f Binary files /dev/null and b/docs/assets/en/WritePro/pict4619596.en.png differ diff --git a/docs/assets/en/WritePro/pict4619694.en.png b/docs/assets/en/WritePro/pict4619694.en.png new file mode 100644 index 00000000000000..4ace1703dab061 Binary files /dev/null and b/docs/assets/en/WritePro/pict4619694.en.png differ diff --git a/docs/assets/en/WritePro/pict4619865.en.png b/docs/assets/en/WritePro/pict4619865.en.png new file mode 100644 index 00000000000000..e708853ddf2c4c Binary files /dev/null and b/docs/assets/en/WritePro/pict4619865.en.png differ diff --git a/docs/assets/en/WritePro/pict4687892.en.png b/docs/assets/en/WritePro/pict4687892.en.png new file mode 100644 index 00000000000000..d6702bd121d3bc Binary files /dev/null and b/docs/assets/en/WritePro/pict4687892.en.png differ diff --git a/docs/assets/en/WritePro/pict5562054.en.png b/docs/assets/en/WritePro/pict5562054.en.png new file mode 100644 index 00000000000000..dee167c5ccf7c3 Binary files /dev/null and b/docs/assets/en/WritePro/pict5562054.en.png differ diff --git a/docs/assets/en/WritePro/pict5562058.en.png b/docs/assets/en/WritePro/pict5562058.en.png new file mode 100644 index 00000000000000..f84f46638756cb Binary files /dev/null and b/docs/assets/en/WritePro/pict5562058.en.png differ diff --git a/docs/assets/en/WritePro/pict5761667.en.png b/docs/assets/en/WritePro/pict5761667.en.png new file mode 100644 index 00000000000000..a6e16bcd3e31bf Binary files /dev/null and b/docs/assets/en/WritePro/pict5761667.en.png differ diff --git a/docs/assets/en/WritePro/pict5761669.en.png b/docs/assets/en/WritePro/pict5761669.en.png new file mode 100644 index 00000000000000..6f56866e06cff7 Binary files /dev/null and b/docs/assets/en/WritePro/pict5761669.en.png differ diff --git a/docs/assets/en/WritePro/pict5761671.en.png b/docs/assets/en/WritePro/pict5761671.en.png new file mode 100644 index 00000000000000..d2b933e6253bd5 Binary files /dev/null and b/docs/assets/en/WritePro/pict5761671.en.png differ diff --git a/docs/assets/en/WritePro/pict5761673.en.png b/docs/assets/en/WritePro/pict5761673.en.png new file mode 100644 index 00000000000000..eef0da9b30d61f Binary files /dev/null and b/docs/assets/en/WritePro/pict5761673.en.png differ diff --git a/docs/assets/en/WritePro/pict5761675.en.png b/docs/assets/en/WritePro/pict5761675.en.png new file mode 100644 index 00000000000000..f21fa89866c9ef Binary files /dev/null and b/docs/assets/en/WritePro/pict5761675.en.png differ diff --git a/docs/assets/en/WritePro/pict5761677.en.png b/docs/assets/en/WritePro/pict5761677.en.png new file mode 100644 index 00000000000000..b6b82029e3bdaa Binary files /dev/null and b/docs/assets/en/WritePro/pict5761677.en.png differ diff --git a/docs/assets/en/WritePro/pict5859437.en.png b/docs/assets/en/WritePro/pict5859437.en.png new file mode 100644 index 00000000000000..8a546866502013 Binary files /dev/null and b/docs/assets/en/WritePro/pict5859437.en.png differ diff --git a/docs/assets/en/WritePro/pict5907013.en.png b/docs/assets/en/WritePro/pict5907013.en.png new file mode 100644 index 00000000000000..e233c502a77cb2 Binary files /dev/null and b/docs/assets/en/WritePro/pict5907013.en.png differ diff --git a/docs/assets/en/WritePro/pict5907021.en.png b/docs/assets/en/WritePro/pict5907021.en.png new file mode 100644 index 00000000000000..bcbe548297f87d Binary files /dev/null and b/docs/assets/en/WritePro/pict5907021.en.png differ diff --git a/docs/assets/en/WritePro/pict5907023.en.png b/docs/assets/en/WritePro/pict5907023.en.png new file mode 100644 index 00000000000000..6eba7f2baedff6 Binary files /dev/null and b/docs/assets/en/WritePro/pict5907023.en.png differ diff --git a/docs/assets/en/WritePro/pict5907026.en.png b/docs/assets/en/WritePro/pict5907026.en.png new file mode 100644 index 00000000000000..d526c51578eb27 Binary files /dev/null and b/docs/assets/en/WritePro/pict5907026.en.png differ diff --git a/docs/assets/en/WritePro/pict5907030.en.png b/docs/assets/en/WritePro/pict5907030.en.png new file mode 100644 index 00000000000000..964245707b6717 Binary files /dev/null and b/docs/assets/en/WritePro/pict5907030.en.png differ diff --git a/docs/assets/en/WritePro/pict5941073.en.png b/docs/assets/en/WritePro/pict5941073.en.png new file mode 100644 index 00000000000000..66f10af3210774 Binary files /dev/null and b/docs/assets/en/WritePro/pict5941073.en.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/commands/pict6013182.en.png b/docs/assets/en/WritePro/pict6013182.en.png similarity index 100% rename from i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/commands/pict6013182.en.png rename to docs/assets/en/WritePro/pict6013182.en.png diff --git a/docs/assets/en/WritePro/pict6014414.en.png b/docs/assets/en/WritePro/pict6014414.en.png new file mode 100644 index 00000000000000..1454f02b49f34c Binary files /dev/null and b/docs/assets/en/WritePro/pict6014414.en.png differ diff --git a/docs/assets/en/WritePro/pict6014426.en.png b/docs/assets/en/WritePro/pict6014426.en.png new file mode 100644 index 00000000000000..5430cc882d6f13 Binary files /dev/null and b/docs/assets/en/WritePro/pict6014426.en.png differ diff --git a/docs/assets/en/WritePro/pict6014429.en.png b/docs/assets/en/WritePro/pict6014429.en.png new file mode 100644 index 00000000000000..12cb8442c5f68c Binary files /dev/null and b/docs/assets/en/WritePro/pict6014429.en.png differ diff --git a/docs/assets/en/WritePro/pict6022144.en.png b/docs/assets/en/WritePro/pict6022144.en.png new file mode 100644 index 00000000000000..ab1d4670b16d55 Binary files /dev/null and b/docs/assets/en/WritePro/pict6022144.en.png differ diff --git a/docs/assets/en/WritePro/pict6131919.en.png b/docs/assets/en/WritePro/pict6131919.en.png new file mode 100644 index 00000000000000..d8b2b0f013f901 Binary files /dev/null and b/docs/assets/en/WritePro/pict6131919.en.png differ diff --git a/docs/assets/en/WritePro/pict6236360.en.png b/docs/assets/en/WritePro/pict6236360.en.png new file mode 100644 index 00000000000000..8a1ada936554a5 Binary files /dev/null and b/docs/assets/en/WritePro/pict6236360.en.png differ diff --git a/docs/assets/en/WritePro/pict6260026.en.png b/docs/assets/en/WritePro/pict6260026.en.png new file mode 100644 index 00000000000000..25b899cdd7ca87 Binary files /dev/null and b/docs/assets/en/WritePro/pict6260026.en.png differ diff --git a/docs/assets/en/WritePro/pict6260033.en.png b/docs/assets/en/WritePro/pict6260033.en.png new file mode 100644 index 00000000000000..d8271cd06a6220 Binary files /dev/null and b/docs/assets/en/WritePro/pict6260033.en.png differ diff --git a/docs/assets/en/WritePro/pict6260036.en.png b/docs/assets/en/WritePro/pict6260036.en.png new file mode 100644 index 00000000000000..a93bbc2deb6580 Binary files /dev/null and b/docs/assets/en/WritePro/pict6260036.en.png differ diff --git a/docs/assets/en/WritePro/pict6421031.en.png b/docs/assets/en/WritePro/pict6421031.en.png new file mode 100644 index 00000000000000..f338bd44caeb38 Binary files /dev/null and b/docs/assets/en/WritePro/pict6421031.en.png differ diff --git a/docs/assets/en/WritePro/pict6421340.en.png b/docs/assets/en/WritePro/pict6421340.en.png new file mode 100644 index 00000000000000..a00a64fa003fe5 Binary files /dev/null and b/docs/assets/en/WritePro/pict6421340.en.png differ diff --git a/docs/assets/en/WritePro/pict6421342.en.png b/docs/assets/en/WritePro/pict6421342.en.png new file mode 100644 index 00000000000000..e7bbdb0445e7dc Binary files /dev/null and b/docs/assets/en/WritePro/pict6421342.en.png differ diff --git a/docs/assets/en/WritePro/pict6421344.en.png b/docs/assets/en/WritePro/pict6421344.en.png new file mode 100644 index 00000000000000..b1da7d4f717589 Binary files /dev/null and b/docs/assets/en/WritePro/pict6421344.en.png differ diff --git a/docs/assets/en/WritePro/pict6421356.en.png b/docs/assets/en/WritePro/pict6421356.en.png new file mode 100644 index 00000000000000..e19848f65d2951 Binary files /dev/null and b/docs/assets/en/WritePro/pict6421356.en.png differ diff --git a/docs/assets/en/WritePro/pict6434575.en.png b/docs/assets/en/WritePro/pict6434575.en.png new file mode 100644 index 00000000000000..b98b7a71deb16b Binary files /dev/null and b/docs/assets/en/WritePro/pict6434575.en.png differ diff --git a/docs/assets/en/WritePro/pict6434579.en.png b/docs/assets/en/WritePro/pict6434579.en.png new file mode 100644 index 00000000000000..232ad5653b5bdf Binary files /dev/null and b/docs/assets/en/WritePro/pict6434579.en.png differ diff --git a/docs/assets/en/WritePro/pict6434721.en.png b/docs/assets/en/WritePro/pict6434721.en.png new file mode 100644 index 00000000000000..199e62f81ef736 Binary files /dev/null and b/docs/assets/en/WritePro/pict6434721.en.png differ diff --git a/docs/assets/en/WritePro/pict6434723.en.png b/docs/assets/en/WritePro/pict6434723.en.png new file mode 100644 index 00000000000000..480da0bfc5f80f Binary files /dev/null and b/docs/assets/en/WritePro/pict6434723.en.png differ diff --git a/docs/assets/en/WritePro/pict6434756.en.png b/docs/assets/en/WritePro/pict6434756.en.png new file mode 100644 index 00000000000000..ffdcce4bd30899 Binary files /dev/null and b/docs/assets/en/WritePro/pict6434756.en.png differ diff --git a/docs/assets/en/WritePro/pict6441966.en.png b/docs/assets/en/WritePro/pict6441966.en.png new file mode 100644 index 00000000000000..e6b76b3b690664 Binary files /dev/null and b/docs/assets/en/WritePro/pict6441966.en.png differ diff --git a/docs/assets/en/WritePro/pict6856159.en.png b/docs/assets/en/WritePro/pict6856159.en.png new file mode 100644 index 00000000000000..18f093b69da71c Binary files /dev/null and b/docs/assets/en/WritePro/pict6856159.en.png differ diff --git a/docs/assets/en/WritePro/pict6856163.en.png b/docs/assets/en/WritePro/pict6856163.en.png new file mode 100644 index 00000000000000..0c3c6665e834d8 Binary files /dev/null and b/docs/assets/en/WritePro/pict6856163.en.png differ diff --git a/docs/assets/en/WritePro/pict7014959.en.png b/docs/assets/en/WritePro/pict7014959.en.png new file mode 100644 index 00000000000000..a667cee2e6696a Binary files /dev/null and b/docs/assets/en/WritePro/pict7014959.en.png differ diff --git a/docs/assets/en/WritePro/pict7148443.en.png b/docs/assets/en/WritePro/pict7148443.en.png new file mode 100644 index 00000000000000..ab64da522a20a6 Binary files /dev/null and b/docs/assets/en/WritePro/pict7148443.en.png differ diff --git a/docs/assets/en/WritePro/pict7148495.en.png b/docs/assets/en/WritePro/pict7148495.en.png new file mode 100644 index 00000000000000..499af8e3737b08 Binary files /dev/null and b/docs/assets/en/WritePro/pict7148495.en.png differ diff --git a/docs/assets/en/WritePro/poweredby4D_web.png b/docs/assets/en/WritePro/poweredby4D_web.png new file mode 100644 index 00000000000000..fbb7fefffac38d Binary files /dev/null and b/docs/assets/en/WritePro/poweredby4D_web.png differ diff --git a/docs/code-editor/write-class-method.md b/docs/code-editor/write-class-method.md index 7782fb1c578ef1..bfcedd590d801f 100644 --- a/docs/code-editor/write-class-method.md +++ b/docs/code-editor/write-class-method.md @@ -892,3 +892,18 @@ Strict syntax rules must be observed in order for macros files to respect the XM - Comments of the "// my comment" type, allowed inside `
[`FORM UNLOAD`](../commands-legacy/form-unload.md)
[`Formula`](formula.md)
-[`Formula from string`](./formula-from-string.md)
+[`Formula from string`](formula-from-string.md)
[`Frontmost process`](../commands-legacy/frontmost-process.md)
[`Frontmost window`](../commands-legacy/frontmost-window.md)
diff --git a/docs/commands/create-deployment-license.md b/docs/commands/create-deployment-license.md index dce3cec3f0bec1..0084093004f50c 100644 --- a/docs/commands/create-deployment-license.md +++ b/docs/commands/create-deployment-license.md @@ -91,10 +91,10 @@ The command returns a *status* object containing the following properties: Use the automatic syntax to create a single-user 4D application: ```4d - var $status : Object - var $application : 4D.File - $application:=Folder(fk desktop folder).folder("myApp.app") - $status:=Create deployment license($application;4D Volume Desktop) + var $status : Object + var $application : 4D.File + $application:=Folder(fk desktop folder).folder("myApp.app") + $status:=Create deployment license($application;4D Volume Desktop) ``` @@ -104,17 +104,17 @@ Use the automatic syntax to create a single-user 4D application: Designate a license to use: ```4d - var $status : Object - var $application : 4D.File - var $license : 4D.File - $license:=Folder(fk licenses folder).file("4UUD200-xxx.license4D") - $application:=Folder(fk desktop folder).folder("myApp.app") - $status:=Create deployment license($application;$license) + var $status : Object + var $application : 4D.File + var $license : 4D.File + $license:=Folder(fk licenses folder).file("4UUD200-xxx.license4D") + $application:=Folder(fk desktop folder).folder("myApp.app") + $status:=Create deployment license($application;$license) ``` ## See also -[Blog post - Finalize an application with 4D commands](https://blog.4d.com/finalize-an-application-with-4d-commands) +[Blog post - Build an application with 4D commands](https://blog.4d.com/build-an-application-with-4d-commands) ## Properties diff --git a/docs/settings/overview.md b/docs/settings/overview.md index 0d52cdbde7c0dc..ede138092298e2 100644 --- a/docs/settings/overview.md +++ b/docs/settings/overview.md @@ -7,8 +7,12 @@ The Settings configure how the current project functions. These parameters may b  -> 4D provides another set of parameters, called **Preferences**, that apply to the 4D IDE application. For more information, refer to [Preferences](../Preferences/general.md). +:::info + +4D provides another set of parameters, called **Preferences**, that apply to the 4D IDE application. For more information, refer to [Preferences](../Preferences/general.md). + +::: ## Accessing the settings @@ -18,7 +22,7 @@ You can access the Settings dialog box: - by clicking **Settings** on the 4D toolbar - on 4D Server, using the **Edit > Settings...** menu option -When [**User settings** mode is enabled](../Desktop/user-settings.md), **Settings...** is renamed **Structure Settings...** and two additional menu commands are available at each location: +When [**User settings** mode is enabled](#user-settings), **Settings...** is renamed **Structure Settings...** and two additional menu commands are available at each location: - **User Settings...** gives you access to settings that can be stored externally in a user file. If these are modified, they are used instead of structure settings. - **User Settings for Data File...** gives you access to settings that can be stored externally in a user file attached to the current data file. If they are modified, they are used instead of user or structure settings. @@ -47,8 +51,137 @@ A parameter still appears in bold even when its value is replaced manually with Most of the settings are applied immediately. However, a few of them (such as the Startup environment setting) only take effect when the database is restarted. In this case, a dialog box appears to inform you that the change will take effect at the next startup. -## Resetting the settings +### Resetting the settings To reset the parameters to their default values and remove the bold style indicating that they have been customized, click **Reset to factory settings**. This button resets all the parameters of the current page. It becomes active when at least one parameter has been modified on the current page. + + +## User Settings + +4D provides two modes of operation for project Settings: + +* **Standard** mode: all settings are stored in the [*settings.4DSettings* file at the project level](../Project/architecture.md#sources) and are applied in all cases. This is the default mode, suitable for development phase (all applications). + +* **User settings** mode: part of the custom settings are stored in a *settings.4DSettings* file [in the Settings folder](../Project/architecture.md#settings-user) (for all data files) or [in the Data folder](../Project/architecture.md#settings-user-data) (for this data file) and are used instead of the structure settings. This mode is suitable for deployment phase for Desktop applications. You enable this mode using an option located on the [Security page](./security.md) of the Settings. + +By defining user settings, you can keep custom settings between updates of your 4D applications, or manage different settings for the same 4D application deployed on several different sites. It also makes it possible to use programming to manage setting files using XML. + +4D can generate and use two types of user settings: + +- **User Settings**: They are used instead of structure settings for any data file opened with the application. +- **User Settings for Data file**: They can be defined specifically for each data file used with your application, configuring for example the port ID or the server cache. + +With this option, you can easily deploy and update several copies of the same desktop application with several data files, each containing different settings. + +Consider for example the following configuration, where an application is duplicated and each copy uses a different Port ID setting. If this user setting is linked to the data file, you will be able to update the application without having to manually change the Port ID: + + + +### Enabling User settings + +To enable user settings, you need to check the **Settings** > **Security** > **Enable User Settings** option: + + + +When you check this option, the settings are separated into three dialog boxes: + +* **Structure Settings** +* **User Settings** +* **User Settings for Data file** + +You can access these dialog boxes using the **Design > Settings...** menu or the **Settings** button in the toolbar: + + + +You can also access these dialog boxes using the [OPEN SETTINGS WINDOW](../commands-legacy/open-settings-window.md) command with the appropriate *settingsType* selector. + +The Structure Settings dialog box is identical to the standard Settings, and provides access to all its properties (which can be overriden by user settings). + +### User Settings and User Settings for Data file + +The **User Settings** and **User Settings for Data File** dialog boxes contain a selection of relevant properties that can be defined for all data files or a single data file: + + + +The following table lists the pages of settings found in the **User Settings** and **User Settings for Data File** dialog boxes and describes their main differences with respect to standard settings: + +| **Page of Structure Settings** | **Page of User Settings** | **Page of User Settings for Data File**| +| --- | --- | --- | +| [General page](./general.md) | N/a | N/a | +| [Interface page](./interface.md) | Identical to standard settings | Identical to standard settings | +| [Compiler page](./compiler.md) | N/a | N/a | +| [Database/Data storage page](./database.md#data-storage-page) | N/a | N/a | +| [Database/Memory page](./database.md#memory-page) | Identical to standard settings | Identical to standard settings | +| [Backup/Scheduler page](./../Backup/settings.md#scheduler) | N/a | Identical to standard settings | +| [Backup/Configuration page](./../Backup/settings.md#configuration) | N/a | Identical to standard settings | +| [Backup/Backup & Restore page](./../Backup/settings.md#backup--restore) | N/a | Identical to standard settings | +| [Client-server/Network options page](./client-server.md#network-options-page) | Identical to standard settings | Identical to standard settings | +| [Client-server/IP configuration page](./client-server.md#ip-configuration-page) | Identical to standard settings | Identical to standard settings | +| [Web/Configuration page](./web.md#configuration) | Identical to standard settings | Identical to standard settings | +| [Web/Options (I) page](./web.md#options-i) | Identical to standard settings | Identical to standard settings | +| [Web/Options (II) page](./web.md#options-ii) | Identical to standard settings | Identical to standard settings | +| [Web/Log (type) page](./web.md#log-type) | Identical to standard settings | Identical to standard settings | +| [Web/Log (backup) page](./web.md#log-backup) | Identical to standard settings | Identical to standard settings | +| [Web/Web Services page](./web.md#web-services) | Method prefixing option not available | Method prefixing option not available | +| [SQL page](./sql.md) | Identical to standard settings | Identical to standard settings | +| [PHP page](./php.md) | Identical to standard settings | Identical to standard settings | +| [Security page](./security.md) | N/a | N/a | +| [Compatibility page](./compatibility.md) | N/a | N/a | + +When you edit settings in this dialog box, they are automatically stored in the corresponding *settings.4DSettings* file (see below) or the *Backup.4DSettings* file (check the [Backup settings](../Backup/settings.md) page for more information). + +### `SET DATABASE PARAMETER` and user settings + +Some of the user settings are also available through the [SET DATABASE PARAMETER](../commands-legacy/set-database-parameter.md) command. User settings are parameters with the **Kept between two sessions** property set to **Yes**. + +When the **User Settings** feature is enabled, user settings edited by the [SET DATABASE PARAMETER](../commands-legacy/set-database-parameter.md) command are automatically saved in the user settings for the data file. + +> `Table sequence number` is an exception; this setting value is always saved in the data file itself. + +### settings.4DSettings files + +When you [check the **Enable User Settings** option](#enabling-user-settings), user settings files are automatically created. Their location depends on the type of user settings defined. + +#### User Settings + +The standard user settings file is automatically created and placed in a settings folder at the following location: + +[`ProjectFolder/Settings/settings.4DSettings`](../Project/architecture.md#settings-user) + +... where *ProjectFolder* is the name of the folder containing the project structure file. + +In merged applications, the user settings file is placed at the following location: + +* In single-user versions: ProjectFolder/Database/Settings/settings.4DSettings +* In client/server versions: ProjectFolder/Server Database/Settings/settings.4DSettings + +#### User Settings for Data File + +The user settings file linked to the data file is automatically created and placed in a settings folder at the following location: + +[`Data/Settings/settings.4DSettings`](../Project/architecture.md#settings-user-data) + +... where *Data* is the name of the folder containing the current data file of the application. + +> When the data file is located at the same level as the project structure file, structure-based and data-based user settings files share the same location and file. The **User Settings for Data File...** menu command is not proposed. + +:::note + +Settings files are XML files; they can be read and modified using integrated 4D XML commands or using an XML editor. This means that you can manage settings by programming, particularly in the context of applications compiled and merged with 4D Volume Desktop. When you modify this file by programming, the changes are only taken into account the next time the database is opened. + +::: + + +### Priority of settings + +Settings can be stored at three levels. Each setting defined at one level overrides the same setting defined at a previous level, if any: + +| **Priority level** | **Name** | **Location** | **Comments** | +|---|---|---|---| +| 3 (lowest) | Structure settings (or Settings when "User settings" feature not enabled) | ***settings.4DSettings*** file in the Sources folder (project databases) or in the Settings folder as the same level as the structure file (binary databases) | Unique location when user settings are not enabled. Applied to all copies of the application. | +| 2 | User settings (all data files) | ***settings.4DSettings*** file in the Settings folder at the same level as the Project folder | Overrides Structure settings. Stored within the application package. | +| 1 (highest) | User settings (current data file) | ***settings.4DSettings*** file in the Settings folder at the same level as the data file | Overrides Structure settings and User settings. Applied only when the linked data file is used with the application. | + +Keep in mind that user settings files only contain a subset of relevant settings, while the structure file contains all custom settings, including core settings. diff --git a/docs/settings/security.md b/docs/settings/security.md index 2b7ffd9cfbf12b..572de63c511aa2 100644 --- a/docs/settings/security.md +++ b/docs/settings/security.md @@ -40,7 +40,7 @@ This page contains options related to data access and protection for your deskto - **Disabled for all**: This option disables control within formulas. When this option is checked, users have access to all the 4D commands and plug-ins as well as all project methods (except for invisible ones). **Note:** This option takes priority over the [`SET ALLOWED METHODS`](../commands/set-allowed-methods.md) command. When it is checked, this command does nothing. -- **Enable User Settings**: You need to check this option to be able to display separated dialog boxes for user settings. When this option is checked, up to three dialog boxes are available: **Structure Settings**, **User Settings**, and **User Settings for Data File**. For more information, refer to [User settings](../Desktop/user-settings.md). +- **Enable User Settings**: You need to check this option to be able to display separated dialog boxes for user settings. When this option is checked, up to three dialog boxes are available: **Structure Settings**, **User Settings**, and **User Settings for Data File**. For more information, refer to [User settings](../settings/overview.md#user-settings). - **Execute "On Host Database Event" method of the components**: The [On Host Database Event database method](../commands-legacy/on-host-database-event-database-method.md) facilitates the initialization and backup phases for 4D components. For security reasons, you must explicitly authorize the execution of this method in each host database. To do this, you must check this option. By default, it is not checked. diff --git a/docs/settings/web.md b/docs/settings/web.md index 2a4227d86e5ca7..4266add5a707ca 100644 --- a/docs/settings/web.md +++ b/docs/settings/web.md @@ -136,11 +136,16 @@ Allows you to set the maximum timeout before closing for inactive Web processes Set the authentication system that you want to apply to your Web server. Three options are proposed: -Custom (default) -Passwords with BASIC protocol -Passwords with DIGEST protocol +- Custom (default) +- Passwords with BASIC protocol +- Passwords with DIGEST protocol + +Using **Custom** authentication is recommended. See [**Authentication**](../WebServer/authentication.md) section. + +#### Generic Web User + +See [Deprecated Settings](../WebServer/webServerConfig.md#deprecated-settings). -Using **Custom** authentication is recommended. See [**Authentication**](../WebServer/authentication.md) chapter in the *Web Development* documentation. ## Options (II) diff --git a/docusaurus.config.js b/docusaurus.config.js index 51c17ad6946ccf..945a250027245c 100644 --- a/docusaurus.config.js +++ b/docusaurus.config.js @@ -268,5 +268,11 @@ module.exports = { maintainCase: false, }, }, - themes: ['@docusaurus/theme-mermaid'], + themes: ['@docusaurus/theme-mermaid'], + scripts: [ + { + src: 'https://kit.fontawesome.com/daeacc3fc4.js', + crossorigin: 'anonymous', + }, + ], } diff --git a/i18n/en/code.json b/i18n/en/code.json index 35cb9dfb30d3b3..fc541a0809078b 100644 --- a/i18n/en/code.json +++ b/i18n/en/code.json @@ -9,6 +9,9 @@ "message": "Working with a project" }, "homepage.sections.core-development.title": { + "message": "Project & IDE" + }, + "homepage.sections.language.title": { "message": "Core Development" }, "Project Management": { @@ -33,7 +36,7 @@ "message": "Preferences" }, "homepage.administration.title": { - "message": "Administration" + "message": "Server & Admin" }, "4D Server Administration Window": { "message": "4D Server Administration Window" @@ -131,8 +134,8 @@ "Build Application": { "message": "Build Application" }, - "homepage.sections.mobile-applications.title": { - "message": "Mobile Applications" + "homepage.sections.more.title": { + "message": "More docs" }, "Go Mobile with 4D": { "message": "Go Mobile with 4D" diff --git a/i18n/en/docusaurus-plugin-content-docs/current.json b/i18n/en/docusaurus-plugin-content-docs/current.json index e4ecc786008c98..fd2157d17ca551 100644 --- a/i18n/en/docusaurus-plugin-content-docs/current.json +++ b/i18n/en/docusaurus-plugin-content-docs/current.json @@ -208,11 +208,11 @@ "description": "The generated-index page description for category 4D Language Concepts in sidebar docs" }, "sidebar.docs.category.Class Functions": { - "message": "Class Functions", + "message": "Classes", "description": "The label for category Class Functions in sidebar docs" }, "sidebar.docs.category.Class Functions.link.generated-index.title": { - "message": "Class Functions", + "message": "Classe", "description": "The generated-index page title for category Class Functions in sidebar docs" }, "sidebar.docs.category.Class Functions.link.generated-index.description": { diff --git a/i18n/en/docusaurus-plugin-content-docs/version-20-R10.json b/i18n/en/docusaurus-plugin-content-docs/version-20-R10.json index 19a062c1fc8ae9..bc0ae4c00bd084 100644 --- a/i18n/en/docusaurus-plugin-content-docs/version-20-R10.json +++ b/i18n/en/docusaurus-plugin-content-docs/version-20-R10.json @@ -388,7 +388,7 @@ "description": "The label for category Classes in sidebar docs" }, "sidebar.docs.category.Classes.link.generated-index.title": { - "message": "Class Functions", + "message": "Classes", "description": "The generated-index page title for category Classes in sidebar docs" }, "sidebar.docs.category.Classes.link.generated-index.description": { diff --git a/i18n/es/docusaurus-plugin-content-docs/current/API/SessionClass.md b/i18n/es/docusaurus-plugin-content-docs/current/API/SessionClass.md index ed2e81d7d4b363..dddc250d0db238 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/API/SessionClass.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/API/SessionClass.md @@ -136,7 +136,7 @@ La función `.createOTP()` crea un Para más información sobre los tokens OTP, por favor consulte [esta sección](../WebServer/sessions.md#session-token-otp). -Por defecto, si se omite el parámetro *lifespan*, el token se crea con el mismo tiempo de vida que el [`.idleTimeOut`](#idletimeout) de la sesión. Puede definir un tiempo de espera personalizado pasando un valor en segundos en *lifespan* (el valor mínimo es de 10 segundos, *lifespan* se restablece a 10 si se pasa un valor menor). Si se utiliza un token caducado para restaurar una sesión de usuario web, se ignora. +Por defecto, si se omite el parámetro *lifespan*, el token se crea con el mismo tiempo de vida que el [`.idleTimeOut`](#idletimeout) de la sesión. You can set a custom timeout by passing a value in seconds in *lifespan*. Si se utiliza un token caducado para restaurar una sesión de usuario web, se ignora. El token devuelto puede ser utilizado en intercambios con aplicaciones de terceros o sitios web para identificar la sesión de forma segura. Por ejemplo, el token OTP de sesión se puede utilizar con una aplicación de pago. diff --git a/i18n/es/docusaurus-plugin-content-docs/current/Concepts/operators.md b/i18n/es/docusaurus-plugin-content-docs/current/Concepts/operators.md index 111a7c8b4391b2..3688ea43d1cff6 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/Concepts/operators.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/Concepts/operators.md @@ -90,7 +90,10 @@ Se admiten los siguientes operadores de asignación compuestos: | | Time \*= Number | Number | `$t1*=5 //$t1:=$t1*5` | | | Picture \*= Number | Picture | `$p1*=5 //$p1:=$p1*5 (redimensionar $p1 de 5)` | -Estos operadores se aplican a todas las [expresiones asignables](quick-tour.md#assignable-vs-non-assignable-expressions) (excepto de las imágenes como propiedades de objeto o elementos de colección). +These operators apply on any [assignable expressions](quick-tour.md#assignable-vs-non-assignable-expressions) except: + +- pictures as object properties or collection elements, +- array index variables. La operación "source `operator` value" no es estrictamente equivalente a "source := source `operator` value" porque la expresión que designa la fuente (variable, campo, propiedad del objeto, elemento de colección) sólo se evalúa una vez. Por ejemplo, en una expresión tal como `getPointer()->+=1` el método `getPointer` es llamado sólo una vez. diff --git a/i18n/es/docusaurus-plugin-content-docs/current/Notes/updates.md b/i18n/es/docusaurus-plugin-content-docs/current/Notes/updates.md index 91b6ee183dfe21..00d698996ae839 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/Notes/updates.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/Notes/updates.md @@ -42,12 +42,6 @@ Lea [**Novedades en 4D 21**](https://blog.4d.com/en-whats-new-in-4d-21/), la ent - Web server: the support of deprecated `4DSYNC/` and `4DCGI/` URLs is removed. No specific processing is done on these URLs anymore. - Web user sessions are now returned by [`Process activity`](../commands/process-activity.md). -#### Cambios de comportamiento - - - Web services (SOAP): when [scalable sessions](../WebServer/sessions.md#enabling-web-sessions) are enabled, web services now run in [**preemptive processes**](../Develop/preemptive.md) in compiled mode. Make sure your SOAP code is thread-safe. - - Web server: the support of deprecated `4DSYNC/` and `4DCGI/` URLs is removed. No specific processing is done on these URLs anymore. - - Web user sessions are now returned by [`Process activity`](../commands/process-activity.md). - ## 4D 20 R10 Lea las [**Novedades en 4D 20 R10**](https://blog.4d.com/en-whats-new-in-4d-20-R10/), la entrada del blog que muestra todas las nuevas funcionalidades y mejoras en 4D 20 R10. diff --git a/i18n/es/docusaurus-plugin-content-docs/current/WritePro/user-legacy/defining-a-4d-write-pro-area.md b/i18n/es/docusaurus-plugin-content-docs/current/WritePro/user-legacy/defining-a-4d-write-pro-area.md new file mode 100644 index 00000000000000..609ccbab8c57cd --- /dev/null +++ b/i18n/es/docusaurus-plugin-content-docs/current/WritePro/user-legacy/defining-a-4d-write-pro-area.md @@ -0,0 +1,252 @@ +--- +id: defining-a-4d-write-pro-area +title: Definir un area 4D Write Pro +displayed_sidebar: docs +--- + + + +## Arrastrar y soltar + +Para configurar las funcionalidades de arrastrar y soltar para sus áreas 4D Write Pro, es necesario seleccionar las opciones adecuadas en el tema "Acción" de la Lista de propiedades: + + + +Las áreas 4D Write Pro soportan dos modos de arrastrar y soltar: + +* **Modo personalizado:** solamente las opciones "Arrastrable" y "Soltable" están marcadas. +En este modo, puede seleccionar texto y empezar a moverlo. El método del objeto se llama con el evento On Begin Drag Over, así que puede definir la acción soltar utilizando código personalizado. +* **Modo automático**: las opciones "Arrastrable", "Soltable", "Arrastrar automático" y "Soltar automático" seleccionadas. +En este modo, puede mover o copiar de forma automática (presione la tecla **Alt/Opción**) el texto seleccionado. El evento On Begin Drag Over no se dispara. + +**Nota:** seleccionando únicamente las opciones "Arrastrar automático" y "Soltar automático" no tendrá ningún efecto en el área 4D Write Pro. + +## Propiedades Vista + +Las propiedades de vista del documento están disponibles directamente en la lista de propiedades para áreas 4D Write Pro para permitirle definir cómo un documento 4D Write Pro se muestra de forma predeterminada en esta área. Estas propiedades le permiten personalizar, por ejemplo, si los documentos 4D Write Pro se muestran igual que si se fueran a imprimir, o a renderizar en un navegador. Se pueden establecer diferentes vistas del mismo documento 4D Write Pro en el mismo formulario. + +**Nota:** la configuración de la vista se puede administrar dinámicamente utilizando los comandos [WP SET VIEW PROPERTIES](../commands/wp-set-view-properties) y [WP Get view properties](../commands/wp-get-view-properties). + +La configuración de vista del documento se manejan a través de temas específicos en el tema **Apariencia** de la lista de propiedades para objetos de formulario 4D Write Pro: + + + +* **Resolución**: define la resolución de pantalla para los contenidos del área 4D Write Pro. De forma predeterminada, se establece en **72 dpi (macOS)**, que es la resolución estándar para formularios 4D en todas las plataformas. Al establecer esta propiedad en **Automático** significa que el documento de renderización será diferente entre las plataformas macOS y Windows. El establecimiento de un valor específico dpi hará la misma renderización del documento en ambas plataformas macOS y Windows. +* **Zoom**: establece el porcentaje de zoom para mostrar los contenidos del área 4D Write Pro. +* **Modo Vista**: establece el modo de visualización del documento 4D Write Pro en el área del formulario. Tres valores están disponibles: + * **Página**: el más completo modo de visualización que incluye contornos de página, orientación, márgenes, saltos de página, encabezados y pies de página, etc. Para más información, consulte el párrafo *Funcionalidades de vista página*. + * **Borrador**: modo borrador con propiedades de documentos básicas + * **Anidado**: modo de visualización adecuado para áreas anidadas; no muestra los márgenes, los pies de página, los encabezados, los marcos de página, etc. + Este modo también se puede utilizar para producir una vista de salida Web (si selecciona también la resolución 96 dpi y la opción **Mostrar HTML WYSIWYG**). + + **Nota**: la propiedad Modo Vista sólo se utiliza para la renderización en pantalla. En cuanto a la configuración de impresión, se utilizan automáticamente las reglas de renderización específicas (ver *Impresión de documentos 4D Write Pro*). +* **Mostrar marco de página:** muestra/oculta el marco de página cuando el modo de vista Página se establece en "Página". +* **Mostrar referencias**: muestra todas las fórmulas (o expresiones) insertadas en el documento como *referencias* (ver *Gestión de fórmulas*). Cuando esta opción no está marcada, las fórmulas 4D se muestran como *valores*. +**Nota**: las referencias de fórmula se pueden mostrar como símbolos  (ver abajo). +* **Mostrar encabezados/pies**: muestra/oculta los encabezados y pies cuando el modo de vista Página se establece en "Página" (que aparece por defecto). Para más información sobre las encabezados y pies de página, por favor consulte la sección *Utilizar un área 4D Write Pro*. +* **Mostrar fondo y elementos anclados**: muestra/oculta imágenes de fondo, color de fondo, imágenes ancladas y cajas de texto. +* **Mostrar caracteres ocultos**: muestra/oculta caracteres invisibles. +* **Mostrar HTML WYSIWYG**: activa/desactiva la vista HTML WYSIWYG, en la que todos los atributos 4D Write Pro avanzados que no son compatibles con todos los navegadores son retirados. +* **Mostrar regla horizontal**: horizontal. Para más información acerca de las reglas en las áreas 4D Write Pro, consulte la sección *Gestión de reglas*. +* **Mostrar regla vertical**: muestra/oculta la regla vertical cuando el documento está en modo Página. Para mayor información sobre reglas en áreas 4D Write Pro, ver la sección *Gestión de reglas*. +* **Mostrar imágenes vacías o no soportadas**: muestra/oculta un rectángulo negro para las imágenes que no se pueden cargar o calcular (imágenes vacías o en un formato no soportado). Para más información, consulte la sección *Imágenes vacías*. +* **Mostrar la fuente de la fórmula como símbolo**: muestra el texto fuente de las fórmulas como  símbolos cuando las expresiones se muestran como referencias (ver arriba). Mostrar las fórmulas como símbolos hace que los documentos de plantilla sean más compactos y más *wysiwyg*. + +## Menú contextual + +Si la propiedad **Menú contextual** está [seleccionada por un área 4D Write Pro](./defining-a-4d-write-pro-area.md#using-the-4d-write-pro-area-object), un menú contextual completo está disponible para los usuarios en modo Aplicación: + + + +Este menú ofrece acceso a todas las funcionalidades de 4D Write Pro. + +## Seleccionar el modo vista + +Los documentos 4D Write Pro se pueden visualizar en tres modos de vista de página: + +* **Borrador**: modo borrador con propiedades básicas +* **Página** (por defecto): modo "vista imprimir" +* **Embebido**: modo de vista conveniente para áreas anidadas; no muestra márgenes, pies de página, encabezados, columnas, marcos de página, etc. +Este modo también se puede utilizar para producir una salida de vista como Web (si selecciona también la resolución 96 dpi y la opción **HTML WYSIWYG**). + +El modo de visualización de la página se puede configurar mediante el menú emergente de área: + + + +**Nota:** el modo de visualización de la página no se almacena con el documento. + +Para las áreas anidadas en formularios 4D, el modo de visualización también se puede configurar por defecto utilizando la lista de propiedades. En este caso, el modo de visualización se almacena como una propiedad del objeto de formulario 4D Write Pro (para más información, consulte el párrafo *Configurar propiedades Vista*). + +## Las acciones estandar + +La interfaz de usuario de áreas 4D Write Pro se puede manejar a través de un amplio conjunto de **acciones estándar**. Las acciones estándar pueden asignarse a: + +* comandos de menú, disponibles a través de la **barra de menú** o del comando [Dynamic pop up menu](../../commands/dynamic-pop-up-menu) +* elementos de lista, disponibles por medio de listas pop-up/desplegables o menús pop-up jerárquicos, +* botones, casillas de selección, +* o ejecutados por el comando [INVOKE ACTION](../../commands/invoke-action). + +Cuando se le asignan a los objetos de interfaz, las acciones estándar manejan la activación/desactivación del objeto en función del contexto. Para más información, consulte la sección *Acciones estándar*. + +Dos tipos de acciones están disponibles para áreas 4D Write Pro: + +* Las acciones específicas 4D Write Pro, que sólo pueden utilizarse con áreas 4D Write Pro, +* *[Otras acciones](#other-actions)*, incluyendo las fuentes, expresiones, corrector ortográfico y acciones de edición, que se pueden utilizar con las áreas 4D Write Pro y las otras áreas 4D (ver *Acciones estándar*). + +### Acciones 4D Write Pro + +Las siguientes acciones estándar están disponibles para las áreas 4D Write Pro. + +**Notas:** + +* Las acciones que muestran un menú/lista automático sólo se pueden asociar a los comandos de menús o a los objetos pop-ups/listas desplegables y menús pop-up jerárquicos (ver *Submenú*). +* Las casillas de selección y las casillas de selección 3D deben estar asociadas con acciones de estado, tales como "section/differentFirstPage" o "visibleHorizontalRuler". La opción de tres estados sólo se admite con casillas de selección estándar. +* Un estado de acción de sección siempre es igual al estado actual de la sección seleccionada (estado heredado si el atributo se hereda de la sección principal o del atributo por defecto) ya que debe reflejar el estado de sección seleccionado (el estado que se aplica actualmente a la sección). Sin embargo, la modificación de un atributo de sección con una acción estándar solo anulará el atributo de sección seleccionado. +* *Submenú*: cuando se utilizan sin parámetros y asociados a un comando de menú, un objeto pop-up/lista desplegable o pop-up menú jerárquico, estas acciones muestran un submenú automático. Por ejemplo, si asigna la acción "backgroundColor" a un comando de menú, la selección de este comando de menú a la ejecución mostrará automáticamente los comandos del submenú "Color de fondo". Si asigna la acción "zoom" a un menú pop-up jerárquico, contendrá automáticamente una lista de valores de zoom predefinidos. Tenga en cuenta que estas acciones no pueden asignarse a botones. +* *showDialog*: agregar la cadena "/showDialog" al nombre de la acción permite la visualización del diálogo estándar asociado a la acción. Por ejemplo, puede utilizar "paragraph/styleSheet/showDialog" para abrir el diálogo de entrada que permite la entrada de un nuevo nombre de hoja de estilo. + +| Acción | Modelo | Disponible con | Descripción | +|---|---|---|---| +| anchorHorizontalAlign | {image \| textBox}/anchorHorizontalAlign?value={left \| center \| right} | Image, Textbox, Submenu | Defines the horizontal alignment of the element, relative to the anchorOrigin for images/text boxes in page, or to the layout box for images/text box in embedded mode. This action will reset the horizontal offset to 0. (not enabled for inline images). | +| anchoring | {image \| textBox}/anchoring | Submenu | Default submenu with anchor settings actions for images or text boxes | +| anchorLayout | image/anchorLayout?value={front \| behind \| wrapTopBottom \| wrapSquareLeft \| wrapSquareRight \| wrapSquareLargest \| wrapSquare \| inline}
textBox/anchorLayout?value={front \| behind \| wrapTopBottom \| wrapSquareLeft \| wrapSquareRight \| wrapSquareLargest \| wrapSquare} | Image, Textbox, Submenu | Defines the anchor layout type for an image or a text box. Can be used to transform an inline image to an anchored image, or the reverse. Note: If an image is moved from an anchored mode to inline, the image is inserted at the beginning of the current selected text. "inline" value is not supported for text boxes | +| anchorOrigin | {image \| textBox}/anchorOrigin?value={paper-box \| header-box \| footer-box} | Image, TextBox, Submenu | Defines the area relative to the absolute position of an anchored image or text box. If the element is relative to the header-box/footer-box which is not visible on a page, the element is not displayed. This action will reset horizontal and vertical offsets to 0. Page mode only, not enabled for inline images. | +| anchorPage | {image \| textBox}/anchorPage?value={all \| current \| currentSubSection} | Image, TextBox, Submenu | Defines the page(s) where the selected image or text box is displayed (not enabled for inline images). Page mode only. | +| anchorSection | {image \| textBox}/anchorSection?value={all \| current} | Image, TextBox, Submenu | Defines the section(s) where the selected image or text box is displayed. (not enabled for inline images). Page mode only. | +| anchorVerticalAlign | {image \| textBox}/anchorVerticalAlign?value={top \| center \| bottom} | Image, TextBox Submenu | Defines the vertical alignment of the image or text box, relative to the anchorOrgin for an image or text box in page, or to the layout box for an image or text box in embedded mode. This action will reset the vertical offset to 0 (not enabled for inline images). Note: See "verticalAlign" action for the vertical alignment inside the text box | +| avoidPageBreakInside | {paragraph/}avoidPageBreakInside | Paragraph | | +| background | {doc \| paragraph \| image \| textBox \| section \| header \| footer \| table \| row \| column \| cell/}background | Document, Paragraph, Image, TextBox, Section, Header, Footer, Table, Row, Column, Cell, Submenu | For menu commands only. Default submenu for all background attributes. | +| backgroundClip | {doc \| paragraph \| image \| textBox \| section \| header \| footer \| table \| row \| column \| cell/}backgroundClip?value={paper-box \| border-box \| padding-box \| content-box} | Document, Paragraph, Image, TextBox, Section, Header, Footer, Table, Row, Column, Cell, Submenu | Changes target background clipping box (default target is paragraph). Paper-box targets document and section only. | +| backgroundColor | {doc \| paragraph \| image \| textBox \| section \| header \| footer \| table \| row \| column \| cell/}backgroundColor?value={
cell/merge | Paragraph, Cell | Used with paragraphs: merges paragraphs. Used with cells: merges the selected cells. | +| minHeight | {paragraph \| image/}minHeight?value=
cell/split | Paragraph, Cell | Used with paragraph: splits paragraph. Used with cells: splits the selected cells (only cells that have been already merged may be split). | +| styleSheet | {paragraph \| image/}styleSheet?value={1<=number<=number of target style sheets} | Paragraph, Image, Submenu, showDialog | Applies Nth stylesheet to the selected target elements. With dialog, new stylesheet will use current attributes from the first selected target. (default target is paragraph) Ex: styleSheet?value=1 //apply first paragraph style sheet to the selected paragraphs and set it as paragraph stylesheets. | +| styleSheets | {paragraph \| image/}styleSheets | Paragraph, Image, Submenu | Default submenu for editing target stylesheets. | +| tabDecimalSeparator | tabDecimalSeparator?value={point \| comma \| pointOrComma \| system} | Document, Submenu | Defines the character used as decimal separator by decimal tabulations. | +| tableAlign | tableAlign?value={left \| center \| right}
or
table/tableAlign?value={left \| center \| right} | Table, Submenu | Specifies horizontal alignment for a table. | +| table/avoidPageBreakInside | table/avoidPageBreakInside | Table | Allows/disallows page breaks inside tables. Disabled if: the current selection does not contain at least one table the table is in a header or a footer | +| table/bottomCarryOverRow | table/bottomCarryOverRow | Table | Toggles between display/not display of carry-over rows (see Carry-over rows). | +| textAlign | textAlign?value={left \| right \| center \| justify \| initial} | Paragraph | Paragraph text alignment (initial=use right for rtl or left for ltr direction). | +| textBox | textBox | Submenu | Submenu with all actions available for the focused/selected text box | +| textBox/remove | textBox/remove | TextBox | Removes the selected text box | +| textIndent | textIndent?value=
** | **Número** | **Obligatorio** | **Condiciones** | **Descripción** | +| ------------------------------------------------------------- | ----------------------------- | ---------- | --------------- | ------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +|  | Líneas de encabezado | hasta 5 | \- | \- | Encabezado de tabla estándar, ver *Encabezados repetidos* | +| 
| Línea de datos | 1 | sí | La fórmula de la fuente de datos debe devolver elementos iterables | Si la tabla no tiene líneas de encabezado y/o líneeas de ruptura, la línea de datos es la primera línea de la tabla; en caso contrario, es la primera línea después del encabezado o las líneas de ruptura. Suele llenarse con expresiones que utilizan **This** (por ejemplo, *This.item.value*) que dan acceso a los datos procesados cuando el documento está modo *Mostrar valores* y la línea está duplicada. | +|  | Líneas de ruptura ordenadas | hasta 5 | \- | La fórmula de la fuente de datos devuelve elementos iterables | La línea o líneas que aparecen antes o después de la línea de datos. Ver *Líneas de ruptura* | +| 
| Líneas de arrastre inferior | 1 | \- | La fórmula de la fuente de datos debe devolver elementos iterables | La primera línea que sigue a la línea de datos o las líneas de ruptura. Ver *Líneas de arrastre* | +|  | Línea de marcador de posición | 1 | \- | La fuente de datos debe estar definida | La fila de marcador de posición se mostrará en lugar de la fila de datos y las filas de interrupción (si las hay) cuando la fuente de datos esté vacía y el atributo "Mostrar fila de marcador de posición" esté activado en la tabla mediante la acción estándar *emptyDatasource* o la constante *wk empty datasource*. La fila del marcador de posición aparece inmediatamente antes de las demás filas. | +| | Otras líneas | ilimitada | \- | \- | Líneas estándar (no duplicadas) | | + +Ejemplo (Mostrar modo referencias): + + + +Cuando se calculan las fórmulas, la línea duplicada se duplica automáticamente según sea necesario para que coincida con todas las entidades o elementos de la colección devueltos por la fórmula de la fuente de datos: + + + +En todo caso, la siguiente instrucción devuelve el número real de líneas: + +```4d + WP GET ATTRIBUTES($table;wk row count;$vcount) //31 para el ejemplo arriba +``` + +##### Líneas de arrastre + +Las tablas basadas en fuentes de datos soportan **líneas de arrastre inferiores** que se muestran automáticamente en la parte inferior de cada página/columna cuando la tabla se divide en más de una página/columna. Una línea de arrastre puede mostrar información adicional basada en los elementos mostrados/impresos anteriormente, gracias a la expresión **This.previousItems** (ver *Expresiones con This*). Esta función permite, por ejemplo, añadir líneas de subtotal. + + + +Se muestran las líneas de arrastre: + +* cuando una tabla de fuente de datos no cabe en una sola página (o columna) +* en la parte inferior de la tabla +* en la primera página (o primera columna) y en todas las demás excepto en la última. + +**Importante:** las líneas de arrastre sólo están disponibles en las tablas llenadas por una fórmula de fuente de datos que devuelva una colección o una selección de entidades no vacía y en el modo de visualización de valores. En todos los demás casos o cuando la fórmula de la fuente de datos no se ha calculado, una línea de arrastre se muestra como una línea normal. + +Para crear líneas de arrastre: + +1. En la plantilla de la tabla, añada una línea justo después de la línea de datos o las líneas de ruptura e inserte las fórmulas necesarias en su interior, utilizando, por ejemplo **This.previousItems**. +2. Active la funcionalidad de arrastre de línes para su documento. Puede: +\- utilizar la acción estándar *bottomCarryOverRow* (ver *Utilizar las acciones estándar 4D Write Pro*), o +\- utilizar el comando [WP SET ATTRIBUTES](../commands/wp-set-attributes) con el selector de atributos wk bottom carry over row *Tablas*. + +**Nota:** no se permiten saltos de página dentro de las líneas cuando la función de traspaso de líneas está activada (ver *Paginación de tablas*). Las opciones correspondientes, si se definen, se ignoran. + +##### Líneas de ruptura + +Las tablas basadas en fuentes de datos soportan una o varias **Líneas de ruptura de orden** que pueden mostrarse antes o después de la línea de datos. Las **Líneas de ruptura de orden** le ayudan a dividir visualmente los elementos de la fuente de datos ya ordenados en la tabla en diferentes partes basadas en un valor de fórmula calculado. + +Cada vez que cambia el valor de la fórmula, se inserta una nueva línea de ruptura. Por lo tanto, para que las tablas se muestren correctamente, la selección de entidades (o colección) utilizada como fuente de datos de la tabla debe estar ordenada en consecuencia. Por ejemplo, si se desean desgloses por países y ciudades, la fuente de datos debe ordenarse del siguiente modo: *ds.people.all().orderBy("country asc, city asc")* + +El valor de ruptura se define mediante el atributo *wk break formula*. El valor suele ser una fórmula basada en una propiedad del elemento como "This.item.name'', de lo contrario el valor calculado puede no cambiar nunca, lo que hace que la fórmula de ruptura sea inútil. El atributo wk break formula se ignora si la tabla no tiene fuente de datos o si la línea es un encabezado. Una línea de ruptura debe ser adyacente a la línea de datos (ya sea antes o después), o a otra línea de interrupción, de lo contrario se ignora. + +```4d + WP SET ATTRIBUTES($row_2;wk break formula;Formula(This.item.country)) +``` + +Gracias a la expresión **This.breakItems** puede utilizar esta funcionalidad, por ejemplo, para mostrar la media total de las líneas de datos dentro de una línea de interrupción. breakItems es un subconjunto evaluado de la fuente de datos de la tabla, ya sea una selección de entidades si la fuente de datos de la tabla es una selección de entidades, o una colección si la fuente de datos es una colección. Así, dentro de una línea de ruptura, puede escribir: This.breakItems.sum("salario") + +Para crear líneas de ruptura: + +1. Ordene la fuente de datos con los niveles correspondientes a las rupturas que desea mostrar, por ejemplo, *ds.People.all().orderBy("continent asc, country asc, city asc")* +2. Dibuje la(s) líneas(s) de ruptura en la plantilla de tabla. Si los saltos se encuentran después de la línea de datos, deben coincidir con el **orden inverso** de la fuente de datos, y si se encuentran antes de la línea de datos, deben coincidir con el mismo orden de la fuente de datos. +3. Defina el atributo *wk break formula* para la(s) línea(s) seleccionada(s): + +```4d + $row:=WP Table get rows($table;2;1) //select the second row as break + WP SET ATTRIBUTES($row_2;wk break formula;Formula(This.item.country)) +``` + +##### Expresiones con This + +Cuando se utiliza en una fórmula dentro de la tabla, la palabra clave **This** da acceso a diferentes datos según el contexto: + +| **Contexto
** | **Expresión** | **Tipo** | **Devuelve** | +| ---------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------ | ------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Todos | This.table | Objeto | Tabla actual | +| | This.row | Objeto | Elemento de la línea actual de la tabla | | +| | This.rowIndex | Número | Índice de la línea actual, empezando por 1 | | +| Cuando se ha definido una fuente de datos para la tabla | This.table.dataSource | Objeto (formula) | Datasource como una fórmula | +| | This.tableData | Colección o selección de entidades (normalmente) | table.dataSource evaluada | | +| En cada línea duplicada cuando una fuente de datos tabla devuelve una colección o una selección de entidades | This.item.xxx | Todos | Asignado a cada elemento de la colección de datasource de la tabla o de la selección de entidades, por ejemplo **This.item.firstName** si la entidad asociada tiene el atributo *firstName* | +| | This.itemIndex | Número | Índice del elemento actual en la colección o selección de entidades, empezando por 0 | | +| En toda línea (excepto en las líneas de encabezado) cuando una fuente de datos tabla devuelve una colección o una selección de entidades | This.previousItems | Colección o selección de entidades | Elementos mostrados en las páginas anteriores a la línea de arrastre inferior (si la hay) o anteriores a la línea de la expresión, incluida la página en la que se muestra la línea que contiene la expresión.
Esta expresión devuelve el mismo tipo de valor que la expresión **This.tableData**. | +| In a break row | This.breakItems | Colección o selección de entidades | Elementos de la colección o selección de entidades mostrados en las líneas entre: la línea de ruptura actual y la línea de ruptura anterior del mismo nivel (o el inicio de la tabla) si la(s) línea(s) de ruptura se muestran después de la línea de datos. la línea de ruptura y la siguiente línea de ruptura del mismo nivel (o el final de la tabla) si la línea o líneas de ruptura se muestran antes de la línea de datos. | + +En cualquier otro contexto, estas expresiones devolverán *undefined*. + +**Nota:** para más información sobre la inserción de fórmulas, ver [WP INSERT FORMULA](../commands/wp-insert-formula). + +##### Trabajar con una tabla fuente de datos + +Cuando se llena una tabla desde una fuente de datos, las filas se crean automáticamente cuando se calculan las referencias. Se pueden insertar o eliminar líneas, editar el contenido de las celdas, cambiar el estilo, etc: + + + +Sin embargo, tenga en cuenta que si la fuente de datos de la tabla se vuelve a calcular, toda modificación realizada en las líneas calculadas (excepto en la primera línea) se pierde. Por otro lado, como la primera línea es la línea de datos, cualquier modificación realizada en esta línea se propagará a todas las líneas si se vuelve a calcular la fuente de datos de la tabla. Lo mismo ocurre con las líneas de interrupción, todas las modificaciones realizadas en las líneas de ruptura calculadas se pierden, excepto en el caso de las líneas de ruptura de plantilla (que pueden estar situadas al final o al principio de la tabla). + +Por ejemplo: + + + +Después de volver a calcular las expresiones: + + + +Cuando el cursor se inserta en una celda de una tabla llenada con una fuente de datos, aparece un icono de advertencia a la izquierda junto con un consejo que muestra información: + + + +Cuando las fórmulas se muestran como referencias o cuando se guarda el documento, sólo se muestra/guarda la primera fila como plantilla (si las fórmulas no están congeladas). + +Cuando se congelan las fórmulas, la tabla se convierte en una tabla estándar y se restablece la fuente de datos de la tabla. + +**Nota:** la acción estándar *freezeExpressions* no recalcula las fórmulas. \ No newline at end of file diff --git a/i18n/es/docusaurus-plugin-content-docs/current/WritePro/user-legacy/importing-4d-write-documents.md b/i18n/es/docusaurus-plugin-content-docs/current/WritePro/user-legacy/importing-4d-write-documents.md new file mode 100644 index 00000000000000..0ec8635eba470a --- /dev/null +++ b/i18n/es/docusaurus-plugin-content-docs/current/WritePro/user-legacy/importing-4d-write-documents.md @@ -0,0 +1,227 @@ +--- +id: importing-4d-write-documents +title: Importar documentos 4D Write +displayed_sidebar: docs +--- + +#### + +Una de las principales funcionalidades del nuevo 4D Write Pro es la capacidad de importar y convertir documentos 4D Write Pro existentes. Esto le permitirá migrar las aplicaciones que se basan en el plug-in 4D Write. + +**Notas de compatibilidad**: + +* Sólo se soportan documentos 4D Write de la última generación ("4D Write v7"). +* No se soporta por el momento copiar\-pegar desde un documento 4D Write a un área 4D Write Pro. La importación de un documento 4D Write sólo puede hacerse utilizando los comandos del lenguaje 4D Write Pro. +* Los retornos de carro (CR) en las fórmulas se comportan de manera diferente en 4D Write y 4D Write Pro. En 4D Write, siempre se interpretan como saltos de párrafo, mientras que en 4D Write Pro se interpretan como saltos de línea por defecto. Para mantener CR en fórmulas como saltos de párrafo en documentos 4D Write importados, después de la conversión utilice: +```4d + WP SET ATTRIBUTES(wp;wk break paragraphs in formulas;wk true) +``` + +Para más información, consulte *Gestión de fórmulas*. + +#### Cómo importar un documento 4D Write + +Los objetos 4D Write Pro ofrecen dos maneras de importar documentos 4D Write: + +* Para los archivos 4D Write Pro almacenados en el disco, se utiliza el comando [WP Import document](../commands/wp-import-document), +* Para las áreas 4D Write almacenadas en campos BLOB, se utiliza el comando [WP New](../commands/wp-new). + +Para más información, consulte la descripción de estos comandos. + +#### ¿Qué propiedades se conservan de 4D Write? + +Para facilitar la migración desde el plug-in 4D Write a 4D Write Pro, queremos soportar tantas funcionalidades 4D Write como sea posible en objetos 4D Write Pro. + +Este párrafo muestra las propiedades del plug-in 4D Write que se recuperan en un área 4D Write Pro después de una importación con los comandos *WP Import document* o *WP New*. + +Tenga en cuenta sin embargo, que hay algunas diferencias, que no se consideran como bugs. Esto se debe, por ejemplo, a la fuente predeterminada utilizada en 4D Write Pro para viñetas, o pequeñas conversiones en el tipo Subrayado. + +##### Información del documento + +| **Plug-in** **4D Write** | **4D Write Pro** | +| ------------------------- | --------------------------------------------------------- | +| Creación fecha y hora | Disponible | +| Modificación fecha y hora | Disponible | +| Bloqueado | No disponible (utilizar la propiedad objeto sólo lectura) | +| Título | Disponible | +| Tema | Disponible (sólo texto plano) | +| Autor | Disponible | +| Empresa | Disponible | +| Notas | Disponible | + +##### Parámetros de visualización del documento + +| **Plug-in** **4D Write** | **4D Write Pro** | +| ---------------------------------- | ------------------------------------------------------------------------------- | +| Vista modo página | No importado (utilizar el modo de vista Documento/Página en el menú contextual) | +| Vista reglas | No importado (utilizar propiedad objeto) | +| Vista marcos | No importado (utilizar propiedad objeto) | +| Vista encabezado | No importado (utilizar propiedad objeto) | +| Vista pie | No importado (utilizar propiedad objeto) | +| Vista encabezado de primera página | No disponible | +| Vista pie de primera página | No disponible | +| Vista imágenes | No disponible | +| Vista HScrollbar | No importado (utilice la propiedad de objeto desplazable hor.) | +| Vista VScrollbar | No importado (utilice la propiedad de objeto desplazable vert.) | +| Vista invisible characters | No importado (utilizar propiedad objeto) | +| Vista referencias | No importado (utilice [ST SET OPTIONS](../../commands/st-set-options)) | +| Vista separadores de columna | Disponible (a partir de v17) | +| Vista H Splitter | No disponible | +| Vista V Splitter | No disponible | +| Vista Wysiwyg | No disponible | +| Vista zoom | No importado (utilice Document/Zoom en el menú contextual) | + +##### Parámetros del documento + +| **Plug-in** **4D Write** | **4D Write Pro** | +| ------------------------ | ------------------------------------------------------------------------ | +| Unidad | No importado (utilizar Documento/Unidad de medida en el menú contextual) | +| Lenguaje | No disponible | +| Conteo de columnas | Disponible (a partir de v17) | +| Espacio entre columnas | (a partir de v17) | +| Viudas y huérfanos | Disponible | +| Pestaña por defecto | Disponible | +| Pestaña Líder | Disponible | +| Color URL | No disponible | +| Color visitado URL | No disponible | + +**Nota:** el separador del sistema (como devuelto por [GET SYSTEM FORMAT](../../commands/get-system-format)) se utiliza como separador décimal para las tabulaciones decimales. Puede cambiar este parámetro utilizando el comando [WP SET ATTRIBUTES](../commands/wp-set-attributes). + +##### Parámetros de paginación de documentos + +| **Plug-in** **4D Write** | **4D Write Pro** | +| ---------------------------------------------------------------- | ---------------- | +| Ancho de página | Disponible | +| Alto página | Disponible | +| Número primera página | Disponible | +| Primera página encabezado pies diferentes | Disponible | +| Página encabezado Izquierda y derecha y pie de página diferentes | Disponible | +| Encuadernación | Disponible | +| Páginas opuestas | Disponible | +| Márgenes página | Disponible | +| Encabezado margen superior | Disponible | +| Encabezado margen inferior | Disponible | +| Pie de página margen superior | Disponible | +| Pie de página margen inferior | Disponible | +| Primera página margen superior | Disponible | +| Primera página margen inferior | Disponible | +| Encabezado primera página margen superior | Disponible | +| Encabezado primera página margen inferior | Disponible | +| Pie de página primera página margen superior | Disponible | +| Pie de página primera página margen inferior | Disponible | +| Primera página es correcta | Disponible | + +##### Parámetros de impresión de documentos + +| **Plug-in 4D Write** | **4D Write Pro** | +| -------------------- | ---------------- | +| Clase de papel | No disponible | +| Paisaje | No disponible | +| Ancho | No disponible | +| Alto | No disponible | +| Márgenes de usuario | No disponible | +| Escala | No disponible | +| Resolución X | No disponible | +| Resolución Y | No disponible | + +##### Imágenes + +**Notas de compatibilidad:** + +* Los modos de visualización de imágenes se importan automáticamente a partir de 4D Write Pro v19 R2, utilizando [WP Import document](../commands/wp-import-document). Puede restaurar el comportamiento anterior (todas las imágenes se escalan para ajustarse) utilizando el atributo *importDisplayMode*. +* En Windows, las imágenes en formato PICT Mac OS son importadas pero no pueden ser renderizadas en 4D Write Pro. Si importa documentos que contengan imágenes de este tipo, es necesario convertirlas a otro formato. Tenga en cuenta que el formato PICT es obsoleto y no debe ser utilizado. + +| **Plug-in** **4D Write** | **4D Write Pro** | +| ---------------------------------------------- | ----------------------------------------------------------- | +| X (izquierda) | (unicamente imágenes en página ) | +| Y (arriba) | (unicamente imágenes en página ) | +| Ancho | Disponible | +| Alto | Disponible | +| Número de página | Disponible (a partir de 4D v16 R6) | +| Detrás | Disponible (a partir de 4D v16 R6) | +| No en primera página | Disponible (a partir de 4D v16 R6) | +| Modo de visualización (escala a ajustar, etc.) | Disponible | +| Es una expresión | Disponible para imágenes en el texto(a partir de 4D v16 R5) | +| Conservar el tamaño | No importado (automático en 4D Write Pro) | + +##### Propiedades de caracteres + +| **Plug-in** **4D Write** | **4D Write Pro (span)** | +| --------------------------------------------- | ------------------------------- | +| Itálica | Disponible | +| Negrita | Disponible | +| Tachado | Disponible | +| Subrayado | Disponible | +| Sombra | Disponible | +| Exponente (superscript o subscript) | Disponible | +| Mayúsculas o pequeñas mayúsculas | Disponible | +| Familia de fuente | Disponible | +| Tamaño de fuente | Disponible | +| Color texto | Disponible | +| Color fondo de texto | Disponible | +| Color subrayado | Disponible | +| Color tachado | Disponible | +| Color sombra | Disponible | +| Propiedad usuario | No disponible | +| Corrección ortográfica (sintaxis y gramática) | No importada (propiedad área) | +| Apariencia | No disponible | +| Hoja de estilo | Disponible (a partir de 4D v18) | + +##### Propiedades párrafos + +| **Plug-in** **4D Write** | **4D Write Pro** | +| ---------------------------------------- | ---------------- | +| Justificación | Disponible | +| Interlinea | Disponible | +| Viñetas | Disponible | +| Margen izquierdo | Disponible | +| Margen derecho | Disponible | +| Indentar texto | Disponible | +| Estilo borde linea | Disponible | +| Color borde linea | Disponible | +| Color fondo borde | Disponible | +| Borde izquierdo | Disponible | +| Borde derecho | Disponible | +| Borde superior y borde interior arriba | Disponible | +| Borde inferior y borde interior inferior | Disponible | +| Espacio de borde | Disponible | +| Hoja de estilo | Disponible | +| Tabulaciones | Disponible | + +##### Hipervínculos + +| **Plug-in** **4** **D Write** | **4D Write Pro** | +| ----------------------------- | ------------------------------------------------- | +| Enlace URL | Disponible (\*) | +| Enlace método 4D | Disponible (\*\*) (starting with v17 R5) | +| Enlace documento abierto | Disponible (convertido a un url de archivo local) | + +* (\*) A partir de 4D v16 R4, los enlaces URLs se convierten en atributos editables. Para mayor información, consulte *Gestión de URLs*. +* (\*\*) Es necesario adaptar los parámetros recibidos dentro de los métodos llamados: + +| **Parámetros** | **Plug-in 4D Write** | **4D Write Pro** | +| -------------- | ----------------------------- | --------- | +| $1 | Entero largo- Referencia del área 4D Write | Texto - Nombre del área 4D Write Pro | +| $2 | Texto - Etiqueta de enlace | Objeto - Descripción del enlace:.method - Nombre del método del enlace. Debe permitirse con el comando [SET ALLOWED METHODS](../../commands/set-allowed-methods). .parameter - valor del parámetro de usuario pasado al método (si se usa).range - Rango de la etiqueta del enlace. Ver *Comandos de gestión de rangos* | +| $3 | Entero largo - Parámetro de usuario (methodRef) | \- | + +##### Expresiones 4D + +| **Plug-in** **4D Write** | **4D Write Pro** | +| ------------------------ | ----------------- | +| Expresión 4D | Disponible\* | +| Fecha y hora | Disponible | +| Expresión HTML | No disponible\*\* | +| Expresión RTF | No disponible | + +\* Utilice el comando [WP SET ATTRIBUTES](../commands/wp-set-attributes) con el atributo wk break paragraphs in formulas para transformar el CR devuelto por las fórmulas en saltos de párrafo en el documento importado (saltos de línea por defecto). (Ver *Gestión de fórmulas*) + +\*\*se puede importar como texto entre las etiquetas **##htmlBegin##** y **##htmlEnd##** si utiliza la constante wk import html expressions as text. + +##### Datos de texto + +| **Plug-in** **4D Write** | **4D Write Pro** | +| -------------------------- | ---------------- | +| Datos de texto principales | Disponible | +| Datos de texto encabezado | Disponible | +| Datos de texto Pie | Disponible | \ No newline at end of file diff --git a/i18n/es/docusaurus-plugin-content-docs/current/WritePro/user-legacy/importing-and-exporting-in-docx-format.md b/i18n/es/docusaurus-plugin-content-docs/current/WritePro/user-legacy/importing-and-exporting-in-docx-format.md new file mode 100644 index 00000000000000..e892bdfde4ffc5 --- /dev/null +++ b/i18n/es/docusaurus-plugin-content-docs/current/WritePro/user-legacy/importing-and-exporting-in-docx-format.md @@ -0,0 +1,195 @@ +--- +id: importing-and-exporting-in-docx-format +title: Importar y Exportar al formato docx +displayed_sidebar: docs +--- + +#### + +4D Write Pro importar y exportar documentos en el formato .docx. Este formato es compatible con aplicaciones de procesamiento de textos como Microsoft Word. + +**Nota de compatibilidad:** el soporte para documentos 4D Write Pro importados o exportados en formato .docx solo está certificado para Microsoft Word 2010 y versiones posteriores. Las versiones anteriores, en particular Microsoft Word 2007, son susceptibles a que no se puedan abrir los documentos. + +#### Cómo importar formato .docx + +Los documentos en formato .docx pueden ser importados a 4D Write Pro con el comando [WP Import document](../commands/wp-import-document). Para más información, consulte la descripción de este comando. + +##### Cambios de comportamiento + +Aunque la mayoría de los ajustes de .docx se conservan, se sabe que algunos ajustes no son compatibles o se comportan de forma diferente en 4D Write Pro. Estos son: + +###### Alineación / Diseño + +| **Configuración** | **Descripción** | +| --------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Áreas de texto ancladas | Las áreas de texto ancladas son importadas como cajas de texto por defecto (también pueden ignorarse o importarse como texto en línea, ver la opción de comando [WP Import document](../commands/wp-import-document)). Sólo se pueden importar áreas de texto simples. Las áreas de texto ancladas con texto alrededor o en línea con texto se importan con sus propiedades de ajuste de texto (excepción: la opción de ajuste .docx "ajustado" se importa como ajustar cuadrado). | +| Disposición de los párrafos | Sólo se soportan disposiciones de texto occidentales. Los estilos de párrafo distribuido, tailandés y asiático no son soportados. | +| Tamaño de página | No se soportan diferentes tamaños de página por sección. Sólo se importa el tamaño de página de la primera sección. | + +###### Fondo + +| **Configuración** | **Descripción** | +| ----------------- | --------------- | +| Marca de agua | No soportado | + +###### Expresiones + +| **Configuración** | **Descripción** | +| ----------------- | --------------------------------------- | +| MS Word equations | No soportado. Los datos no se importan. | +| MS Word charts | No soportado. Los datos no se importan. | + +###### Listas + +| **Configuración** | **Descripción** | +| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| Listas jerárquicas | Las listas multiniveles no son soportadas. Las listas multinivel se convierten en listas de un solo nivel, por lo que el aspecto y/o la numeración de la lista pueden ser diferentes | + +###### Imágenes + +| **Configuración** | **Descripción** | +| --------------------- | ------------------------------------------------------------------------------------------------------------------- | +| Formas DrawingML | Sólo se importan las imágenes DrawingML simples (en línea o ancladas). No se soportan formas DrawingML complejas. | +| Formas o imágenes VML | No soportadas. VML es obsoleto en MS Word y no debe utilizarse en documentos creados con MS Word 2010 o anteriores. | +| Modelos 3D | No soportados, aunque la última imagen 2D renderizada del modelo 3D puede importarse si está presente en el .docx. | +| SmartArt | No soportado. | + +###### Referencias + +| **Configuración** | **Descripción** | +| --------------------- | ------------------------------------------- | +| Comentarios | No se soportan. El contenido no se importa. | +| Notas a pie de página | No se soportan. El contenido no se importa. | + +###### Espaciado + +| **Configuración** | **Descripción** | +| ----------------------- | ---------------------------------------------------------------------------------------- | +| Interlineado "At least" | No se soporta. El interlineado "At least" se convierte en un interlineado fijo (simple). | +| Ajustar texto | No se soporta. Se utiliza el estilo normal de 4D Write Pro. | + +###### Tablas + +| **Parámetro** | **Descripción** | +| ------------- | ---------------------------------------------------- | +| Tablas | Las tablas contiguas no se fusionan automáticamente. | + +###### Texto + +| **Configuración** | **Descripción** | +| -------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Temas | Los temas de texto no se importan. Si una definición de color o fuente hace referencia a un color o fuente en un tema, se utilizará el último color o fuente calculado. En caso contrario, se utilizará el | +| color o la fuente definida en el tema. | | + +##### Historial de importación + +Cuando se importa el formato .docx en 4D Write Pro, se crea un objeto historial que se incluye dentro del objeto de documento importado. Este objeto puede ser recuperado por medio del atributo personalizado "importLog" (o la constante wk import log): + +```4d + $myDoc:=WP Import document("test.docx") + if($myDoc#Null) + var $log : Object + $log:=$myDoc[wk import log] + End if +``` + +El objeto historial de importación contiene las siguientes propiedades: + +| Constante | Comentario | +| ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| wk import log | Objeto de registro que contiene información sobre la operación de importación .docx. Las propiedades son de sólo lectura y no se pueden definir:
| **Propiedad ** | **Tipo ** | **Descripción** | |
| status | Texto | Estado de la importación: exitoso - el documento es importado a 4D Write Pro fallido - se devuelve un documento vacío de 4D Write Pro | |
| developer | Colección | Colección de objetos mensaje para los desarrolladores de 4D Write Pro. | |
| \[ \].type | Texto | El tipo de mensaje registrado: info warning error | |
| \[ \].message | Texto | Mensaje sobre la operación de importación. | |
| user | Colección | Colección de objetos mensaje para los usuarios de 4D Write Pro. | |
| \[ \].type | Texto | El tipo de mensaje registrado: info warning | |
| \[ \].messageShort | Texto | Mensaje breve sobre la operación de importación. | |
| \[ \].messageLong | Texto | Mensaje extenso sobre la operación de importación. |
**Tipo de valor**: Entero largo *(valor para `wk type table row`)* | +| `wk column count` | `columnCount` | *(Atributo de rango de sólo lectura)* Número total de columnas del rango.
**Tipo de valor**: Entero largo | +| `wk first column` | `firstColumn` | *(Atributo de rango de sólo lectura)* Número de la primera columna del rango.
**Valor**: Entero largo | +| `wk first row` | `firstRow` | *(Atributo de rango de sólo lectura)* Número de la primera fila del rango.
**Valor**: Entero largo | +| `wk header row count` | `headerRowCount` | *(Lectura/Escritura)* Número de líneas de la tabla con el atributo `wk header` definido como True.
El valor máximo es 5. Si se pasa un valor superior a 5, `wk header` se define como True sólo para las cinco primeras líneas *(ver [Encabezados repetidos](./handling-tables.md#repeated-headers))* | +| `wk row count` | `rowCount` | *(Atributo de rango de sólo lectura)* Número total de columnas en el rango.
**Valor**: Entero largo | +| `wk table` | `table` | *(Atributo de solo lectura)* La tabla padre.
**Tipo de valor**: objeto | +| `wk table ID` | `tableID` | *(Atributo de rango de sólo lectura)* ID de la tabla principal del rango.
**Valor**: cadena | + + + +Varios comandos le permiten definir rangos: + +- [WP Text range](../commands-legacy/wp-text-range.md): devuelve un nuevo rango correspondiente a los límites que pasa como parámetros. +- [WP Selection range](../commands-legacy/wp-selection-range): devuelve un nuevo rango que corresponde a la selección usuario actual. +- [WP Picture range](../commands-legacy/wp-picture-range): devuelve un nuevo rango que contiene solo las imágenes. +- [WP Paragraph range](../commands-legacy/wp-paragraph-range): devuelve un nuevo rango que contiene solo los párrafos. +- [WP Table range](../commands-legacy/wp-table-range): devuelve un nuevo rango que contiene solo las tablas. + +Puede obtener información sobre la posición de un rango en un documento (número de página, número de columna…) usando la comando [WP Get position](../commands-legacy/wp-get-position). + + + diff --git a/i18n/es/docusaurus-plugin-content-docs/current/WritePro/user-legacy/storing-4d-write-pro-documents-in-4d-object-fields.md b/i18n/es/docusaurus-plugin-content-docs/current/WritePro/user-legacy/storing-4d-write-pro-documents-in-4d-object-fields.md new file mode 100644 index 00000000000000..3818e96a527ca0 --- /dev/null +++ b/i18n/es/docusaurus-plugin-content-docs/current/WritePro/user-legacy/storing-4d-write-pro-documents-in-4d-object-fields.md @@ -0,0 +1,175 @@ +--- +id: 4d-write-pro-documents +title: Documentos 4D Write Pro +displayed_sidebar: docs +--- + +## Formato del documento .4wp + +Puede guardar los documentos 4D Write Pro en el disco y reabrirlos sin pérdidas con el formato **.4wp** nativo. + +El formato **.4wp** consiste en una carpeta zip cuyo nombre es el título del documento y cuyo contenido es el texto HTML y las imágenes: + +* el texto HTML combina HTML estándar con expresiones 4D (no interpretadas), así como también etiquetas 4D específicas, +* las imágenes se almacenan en una carpeta con el mismo nombre que el título del documento, junto al archivo HTML. + +Como los documentos .4wp se basan en HTML, pueden importarse o abrirse en cualquier aplicación externa que soporte HTML. + +El formato interno de los documentos 4D Write Pro es HTML extendido propietario, compatible con HTML5/XHTML5, pero utiliza su propio subconjunto de atributos y de etiquetas HTML/CSS. Como resultado, sólo los documentos HTML exportados por 4D Write Pro pueden ser abiertos por 4D Write Pro sin riesgo de perder información. La importación de documentos HTML creados externamente puede producir errores. + +Para mayor información puede [**descargar la lista de atributos de 4D Write pro con la definición asociada como estilo CSS o etiqueta XHTML**](https://download.4d.com/Documents/Products%5FDocumentation/LastVersions/Line%5F19/4DWP-attributes-and-xhtml.pdf) en 4D Write Pro XHTML. + +### Retrocompatibilidad + +Siempre puede reabrir un documento .4wp con una versión anterior de 4D Write Pro. Si contiene atributos que fueron añadidos en versiones más recientes, estos atributos son simplemente ignorados. Sin embargo, si guarda el documento, los atributos se eliminan del documento y se pierden. + +## Almacenar los documentos 4D Write Pro en los campos objeto 4D + +Puede guardar automáticamente sus documentos 4D Write Pro en el archivo de datos de 4D. Si ha creado un área 4D Write Pro en un formulario y crear un campo Objeto para almacenar el contenido del área, el texto introducido en el área y se guarda automáticamente con cada registro cuando se valida el registro. Luego puede utilizar el comando [QUERY BY ATTRIBUTE](../../commands/query-by-attribute) para seleccionar los registros en función del valor de sus atributos internos. También puede añadir y consultar sus propios atributos con las áreas 4D Write Pro. + +Esta sección describe las siguientes funcionalidades: + +* Asociar un campo objeto 4D a un área 4D Write Pro en un formulario +* Definir, leer o buscar atributos personalizados en los documentos 4D Write Pro, utilizando los comandos estándar [OB SET](../../commands/ob-set), [OB Get](../../commands/ob-get) y [QUERY BY ATTRIBUTE](../../commands/query-by-attribute). + +### Asociar un campo objeto 4D a un área 4D Write Pro + +Para asociar un área 4D Write Pro con un campo 4D Objeto, sólo tiene que hacer referencia al campo en la propiedad Nombre de la variable del área. + +### Crear el campo objeto en estructura + +En la estructura de su base de datos, todo campo objeto 4D se puede utilizar para almacenar los documentos 4D Write Pro. Como en cualquier campo Objeto, debe definir, en función de sus necesidades: + +* el nombre del campo, +* los atributos, como "Exponer con REST resource," así como también el índice, +* la opción de almacenamiento. + + + +Estos parámetros son estándar para los campos Objeto. + +### Asignar el campo objeto al área 4D Write Pro + +Una vez haya definido el campo objeto destinado a almacenar sus documentos 4D Write Pro, sólo tiene que hacer referencia a él en el formulario que contiene el área. Puede utilizar cualquier tabla o formulario proyecto. +En el editor de formularios, escriba el nombre del campo, utilizando la notación estándar "\[Tabla\]Campo" en el área **Nombre de la variable** de la Lista de propiedades para el área 4D Write Pro: + + + +Su área 4D Write Pro se asocia a continuación al campo, lo que garantiza que su contenido se guardará automáticamente con cada registro. Tenga en cuenta que si no utiliza los botones automáticos de 4D, tendrá que guardar el área de forma manual utilizando los comandos 4D. + +### Utilizar atributos personalizados + +Cuando las áreas 4D Write Pro se almacenan en los campos de tipo Objeto, puede guardar y leer los atributos personalizados en los documentos 4D Write Pro, tal como, por ejemplo, el nombre del autor, la categoría del documento, o cualquier información adicional que puede resultar útil. A continuación, puede buscar los atributos personalizados con el fin de seleccionar los registros que cumplen los criterios. + +Los atributos personalizados se exportarán con los comandos [WP EXPORT DOCUMENT](../commands/wp-export-document) o [WP EXPORT VARIABLE](../commands/wp-export-variable). Los atributos personalizados se exportarán al convertir un campo objeto 4D Write Pro a JSON utilizando el comando [JSON Stringify](../../commands/json-stringify) (junto con los atributos del documento principal 4D Write Pro). + +Para definir o leer los atributos personalizados, puede utilizar notación objeto o los comandos [OB Get](../../commands/ob-get) y [OB SET](../../commands/ob-set). + +Por ejemplo, en el método de formulario, puede escribir: + +```4d + If(Form event code=On Validate) + [MyDocuments]My4DWP["myatt_Last edition by"]:=Current user + [MyDocuments]My4DWP.myatt_Category:="Memo" + [MyDocuments]My4DWP:=[MyDocuments]My4DWP //to record the edit + End if +``` + +o: + +```4d + If(Form event code=On Validate) + OB SET([MyDocuments]My4DWP;"myatt_Last edition by";Current user) + OB SET([MyDocuments]My4DWP;"myatt_Category";"Memo") + End if +``` + +También puede leer los atributos personalizados de los documentos: + +```4d + vAttrib:=[MyDocuments]My4DWP.myatt_Category +``` + +o: + +```4d + vAttrib:=OB Get([MyDocuments]My4DWP;"myatt_Category") +``` + +Si ha guardado los atributos personalizados con los documentos 4D Write Pro en su archivo de datos, puede efectuar las búsqueda en estos atributos para crear una selección de registros que contienen el valor del atributo apropiado. En el siguiente ejemplo, se consulta la tabla que contiene el campo Objeto para seleccionar registros: + +```4d + QUERY BY ATTRIBUTE([MyDocuments];[MyDocuments]My4DWP;"myatt_Category";=;"Memo") + //selecciona todos los registros en MyDocuments cuyo atributo personalizado "myatt_Category" tiene el valor "Memo" + //en el campo objeto My4DWP (asociado a un área 4D Write Pro) +``` + +:::warning Sobre los nombres de los atributos personalizados + +como los atributos personalizados comparten el mismo espacio de nombre que los atributos internos de los documentos 4D Write Pro, le recomendamos encarecidamente que utilice prefijos al definir sus propios nombres de atributos, con el fin de evitar cualquier conflicto entre los atributos internos y personalizados. Los nombres sin prefijo están reservados para los atributos internos de 4D Write Pro. Puede utilizar cualquier prefijo personalizado (utilizamos "myatt\_" como prefijo en el ejemplo anterior). + +::: + +**Nota:** Los atributos personalizados no pueden ser gestionados por los comandos [WP SET ATTRIBUTES](../commands/wp-set-attributes), [WP GET ATTRIBUTES](../commands/wp-get-attributes), y [WP RESET ATTRIBUTES](../commands/wp-reset-attributes) (sólo soportan atributos internos de 4D Write Pro). + +## Abrir y exportar documentos + +En las aplicaciones 4D, los documentos, 4D Write Pro son creados importados y exportados por medio de comandos específicos que se encuentran en el tema **4D Write Pro** ([WP EXPORT DOCUMENT](../commands/wp-export-document), [WP EXPORT VARIABLE](../commands/wp-export-variable), [WP Import document](../commands/wp-import-document), [WP New](../commands/wp-new)). + +También puede [asociar un área 4D Write Pro con un campo Objeto](../user-legacy/defining-a-4d-write-pro-area.md#storing-4d-write-pro-documents-in-4d-object-fields) de la base. De esta manera, cada documento 4D Write Pro se guarda automáticamente con el registro y se almacena en los datos de la base. + +## Impresion de documentos 4D Write Pro + +Los documentos 4D Write Pro se pueden imprimir de dos formas + +* como partes de formularios 4D +* como documentos independientes + +### Impresión de documentos + +Puede imprimir objetos 4D Write Pro incluidos en cualquier tipo de [formulario 4D](../../FormEditor/forms.md) (proyecto, tabla, entrada, o salida) utilizando comandos de impresión 4D estándar como [PRINT SELECTION](../../commands/print-selection) o [PRINT RECORD](../../commands/print-record). + +La opción estándar *Impresión tamaño variable* también es soportada(\*) para las áreas 4D Write Pro, lo que permite gestionar cambios de tamaño durante la impresión. Cuando se activa esta opción, el margen (exterior e interior) y el borde superior se aplican sólo a la primera página. El margen (exterior e interior) y el borde inferior se aplican sólo a la última página. Las propiedades de paginación del documento se ignoran: el control de viudas y huérfanos se desactiva y los saltos de página no se aplican (estas propiedades sólo se utilizan para la renderización de páginas en la pantalla o en la impresión independiente del documento). Cuando se selecciona la opción **Impresión tamaño variable**, se imprimen sólo los objetos situados por encima del área en el formulario. Para obtener más información sobre esta opción, consulte "*Impresión tamaño variable*" en el Manual de Diseño. + +(\*) Los comandos [Print object](../../commands/print-object) y [Print form](../../commands/print-form) no son compatibles con esta opción. + +#### Modo Vista para impresión + +Cualquiera que sea el **modo Vista** para el área 4D Write Pro (ver *Configurar propiedades Vista*), siempre se imprime como en el modo **Anidado** cuando se utiliza un comando de impresión 4D como [Print form](../../commands/print-form). En este caso, las siguientes opciones de Apariencia no se tienen en cuenta para los objetos de formulario 4D Write Pro: modo vista Página (siempre "Anidado"), Mostrar encabezados, Mostrar pies de página, Mostrar marco de página (siempre "no"), Mostrar caracteres ocultos (siempre "no"). + +#### Ejemplo + +El siguiente ejemplo muestra el efecto de la opción **Impresión tamaño variable** en un área 4D Write Pro anidada en el formulario de salida por defecto. El siguiente código se ejecuta: + +```4d + ALL RECORDS([Movies]) + ORDER BY([Movies]Title) + PRINT SELECTION([Movies]) +``` + +* Con la opción Imprimir tamaño variable no **seleccionada**, tendrá el siguiente resultado: + +* Con la opción de Imprimir tamaño variable **seleccionada**, tendrá el siguiente resultado: + +*(fuente del texto de ejemplo: Wikipedia)* + +### Impresión de documentos independientes + +A partir de 4D v15 R5, 4D Write Pro incluye nuevas funcionalidades de impresión. Utilizando estas funcionalidades estándar, podrá imprimir documentos 4D Write Pro independientes, así como también controlar las opciones de impresión estándar tales como formato, orientación o números de página. + +#### Comandos 4D Write Pro + +Básicamente, dos comandos manejan la función de impresión 4D Write Pro: *WP PRINT* y *WP USE PAGE SETUP*. + +* [WP PRINT](../commands/wp-print) inicia un trabajo de impresión para el documento 4D Write Pro o agrega el documento al trabajo de impresión actual. +* [WP USE PAGE SETUP](../commands/wp-use-page-setup) modifica la configuración de página de la impresora actual de los atributos de documento 4D Write Pro para el tamaño y orientación. + +**Nota:** en máquinas con Windows 7 o Windows Server 2008 R2, asegúrese de que la *actualización de plataforma para Windows 7* se ha instalado de manera que las funcionalidades de impresión sean compatibles. + +#### Comandos 4D regulares + +Los siguientes comandos 4D soportan las funcionalidades de impresión 4D Write Pro: + +* [SET PRINT OPTION](../../commands/set-print-option) y [GET PRINT OPTION](../../commands/get-print-option): todas las opciones son soportadas para documentos 4D Write Pro impresos por [WP PRINT](../commands/wp-print). Para Paper option y Orientation option, es más eficiente llamar a [WP USE PAGE SETUP](../commands/wp-use-page-setup) para sincronizar fácilmente estos atributos con la configuración del documento 4D Write Pro. Page range option (15) le permite definir el rango de página a imprimir. +* [PRINT SETTINGS](../../commands/print-settings): permite establecer los ajustes de impresión para la impresora actual; si [WP PRINT](../commands/wp-print) se llama después, se utilizará la configuración de impresora modificada si son modificados por diálogos de configuración de impresión (con excepción de los márgenes de diálogo de configuración de página que siempre se basan en el documento 4D Write Pro). +* [OPEN PRINTING JOB](../../commands/open-printing-job) y [CLOSE PRINTING JOB](../../commands/close-printing-job): [WP PRINT](../commands/wp-print) puede llamarse entre estos comandos para insertar uno o más documentos 4D Write Pro en un trabajo de impresión. \ No newline at end of file diff --git a/i18n/es/docusaurus-plugin-content-docs/current/WritePro/user-legacy/stylesheets.md b/i18n/es/docusaurus-plugin-content-docs/current/WritePro/user-legacy/stylesheets.md new file mode 100644 index 00000000000000..605d0ffc4cf898 --- /dev/null +++ b/i18n/es/docusaurus-plugin-content-docs/current/WritePro/user-legacy/stylesheets.md @@ -0,0 +1,138 @@ +--- +id: stylesheets +title: Hojas de estilo +displayed_sidebar: docs +slug: /WritePro/user/stylesheets +--- + + +Una hoja de estilo es un objeto de un conjunto definido de configuraciones de atributos utilizadas para controlar la apariencia de sus documentos 4D Write Pro. Esta configuración se puede aplicar a párrafos y caracteres, como la fuente a mostrar, así como el tamaño, el color y el peso de la fuente. Una vez que se define una hoja de estilo, se guarda como un objeto en el documento 4D Write Pro para que pueda reutilizarse fácilmente. Las hojas de estilo le permiten dar a sus documentos un aspecto distintivo y único, al tiempo que le ahorra tiempo y esfuerzo. + +## Estilo por defecto + +Todos los documentos 4D Write Pro tienen una hoja de estilo de párrafo predeterminada, “Normal”. Las nuevas hojas de estilo (creadas con el comando [WP New style sheet](../commands-legacy/wp-new-style-sheet)) se heredan automáticamente del estilo Normal. Los atributos modificados por una hoja de estilo solo afectan a los párrafos a los que se aplican, el resto del documento conserva la configuración Normal predeterminada. Si se elimina una hoja de estilo, los atributos modificados volverán al estilo Normal. + +El estilo Normal define un valor predeterminado para cada atributo de hoja de estilo en un documento 4D Write Pro y se puede recuperar con el comando [WP Get style sheet](../commands-legacy/wp-get-style-sheet). La hoja de estilo Normal se puede modificar (pero no renombrar) con el comando [WP SET ATTRIBUTES](../commands/wp-set-attributes). Si bien las hojas de estilo creadas con el comando [WP New style sheet](../commands-legacy/wp-new-style-sheet) se pueden eliminar con el comando [WP DELETE STYLE SHEET](../commands-legacy/wp-delete-style-sheet), la hoja de estilo Normal no se puede eliminar. + +## Atributos de hojas de estilo de párrafo y de carácter + +Las hojas de estilo le permiten definir los atributos de párrafos enteros o caracteres específicos: + +- **Párrafo** - La gran mayoría de los atributos que se pueden modificar se aplican solo a los párrafos. Las hojas de estilo de párrafo incluyen configuraciones de estilo de caracteres, así como atributos de formato que solo se pueden aplicar a nivel de párrafo (por ejemplo, márgenes, bordes, pestañas, etc.). +- **Carácter** - Las hojas de estilo de caracteres utilizan solo los atributos apropiados para distinguir el texto (uno o más caracteres) del estilo de párrafo (por ejemplo, encabezados, títulos, texto subrayado, etc.). + +Tenga en cuenta que los estilos de párrafo se aplican a párrafos completos. Para aplicar un estilo solo a una parte específica de un párrafo, debe utilizar una hoja de estilo de caracteres. + +## Precedencia de hoja de estilo + +Se pueden combinar varias hojas de estilo de párrafos y caracteres en el mismo documento 4D Write Pro. Es importante tener en cuenta que la prioridad de la hoja de estilo está determinada por el orden en que se aplican. + +- Si aplica una hoja de estilo de párrafo y luego aplica una hoja de estilo de carácter, la hoja de estilo de carácter tendrá prioridad sobre la hoja de estilo de párrafo. Por ejemplo, podría aplicar una hoja de estilo de párrafo al cuerpo de su documento, luego podría crear una hoja de estilo de caracteres “en negrita” y aplicarla a palabras específicas. La hoja de estilo de párrafo se aplicará al resto del texto, sin embargo, la hoja de estilo de caracteres tendrá prioridad para las palabras designadas. +- Si aplica una hoja de estilo de carácter y luego aplica una hoja de estilo de párrafo, la hoja de estilo de párrafo se aplicará a todo el texto y se eliminarán todos los estilos de caracteres de la hoja de estilo de caracteres. + +## Aplicando hojas de estilo + +Las hojas de estilo se aplican con el comando [WP SET ATTRIBUTES](../commands/wp-set-attributes) utilizando las constantes `wk style sheet` o `wk new line style sheet` (utilizando notación de objetos). + +## Recuperando hojas de estilo + +El comando [WP Get style sheets](../commands-legacy/wp-get-style-sheets) le permite recuperar todas las hojas de estilo de un documento de acuerdo con su tipo específico. El comando [WP Get style sheet](../commands-legacy/wp-get-style-sheet) permite recuperar una sola hoja de estilo por su nombre. + +## Importar y exportar hojas de estilo + +Debido a que las hojas de estilo se almacenan como objetos, pueden importarse fácilmente en otros documentos 4D Write Pro o mantenerse cuando se exportan en múltiples formatos. + +- **Importar** - puede obtener todos los objetos de hoja de estilo de un documento 4D Write Pro designado y usarlos en un nuevo documento con el comando [WP IMPORT STYLE SHEETS](../commands-legacy/wp-import-style-sheets). +- **Exportar** - los comandos [WP EXPORT DOCUMENT](../commands/wp-export-document) o [WP EXPORT VARIABLE](../commands/wp-export-variable.md) exportan sus documentos con hojas de estilo. + +## Atributos de hojas de estilo + +Los siguientes atributos de hoja de estilo de párrafos y caracteres se pueden modificar con los comandos [WP SET ATTRIBUTES](../commands/wp-set-attributes) y [WP RESET ATTRIBUTES](../commands/wp-reset-attributes), o recuperarse con el comando [WP GET ATTRIBUTES](../commands/wp-get-attributes). + +:::note + +Nota: algunos atributos están vinculados entre sí. Por lo tanto, al agregar solo uno de estos atributos, los demás atributos vinculados también se crearán con los valores predeterminados. Para los atributos vinculados, el valor predeterminado puede ser diferente del valor definido en la hoja de estilo Normal. Por ejemplo, si solo define un borde izquierdo rojo, los otros bordes serán negros (valor predeterminado) incluso si en la hoja de estilo Normal se habían definido previamente como púrpura. + +::: + + +| Atributos | Párrafo | Caracter | Asociado con | +|----------------------------------|-----------|-----------|-------------| +| `wk avoid widows and orphans` | X | | | +| `wk background clip` | X | | | +| `wk background color` | X | X | | +| `wk background height` | X | | `wk background width` | +| `wk background image` | X | | | +| `wk background image url` | X | | | +| `wk background origin` | X | | | +| `wk background position horizontal` | X | | `wk background position vertical` | +| `wk background position vertical` | X | | `wk background position horizontal` | +| `wk background repeat` | X | | | +| `wk background width` | X | | `wk background height` | +| `wk border color` | X | | `wk border color bottom`, `wk border color left`, `wk border color right`, `wk border color top` | +| `wk border color bottom` | X | | `wk border color`, `wk border color left`, `wk border color right`, `wk border color top` | +| `wk border color left` | X | | `wk border color`, `wk border color bottom`, `wk border color right`, `wk border color top` | +| `wk border color right` | X | | `wk border color`, `wk border color bottom`, `wk border color left`, `wk border color top` | +| `wk border color top` | X | | `wk border color`, `wk border color bottom`, `wk border color left`, `wk border color right` | +| `wk border radius` | X | | | +| `wk border style` | X | | `wk border style bottom`, `wk border style left`, `wk border style right`, `wk border style top` | +| `wk border style bottom` | X | | `wk border style`, `wk border style left`, `wk border style right`, `wk border style top` | +| `wk border style left` | X | | `wk border style`, `wk border style bottom`, `wk border style right`, `wk border style top` | +| `wk border style right` | X | | `wk border style`, `wk border style bottom`, `wk border style left`, `wk border style top` | +| `wk border style top` | X | | `wk border style`, `wk border style bottom`, `wk border style left` | +| `wk border width` | X | | `wk border width bottom`, `wk border width left`, `wk border width right`, `wk border width top` | +| `wk border width bottom` | X | | `wk border width`, `wk border width left`, `wk border width right`, `wk border width top` | +| `wk border width left` | X | | `wk border width`, `wk border width bottom`, `wk border width right`, `wk border width top` | +| `wk border width right` | X | | `wk border width`, `wk border width bottom`, `wk border width left`, `wk border width top` | +| `wk border width top` | X | | `wk border width`, `wk border width bottom`, `wk border width left`, `wk border width right` | +| `wk direction` | X | | | +| `wk font` | X | X | `wk font bold`, `wk font italic`, `wk font size` | +| `wk font bold` | X | X | `wk font`, `wk font family`, `wk font italic`, `wk font size` | +| `wk font family` | X | X | `wk font`, `wk font bold`, `wk font italic`, `wk font size` | +| `wk font italic` | X | X | `wk font`, `wk font bold`, `wk font family`, `wk font size` | +| `wk font size` | X | X | `wk font`, `wk font bold`, `wk font family`, `wk font italic` | +| `wk line height` | X | | | +| `wk list font` | X | | | +| `wk list string format LTR` | X | | | +| `wk list string format RTL` | X | | | +| `wk list style image` | X | | | +| `wk list style image height` | X | | | +| `wk list style image url` | X | | | +| `wk list style type` | X | | | +| `wk margin` | X | | `wk margin bottom`, `wk margin left`, `wk margin right`, `wk margin top` | +| `wk margin bottom` | X | | `wk margin`, `wk margin left`, `wk margin right`, `wk margin top` | +| `wk margin left` | X | | `wk margin`, `wk margin bottom`, `wk margin right`, `wk margin top` | +| `wk margin right` | X | | `wk margin`, `wk margin bottom`, `wk margin left`, `wk margin top` | +| `wk margin top` | X | | `wk margin`, `wk margin bottom`, `wk margin left`, `wk margin right` | +| `wk min height` | X | | | +| `wk min width` | X | | | +| `wk name` | X | X | | +| `wk new line style sheet` | X | | | +| `wk owner` | X | X | | +| `wk padding` | X | | `wk padding bottom`, `wk padding left`, `wk padding right`, `wk padding top` | +| `wk padding bottom` | X | | `wk padding`, `wk padding left`, `wk padding right`, `wk padding top` | +| `wk padding box` | X | | | +| `wk padding left` | X | | `wk padding`, `wk padding bottom`, `wk padding right`, `wk padding top` | +| `wk padding right` | X | | `wk padding`, `wk padding bottom`, `wk padding left`, `wk padding top` | +| `wk padding top` | X | | `wk padding`, `wk padding bottom`, `wk padding left`, `wk padding right` | +| `_o_wk page break inside` | X | | | +| `wk tab default` | X | | `wk tabs`, `wk tab stop offsets`, `wk tab stop types`, `wk tab stop leadings` | +| `wk tabs` | X | | `wk tab default`, `wk tab stop offsets`, `wk tab stop types`, `wk tab stop leadings` | +| `wk tab stop offsets` | X | | `wk tabs`, `wk tab default`, `wk tab stop types`, `wk tab stop leadings` | +| `wk tab stop types` | X | | `wk tabs`, `wk tab default`, `wk tab stop offsets`, `wk tab stop leadings` | +| `wk tab stop leadings` | X | | `wk tabs`, `wk tab default`, `wk tab stop offsets`, `wk tab stop types` | +| `wk text align` | X | | | +| `wk text color` | X | X | | +| `wk text indent` | X | | | +| `wk text linethrough color` | X | X | | +| `wk text linethrough style` | X | X | `wk text underline style` | +| `wk text shadow color` | X | X | `wk text shadow offset` | +| `wk text shadow offset` | X | X | `wk text shadow color` | +| `wk text transform` | X | X | | +| `wk text underline color` | X | X | | +| `wk text underline style` | X | X | `wk text linethrough style` | +| `wk type` | X (read only) | X (read only) | | +| `wk vertical align` | X | X | | +| `wk width` | X | | | + + diff --git a/i18n/es/docusaurus-plugin-content-docs/current/WritePro/user-legacy/text-boxes.md b/i18n/es/docusaurus-plugin-content-docs/current/WritePro/user-legacy/text-boxes.md new file mode 100644 index 00000000000000..f5ffb3cae1c220 --- /dev/null +++ b/i18n/es/docusaurus-plugin-content-docs/current/WritePro/user-legacy/text-boxes.md @@ -0,0 +1,55 @@ +--- +id: text-boxes +title: Text boxes +displayed_sidebar: docs +slug: /WritePro/user/text-boxes +--- + + + +Las cajas de texto son áreas que se anclan a una página o sección y pueden llenarse con texto, imágenes en línea o tablas. Las cajas de texto pueden colocarse en cualquier lugar de la página y responder a necesidades específicas, por ejemplo, para insertar el nombre o el logotipo de una empresa o un área de direcciones. + + + +**Nota:** una caja de texto no puede contener encabezados, pies de página, columnas, imágenes ancladas u otras cajas de texto. + +Las cajas de texto se añaden con una posición absoluta, delante/detrás del texto, así como ancladas a una página o a partes específicas de un documento en el modo Página: encabezado, pie de página, una sección, todas las secciones o una subsección. Las cajas de texto también pueden utilizarse en modo anidado (ancladas a la caja de capa). + +Añadir una caja de texto a un documento 4D Write Pro puede hacerse de las siguientes maneras: + +* utilizando el comando **WP New text box**, +* utilizando la acción estándar *insertTextBox* + +Para seleccionar una caja de texto, el usuario tiene que hacer clic sobre ella (**Ctrl/Cmd+clic** si la caja de texto está en la capa de fondo). Una vez seleccionado, se puede mover o redimensionar la caja de texto utilizando el ratón o las teclas de flecha. + +Para eliminar una caja de texto seleccionada, puede presionar la tecla **Suprimir** o **Retroceso**, utilizar la acción estándar **textBox/eliminar**, o ejecutar el comando **WP DELETE TEXT BOX**. + +Los atributos de las cajas de texto se manejan con el comando [WP SET ATTRIBUTES](../commands/wp-set-attributes) o *Acciones 4D Write Pro*. Están disponibles los siguientes atributos y acciones: + +| **Propiedad (constante)** | **Acción estándar** | **Comentarios** | +| ------------------------- | --------------------- | ------------------------------------------------------------------------------------------------------------ | +| wk width | textBox/ancho | Si se define en "auto", el ancho se convierte a 8cm ya que el ancho de la caja de texto no puede ser "auto". | +| wk height | textBox/alto | Si está en "auto", la altura se ajusta al contenido. | +| wk padding | textBox/relleno | | +| wk border \[...\] | textBox/borde\[...\] | | +| wk background \[...\] | textBox/fondo\[...\] | | +| wk vertical align | textBox/verticalAlign | | +| wk id | \- | no puede estar vacío para una caja de texto | +| wk anchor \[...\] | textBox/anchor\[...\] | | +| wk owner | \- | sólo lectura | +| wk protected | \- | | +| wk style sheet | \- | sólo lectura y siempre "" (sin hoja de estilo) | + +Las cajas de texto soportan el ajuste automático del texto cuando se anclan a un documento con opciones como a la izquierda, a la derecha, en el lado más grande, arriba y abajo, o todo alrededor suministradas a través de la propiedad wk anchor layout o la acción estándar anchorLayout. Ver esta entrada del blog para más detalles. + + + +Las cajas de texto con ajuste de texto ancladas al cuerpo de la página no afectan al encabezado ni al pie de página (la caja de texto se muestra delante del encabezado o del pie de página); por el contrario, las cajas de texto ancladas al encabezado y al pie de página afectan al cuerpo de la página si se solapan con él. + +**Nota**: si desea anclar una caja de texto con ajuste de texto al encabezado o al pie de página, también debe definir la alineación vertical de la caja de texto en la parte superior. + +Las cajas de texto no se muestran si: + +* el modo de vista es Borrador; +* están centrados o anclados a secciones y la opción **Mostrar HTML WYSIWYG** está marcada; +* la opción "fondo visible" no está activada. \ No newline at end of file diff --git a/i18n/es/docusaurus-plugin-content-docs/current/WritePro/user-legacy/using-a-4d-write-pro-area.md b/i18n/es/docusaurus-plugin-content-docs/current/WritePro/user-legacy/using-a-4d-write-pro-area.md new file mode 100644 index 00000000000000..7a80857b53bd6e --- /dev/null +++ b/i18n/es/docusaurus-plugin-content-docs/current/WritePro/user-legacy/using-a-4d-write-pro-area.md @@ -0,0 +1,410 @@ +--- +id: using-a-4d-write-pro-area +title: Utilizar un area 4D Write Pro +displayed_sidebar: docs +--- + + + + +## Conceptos básicos + +Cuando el documento está en el [modo de vista **Página**](./defining-a-4d-write-pro-area.md#selecting-the-view-mode), las siguientes propiedades del documento se muestran al usuario: + +* Trazos de página para representar los límites de impresión +* Ancho de página y Altura de la página (por defecto: 21x29.7 cm) +* Orientación de la página (por defecto: retrato) +* Margen de la página (por defecto: 2.5 cm) + +También puede utilizar comandos adicionales relacionados con la página como **Document.../Page size** o **Document.../Page orientation**. + +**Nota:** cuando un documento está en modo vista **Anidado** o **Borrador**, las propiedades de la página se pueden definir, aunque su efecto no sea visible. En el modo **Borrador**, los siguientes efectos propiedad de párrafo son visibles: +* Limitación de altura página (líneas dibujadas) +* Columnas +* Evitar salto de página dentro de la propiedad +* Control de viudas y huérfanos. + +## Saltos de párrafo + +Cuando se muestra en modo Página o Borrador (o en el contexto de la impresión de un documento), los párrafos de 4D Write Pro pueden romperse + +* automáticamente, si la altura del párrafo es mayor que la altura de la página disponible, +* en función de los saltos de párrafo establecidos por la programación o por el usuario. + +Los saltos pueden ser añadidos por programación o por el usuario. Las acciones disponibles son: + +* comando [WP INSERT BREAK](../commands/wp-insert-break) +* acción estándar *insertPageBreak* +* Opción **Inserción de salto de página** del menú contextual por defecto + +### Controlar los saltos automáticos + +Puede controlar los saltos automáticos en los párrafos mediante las siguientes funcionalidades: + +* **Control de viudos y huérfanos**: cuando se define esta opción para un párrafo, 4D Write Pro no permite viudas (última línea de un párrafo aislada en la parte superior de una página) ni huérfanas (primera línea de un párrafo aislada en la parte inferior de una página) en el documento. En el primer caso, la línea anterior del párrafo se añade a la parte superior de la página para que se muestren allí dos líneas. En el segundo caso, la primera línea aislada se traslada a la página siguiente. +* **Evitar el salto de página en el interior**: cuando se define esta opción para un párrafo, 4D Write Pro impide que este párrafo se divida en partes en dos o más páginas. +* **Mantener con el siguiente**: cuando se establece esta opción para un párrafo, ese párrafo no puede separarse del que le sigue por un salto automático. Ver wk keep with next y la [acción estándar](./defining-a-4d-write-pro-area.md#standard-actions) correspondiente. + +Estas opciones pueden definirse mediante el menú contextual, o los [atributos](../commands-legacy/4d-write-pro-attributes.md) (`wk avoid widows and orphans`, `wk page break inside paragraph`, o las [acciones estándar](./defining-a-4d-write-pro-area.md#standard-actions) *widowAndOrphanControlEnabled*, *avoidPageBreakInside*). + +## Fondo + +El fondo de los documentos 4D Write Pro y los elementos del documento (tablas, párrafos, secciones, encabezados/pies, etc.) se pueden configurar con los siguientes efectos: + +* colores +* bordes +* imágenes +* origen, posicionamiento horizontal y vertical +* área de dibujo +* repetir + +Estos [atributos](../commands-legacy/4d-write-pro-attributes.md) se pueden definir por programación para elementos individuales en una página y/ o fondos de documento completos con el comando [WP SET ATTRIBUTES](../commands/wp-set-attributes) o por las [acciones estándar](./defining-a-4d-write-pro-area.md#standard-actions). + +Los usuarios pueden modificar atributos de fondo a través del menú contextual como se muestra a continuación: + + + + +Para ver un ejemplo de cómo añadir una imagen de tamaño completo como fondo, vea la demostración de cómo hacerlo [aquí](http://download.4d.com/Demos/4D%5Fv16%5FR5/HDI%5F4DWP%5FBackImagePaperBox.zip). + +## Encabezados, pies y secciones + +Los documentos 4D Write Pro soportan encabezados y pies de página. Los encabezados y pies de página están relacionados con las secciones. + +Una sección es una parte de un documento que está definida por un rango de páginas y puede tener su propia paginación y atributos comunes. Un documento puede contener cualquier número de secciones (de uno al número total de páginas). Cada página sólo puede pertenecer a una sección, excepto las páginas con saltos de sección continuos (ver abajo). + +Los documentos 4D Write Pro pueden contener: + +- una o más secciones (una sección por defecto) +- para cada sección, hasta tres subsecciones: + - subsección de la primera página + - subsección de la(s) página(s) izquierda(s) + - subsección de la(s) página(s) derecha(s) + +Se puede definir un conjunto de encabezados y pies de página para cada sección. + +### Definir una sección + +Una sección es un subconjunto de páginas continuas en un documento 4D Write Pro. Un documento puede contener una o más secciones. Una sección puede contener cualquier número de páginas, desde una sola página a el número total de páginas del documento. Una sección puede contener una sola columna o hasta 20 columna(s). + +Por defecto, un documento contiene una sola sección, llamada **Sección 1**. 4D Write Pro muestra el menú contextual de este número de la sección donde se hace clic en el documento: + + + +Se crea una nueva sección añadiendo una ruptura de sesión en el flujo de texto: + + + +Cuando se ha añadido una ruptura de sección, el menú contextual muestra un número incrementado para cada sección. Sin embargo, puede cambiar el nombre de cualquier sección: + + + +El nombre introducido se utiliza como el nombre de sección en todo el documento: + +  + +Tenga en cuenta que si se ha definido una primera página diferente o diferentes páginas izquierda/derecha para una sección, el tipo de página también se muestra en el menú (ver abajo). + +### Insertar un salto de sección continuo + +Un salto de sección continuo crea una nueva sección en la misma página. Esto permite crear páginas con secciones que tienen diferentes números de columnas (vet *Creación de una página con secciones de varias columnas y de una sola columna*). + +Las secciones creadas con saltos de sección continuos se cuentan en el documento (tienen números de sección), pero a diferencia de las secciones creadas con saltos de sección estándar, sus encabezados, pies, imágenes ancladas, etc. sólo se tienen en cuenta cuando se ha producido un salto de página físico. + +**Nota:** si cambia la orientación de la página de la nueva sección después de insertar un salto de sección continuo, éste se convierte en un salto de sección estándar. + +### Atributos Sección + +Las secciones heredan atributos de los documentos. Sin embargo, los atributos de documentos comunes, incluyendo los encabezados y pies de página, se pueden modificar por separado para cada sección. El menú emergente contextual muestra las propiedades y atributos disponibles en el nivel de sección: + + + +* **Orientación de página**: le permite definir una orientación de página específica (vertical u horizontal) por sección +* **Primera página diferente**: le permite definir diferentes atributos para la primera página de la sección; esta funcionalidad se puede utilizar para crear hojas de guarda, por ejemplo. Cuando se selecciona este atributo, la primera página de la sección se maneja como una subsección y puede tener sus propios atributos. + ">/\] +* **Diferentes páginas derecha e izquierda**: le permite establecer diferentes atributos para las páginas izquierda y derecha de la sección. Cuando se activa este atributo, las páginas izquierda y derecha de la sección se manejan como subsecciones y puede tener sus propios atributos. + ">/\] +* Comandos **Columnas**: permiten definir el número y propiedades de columnas para la sección. Estas opciones se detallan a continuación. +* Comandos **Header** y **Footer**: estas opciones permiten definir encabezados y pies de página separados. Estas opciones se detallan a continuación. +* **Márgenes**/**Relleno**/**Bordes**/**Fondo**: estos atributos pueden definirse por separado para cada sección. Para más información acerca de estos atributos, consulte el artículo *Atributos 4D Write Pro*. + +### Insertar encabezados y pies de página + +Cada sección puede tener encabezado y pie de página específicos. Los encabezados y pies de página sólo se muestran cuando el documento modo vista página está en **Página**. + +Dentro de una sección, puede definir hasta tres encabezados y pies diferentes, dependiendo de las opciones activadas: + +* primera página, +* página(s) izquierda(s), +* página(s) derecha(s). + +Para crear un encabezado o un pie de página: + +1. Asegúrese de que el documento está en el modo de visualización **Página**. +2. Haga doble clic en el área de encabezado o pie de página de la sección y página deseada para entrar en el modo de edición. + * El área de encabezado está en la parte superior de la página: +  + * El área de pie de página es en la parte inferior de la página: +  + + +A continuación, puede introducir contenidos estáticos, que se repetirán automáticamente en cada página de la sección (a excepción de la primera página, si está habilitada). + + + +También puede insertar contenidos dinámicos tales como el número de página o el conteo de páginas utilizando el comando [ST INSERT EXPRESSION](../../commands/st-insert-expression) (para más información, consulte el párrafo *Insertar expresiones de documento y de página*). + +Una vez definidos un encabezado o un pie de página para una sección, puede configurar sus atributos comunes utilizando el menú contextual: + + + +Para más información sobre atributos **Márgenes**, **Rellenos**, **Bordes** y **Fondo**, consulte la sección *Atributos 4D Write Pro*. + +Puede eliminar toda la definición de un encabezado o de un pie de página (contenidos y atributos) seleccionando **Eliminar encabezado** o **Eliminar pie** en el menú contextual. + +### Compatibilidad + +4D Write Pro maneja encabezados y pies de página de documentos convertidos desde el plug-in 4D Write conuna altura fija. + +Las siguientes expresiones y propiedades también son soportadas y se convierten de los encabezados y pies de página del plug-in 4D Write: + +* número de página y variables de conteo de página +* distinta primera página +* distintas páginas izquierda/derecha + + +## Reglas + +Las reglas están disponibles en todos los modos de visualización de 4D Write Pro y tienen las siguientes características: + +* Graduaciones en cm, mm, pulgadas o pt de acuerdo con la unidad de diseño actual definida en el documento 4D Write Pro. Puede cambiar las unidades de medida mediante el menú contextual o modificando el atributo wk layout unit. +* Símbolo de indentación de primera línea +* Símbolo de margen de párrafo izquierdo +* Símbolo de margen de párrafo derecho +* Tabulaciones mostradas a lo largo del borde inferior de la regla +* El contraste de color visible representa los márgenes de página izquierdo y derecho + +Las reglas verticales están disponibles solo en modo Página y tienen las siguientes características: + +* Graduaciones en cm, mm, pulgadas o pt según la unidad de diseño actual definida en el documento 4D Write Pro. Puede cambiar las unidades de medida utilizando el menú contextual o modificando el atributo wk layout unit. +* Contraste de color visible que representa los márgenes superior e inferior de la página. + +Puede cambiar el estado de visualización de las reglas por medio de acciones estándar (ver *Utilizar las acciones estándar 4D Write Pro*) o marcando o desmarcando la opción **Mostrar regla horizontal** o **Mostrar regla vertical** en el menú contextual del área 4D Write Pro: + + + +**Nota:** una propiedad específica del área 4D Write Pro permite definir la visualización predeterminada para las reglas (ver la sección *Configurar propiedades Vista*). + +### Ajustar márgenes de texto e indentaciones + +#### Regla horizontal + +Puede modificar márgenes izquierda y derecha, indentaciones y posiciones de tabulación haciendo clic y arrastrando los símbolos correspondientes en la regla horizontal: + + + +Cuando coloca el ratón sobre uno de estos símbolos, el cursor cambia para indicar que puede moverse y aparece una línea de guía vertical mientras lo arrastra: + + + +Cuando se seleccionan varios párrafos, arrastrar márgenes o símbolos de indentación aplica estos márgenes o indentaciones a todos los párrafos seleccionados. Manteniendo presionada la tecla Mayús mientras arrastra estos símbolos mantiene los intervalos existentes entre indentaciones o márgenes en los párrafos seleccionados. + +#### Regla Vertical + +Puede modificar los márgenes superior e inferior con la regla vertical. Cuando mueve el ratón sobre el límite del margen, el cursor cambia para indicar que se puede mover, y aparece una línea de guía horizontal mientras lo arrastra: + + + +Esta acción se puede utilizar para modificar el espacio entre la parte superior e inferior de la página y el cuerpo y el encabezado y pie de página de un documento. + +### Gestión de tabulaciones + +Puede utilizar el menú contextual de la regla para crear, modificar o eliminar tabulaciones: + + + +Para crear una tabulación, simplemente haga clic directamente en la regla y elija su tipo en el menú contextual. Un solo clic izquierdo crea automáticamente una tabulación izquierda predeterminada. También puede hacer clic con el botón derecho en las tabulaciones existentes para modificar su tipo utilizando el menú contextual. + +**Eliminar tabulación** solo está disponible cuando hace clic con el botón derecho del ratón directamente en una tabulación existente; También puede eliminar tabulaciones arrastrándolas fuera del área de la regla horizontal. + +:::note Notas + +* La tabulación también se pueden definir por programación con los comandos [WP SET ATTRIBUTES](../commands/wp-set-attributes), [WP GET ATTRIBUTES](../commands/wp-get-attributes), y [WP RESET ATTRIBUTES](../commands/wp-reset-attributes) con los selectores wk tab default y wk tabs. +* Para las tabulaciones decimales, 4D Write Pro considera el primer punto o coma de la derecha como el separador decimal; esta configuración predeterminada puede modificarse con el selector wk tab decimal separator. + +::: + +#### Definir caracteres iniciales + +Los caracteres que preceden a las tabulaciones (caracteres iniciales) se pueden definir seleccionando entre cinco caracteres predefinidos o designando un carácter específico a usar. Los caracteres predefinidos son: + +* Ninguno (no se muestran los caracteres - *predeterminado*) +* .... (puntos) +* \--- (guiones) +* \_\_ (guiones bajos) +* \*\*\* (asteriscos) + +Los caracteres iniciales siempre aparecen antes de la tabulación y siguen la dirección del texto (de izquierda a derecha o de derecha a izquierda). Se pueden definir por programación con los comandos [WP SET ATTRIBUTES](../commands/wp-set-attributes), [WP GET ATTRIBUTES](../commands/wp-get-attributes) y [WP RESET ATTRIBUTES](../commands/wp-reset-attributes) utilizando `wk leading` con los selectores `wk tab default` o `wk tabs`, o vía el menú contextual de regla horizontal (como se muestra a continuación). + + + +Cuando se selecciona **Otro...**, se muestra un diálogo donde se puede definir un carácter principal personalizado. + +### Reglas Multi columnas + +Cuando se definen dos o más columnas para el documento o la sección, la regla horizontal muestra un área específica para cada columna: + + + +**Nota:** la funcionalidad de múltiples columnas no está disponible en el modo de vista **Embebido**. + +### Evento On After Edit + +Un evento de formulario [`On After Edit`](../../Events/onAfterEdit.md) se dispara para un objeto de formulario de área 4D Write Pro siempre que se muevan, agreguen o eliminen cualquier tabulación o control de margen, ya sea arrastrándolos o utilizando el menú contextual. + +## Columnas + +4D Write Pro le permite administrar columnas en sus documentos. Las columnas están encadenadas desde la columna de la izquierda hasta la columna de la derecha. En otras palabras, al ingresar texto, el flujo de texto comenzará a llenar la columna izquierda y continuará con la columna directamente hacia la derecha hasta que llegue al final de la página. Una vez que se llega al final de la página, el flujo de texto pasa por la siguiente página. Para poder equilibrar la configuración de la página, 4D Write Pro le permite insertar saltos de columna. + + + +Las columnas se pueden definir a nivel de documento (se muestran en el documento completo) y/o en el nivel de sección (cada sección puede tener su propia configuración de columna). + +**Nota:** las columnas solo se soportan en el modo **Vista de página** y **Vista Borrador** (no se muestran en modo de vista **Embebido**) y se exportan a .docx utilizando [WP EXPORT DOCUMENT](../commands/wp-export-document) pero no a formatos HTML y MIME HTML wk web page complete). + +Las columnas se pueden configurar utilizando: + +* el submenú **Columnas** del menú contextual del área 4D Write Pro, +* [Atributos](../commands-legacy/4d-write-pro-attributes.md) 4D Write Pro, +* [Acciones estándar](./defining-a-4d-write-pro-area.md#standard-actions) 4D Write Pro. + +Puede definir u obtener las siguientes propiedades y acciones para las columnas: + +| **Propiedad** | **Descripción** | **Atributos** *Documento* | **Acciones estándar** | +| -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------- | ------------------------------------------------------- | +| Número de columnas | Puede definir hasta 20 columnas para el documento/sección | wk column count | *columnCount* | +| Espacio entre columnas | Espacio entre columnas en pts, pulgadas o cm. Tenga en cuenta que todas las columnas tendrán el mismo tamaño. Cada ancho de columna se calcula automáticamente con 4D Write Pro según el número de columnas, el ancho de página y el espaciado | wk column spacing | *columnSpacing* | +| Ancho de columna | (atributo de solo lectura) Ancho actual para cada columna, es decir, ancho calculado | wk column width | \- | +| Estilo, color y ancho de la regla de columna | Puede agregar un separador vertical (una línea decorativa) entre columnas. Estas opciones le permiten diseñar el estilo, el color y el ancho del separador. Para eliminar el separador vertical, seleccione **Ninguno** como estilo. | wk column rule style, wk column rule color, wk column rule width | *columnRuleStyle*, *columnRuleColor*, *columnRuleWidth* | +| Insertar salto | Insertar salto de columna | wk column break, ver también [WP INSERT BREAK](../commands/wp-insert-break) | *insertColumnBreak* | +| Menú Columnas | Crear un submenú Columna | \- | *columns* | + +### Creación de una página con secciones de varias columnas y de una sola columna + +*Insertar un salto de sección continuo* en su documento le permite tener secciones de varias columnas y secciones de una columna en la misma página. + +Por ejemplo: + + + +Puede insertar un salto de sección continuo y cambiar el número de columnas a dos para la primera sección: + + + +## Marcadores + +4D Write Pro le permite crear y trabajar con referencias dinámicas para intervalos, llamados **marcadores**. Un marcador es una referencia con nombre asociada a un [rango](./ranges.md) específico en un documento 4D Write Pro. + +Los marcadores son dinámicos, lo que significa que si el usuario mueve, añade o elimina del texto el marcador, el rango asociado se actualizará automáticamente y el marcador seguirá haciendo referencia al mismo contenido dentro del documento. Por ejemplo: + +- Se crea un marcador llamado "MyBM" que hace referencia al texto "Hola mundo" en la página 20 del documento. +- Luego, inserta 50 páginas al principio del documento. +- Usted aún podrá acceder automáticamente al mismo texto "Hola mundo", ahora en la página 70 del documento, mediante el marcador "MyBM". + +Un documento puede contener un número ilimitado de marcadores. Varios marcadores pueden hacer referencia al mismo rango, y los rangos de marcadores pueden ser intercalados. Sin embargo, cada nombre de marcador debe ser único en el documento. Los marcadores no se importan cuando se utiliza el comando [WP INSERT DOCUMENT BODY](../commands/wp-insert-document-body) (los marcadores en el documento de destino no pueden ser sobrescritos). + +Una vez creado, un marcador se almacena dentro del documento. Se guarda con el documento y puede ser manejado por diferentes comandos. También se puede utilizar para hacer referencia a partes de un documento plantilla. Estas piezas pueden ensamblarse de forma automática con los datos de la base para producir documentos de salida dinámicos tales como facturas o catálogos. + +Varios comandos permiten crear, eliminar y utilizar marcadores: + +- [WP NEW BOOKMARK](../commands-legacy/wp-new-bookmark.md) para crear un nuevo marcador en un rango, +- [WP GET BOOKMARKS](../commands-legacy/wp-get-bookmarks.md) para obtener todos los marcadores definidos en un documento, +- [WP Bookmark range](../commands-legacy/wp-bookmark-range.md) para recuperar un rango de un marcador existente, +- [WP DELETE BOOKMARK](../commands-legacy/wp-delete-bookmark.md) para eliminar un marcador. + +## Enlaces + +4D Write Pro le permite asignar hipervínculos a todo rango de su documento, incluyendo rangos (texto, imagen, etc.), elementos (tabla, cuerpo, pie de página, etc.) o todo el documento. Por ejemplo, puede definir un hipervínculo a un rango imagen; si el documento 4D Write Pro se exporta a HTML, los usuarios pueden hacer clic en la imagen para abrir una página en una dirección específica. + +Los hipervínculos se pueden activar desde documentos 4D Write Pro utilizando el atajo **Ctrl+clic** (Windows) o **Cmd+clic** (macOS). En un documento 4D Write Pro, un enlace se puede activar utilizando un simple clic. + +4D Write Pro soporta enlaces de los siguientes tipos: + +| Tipo de enlace | Descripción | +|----------------|-------------| +| `url` | Enlaces a páginas web o a cualquier documento, abre la aplicación asociada cuando se activa (\*). La activación de un enlace URL al documento 4D Write Pro (`.4wp`, `.4w7`) reemplaza al documento actual en el área de 4D Write Pro.
(\*) Igual que el comando [OPEN URL](../../commands-legacy/open-url.md). | +| `bookmark` | Enlaces a marcadores en el documento | +| `method` | Activando un enlace a un método 4D ejecuta el método (siempre que esté registrado por el método [SET ALLOWED METHODS](../../commands/set-allowed-methods.md)). | + +Los hipervínculos se manejan por medio de los siguientes comandos: + +- [WP SET LINK](../commands-legacy/wp-set-link.md) para insertar un enlace utilizando un objeto de destino. +- [WP Get links](../commands-legacy/wp-get-links.md) para obtener la colección de todos los enlaces en un objeto de destino. + +:::note + +Nota: los enlaces se manejan como atributos, por lo tanto se pueden definir u obtener utilizando los comandos [WP SET ATTRIBUTES](../commands/wp-set-attributes) y [WP GET ATTRIBUTES](../commands/wp-get-attributes) junto con la constante `wk link url`. Sin embargo, recomendamos utilizar [WP SET LINK](../commands-legacy/wp-set-link.md) y [WP Get links](../commands-legacy/wp-get-links.md) porque automáticamente codifican/decodifican enlaces como URLs. Cuando se leen enlaces utilizando el comando [WP GET ATTRIBUTES](../commands/wp-get-attributes), si el rango contiene varios hipervínculos, el comando devuelve la primera cadena de url. + +::: + +Por ejemplo, si desea transformar el texto seleccionado por el usuario en una URL en un sitio web: + + + +Puede escribir: + +```4d +$range:=WP Get selection(*;"WParea") +WP SET LINK($range;New object("url";"http://www.4d.com")) +``` + + + +Para eliminar un vínculo de rango, puede escribir: + +```4d +WP RESET ATTRIBUTES($range;wk link url) +``` + +o + +```4d +WP SET ATTRIBUTES($range;wk link url;"") +``` + +**Nota**: si *$range* no incluye todo el enlace, el enlace se trunca pero no se elimina completamente. + +## Utilizar los comandos del tema Objeto (Formularios) + +Los siguientes comandos 4D del tema [Objetos (Formularios)](../../commands/theme/Objects_Forms.md) son compatibles con los objetos de formulario de 4D Write Pro: + +| Comando | Comentarios | +|--------|-------------| +| OBJECT DUPLICATE | | +| OBJECT Get auto spellcheck / OBJECT SET AUTO SPELLCHECK | | +| OBJECT Get border style / OBJECT SET BORDER STYLE | | +| OBJECT Get context menu / OBJECT SET CONTEXT MENU | | +| OBJECT GET COORDINATES / OBJECT SET COORDINATES | | +| OBJECT Get data source / OBJECT SET DATA SOURCE | | +| OBJECT GET DRAG AND DROP OPTIONS / OBJECT SET DRAG AND DROP OPTIONS | | +| OBJECT Get enabled / OBJECT SET ENABLED | | +| OBJECT Get enterable / OBJECT SET ENTERABLE | | +| OBJECT GET EVENTS / OBJECT SET EVENTS | | +| OBJECT Get focus rectangle invisible / OBJECT SET FOCUS RECTANGLE INVISIBLE | | +| OBJECT Get font / OBJECT SET FONT | Aplicado a la selección actual (si la hay) | +| OBJECT Get font size / OBJECT SET FONT SIZE | Aplicado a la selección actual (si la hay) | +| OBJECT Get font style / OBJECT SET FONT STYLE | Aplicado a la selección actual (si la hay) | +| OBJECT Get horizontal alignment / OBJECT SET HORIZONTAL ALIGNMENT | Aplicado a la selección actual (si la hay). Soporte de la constante wk justify para áreas 4D Write Pro | +| OBJECT GET RESIZING OPTIONS / OBJECT SET RESIZING OPTIONS | | +| _o_ OBJECT SET COLOR | Aplicado a la selección actual (si la hay) | +| OBJECT GET RGB COLORS / OBJECT SET RGB COLORS | Aplicado a la selección actual (si la hay) | +| OBJECT Get type | | +| OBJECT Get vertical alignment / OBJECT SET VERTICAL ALIGNMENT | Alineación vertical de párrafos: sólo tiene efecto cuando la altura del párrafo es mayor a la altura del texto del párrafo | +| OBJECT Get visible / OBJECT SET VISIBLE | | +| OBJECT Is styled text | Devuelve true | +| OBJECT MOVE | | +| OBJECT GET SUBFORM CONTAINER SIZE | | +| OBJECT Get name | | +| OBJECT Get pointer | | + +Todos los comandos OBJECT no enumerados anteriormente no son aplicables a áreas 4D Write Pro. diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/ak_400.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/ak_400.png new file mode 100644 index 00000000000000..03ddd799fa0a3a Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/ak_400.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/ak_700.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/ak_700.png new file mode 100644 index 00000000000000..67de2c6ccbeac1 Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/ak_700.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/comment.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/comment.png new file mode 100644 index 00000000000000..7bc9233ea63c89 Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/comment.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/header_title_olv.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/header_title_olv.png new file mode 100644 index 00000000000000..96e9102ce17d7b Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/header_title_olv.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/commands/pict6013182.en.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/icon-f.png similarity index 100% rename from i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/commands/pict6013182.en.png rename to i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/icon-f.png diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/link1.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/link1.png new file mode 100644 index 00000000000000..37389843e8f050 Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/link1.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/link2.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/link2.png new file mode 100644 index 00000000000000..a49860493ce8e7 Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/link2.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2584929.es.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2584929.es.png new file mode 100644 index 00000000000000..8287ae4ca5e1a0 Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2584929.es.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2584938.es.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2584938.es.png new file mode 100644 index 00000000000000..4d05904c4acb7c Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2584938.es.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2646292.EN.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2646292.EN.png new file mode 100644 index 00000000000000..2f6dd9ff7667f9 Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2646292.EN.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2646294.EN.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2646294.EN.png new file mode 100644 index 00000000000000..c5706f5b23244e Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2646294.EN.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2878453.es.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2878453.es.png new file mode 100644 index 00000000000000..962a313ddc7e48 Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2878453.es.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994900.es.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994900.es.png new file mode 100644 index 00000000000000..2380ba7ed23dce Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994900.es.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994904.es.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994904.es.png new file mode 100644 index 00000000000000..2368cce52c8787 Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994904.es.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994907.es.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994907.es.png new file mode 100644 index 00000000000000..162c97dd54bba1 Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994907.es.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994910.es.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994910.es.png new file mode 100644 index 00000000000000..123e8eb6790242 Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994910.es.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994913.es.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994913.es.png new file mode 100644 index 00000000000000..df744c2ba7a3a1 Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994913.es.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994942.es.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994942.es.png new file mode 100644 index 00000000000000..de69462e1835ee Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994942.es.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994945.es.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994945.es.png new file mode 100644 index 00000000000000..c58bef4dbd7693 Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994945.es.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994956.es.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994956.es.png new file mode 100644 index 00000000000000..9f6ae8a5929370 Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994956.es.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994958.es.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994958.es.png new file mode 100644 index 00000000000000..b59ab72c7c0d6a Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994958.es.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994965.es.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994965.es.png new file mode 100644 index 00000000000000..c77e56c5857e39 Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994965.es.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2995027.es.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2995027.es.png new file mode 100644 index 00000000000000..7b41c8b804aa88 Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2995027.es.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3033006.EN.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3033006.EN.png new file mode 100644 index 00000000000000..ad7e034e246705 Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3033006.EN.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3033008.EN.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3033008.EN.png new file mode 100644 index 00000000000000..51f1aa5c128b59 Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3033008.EN.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3071271.EN.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3071271.EN.png new file mode 100644 index 00000000000000..e7f020cc979f5e Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3071271.EN.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3254912.es.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3254912.es.png new file mode 100644 index 00000000000000..f26f553b9d0924 Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3254912.es.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3307937.EN.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3307937.EN.png new file mode 100644 index 00000000000000..fb12b681bed355 Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3307937.EN.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3307941.EN.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3307941.EN.png new file mode 100644 index 00000000000000..0016bc2e11049d Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3307941.EN.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3308424.EN.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3308424.EN.png new file mode 100644 index 00000000000000..17c545dcd5e7cc Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3308424.EN.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3513503.EN.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3513503.EN.png new file mode 100644 index 00000000000000..eddf97544e0575 Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3513503.EN.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3513505.EN.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3513505.EN.png new file mode 100644 index 00000000000000..5e8669f5c2aace Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3513505.EN.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3514201.es.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3514201.es.png new file mode 100644 index 00000000000000..fa62fdaaf70f9f Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3514201.es.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3541581.EN.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3541581.EN.png new file mode 100644 index 00000000000000..8d2321c8b19748 Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3541581.EN.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3626363.EN.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3626363.EN.png new file mode 100644 index 00000000000000..823fcf7c97fbcb Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3626363.EN.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3751849.es.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3751849.es.png new file mode 100644 index 00000000000000..4ce29fef319527 Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3751849.es.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3752166.EN.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3752166.EN.png new file mode 100644 index 00000000000000..40ec61e14638df Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3752166.EN.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3752176.EN.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3752176.EN.png new file mode 100644 index 00000000000000..1b09211ea8ac30 Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3752176.EN.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3893246.EN.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3893246.EN.png new file mode 100644 index 00000000000000..84c289b866e8e6 Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3893246.EN.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3893248.EN.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3893248.EN.png new file mode 100644 index 00000000000000..c21d5b60eeb195 Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3893248.EN.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101161.es.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101161.es.png new file mode 100644 index 00000000000000..63473774d42308 Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101161.es.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101210.es.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101210.es.png new file mode 100644 index 00000000000000..71b0dbae6cce73 Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101210.es.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101242.es.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101242.es.png new file mode 100644 index 00000000000000..c4edefac85dd9d Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101242.es.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101252.es.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101252.es.png new file mode 100644 index 00000000000000..c79049f4e6bea8 Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101252.es.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101267.es.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101267.es.png new file mode 100644 index 00000000000000..44c321eddbf61c Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101267.es.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4619596.EN.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4619596.EN.png new file mode 100644 index 00000000000000..0c0a886b53349f Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4619596.EN.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4619694.EN.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4619694.EN.png new file mode 100644 index 00000000000000..4ace1703dab061 Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4619694.EN.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4619865.EN.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4619865.EN.png new file mode 100644 index 00000000000000..e708853ddf2c4c Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4619865.EN.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5562054.EN.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5562054.EN.png new file mode 100644 index 00000000000000..dee167c5ccf7c3 Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5562054.EN.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5562058.EN.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5562058.EN.png new file mode 100644 index 00000000000000..f84f46638756cb Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5562058.EN.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5761667.EN.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5761667.EN.png new file mode 100644 index 00000000000000..a6e16bcd3e31bf Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5761667.EN.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5761669.EN.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5761669.EN.png new file mode 100644 index 00000000000000..6f56866e06cff7 Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5761669.EN.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5761671.EN.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5761671.EN.png new file mode 100644 index 00000000000000..d2b933e6253bd5 Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5761671.EN.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5761673.EN.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5761673.EN.png new file mode 100644 index 00000000000000..eef0da9b30d61f Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5761673.EN.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5761675.EN.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5761675.EN.png new file mode 100644 index 00000000000000..f21fa89866c9ef Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5761675.EN.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5761677.EN.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5761677.EN.png new file mode 100644 index 00000000000000..b6b82029e3bdaa Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5761677.EN.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5859437.EN.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5859437.EN.png new file mode 100644 index 00000000000000..8a546866502013 Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5859437.EN.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5907013.en.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5907013.en.png new file mode 100644 index 00000000000000..e233c502a77cb2 Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5907013.en.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5907021.EN.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5907021.EN.png new file mode 100644 index 00000000000000..bcbe548297f87d Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5907021.EN.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5907023.EN.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5907023.EN.png new file mode 100644 index 00000000000000..6eba7f2baedff6 Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5907023.EN.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5907026.EN.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5907026.EN.png new file mode 100644 index 00000000000000..d526c51578eb27 Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5907026.EN.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5907030.EN.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5907030.EN.png new file mode 100644 index 00000000000000..964245707b6717 Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5907030.EN.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5941073.EN.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5941073.EN.png new file mode 100644 index 00000000000000..66f10af3210774 Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5941073.EN.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6014414.EN.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6014414.EN.png new file mode 100644 index 00000000000000..1454f02b49f34c Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6014414.EN.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6014426.EN.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6014426.EN.png new file mode 100644 index 00000000000000..5430cc882d6f13 Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6014426.EN.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6014429.EN.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6014429.EN.png new file mode 100644 index 00000000000000..12cb8442c5f68c Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6014429.EN.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6022144.EN.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6022144.EN.png new file mode 100644 index 00000000000000..ab1d4670b16d55 Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6022144.EN.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6131919.EN.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6131919.EN.png new file mode 100644 index 00000000000000..d8b2b0f013f901 Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6131919.EN.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6260026.EN.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6260026.EN.png new file mode 100644 index 00000000000000..25b899cdd7ca87 Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6260026.EN.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6260030.EN.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6260030.EN.png new file mode 100644 index 00000000000000..e9bb58906cfd9b Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6260030.EN.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6260033.EN.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6260033.EN.png new file mode 100644 index 00000000000000..d8271cd06a6220 Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6260033.EN.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6260036.EN.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6260036.EN.png new file mode 100644 index 00000000000000..a93bbc2deb6580 Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6260036.EN.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6421031.EN.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6421031.EN.png new file mode 100644 index 00000000000000..f338bd44caeb38 Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6421031.EN.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6421340.EN.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6421340.EN.png new file mode 100644 index 00000000000000..a00a64fa003fe5 Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6421340.EN.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6421342.EN.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6421342.EN.png new file mode 100644 index 00000000000000..e7bbdb0445e7dc Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6421342.EN.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6421344.EN.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6421344.EN.png new file mode 100644 index 00000000000000..b1da7d4f717589 Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6421344.EN.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6421356.EN.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6421356.EN.png new file mode 100644 index 00000000000000..e19848f65d2951 Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6421356.EN.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6434575.EN.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6434575.EN.png new file mode 100644 index 00000000000000..b98b7a71deb16b Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6434575.EN.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6434579.EN.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6434579.EN.png new file mode 100644 index 00000000000000..232ad5653b5bdf Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6434579.EN.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6434721.EN.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6434721.EN.png new file mode 100644 index 00000000000000..199e62f81ef736 Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6434721.EN.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6434723.EN.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6434723.EN.png new file mode 100644 index 00000000000000..480da0bfc5f80f Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6434723.EN.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6434756.EN.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6434756.EN.png new file mode 100644 index 00000000000000..ffdcce4bd30899 Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6434756.EN.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6441966.EN.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6441966.EN.png new file mode 100644 index 00000000000000..e6b76b3b690664 Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6441966.EN.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6856159.en.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6856159.en.png new file mode 100644 index 00000000000000..18f093b69da71c Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6856159.en.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6856163.en.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6856163.en.png new file mode 100644 index 00000000000000..0c3c6665e834d8 Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6856163.en.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict7014959.en.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict7014959.en.png new file mode 100644 index 00000000000000..a667cee2e6696a Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict7014959.en.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict7148443.en.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict7148443.en.png new file mode 100644 index 00000000000000..ab64da522a20a6 Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict7148443.en.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict7148495.en.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict7148495.en.png new file mode 100644 index 00000000000000..499af8e3737b08 Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict7148495.en.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/poweredby4D_web.png b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/poweredby4D_web.png new file mode 100644 index 00000000000000..fbb7fefffac38d Binary files /dev/null and b/i18n/es/docusaurus-plugin-content-docs/current/assets/en/WritePro/poweredby4D_web.png differ diff --git a/i18n/es/docusaurus-plugin-content-docs/version-20-R10/API/SessionClass.md b/i18n/es/docusaurus-plugin-content-docs/version-20-R10/API/SessionClass.md index 7989dc74b49fca..e456013c808238 100644 --- a/i18n/es/docusaurus-plugin-content-docs/version-20-R10/API/SessionClass.md +++ b/i18n/es/docusaurus-plugin-content-docs/version-20-R10/API/SessionClass.md @@ -136,7 +136,7 @@ La función `.createOTP()` crea un Para más información sobre los tokens OTP, por favor consulte [esta sección](../WebServer/sessions.md#session-token-otp). -Por defecto, si se omite el parámetro *lifespan*, el token se crea con el mismo tiempo de vida que el [`.idleTimeOut`](#idletimeout) de la sesión. Puede definir un tiempo de espera personalizado pasando un valor en segundos en *lifespan* (el valor mínimo es de 10 segundos, *lifespan* se restablece a 10 si se pasa un valor menor). Si se utiliza un token caducado para restaurar una sesión de usuario web, se ignora. +Por defecto, si se omite el parámetro *lifespan*, el token se crea con el mismo tiempo de vida que el [`.idleTimeOut`](#idletimeout) de la sesión. You can set a custom timeout by passing a value in seconds in *lifespan*. Si se utiliza un token caducado para restaurar una sesión de usuario web, se ignora. El token devuelto puede ser utilizado en intercambios con aplicaciones de terceros o sitios web para identificar la sesión de forma segura. Por ejemplo, el token OTP de sesión se puede utilizar con una aplicación de pago. diff --git a/i18n/es/docusaurus-plugin-content-docs/version-20-R10/Concepts/operators.md b/i18n/es/docusaurus-plugin-content-docs/version-20-R10/Concepts/operators.md index 111a7c8b4391b2..3688ea43d1cff6 100644 --- a/i18n/es/docusaurus-plugin-content-docs/version-20-R10/Concepts/operators.md +++ b/i18n/es/docusaurus-plugin-content-docs/version-20-R10/Concepts/operators.md @@ -90,7 +90,10 @@ Se admiten los siguientes operadores de asignación compuestos: | | Time \*= Number | Number | `$t1*=5 //$t1:=$t1*5` | | | Picture \*= Number | Picture | `$p1*=5 //$p1:=$p1*5 (redimensionar $p1 de 5)` | -Estos operadores se aplican a todas las [expresiones asignables](quick-tour.md#assignable-vs-non-assignable-expressions) (excepto de las imágenes como propiedades de objeto o elementos de colección). +These operators apply on any [assignable expressions](quick-tour.md#assignable-vs-non-assignable-expressions) except: + +- pictures as object properties or collection elements, +- array index variables. La operación "source `operator` value" no es estrictamente equivalente a "source := source `operator` value" porque la expresión que designa la fuente (variable, campo, propiedad del objeto, elemento de colección) sólo se evalúa una vez. Por ejemplo, en una expresión tal como `getPointer()->+=1` el método `getPointer` es llamado sólo una vez. diff --git a/i18n/es/docusaurus-plugin-content-docs/version-20-R9/API/SessionClass.md b/i18n/es/docusaurus-plugin-content-docs/version-20-R9/API/SessionClass.md index 7aebce5712f4c2..e8d3b5866e053a 100644 --- a/i18n/es/docusaurus-plugin-content-docs/version-20-R9/API/SessionClass.md +++ b/i18n/es/docusaurus-plugin-content-docs/version-20-R9/API/SessionClass.md @@ -133,7 +133,7 @@ La función `.createOTP()` crea un Para más información sobre los tokens OTP, por favor consulte [esta sección](../WebServer/sessions.md#session-token-otp). -Por defecto, si se omite el parámetro *lifespan*, el token se crea con el mismo tiempo de vida que el [`.idleTimeOut`](#idletimeout) de la sesión. Puede definir un tiempo de espera personalizado pasando un valor en segundos en *lifespan* (el valor mínimo es de 10 segundos, *lifespan* se restablece a 10 si se pasa un valor menor). Si se utiliza un token caducado para restaurar una sesión de usuario web, se ignora. +Por defecto, si se omite el parámetro *lifespan*, el token se crea con el mismo tiempo de vida que el [`.idleTimeOut`](#idletimeout) de la sesión. You can set a custom timeout by passing a value in seconds in *lifespan*. Si se utiliza un token caducado para restaurar una sesión de usuario web, se ignora. El token devuelto puede ser utilizado en intercambios con aplicaciones de terceros o sitios web para identificar la sesión de forma segura. Por ejemplo, el token OTP de sesión se puede utilizar con una aplicación de pago. diff --git a/i18n/es/docusaurus-plugin-content-docs/version-20-R9/Concepts/operators.md b/i18n/es/docusaurus-plugin-content-docs/version-20-R9/Concepts/operators.md index 111a7c8b4391b2..3688ea43d1cff6 100644 --- a/i18n/es/docusaurus-plugin-content-docs/version-20-R9/Concepts/operators.md +++ b/i18n/es/docusaurus-plugin-content-docs/version-20-R9/Concepts/operators.md @@ -90,7 +90,10 @@ Se admiten los siguientes operadores de asignación compuestos: | | Time \*= Number | Number | `$t1*=5 //$t1:=$t1*5` | | | Picture \*= Number | Picture | `$p1*=5 //$p1:=$p1*5 (redimensionar $p1 de 5)` | -Estos operadores se aplican a todas las [expresiones asignables](quick-tour.md#assignable-vs-non-assignable-expressions) (excepto de las imágenes como propiedades de objeto o elementos de colección). +These operators apply on any [assignable expressions](quick-tour.md#assignable-vs-non-assignable-expressions) except: + +- pictures as object properties or collection elements, +- array index variables. La operación "source `operator` value" no es estrictamente equivalente a "source := source `operator` value" porque la expresión que designa la fuente (variable, campo, propiedad del objeto, elemento de colección) sólo se evalúa una vez. Por ejemplo, en una expresión tal como `getPointer()->+=1` el método `getPointer` es llamado sólo una vez. diff --git a/i18n/es/docusaurus-plugin-content-docs/version-20-R9/WritePro/commands-legacy/4d-write-pro-attributes.md b/i18n/es/docusaurus-plugin-content-docs/version-20-R9/WritePro/commands-legacy/4d-write-pro-attributes.md index eb11d3d1d1d273..20ce1796a6e212 100644 --- a/i18n/es/docusaurus-plugin-content-docs/version-20-R9/WritePro/commands-legacy/4d-write-pro-attributes.md +++ b/i18n/es/docusaurus-plugin-content-docs/version-20-R9/WritePro/commands-legacy/4d-write-pro-attributes.md @@ -394,11 +394,12 @@ Los atributos de rango son de solo lectura y brindan información sobre las prop | Constante | Comentario | | ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| wk container| (Atributo de sólo lectura) Contenedor de texto del rango, es decir, un encabezado, un pie de página o un cuadro de texto. Tipo de valor: Objeto (*undefined* si el rango se encuentra en el cuerpo del documento) | | wk break type | (Atributo de sólo lectura) Tipo de ruptura dentro de un objeto rango ruptura devuelto por [WP Get breaks](WritePro/commands/wp-get-breaks.md). Valores posibles:
- wk line break,
- wk paragraph break,
- wk column break,
- wk page break,
- wk section break
- Booleano: True si la línea es una línea de encabezado. False en caso contrario.
- Entero: wk true wk false wk mixed
- a todas las líneas dentro del objetivo
- a las líneas padre cuando el objetivo es un rango de texto o un rango de celdas
- wk auto (por defecto): una línea puede dividirse en dos partes cuando el contenido de cualquier celda (de la línea) no cabe en la página cuando se produce un salto de página físico
- wk avoid: las líneas de la tabla nunca se dividen
- wk mixed al leer el atributo
Valores posibles: Cadena (por defecto es '', lo que significa que se usará el nombre de visualización predeterminado). | -| wk start | (Atributo de rango de sólo lectura) | -| wk type | (Atributo de rango de sólo lectura) Tipo de rango 4D Write Pro. Puede ser 0: rango por defecto (por defecto), 1: rango párrafo, 2: rango imagen | +| wk start | (Atributo de sólo lectura) | +| wk type | (Atributo de sólo lectura) Tipo de rango 4D Write Pro. Puede ser 0: rango por defecto (por defecto), 1: rango párrafo, 2: rango imagen | ### Hojas de estilo @@ -476,12 +477,12 @@ Los atributos de la tabla son específicos a las tablas. Se pueden aplicar a los | wk column count | (Atributo de rango de sólo lectura) Número total de columnas del rango. Valor: Entero largo | | wk datasource | Especifica la fuente de datos para la tabla. Valores posibles:
- *formula object*: la tabla está asociada a una fuente de datos. Si la fórmula devuelve una selección de entidades o una colección no vacía, las líneas se duplican a partir de la línea de la plantilla y se llenan automáticamente con los datos de las entidades o los elementos de la colección (ver *Tabla fuentes de datos*). En caso contrario, las líneas son estándar.
- *null*: la tabla no está asociada a una fuente de datos (tabla estándar).
- wk show data row: valor por defecto. Muestra la fila de datos y las filas de interrupción (si las hay) además de los encabezados y las filas adicionales.
- wk hide data row : oculta la fila de datos y las filas de interrupción (si se ha definido alguna), se siguen mostrando los encabezados y las filas extra.
- wk show placeholder row : muestra una fila de marcador de posición en lugar de la fila de datos y las filas de interrupción (si las hay), los encabezados y las filas adicionales se siguen mostrando. La fila de marcador de posición sigue a la fila de arrastre inferior en el modo de visualización de referencias.
- wk hide table: oculta la tabla completa.
- a todas las tablas dentro del objetivo (documento, sección, rango de tablas o elemento)
- por extensión, a la(s) tabla(s) padre cuando el objetivo es un rango de texto, un rango de líneas o un rango de celdas
Valores posibles:
- wk auto (por defecto): no hay restricciones en cuanto a los saltos de página dentro de la tabla
- wk avoid: evita que la tabla se rompa entre dos líneas (cuando es posible)
- wk mixed al leer el atributo
- wk left (por defecto)
- wk right
- wk center
zone de texte,
*Sous-menu* | Définit l'alignement horizontal de l'élément, relatif à **anchorOrigin** pour les images/zones de texte en page ou à la zone de format pour les images/zones de texte en mode inclus. Cette action réinitialise à 0 le décalage horizontal. (non activée pour les images en ligne). | +| anchoring | {image \| textBox}/anchoring | *Sous-menu* | Sous-menu par défaut avec des actions de paramètres d'ancrage pour les images ou les zones de texte | +| anchorLayout | image/anchorLayout?value={front \| behind | wrapTopBottom | wrapSquareLeft | wrapSquareRight | wrapSquareLargest | wrapSquare | inline}
textBox/anchorLayout?value={front | behind | wrapTopBottom | wrapSquareLeft | wrapSquareRight | wrapSquareLargest | wrapSquare} | Image,
zone de texte,
*Sous-menu* | Définit le type de position d'ancre pour une image ou une zone de texte. Peut être utilisée pour transformer une image en ligne en image ancrée, ou l'inverse.
Note : Si une image ancrée est transformée en image en ligne, elle est insérée au début du texte sélectionné.
La valeur " en ligne " n'est pas supportée pour les zones de texte.
| +| anchorOrigin | {image \| textBox}/anchorOrigin?value={paper-box | header-box | footer-box} | Image,
zone de texte,
*Sous-menu* |
Définit la zone relative à la position absolue d'une image ancrée ou d'une zone de texte. Si l'élément est relative à la zone d'en-tête ou de pied (header-box/footer-box) qui n'est pas visible sur une page, l'image n'est pas affichée. Cette action remet à zéro les valeurs de décalage horizontal et vertical.
Mode Page uniquement, non activée pour les images en ligne.
| +| anchorPage | {image \| textBox}/anchorPage?value={all | current | currentSubSection} | Image,
zone de texte,
*Sous-menu* |
Définit la ou les page(s) où l'image ou la zone de texte sélectionnée est affichée (non activée pour les images en ligne).
Mode page uniquement.
| +| anchorSection | {image \| textBox}/anchorSection?value={all | current} | Image,
zone de texte,
*Sous-menu* |
Définit la ou les section(s) où l'image ou la zone de texte sélectionnée est affichée (non activée pour les images en ligne).
Mode page uniquement.
| +| anchorVerticalAlign | {image \| textBox}/anchorVerticalAlign?value={top | center | bottom} | Image,
zone de texte,
*Sous-menu* |
Définit l'alignement vertical de l'image ou la zone de texte, relatif à **anchorOrigin** pour une image ou une zone texte en page, ou à la zone de format pour une image ou une zone texte en mode inclus. Cette action réinitialise à 0 le décalage vertical (non activée pour les images en ligne).
Note : Voir l'action "verticalAlign" pour l'alignement vertical à l'intérieur de la zone de texte.
| +| avoidPageBreakInside | {paragraph/}avoidPageBreakInside | Paragraphe |
| +| background | {doc \| paragraph \| image \| textBox \| section \| header \| footer \| table \| row \| column \| cell/}background | Document, Paragraphe, Image, zone de texte, Section, En-tête, Pied, Table, Ligne, Colonne, Cellule, *Sous-menu* | Pour les commandes de menu uniquement. Sous-menu par défaut pour tous les attributs de fond. | +| backgroundClip | {doc \| paragraph \| image \| textBox \| section \| header \| footer \| table \| row \| column \| cell/}backgroundClip?value={paper-box \| border-box \| padding-box \| content-box} | Document, Paragraphe, Image, zone de texte, Section, En-tête, Pied, Tableau, Ligne, Colonne, Cellule, *Sous-menu* | Modifie la zone de découpe du fond de la cible (par défaut, la cible est le paragraphe). Paper-box est disponible uniquement avec doc et section. | +| backgroundColor | {doc \| paragraph \| image \| textBox \| section \| header \| footer \| table \| row \| column \| cell/}backgroundColor?value={
Ex: `paragraph/backgroundPositionH?value=left` | +| backgroundPositionV | {doc \| paragraph \| image \| textBox \| section \| header \| footer \| table \| row \| column \| cell/}backgroundPositionV?value={top \| bottom \| center} | Document, Paragraphe, Image, zone de texte, Section, En-tête, Pied, Tableau, Ligne, Colonne, Cellule, *Sous-menu* | Modifie l'alignement vertical de l'image d'arrière-plan de la cible (la cible par défaut est le paragraphe).
Ex: `paragraph/backgroundPositionV?value=top` | +| backgroundRepeat | {doc \| paragraph \| image \| textBox \| section \| header \| footer \| table \| row \| column \| cell/}backgroundRepeat?value={no-repeat \| repeat \| repeat-x \| repeat-y} | Document, Paragraphe, Image, zone de texte, Section, En-tête, Pied, Tableau, Ligne, Colonne, Cellule, *Sous-menu* | Modifie le mode de répétition de l'image d'arrière-plan de la cible (la cible par défaut est le paragraphe). | +| backgroundSizeH | {doc \| paragraph \| image \| textBox \| section \| header \| footer \| table \| row \| column \| cell/}backgroundSizeH?value={
Ex: `paragraph/backgroundSizeH?value=100%`, `section/backgroundSizeH?value=cover` | +| backgroundSizeV | {doc \| paragraph \| image \| textBox \| section \| header \| footer \| table \| row \| column \| cell/}backgroundSizeV?value={
Ex: `paragraph/backgroundSizeV?value=50%`, `section/backgroundSizeV?value=40pt` | +| bookmark | bookmark?index=\
Ex: *bookmark?index=2 // sélectionne le deuxième signet* | +| borderCollapse | borderCollapse | Paragraphe | Fusionne les bordures de paragraphes et les marges intérieures (padding). | +| borderColor | {doc \| paragraph \| image \| textBox \| section \| header \| footer \| table \| row \| column \| cell/}{inside \| outside/}{borderColor \| borderColorLeft \| borderColorRight \| borderColorTop \| borderColorBottom \| borderColorLeftRight \| borderColorTopBottom}?value=\
Paragraphe,
Image,
zone de texte,
Section,
En-tête,
Pied,
Tableau,
Ligne,
Colonne,
Cellule,
*Sous-menu*,
*showDialog* | Modifie la couleur de la bordure de la cible (la cible par défaut est le paragraphe).
Ex: *paragraph/borderColorLeft?value=green* | +| borderRadius | {doc \| paragraph \| image \| textBox \| section \| header \| footer/}borderRadius?value=\
Paragraphe,
Image,
zone de texte,
Section,
En-tête,
Pied,
*Sous-menu* | Change le rayon pour les coins arrondis de la cible (par défaut la cible est le paragraphe).
Ex: *paragraph/borderRadius?value=4pt* | +| borders | {doc \| paragraph \| image \| textBox \| section \| header \| footer \| table \| row \| column \| cell/}{inside \| outside/}borders | Document,
Paragraphe,
Image,
zone de texte,
Section,
En-tête,
Pied,
Table,
Ligne,
Colonne,
Cellule,
*Sous-menu* | Sous-menu par défaut pour les bordures de la cible. | +| borderStyle | {doc \| paragraph \| image \| textBox \| section \| header \| footer \| table \| row \| column \| cell/}{inside \| outside/}{borderStyle \| borderStyleLeft \| borderStyleRight \| borderStyleTop \| borderStyleBottom \| borderStyleLeftRight \| borderStyleTopBottom}?value={none \| hidden \| dotted \| dashed \| solid \| double \| groove \| ridge \| inset \| outset} | Document,
Paragraphe,
Image,
zone de texte,
Section,
En-tête,
Pied,
Tableau,
Ligne,
Colonne,
Cellule,
*Sous-menu* | Modifie le style de la bordure de la cible (par défaut la cible est le paragraphe).
Ex: *paragraph/borderStyleLeft?value=double*
Ex: *outside/borderStyle?value=solid*
Ex: *inside/borderStyle?value=none* | +| borderWidth | {doc \| paragraph \| image \| textBox \| section \| header \| footer \| table \| row \| column \| cell/}{inside \| outside/}{borderWidth \| borderWidthLeft \| borderWidthRight \| borderWidthTop \| borderWidthBottom \| borderWidthLeftRight \| borderWidthTopBottom}?value=\
Paragraphe,
Image,
zone de texte,
Section,
En-tête,
Pied,
Tableau,
Ligne,
Colonne,
Cellule,
*Sous-menu* | Modifie la largeur de la bordure de la cible (par défaut la cible est le paragraphe).
Ex: *paragraph/borderWidthLeft?value=4pt* | +| columnCount | {section/}columnCount?value={1<=number<=20} | Document,
Section,
*Sous-menu* | Nombre de colonnes dans le document et/ou la section courante (la cible par défaut est le document).
Ex: *section/columnCount?value=3* | +| columnRuleColor | {section/}columnRuleColor?value={CSS color} | Document,
Section,
*Sous-menu*,
*showDialog* | Couleur de la ligne de séparation verticale entre les colonnes du document ou de la section.
Ex: *columnRuleColor?value="#FFFFFF"* | +| columnRuleStyle | {section/}columnRuleStyle?value={none \| dotted \| dashed \| solid \| double \| groove \| ridge \| inset \| outset} | Document,
Section,
*Sous-menu* | Style de la ligne de séparation verticale entre les colonnes du document ou de la section.
Ex: *columnRuleStyle?value=solid* | +| columnRuleWidth | {section/}columnRuleWidth?value={CSS length} | Document,
Section,
*Sous-menu* | Largeur de la ligne de séparation verticale entre les colonnes du document ou de la section.
Ex: *columnRuleWidth?value=2pt* | +| columns | {section/}columns | Document,
Section,
*Sous-menu* | Pour les commandes de menu uniquement. Crée automatiquement un sous-menu **Colonnes** complet avec tous les sous-menus d'action de colonne (hormis *insertColumnBreak*). | +| columnSpacing | {section/}columnSpacing?value={CSS length} | Document,
Section,
*Sous-menu* | Espacement entre deux colonnes dans le document et/ou la section courante.
Ex: *columnSpacing?value=1cm* | +| deleteColumns | deleteColumns | Table | Supprime toutes les colonnes sélectionnées. | +| deleteRows | deleteRows | Table | Supprime toutes les lignes sélectionnées. | +| deleteStyleSheet | {paragraph \| image/}deleteStyleSheet?index={1<= number <= number of target style sheets} | Paragraphe,
Image,
*Sous-menu* | Supprime la Nième feuille de style parmi les feuilles de style stockées pour la cible sélectionnée (par défaut la cible est le paragraphe). Le nom de l'élément de menu est remplacé, au moment de l'exécution, par le nom de la feuille de style sur le point d'être supprimée. | +| direction | direction?value={ltr \| rtl} | Paragraphe,
*Sous-menu* | Sens de l'écriture du paragraphe (ltr : left to right - rtl : right to left). | +| displayFormulaAsSymbol | displayFormulaAsSymbol | Document | Affiche les références de formules sous la forme d'un symbole . Ne peut être utilisé que lorsque les formules sont affichées en tant que références. | +| doc | doc | Document,
*Sous-menu* | Sous-menu par défaut pour la disposition du corps du document (attributs du mode inclus ou attributs par défaut des sections - mais pour la marge réservée au mode inclus seulement). | +| dpi | dpi?value=\
Ex: *dpi?value=72* | +| emptyDatasource | {table}/emptyDatasource?value={showDataRow \| hideDataRow \| showPlaceholderRow \| hideTable} | Table,
*Sous-menu* | Définit la manière dont la table est affichée lorsque sa source de données est vide. | +| fontStyleWrite | fontStyleWrite | *Sous-menu* | Pour les commandes de menu uniquement. Affiche le sous-menu Style de police par défaut de 4D Write Pro. | +| fontSubscript | fontSubscript | | Bascule l'attribut de police indice. | +| fontSuperscript | fontSuperscript | | Bascule l'attribut de police exposant. | +| footer | footer | *Sous-menu* | Affiche le sous-menu Pied de page. | +| footer/remove | footer/remove | Pied | Supprime le pied de page sélectionné. | +| formulaHighlight | formulaHighlight?value={values \| references \| always \| never} | Document, *Sous-menu* | Mode de surbrillance de formule pour le document. Peut être utilisé avec un menu déroulant ou un bouton. | +| formulaHighlightColor | formulaHighlightColor?value=
Ex : image/height?value=50pt.
Pour image/width, voir width.
Ex : row/height?value=12pt | +| headerRowCount | {table}/headerRowCount | Tableau, *Sous-menu* | Définit le nombre de lignes d’en-tête dans un tableau (5 au maximum). | +| htmlWYSIWIGEnabled | htmlWYSIWIGEnabled | Document | Bascule du mode html au mode wysiwyg. | +| image | image | Image, *Sous-menu* | Affiche le sous-menu Image. | +| image/displayMode | image/displayMode?value=scaledToFit \| truncated \| truncatedCentered \| proportional \| proportionalCentered \| replicated \| replicatedCentered | Image, *Sous-menu* | Définit le mode d'affichage des images ancrées et des images en ligne.
Ex : image/displayMode?value=scaledToFit | +| image/verticalAlign | image/verticalAlign?value={top \| middle \| bottom \| baseline \| super \| sub} | Image, *Sous-menu* | Alignement vertical de l'image.
Ex: image/verticalAlign?value=super | +| insertColumnBreak | insertColumnBreak | Paragraphe | Insère un saut de colonne dans la sélection. | +| insertColumnToTheLeft | insertColumnToTheLeft | Table | Insère une colonne à gauche de la première colonne sélectionnée. | +| insertColumnToTheRight | insertColumnToTheRight | Table | Insère une colonne à droite de la dernière colonne sélectionnée. | +| insertContinuousSectionBreak | insertContinuousSectionBreak | Paragraphe | Insère un saut de section continu à la sélection. | +| insertImage | insertImage | | Ouvre une boîte de dialogue de sélection d'image et insère l'image sélectionnée (le cas échéant) en tant que caractère dans la zone. | +| insertPageBreak | insertPageBreak | Paragraphe | Insère un saut de page à l'endroit sélectionné. | +| insertRowAbove | insertRowAbove | Table | Insère une ligne au-dessus de la ligne ou des lignes sélectionnée(s). | +| insertRowBelow | insertRowBelow | Table | Insère une ligne en-dessous de la ligne ou des lignes sélectionnée(s). | +| insertSectionBreak | insertSectionBreak | Paragraphe | Insère un saut de section à l'endroit sélectionné. | +| insertSoftHyphen | insertSoftHyphen | | Insère un trait d'union au niveau du curseur. | +| keepWithNext | keepWithNext | Paragraphe | Relie un paragraphe au suivant afin qu'ils ne puissent pas être séparés par des sauts de page ou de colonne automatiques.
Si cette action est appliquée au dernier paragraphe de la dernière cellule d'un tableau, la dernière ligne du tableau est reliée au paragraphe suivant. | +| lineHeight | lineHeight?value={
Ex: lineHeight?value=120% | +| listStartNumber | listStartNumber?value={
Ex: listStartNumber?value=10 | +| listStyleImage | listStyleImage/showDialog | Paragraphe, *showDialog* | Ouvre un dialogue d'ouverture de fichier pour choisir une image à afficher en tant que puce pour une liste ; définit également un élément de liste sous forme de disque – style à utiliser si l'image n'est pas trouvée. | +| listStyleType | listStyleType?value={none \| disc \| circle \| square \| hollow-square \| diamond \| club \| decimal \| decimal-leading-zero \| lower-latin \| lower-roman \| upper-latin \| upper-roman \| lower-greek \| decimal-greek \| armenian \| georgian \| hebrew \| hiragana \| katakana \| cjk-ideographic} | Paragraphe, *Sous-menu* | Type de style de liste de paragraphes. | +| margin | {doc \| paragraph \| image \| textBox \| section \| header \| footer \| table}/{inside \| outside}/{margin \| marginLeft \| marginRight \| marginTop \| marginBottom \| marginLeftRight \| marginTopBottom}?value={
Ex : `margin?value=4pt` – définit toutes les marges du paragraphe sur 4pt.
Ex : `outside/margin?value=4pt` – définit les marges extérieures du paragraphe sur 4pt.
Ex : `doc/marginLeft?value=1cm` – définit la marge gauche à 1cm pour le document, comme dans le mode intégré.
Ex : `section/marginLeft?value=1cm` – définit la marge gauche à 1cm pour les pages de la première section sélectionnée. | +| merge | {paragraph/}merge cell/merge | Paragraphe, cellule | Utilisé avec les paragraphes : fusionne les paragraphes. Utilisé avec les cellules : fusionne les cellules sélectionnées. | +| minHeight | {paragraph \| image}/minHeight?value=
Ex: paragraph/minHeight?value=50pt | +| minWidth | {paragraph \| image}/minWidth?value=
Ex: paragraph/minWidth?value=50pt | +| moveToFront | moveToFront | Image | Place l'image au premier plan (non activée pour les images en ligne). | +| moveToBack | moveToBack | Image | Place l'image à l'arrière-plan (non activée pour les images en ligne). | +| newLineStyleSheet | newLineStyleSheet?index={1<=number<=nombre de feuilles de style paragraphe} \| newLineStyleSheet?value=auto | Paragraphe, *Sous-menu* | Les éléments du paragraphe sélectionné utiliseront la Nième feuille de style pour les nouveaux paragraphes créés par Retour Chariot ou lors d'un fractionnement de paragraphes. Si value=auto, les nouveaux paragraphes utiliseront la même feuille de style (fonctionnement par défaut).
(Le libellé de la ligne de menu est remplacé, à l'exécution, par le nom de la feuille de style.) | +| padding | {doc \| paragraph \| image \| textBox \| section \| header \| footer \| column \| row \| cell}/{inside \| outside}/{padding \| paddingLeft \| paddingRight \| paddingTop \| paddingBottom \| paddingLeftRight \| paddingTopBottom}?value=
Ex: pageMode?value=page | +| pageOrientation | {section}/pageOrientation?value={landscape \| portrait} | Section, *Sous-menu* | Modifie l'orientation de la page de la première section sélectionnée.
Si la section n'est pas spécifiée, l'orientation s'applique à toutes les sections.
Ex: pageOrientation?value=portrait // change l'orientation en Portrait pour tout le document.
Ex: section/pageOrientation?value=landscape // change l'orientation en Paysage pour la première section sélectionnée. | +| pageSize | pageSize?index=
La liste contient les formats courants de l'imprimante, les formats ISO et les formats personnalisés définis par l'utilisateur. | +| paragraph | paragraph | Paragraphe, *Sous-menu* | Sous-menu par défaut pour le paragraphe. | +| print | print | Document | Imprime le document en mode Page avec les paramètres de vue courants de la zone 4D Write Pro qui a le focus. | +| refreshImages | refreshImages | Image | Recharge les images du réseau pour les images avec URLs. | +| removeSoftHyphens | removeSoftHyphens | | Supprime tous les traits d'union conditionnels de la sélection courante. Si la sélection est vide, supprime le trait d'union conditionnel avant ou après le curseur, le cas échéant. | +| row/avoidPageBreakInside | row/avoidPageBreakInside | Tableau, Ligne | Autorise ou désactive les sauts de page à l'intérieur des lignes du tableau.
Cette action est désactivée si :
- la sélection courante ne contient pas de tableau
- le tableau n'autorise pas les sauts de page
- le tableau se trouve dans un en-tête ou un pied de page.
Note : si plusieurs tableaux sont sélectionnés et que certains n'autorisent pas les sauts de page, cette option sera activée mais ne s'appliquera qu'aux tableaux qui les autorisent. | +| section | section | Section, *Sous-menu* | Sous-menu par défaut de disposition de la page pour la première section sélectionnée. | +| section/differentFirstPage | section/differentFirstPage | Section | Active ou désactive une première page différente pour la section. | +| section/differentLeftRightPages | section/differentLeftRightPages | Section | Active ou désactive des pages droites et gauches différentes pour la section. | +| section/name/showDialog | section/name/showDialog | Section, *showDialog* | Affiche un dialogue permettant d'entrer le nom de la première section sélectionnée. | +| section/reset | section/reset | Section | Réinitialise tous les attributs de la première section sélectionnée pour les remplacer par les valeurs par défaut :
- héritées du document pour l'arrière-plan, la bordure et les marges intérieures (même en mode inclus)
- 2,5 cm pour les marges de page.
Les propriétés de colonnes de la première section sélectionnée sont également réinitialisées (seules les propriétés par défaut sont appliquées). | +| split | {paragraph}/split \| cell/split | Paragraphe, Cellule | Utilisé avec un paragraphe : fractionne le paragraphe.
Utilisé avec une cellule : fractionne les cellules sélectionnées (seules les cellules préalablement fusionnées peuvent être fractionnées). | +| styleSheet | {paragraph \| image}/styleSheet?value={1<=number<=nombre de feuilles de style} | Paragraphe, Image, *Sous-menu*, *showDialog* | Applique la Nième feuille de style aux éléments sélectionnés de la cible.
Avec la boîte de dialogue, la nouvelle feuille de style utilise les attributs courants de la prem +| tabDecimalSeparator | tabDecimalSeparator?value={point \| comma \| pointOrComma \| system} | Document, *Sous-menu* | Définit le caractère utilisé comme séparateur décimal par les tabulations décimales. | +| tableAlign | tableAlign?value={left \| center \| right}
ou
table/tableAlign?value={left \| center \| right} | Tableau, *Sous-menu* | Indique l'alignement horizontal d'un tableau. | +| table/avoidPageBreakInside | table/avoidPageBreakInside | Table | Active ou désactive les sauts de page dans les tableaux.
Désactivée si :
- la sélection courante ne contient pas de tableau
- le tableau se trouve dans un en-tête ou un pied de page | +| table/bottomCarryOverRow | table/bottomCarryOverRow | Table | Bascule l'affichage des lignes à reporter en bas (voir *Carry-over rows*). | +| textAlign | textAlign?value={left \| right \| center \| justify \| initial} | Paragraphe | Alignement du texte du paragraphe.
(`initial` utilise `right` pour la direction RTL ou `left` pour la direction LTR). | +| textBox | textBox | *Sous-menu* | Sous-menu avec toutes les actions disponibles pour la zone de texte ciblée ou sélectionnée. | +| textBox/remove | textBox/remove | Zone de texte | Supprime la zone de texte sélectionnée. | +| textIndent | textIndent?value=
Ex: textIndent?value=2cm | +| textLinethrough | textLinethrough | *Sous-menu* | Pour les commandes de menu uniquement. Sous-menu Texte barré (avec style et couleur). | +| textLinethroughColor | textLinethroughColor?value={
Ex: textLinethroughColor?value=red | +| textLinethroughStyle | textLinethroughStyle?value={none \| solid \| dotted \| dashed \| double \| semi-transparent \| word} | *Sous-menu* | Définit le style du texte barré.
Ex: textLinethroughStyle?value=dotted | +| textShadow | textShadow | *Sous-menu* | Pour les commandes de menu uniquement. Sous-menu Texte ombré (avec couleur et décalage). | +| textShadowColor | textShadowColor?value={
Ex: textShadowColor?value=green | +| textShadowOffset | textShadowOffset?value=
Ex: textShadowOffset?value=2pt | +| textTransform | textTransform?value={none \| capitalize \| uppercase \| lowercase \| small-uppercase} | *Sous-menu* | Formate le texte.
Ex: textTransform?value=capitalize | +| textUnderline | textUnderline | *Sous-menu* | Pour les commandes de menu uniquement. Sous-menu Texte souligné (avec style et couleur). | +| textUnderlineColor | textUnderlineColor?value={
Ex: textUnderlineColor?value=red | +| textUnderlineStyle | textUnderlineStyle?value={none \| solid \| dotted \| dashed \| double \| semi-transparent \| word} | *Sous-menu* | Définit le style du soulignement.
Ex: textUnderlineStyle?value=dotted | +| updateStyleSheet | {paragraph \| image}/updateStyleSheet | Paragraphe, Image, *Sous-menu* | Met à jour la première feuille de style de la cible sélectionnée (la cible par défaut est le paragraphe). | +| userUnit | userUnit?value={cm \| mm \| in \| pt} | *Sous-menu* | Modifie l'unité de mise en page du document (répercutée sur les règles). | +| verticalAlign | {paragraph \| row \| column \| cell \| textBox}/verticalAlign?value={top \| middle \| bottom} | Paragraphe, Ligne, Colonne, Cellule, zone de texte, *Sous-menu* | Alignement vertical de la cible (par défaut le paragraphe).
Ex: verticalAlign?value=top
L'effet dépend de la valeur `minHeight` de la cible. | +| view | view | *Sous-menu* | Pour les commandes de menu uniquement. Sous-menu par défaut pour les paramétrages de vue. | +| visibleBackground | visibleBackground | Document | Affiche ou masque l'arrière-plan, les images ancrées et les zones de texte. | +| visibleEmptyImages | visibleEmptyImages | Document | Affiche ou masque un rectangle noir par défaut pour les images qui ne peuvent pas être chargées ou calculées (images vides ou dans un format non supporté). | +| visibleFooters | visibleFooters | Document | Affiche ou masque les pieds de page. | +| visibleHeaders | visibleHeaders | Document | Affiche ou masque les en-têtes. | +| visibleHiddenChars | visibleHiddenChars | Document | Affiche ou masque les caractères cachés. | +| visibleHorizontalRuler | visibleHorizontalRuler | Document | Affiche ou masque la règle horizontale. | +| visiblePageFrames | visiblePageFrames | Document | Affiche ou masque les cadres des pages. | +| visibleVerticalRuler | visibleVerticalRuler | Document | Affiche ou masque la règle verticale (Mode Page uniquement). | +| widowAndOrphanControlEnabled | widowAndOrphanControlEnabled | Paragraphe | Active ou désactive le contrôle des veuves et orphelines. | +| width | {paragraph \| image \| textBox \| column}/width?value={
La valeur `auto` n'est pas disponible pour les zones de texte (converties en 8 cm) et pour les colonnes.
Ex: image/width?value=50pt | +| zoom | zoom?value={25% <= percentage <= 400%} | Document, *Sous-menu* | Modifie le zoom du document.
Ex: zoom?value=120% | + + +### Autres actions + +De nombreuses autres actions standard proposées avec les formulaires 4D peuvent être utilisées dans les zones 4D Write Pro : + +* *Actions d'édition*, comme les actions Copier/Coller. +* Actions sur la *Police*, telles que **fontBold** ou **fontSize**. +* Actions sur les *Expressions dynamiques*, permettant de gérer l'insertion d'expressions. +* Actions du *Correcteur orthographique*. \ No newline at end of file diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/WritePro/user-legacy/exporting-to-html-and-mime-html-formats.md b/i18n/fr/docusaurus-plugin-content-docs/current/WritePro/user-legacy/exporting-to-html-and-mime-html-formats.md new file mode 100644 index 00000000000000..ed7863b8387aaf --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/current/WritePro/user-legacy/exporting-to-html-and-mime-html-formats.md @@ -0,0 +1,179 @@ +--- +id: exporting-to-html-and-mime-html-formats +title: Exporter aux formats HTML et MIME HTML +displayed_sidebar: docs +--- + +#### + +Les documents 4D Write Pro peuvent être exportés aux formats HTML et MIME HTML à l'aide des commandes [WP EXPORTER DOCUMENT](../commands/wp-exporter-document) et [WP EXPORTER VARIABLE](../commands/wp-exporter-variable). Utilisez ces tableaux pour vérifier quels attributs et fonctionnalités de 4D Write Pro sont exportés vers HTML et HTML MIME. Les attributs/fonctionnalités sont triés par ordre alphabétique. Pour une liste détaillée des attributs, reportez-vous à la page *Attributs 4D Write Pro*. + +#### Common attributes + +| **Attribut/Fonctionnalités** | **Exporté(e)** | **Commentaire** | +| --------------------------------------------- | -------------- | --------------- | +| Background clip | oui | | +| Background color (for element, not character) | oui | | +| Background image | oui | | +| Background repeat | oui | | +| Background origin | oui | | +| Background position | oui | | +| Background width and height | oui | | +| Border color | oui | | +| Border radius | oui | | +| Border style | oui | | +| Border width | oui | | +| Element id | oui | | +| Margin | oui | | +| Padding | oui | | +| Protected | non | | +| Style sheet | oui | | + +#### Caractères + +| **Attribut/Fonctionnalité** | **Exporté(e)** | **Commentaire** | +| --------------------------- | -------------- | -------------------------------------------- | +| Background color | oui | | +| Font and font styles | oui | | +| Font size | oui | | +| Strikethrough color | non | | +| Strikethrough styles | partiellement | Seul le gras est exporté | +| Superscript, subscript | oui | | +| Text color | oui | | +| Text shadow | oui | | +| Text transform | partiellement | Les petites majuscules ne sont pas exportées | +| Underline color | non | | +| Underline styles | partiellement | Seul le gras est exporté | + +#### Colonnes + +| **Attribut/Fonctionnalité** | **Exporté(e)** | **Commentaire** | +| --------------------------- | -------------- | --------------- | +| Column count | non | | +| Column rule color | non | | +| Column rule style | non | | +| Column rule width | non | | +| Column spacing | non | | + +#### Document + +| **Attribut/Fonctionnalité** | **Exporté(e)** | **Commentaire** | +| ---------------------------- | -------------- | ---------------------------------------- | +| Break paragraphs in formulas | non | | +| Document (meta) information | partiellement | Seuls le titre et le sujet sont exportés | +| Dpi | non | | +| Font default | non | | +| Header and footer autofit | non | | +| Page margin | non | | +| Page orientation | non | | +| Page width/height | non | | +| Protection enabled | non | | +| Tab decimal separator | non | | +| User unit | non | | + +#### Images + +| **Attribut/Fonctionnalité** | **Exporté** | **Commentaire** | +| -------------------------------------------- | ------------- | ------------------------------------------------------------------------------- | +| Alternate text | oui | | +| Anchor align | partiellement | Uniquement droite, gauche, haut ou bas | +| Anchor embedded | oui | | +| Anchor offset | oui | | +| Anchor origin | partiellement | Uniquement pour le conteneur (bordures de la page web) | +| Anchor to a single page | non | | +| Anchor to all pages | non | | +| Anchor to all sections of a page | non | | +| Background image (et attributs de fond liés) | oui | | +| Image display mode | partiellement | Si une image contient une image de fond, elle est exportée et mise à l'échelle. | +| Image URL | oui | | +| Vertical align | oui | | + +#### Zones de texte + +| **Attribut/Fonctionnalité** | **Exporté** | **Commentaire** | +| -------------------------------- | ------------- | ------------------------------------------------------ | +| Anchor align | oui | | +| Anchor embedded | oui | comme div | +| Anchor offset | oui | | +| Anchor origin | partiellement | Uniquement pour le conteneur (bordures de la page web) | +| Anchor to a single page | non | | +| Anchor to all pages | non | | +| Anchor to all sections of a page | non | | +| Vertical align | oui | | + +#### Paragraphes + +| **Attribute/Fonctionnalité** | **Exporté** | **Commentaire** | +| --------------------------------------- | ------------- | ----------------------------------------------------------------------------------------------- | +| Absolute tab stops | non | | +| Column break after | oui | Une seule colonne uniquement (colonnes multiples non prises en charge) | +| Direction | oui | | +| Keep with next | oui | | +| Line height | yes | | +| List font | non | | +| List image | oui | | +| List image height | non | | +| List start number | oui | | +| List string format (custom format) | non | | +| List style type | partiellement | Hollow-square, diamond, et club ne sont pas exportés, decimal-greek est identique à lower-greek | +| Min-height | oui | | +| Min-width | non | | +| New line style sheet | non | | +| Page break after | oui | | +| Page break inside | oui | | +| Section break after (continuous or not) | non | | +| Text align | oui | | +| Text indent | oui | | +| Vertical-align | oui | | +| Widow and orphan control | non | | +| Width | oui | | + +#### Elements de section et de page + +| **Attribut/Fonctionnalité** | **Exporté** | **Commentaire** | +| -------------------------------- | ----------- | --------------------------------------------------------------------- | +| First page sub-section | non | | +| Headers and footers | non | | +| Left and right page sub-sections | non | | +| Main sections | non | Seuls les attributs au niveau du document sont exportés au corps html | +| Page margin | non | | +| Page orientation | non | | + +#### Tableaux + +| **Attribut/Fonctionnalité** | **Exporté** | **Commentaire** | +| ------------------------------------ | ----------- | ---------------------------------------------------------------------- | +| Background image (et attributs liés) | oui | | +| Column break after | oui | Une seule colonne uniquement (colonnes multiples non prises en charge) | +| Horizontal alignment | oui | | +| Page break after | oui | | +| Page break inside | oui | | +| Section break after | non | | +| Bottom carry-over rows | non | | + +#### Cellules de tableau + +| **Attribut/Fonctionnalité** | **Exporté** | **Commentaire** | +| ---------------------------------------- | ----------- | --------------- | +| Background image (et attributs relatifs) | oui | | +| Height | oui | | +| Vertical align | oui | | +| Width | oui | | + +#### Ligne de tableau + +| **Attribut/Fonctionnalité** | **Exporté** | **Commentaire** | +| ------------------------------------ | ----------- | --------------------------------------------------------------------------------- | +| Background image (et attributs liés) | oui | | +| Column break after | oui | Une seule colonne seulement (les colonnes multiples ne sont pas prises en charge) | +| Height | oui | | +| Page break after | oui | | + +#### Autres fonctionnalités + +| **Attribut/Fonctionnalité** | **Exporté** | **Commentaire** | +| ---------------------------- | ----------- | --------------------------------- | +| 4D formulas | non | Calculées et gelées pour l'export | +| 4D method links | non | | +| Bookmarks and bookmark links | oui | | +| URL links | oui | | \ No newline at end of file diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/WritePro/user-legacy/exporting-to-svg-format.md b/i18n/fr/docusaurus-plugin-content-docs/current/WritePro/user-legacy/exporting-to-svg-format.md new file mode 100644 index 00000000000000..e804b9c87d8ade --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/current/WritePro/user-legacy/exporting-to-svg-format.md @@ -0,0 +1,79 @@ +--- +id: exporting-to-svg-format +title: Exporter au format SVG +displayed_sidebar: docs +--- + +#### + +Vous pouvez exporter les pages d’un document 4D Write Pro au format SVG à l'aide des commandes [WP EXPORTER DOCUMENT](../commands/wp-exporter-document) et [WP EXPORTER VARIABLE](../commands/wp-exporter-variable). Cette page contient des informations et des notes supplémentaires sur l'exportation SVG. + +#### Rendu SVG + +Les images SVG et les zones de texte sont rendues selon les paramètres de la page affichée en Mode d'affichage de la page. Les propriétés suivantes sont prises en compte : + +* Attributs d'arrière-plan (si exportés) +* Bordures +* Marges +* Orientation +* Marges intérieures (padding) +* Taille de la page +* Sections (le rendu SVG prend en compte les attributs des sections, mais les sections elles-mêmes ne sont pas exportées) + +Parties du document qui sont exportées en SVG : + +* Corps +* Images en ligne +* Zones de texte +* Titre (la métadonnée wk title) + +Parties du document qui sont exportées en SVG en fonction du paramètre *option* : + +* En-têtes +* Pieds de page +* Références ou valeurs (concernant les valeurs, l'option wk recompute formulas détermine si les formules sont évaluées avant l'exportation) +* Couleurs d'arrière-plan +* Images définies comme images de fond et images ancrées + +Les éléments suivants ne sont pas exportés en SVG : + +* Polices (converties en styles CSS, mais non intégrées dans le SVG exporté. Voir *Gestion des polices*) +* Liens vers des signets (rendus mais non actifs) +* Liens vers des URL (rendus mais non actifs) +* Mise en évidence des formules personnalisées +* Zones de texte ancrées dans le mode d'affichage intégré +* Métadonnées + * Auteur + * Sujet + * Date de création + * Date de modification + +#### Gestion des polices + +Les polices ne sont pas intégrées dans le SVG exporté. Le texte ne sera donc rendu correctement que si la famille et le style de police sont supportés sur la plateforme où l'image SVG est rendue. + +Si vous voulez vous assurer que le rendu sera équivalent sur toutes les plateformes, même lorsque les polices ne sont pas disponibles, vous pouvez utiliser l'option wk import google fonts lors de l'exportation d'un document 4D Write Pro. + +Les polices Google importées remplacent les polices natives lors du rendu du SVG. Si votre intention est de rendre l'image SVG sur la même plateforme, nous vous recommandons de ne pas utiliser l'option wk import google fonts option puisque le rendu avec les polices natives est toujours meilleur. + +**Note :** Seuls les styles en gras et en italique sont préservés. La compatibilité à 100 % entre les styles de police natifs et la définition des styles de police en CSS (et ainsi en SVG) n'est pas garantie. L'exportation vers PDF est plus adaptée pour la distribution vers toutes les plateformes ou pour un meilleur support WYSIWYG des polices, puisque les polices sont intégrées dans le PDF. + +#### Exemple + +Cet exemple exporte une page de document au format SVG et crée un aperçu de l'image en utilisant [SVG EXPORTER VERS IMAGE](../../commands/svg-exporter-vers-image). + +```4d + +var $preview : Picture + var $options : Object + var $svgRoot : Text + var $options Object + +$options: :=Créer objet + $options[wk max picture DPI]:=96 + WP EXPORTER VARIABLE(wpDoc;$text;wk svg;$options) + $svgRoot:=DOM Analyser variable XML($text;Faux) + SVG EXPORTER VERS IMAGE($svgRoot;$preview;Posséder source données XML) + + +``` \ No newline at end of file diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/WritePro/user-legacy/handling-pictures.md b/i18n/fr/docusaurus-plugin-content-docs/current/WritePro/user-legacy/handling-pictures.md new file mode 100644 index 00000000000000..154c005559a9a8 --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/current/WritePro/user-legacy/handling-pictures.md @@ -0,0 +1,209 @@ +--- +id: handling-pictures +title: Manipuler des images +displayed_sidebar: docs +--- + +#### Images en arrière-plan + +Des images peuvent être mises en place en tant qu'arrière-plan de documents 4D Write Pro ou de partie du document (tableau, paragraphe, sections, en-têtes/pieds, etc.). + +Voici un exemple montrant deux façons différentes d'utiliser une image comme arrière-plan d'un document : + +>  + +Les images d'arrière-plan peuvent être placées soit par programmation, soit via le menu contextuel. Pour plus d'informations, voir la section *Fond* dans l'article *Utiliser une zone 4D Write Pro*. + +L'affichage de l'image d'arrière-plan peut également être défini par programmation ou via le menu contextuel. A noter que les valeurs du mode d'affichage en arrière-plan définissent des préréglages des paramètres d'arrière-plan, comme indiqué dans la description de la constante : + +| Constante | Comment | +| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| wk proportional | Lorsqu'elle est utilisée comme valeur de wk image display mode, l'image est alignée en haut à gauche de la zone de contenu, non répliquée, mise à l'échelle pour s'adapter à la zone de contenu, et conserve son rapport hauteur/largeur. Lorsqu'elle est utilisée comme valeur de wk background display mode, elle prédéfinit les attributs suivants : wk background width \= "contain" wk background height \= "auto" wk background repeat \= wk no repeat wk background origin \= wk padding box wk background position horizontal \= wk left wk background position vertical \= wk top | +| wk proportional centered | Lorsqu'elle est utilisée comme valeur de wk image display mode, l'image est centrée dans la zone de contenu, non répliquée, mise à l'échelle pour s'adapter à la zone de contenu, et conserve son rapport hauteur/largeur. Lorsqu'elle est utilisé comme valeur de wk background display mode, elle prédéfinit les attributs suivants : wk background width \= "contain" wk background height \= "auto" wk background repeat \= wk no repeat wk background origin \= wk padding box wk background position horizontal \= wk center wk background position vertical \= wk center | +| wk replicated | Lorsqu'elle est utilisée comme valeur de wk image display mode, l'image est alignée en haut à gauche de la zone de contenu, répliquée, et conserve sa taille d'origine. Lorsqu'elle est utilisée comme valeur de wk background display mode, elle prédéfinit les attributs suivants : wk background width \= "auto" wk background height \= "auto" wk background repeat \= wk repeat wk background origin \= wk padding box wk background position horizontal \= wk left wk background position vertical \= wk top | +| wk replicated centered | Lorsqu'elle est utilisée comme valeur de wk image display mode, l'image est centrée dans la zone de contenu, répliquée, et conserve sa taille d'origine. Lorsqu'elle est utilisée comme valeur de wk background display mode, elle prédéfinit les attributs suivants : wk background width \= "auto" wk background height \= "auto" wk background repeat \= wk repeat wk background origin \= wk padding box wk background position horizontal \= wk center wk background position vertical \= wk center | +| wk scaled to fit | Lorsqu'elle est utilisée comme valeur de wk image display mode, l'image est mise à l'échelle pour s'adapter à la zone de contenu et n'est pas répliquée. Lorsqu'elle est utilisée comme valeur de wk background display mode, elle prédéfinit les attributs suivants : wk background width \= "100%" wk background height \= "100%" wk background repeat \= wk no repeat wk background origin \= wk padding box wk background position horizontal \= wk left wk background position vertical \= wk top | +| wk truncated | Lorsqu'elle est utilisée comme valeur de wk image display mode, l'image est alignée en haut à gauche de la zone de contenu, non répliquée, et conserve sa taille d'origine. Lorsqu'elle est utilisée comme valeur de wk background display mode, elle prédéfinit les attributs suivants : wk background width \= "auto" wk background height \= "auto" wk background repeat \= wk no repeat wk background origin \= wk padding box wk background position horizontal \= wk left wk background position vertical \= wk top | +| wk truncated centered | Lorsqu'elle est utilisée comme valeur de wk image display mode, l'image est centrée dans la zone de contenu, non répliquée, et conserve sa taille d'origine. Lorsqu'elle est utilisée comme valeur de wk background display mode, elle prédéfinit les attributs suivants : wk background width \= "auto" wk background height \= "auto" wk background repeat \= wk no repeat wk background origin \= wk padding box wk background position horizontal \= wk center wk background position vertical \= wk center | + +#### Ajouter des images + +Ajouter des images dans un document 4D Write Pro peut se faire de multiples façons et dépend de vos besoins : + +* pour ajouter une **image d'arrière-plan**, utilisez l'attribut wk background image ou wk background image url avec la commande [WP FIXER ATTRIBUTS](../commands/wp-fixer-attributs) +* pour ajouter une **image en ligne**, *i.e.* insérée dans le texte comme un caractère, utilisez la commande [WP INSERER IMAGE](../commands/wp-inserer-image) ou la commande [ST INSERER EXPRESSION](../../commands/st-inserer-expression) +* pour ajouter une **image ancrée** dans la page (derrière ou devant le texte), utilisez la commande [WP Ajouter image](../commands/wp-ajouter-image). + +La façon dont vous ajoutez une image détermine la couche où elle est positionnée, comme le montre le diagramme ci-dessous : + + + +#### Positionnement et affichage des images ancrées + +Les images ancrées sont ajoutées avec une position absolue, devant/derrière le texte, et ancrées à la page ou à des parties spécifiques d'un document (*i.e.*, en-tête, pied de page, section). La définition d'une position absolue pour une image se fait grâce aux commandes [WP Ajouter image](../commands/wp-ajouter-image) et [WP FIXER ATTRIBUTS](../commands/wp-fixer-attributs). + +Les positions d'images ancrées peuvent être modifiées avec les attributs spécifiques et / ou les actions standard suivants : + +| **Propriété (constante)** | **Action standard** | +| --------------------------- | ----------------------- | +| wk anchor layout | *anchorLayout* | +| wk anchor horizontal offset | | +| wk anchor horizontal align | *anchorHorizontalAlign* | +| wk anchor vertical offset | | +| wk anchor vertical align | *anchorVerticalAlign* | +| wk anchor origin | *anchorOrigin* | +| wk anchor page | *anchorPage* | +| wk anchor section | *anchorSection* | +| | *moveToBack* | | +| | *moveToFront* | | + +Les images ancrées supportent l'habillage automatique du texte lorsqu'elles sont ancrées dans un document avec des options telles que à gauche, à droite, sur le plus grand côté, au-dessus et au-dessous, ou tout autour, fournies par la propriété wk anchor layout ou l'action standard **anchorLayout**. Consultez cet [article de blog](https://blog.4d.com/fr/4d-write-pro-more-display-options-for-anchored-pictures-and-text-boxes/) pour plus de détails. + + + +Les images avec habillage ancrées dans le corps de la page n'affectent pas l'en-tête ou le pied de page (l'image est affichée devant l'en-tête ou le pied de page) ; au contraire, les images ancrées dans l'en-tête et le pied de page affectent le corps de la page si elles le chevauchent. + +**Note :** Si vous souhaitez ancrer une image avec habillage de texte à l'en-tête ou au pied de page, vous devez également définir l'alignement vertical de l'image sur le haut. + +Les images ancrées sont affichées uniquement en mode Page. Elles ne sont pas affichées si : + +* elles sont ancrées à un en-tête ou un pied de page qui n'est pas visible ; +* le mode d'affichage est le mode Brouillon ; +* elles sont centrées ou ancrées aux sections, et l'option **Afficher HTML WYSIWYG** est cochée ; +* l'option "Afficher l'arrière-plan" n'est pas sélectionnée. + +#### Expressions image + +Vous pouvez insérer des expressions 4D qui retournent des images dans vos zones 4D Write Pro. Les expressions peuvent être des variables, champs, méthodes projet, attributs d'objets ou éléments de collections. + +Vous pouvez visualiser la référence d'une expression dans l'infobulle de l'image(\*) : + + + +(\*)Comme il n'y a pas de texte associé à une image ancrée, une référence d'expression ne peut pas être affichée. + +Tous les attributs d'images peuvent être appliqués aux expressions image (les attributs wk image et wk image url peuvent uniquement être lus). Notez cependant que, comme les images ont des attributs spécifiques, 4D Write Pro doit évaluer l'expression au moins une fois pour détecter que son résultat est une image et pouvoir la traiter comme expression image. Cela signifie que lorsqu'une expression image est insérée avec [WP INSERER FORMULE](../commands/wp-inserer-formule), [WP CALCULER FORMULES](../commands/wp-calculer-formules) doit être appelée avant d'appliquer le moindre attribut d'image. + +Si l'image résultant de l'expression ne peut pas être calculée ou chargée, 4D Write Pro affiche un cadre d'image par défaut noir : + + + +**Note** : Comme les autres expressions, les expressions image sont aussi impactées par les commandes [WP CALCULER FORMULES](../commands/wp-calculer-formules) et [WP FIGER FORMULES](../commands/wp-figer-formules). + +##### Images ancrées + +Les expression image ancrées sont ajoutées à l'aide la commande [WP Ajouter image](../commands/wp-ajouter-image) (sans le second paramètre), suivie par un appel à la commande [WP FIXER ATTRIBUTS](../commands/wp-fixer-attributs) avec le sélecteur wk image formule. + +Exemple : + +```4d + obImage:=WP Ajouter image(myDoc) + WP FIXER ATTRIBUTS(obImage;wk image formule;Formule(m_buildPict)) +``` + +Vous pouvez aussi insérer des expressions image en utilisant [WP FIXER ATTRIBUTS](../commands/wp-fixer-attributs) et wk image formule sur des images ancrées existantes. + +**Note de compatibilité :** wk image expression peut toujours être utilisée pour définir des expressions image via du texte. Toutefois, il est recommandé d'utiliser wk image expression et des objets. + +L'appel de la commande [WP REINITIALISER ATTRIBUTS](../commands/wp-reinitialiser-attributs) avec wk image formule est similaire à l'appel de [WP FIGER FORMULES](../commands/wp-figer-formules) (sur le document entier) dans la mesure où l'expression est effacée de l'attribut image. Cependant, [WP FIGER FORMULES](../commands/wp-figer-formules) calcule l'expression avant de l'effacer, contrairement à [WP REINITIALISER ATTRIBUTS](../commands/wp-reinitialiser-attributs). Si une expression n'a jamais été calculée, le cadre d'image par défaut noir est affiché. + +##### Images en ligne + +Les expressions image en ligne sont ajoutées dans vos zones 4D Write Pro à l'aide de la commande [WP INSERER FORMULE](../commands/wp-inserer-formule). + +Exemples : + +```4d + //Insertion d'une variable image + ST INSERER FORMULE(wpRange;Formule($vpict);wk prepend) + + //Insertion d'un champ + ST INSERER FORMULE(wpRange;Formule([DOC]SamplePict);wk prepend) + + //Insertion d'une méthode 4D + ST INSERER FORMULE(wpRange;Formule(M_ComputeChart);wk prepend) +``` + +#### Empty pictures + +If an image is empty (e.g. it could not be loaded, or it results from an expression that could not be computed, or it uses an unsupported picture format), by default 4D Write Pro displays a black frame rectangle: + + + +You can remove these black rectangles from the current view using: + +* the "Show empty or unsupported images" option of the Property list (see *Configuring View properties*), or +* the [WP SET VIEW PROPERTIES](../commands/wp-set-view-properties) command with the wk visible empty images selector, or +* the *visibleEmptyImage* standard action (see *Using 4D Write Pro standard actions*). + +You can also use the wk visible empty images selector with the [WP EXPORT DOCUMENT](../commands/wp-export-document) and [WP EXPORT VARIABLE](../commands/wp-export-variable) commands to remove the black rectangles from exported contents. + +Note that when this option is set, missing image elements will not be displayed at all even if they have borders, width, height, or background; this may impact the page layout for inline images. + +#### Propriétés des images + +Toutes les images ont des propriétés (attributs) telles que la hauteur, la largeur, les bordures, le mode d'affichage, etc., qui peuvent être lues ou fixées via le langage 4D Write Pro ([WP LIRE ATTRIBUTS](../commands/wp-lire-attributs) et [WP FIXER ATTRIBUTS](../commands/wp-fixer-attributs)) ou les actions standard. + +* La liste complète des propriétés utilisables pour les images est disponible sur la page *Attributs 4D Write Pro*. +* La section *Image* contient les attributs spécifiques aux images seules. +* La page *Utiliser les actions standard 4D Write Pro* liste aussi les propriétés image disponibles. + +##### Référence d'image ou URL d'image + +Vous pouvez travailler avec des références d'images (variable, champ ou expression image) ou des URLs d'images (texte contenant l'adresse locale ou réseau de l'image). + +Deux ensembles d'attributs vous permettent de définir si vous voulez fixer ou lire une référence ou un URL d'image : + +* wk image, wk background image, wk list style image : pour lire ou fixer des références d'images. +Lorsque vous lisez une image à l'aide d'un de ces attributs, vous recevez une image 4D quelle que soit la manière dont l'image a été initialement définie. +* wk image url, wk background image url, wk list style image url : pour lire ou fixer des URLs d'images. +Lorsque vous lisez une image à l'aide d'un de ces attributs, vous recevez un texte. Si l'image a été définie via une référence (par exemple une variable image), vous recevez un URI local suivi de l'image encodée en Base64. + +**Exemple :** + +```4d + $range:=WP Lire selection(WPArea) //lire l'image sélectionnée par l'utilisateur + $range:=WP Plage images($range) //creer une plage + $url:="http://doc.4d.com/image/logo/poweredby4D_web.png" + + WP FIXER ATTRIBUTS($range;wk image;$url) //définir une image via un URL + + //lire l'image + C_IMAGE(vPictureGet) + WP LIRE ATTRIBUTS($range;wk image;vPictureGet) //vPictureGet contient une image + C_TEXTE(vPictureURLGet) + WP LIRE ATTRIBUTS($range;wk image url;vPictureURLGet) //vPictureURLGet=$url +``` + +#### Récupérer des images + +Les commandes ci-dessous peuvent être utilisées pour récupérer des images : + +* [WP Plage images](../commands/wp-plage-images) \- s'applique uniquement aux images en ligne +* [WP Plage selection](../commands/wp-plage-selection) \- s'applique uniquement aux images sélectionnées par l'utilisateur + +#### Supprimer des images + +Vous pouvez supprimer des images en ligne et ancrées à l'aide de : + +* *Actions souris / clavier* +* la commande [WP SUPPRIMER IMAGE](../commands/wp-supprimer-image) + +#### Actions souris / clavier + +Les images peuvent être manipulées via la souris ou le clavier. Les actions disponibles incluent : + +* **Sélectionner** + * Les images en avant-plan peuvent être sélectionnées en cliquant dessus ; + * Les images d'arrière-plan peuvent être sélectionnées avec CTRL+ clic (Windows) ou COMMAND+clic (Mac) ; + * Une seule image avec une position absolue peut être sélectionnée à la fois : la sélection multiple n'est pas possible. +* **Déplacer** + * Les images peuvent être déplacées et redimensionnées à l'aide de la souris. (Les images en ligne ne peuvent pas être déplacées en dehors du document). +* **Insérer** + * Si des images avec position absolue sont collées en mode Brouillon, elles sont affichées en ligne au début de la sélection courante au clavier. +* **Couper/Coller/Copier** + * Les images peuvent être copiées dans le presse-papiers, ou coupées/collées, lorsqu'elles sont sélectionnées. + * Coller une image avec une position absolue en mode Page, collera l'image dans la première page sélectionnée et l'ancrera à cette page, quels que soient les paramètrages d'ancrage de la page d'origine ; les images collées conserveront leurs décalages (offsets), sauf si elles sont collées dans un mode différent de celui d'origine (par exemple, si l'image est copiée en mode Page et collée en mode Inclus, les décalages sont réinitialisés à 0). +* Supprimer \- Les images peuvent être supprimées lorsqu'elles sont sélectionnées avec : + * la touche SUPPRIMER, ou + * le raccourci-clavier pour l'action Effacer \ No newline at end of file diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/WritePro/user-legacy/handling-tables.md b/i18n/fr/docusaurus-plugin-content-docs/current/WritePro/user-legacy/handling-tables.md new file mode 100644 index 00000000000000..bd8cd28cec2cea --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/current/WritePro/user-legacy/handling-tables.md @@ -0,0 +1,356 @@ +--- +id: handling-tables +title: Manipuler des tableaux +displayed_sidebar: docs +--- + +#### + +Les documents 4D Write Pro peuvent contenir des tableaux. Les tableaux 4D Write Pro sont créés et construits par programmation, mais leur contenu peut être modifié et géré par l'utilisateur. Plusieurs attributs de tableau 4D Write Pro peuvent être définis, notamment la hauteur de ligne, l'alignement, les marges, le style de texte, la couleur, ou encore les bordures. + + + +**Note :** Comme les tableaux de 4D Write Pro peuvent être remplis par programmation, ils peuvent contenir un grand nombre de colonnes et de lignes. Gardez à l'esprit que de très grands tableaux peuvent avoir un impact sur les performances, surtout s'ils sont affichés à l'écran. Voir aussi [cet article de blog](https://blog.4d.com/4d-write-pro-tables-without-limit) pour plus d'informations. + +#### Créer un tableau + +Pour créer un tableau 4D Write Pro, vous devez appeler la commande [WP Inserer tableau](../commands/wp-inserer-tableau). Vous pouvez ensuite ajouter des lignes à l'aide de la commande [WP Tableau ajouter ligne](../commands/wp-tableau-ajouter-ligne). + +**Note :** L'utilisateur peut créer un tableau par copier-coller d'une plage de cellules : + + +#### Modifier les tableaux + +Le contenu des cellules peut être ajouté par programmation à l'aide de la commande [WP Tableau ajouter ligne](../commands/wp-tableau-ajouter-ligne). + +Une fois qu'un tableau est créé, le contenu des cellulles peut également être modifié à l'exécution par l'utilisateur. Il peut cliquer dans les cellules, puis sélectionner, modifier, copier/coller ou supprimer le texte et les images comme dans tout paragraphe. Il peut naviguer parmi les cellules en appuyant sur la touche **Tabulation** (**Maj+Tabulation** pour se déplacer dans la direction inverse). + +Utiliser la touche **Retour chariot** dans une cellule crée un nouveau paragraphe dans la cellule. + +Notez que la largeur des cellules est fixe : lorsque l'utilisateur saisit du texte ou colle une image, la hauteur de la ligne est automatiquement ajustée si nécessaire et le texte passe automatiquement à la ligne : + + + +Les utilisateurs peuvent également sélectionner des colonnes, des lignes ou des cellules et appliquer divers attributs relatifs au style de texte, aux couleurs, alignements etc., via le pop up menu intégré ou une interface personnalisée. 4D Write Pro fournit plusieurs commandes permettant de sélectionner toutes les parties d'un tableau : + +* [WP Tableau lire lignes](../commands/wp-tableau-lire-lignes) pour obtenir une plage de lignes +* [WP Tableau lire colonnes](../commands/wp-tableau-lire-colonnes) pour obtenir une plage de colonnes(\*) +* [WP Tableau lire cellules](../commands/wp-tableau-lire-cellules) pour obtenir une plage de cellules + +(\*) Les colonnes n'ont pas d'équivalent en html. Dans 4D Write Pro, une plage de colonne est en réalité une plage de cellules, ce qui signifie que les colonnes ont la même priorité que les cellules (cf. ci-dessous). + +Une fois que vous avez sélectionné une plage, vous pouvez lui appliquer un attribut à l'aide de la commande [WP FIXER ATTRIBUTS](../commands/wp-fixer-attributs). A l'intérieur des cellules, les attributs sont appliqués aux paragraphes, caractères ou images, suivant leur contenu. Par exemple, vous pouvez définir la hauteur, la taille de police, la bordure, la marge intérieure etc. d'un tableau ou des cellules d'un tableau (pour plus d'informations, veuillez vous référer à la section *Attributs 4D Write Pro*). + +Lorsque des attributs différents sont appliqués à des éléments concurrents d'un tableau, l'ordre de priorité suivant est utilisé pour le rendu : + +1. Le tableau est dessiné en premier +2. Les lignes sont ensuite dessinées (écrasant les attributs du tableau) +3. Les cellules/colonnes sont ensuite dessinées (écrasant les attributs des lignes). + +##### Redimensionner les colonnes + +La largeur des colonnes du tableau peut être modifiée en faisant glisser le séparateur de colonne vers la gauche ou la droite. Le curseur change pour indiquer qu'il peut être déplacé horizontalement et une ligne verticale apparait dans la règle : + + + +Le redimensionnement des colonne génère un événement formulaire Sur après modification. + +Pour redimensionner une colonne, cliquez sur le séparateur de colonnes et glissez-le vrs la gauche ou la droite. La taille minimale d'une colonne est de 8 points. Si la colonne adjacente située à droite atteint la plus petite taille, toutes les colonnes de droite seront déplacées. Si la première colonne ou une colonne adjacente située à gauche atteint la plus petite taille, aucun redimensionnement ne peut s'effectuer dans cette direction. + + + + +Si vous appuyez sur la touche **Shift** tout en redimensionnant une colonne, la taille de la colonne adjacente de droite ne sera pas modifiée. + + + + +**Note** : La propriété Saisissable doit être activée pour que le document 4D Write Pro autorise le redimensionnement des colonnes. + +##### Fusionner et fractionner des cellules + +Avec 4D Write Pro, vous pouvez fusionner et fractionner des cellules dans un tableau. La fusion de cellules consiste à combiner deux ou plusieurs cellules de tableau adjacentes situées sur la même ligne ou colonne en une seule cellule. La division de cellules consiste à prendre des cellules déjà fusionnées et à les fusionner en plusieurs cellules adjacentes sur la même ligne ou colonne. Les cellules peuvent être fusionnées à l'aide de la commande [WP TABLE MERGE CELLS](../commands/wp-table-merge-cells) ou de l'action standard **cell/merge**, et fractionnées à l'aide de la commande [WP TABLE SPLIT CELLS](../commands/wp-table-split-cells) ou de l'action standard **cell/split**. + + + +Les cellules du tableau peuvent être fusionnées : + + + +**Exemple de fusion de cellules à l'aide du langage :** + +1. Désignez une plage de cellules à fusionner dans votre tableau. Les cellules doivent être adjacentes horizontalement, verticalement, ou les deux. +2. Appelez la commande [WP TABLE MERGE CELLS](../commands/wp-table-merge-cells) sur la plage sélectionnée. + +```4d + $cells:=WP Table get cells($table;1;1;3;1) + WP TABLE MERGE CELLS($cells) + //or + WP TABLE MERGE CELLS($table;1;1;3;1) +``` + +Les données existantes dans les cellules initiales sont concaténées dans la cellule fusionnée résultante. + +Avant + + + +Après + + +**Exemple de fractionnement de cellules à l'aide du langage :** + +1. Désignez une plage de cellules à fractionner dans votre tableau. La plage sélectionnée doit contenir des cellules déjà fusionnées. +2. Appeler la commande [WP TABLE SPLIT CELLS](../commands/wp-table-split-cells) sur la plage sélectionnée. + +```4d + $cells:=WP Table get cells($table;1;1;1;1) + WP TABLE SPLIT CELLS($cells) + //or + WP TABLE SPLIT CELLS($table;1;1;1;1) +``` + +Les données de la cellule déjà fusionnée sont toutes conservées dans la première cellule résultante (en haut à gauche) après le fractionnement, les autres cellules résultantes du fractionnement restent vides. + +Avant + + + +Après + + +**Important** : + +* Toute cellule appartenant à une ligne spéciale (lligne de données, ligne de rupture ou ligne à reporter en bas) ne peut pas être fusionnée verticalement. +* Les cellules appartenant aux lignes d'en-tête peuvent être fusionnées verticalement uniquement si elles appartiennent toutes à d'autres lignes d'en-tête (elles ne peuvent pas être fusionnées avec des lignes qui ne sont pas des en-têtes et qui suivent les lignes d'en-tête). + +**Désignation des cellules fusionnées :** + +Une cellule fusionnée peut être manipulée de la même manière qu'une cellule individuelle (couleur de fond, style de bordure, styles de paragraphe...) en utilisant l'interface de 4D Write Pro, les actions standard ou la commande [WP FIXER ATTRIBUTS](../commands/wp-fixer-attributs) . + +Toutes les commandes de tableau existantes s'appliquent aux plages ou aux éléments contenant des cellules fusionnées. Dans un tableau qui contient des cellules fusionnées, les index des cellules restent les mêmes que si aucune cellule n'avait été fusionnée. + +Exemple : + +```4d + $cell1:=WP Table get cells($table;1;1;1;1) + $cell4:=WP Table get cells($table;4;1;1;1) + WP SET ATTRIBUTES($cell1;wk background color;"yellow") + WP SET ATTRIBUTES($cell4;wk background color;"pink") +``` + +Avant + + +Après + + +Dans cet exemple, vous pouvez également passer $cell2 ou $cell3 au lieu de $cell1, tel que : + +```4d + $cell2:=WP Table get cells($table;2;1;1;1) +``` + +```4d + $cell3:=WP Table get cells($table;3;1;1;1) +``` + +et le résultat sera le même qu'en utilisant $cell1 car $cell1, $cell2 et $cell3 font tous référence à la même cellule après la fusion, et toute modification appliquée à $cell1, $cell2 ou $cell3 est en fait appliquée à la nouvelle cellule fusionnée. + +Toutefois, si un nombre x de lignes entières ou de colonnes entières sont fusionnées, les index des lignes ou des colonnes suivantes sont décrémentés de x. + +#### Pagination des tableaux + +Lorsqu'ils sont affichés en mode Page ou en mode Brouillon (ou dans le contexte de l'impression de document), les tableaux 4D Write Pro peuvent être coupés : + +* automatiquement, si la hauteur du tableau est supérieure à la hauteur de page/colonne disponible, +* en fonction des sauts de pages/sauts de colonnes définis par programmation ou par l'utilisateur. + +Les coupures de tableaux peuvent s'effectuer entre les lignes (les paragraphes à l'intérieur des lignes ne sont jamais coupés). + +Les coupures de tableaux peuvent s'effectuer entre les lignes et les coupures de rangées sont également possibles. La pagination de la table est mise à jour dynamiquement si l'orientation ou le numéro de colonne sont modifiés. + +**Notes :** + +* Vous pouvez désactiver les sauts de tableaux automatiques en utilisant les attributs wk page break inside row / wk page break inside table (voir Attributs 4D Write Pro) ou les actions standard table/avoidPageBreakInside et row/avoidPageBreakInside (voir Utilisation des actions standard 4D Write Pro). +* Lorsqu'une ligne de tableau et un paragraphe ont des options de saut de page différentes, les options appliquées à la ligne sont prioritaires. Par exemple, lorsqu'un paragraphe autorise les sauts de page, mais que sa ligne mère ne les autorise pas, la ligne ne sera pas divisée. + +La pagination des tableaux peut également être contrôlée par programmation ou par l'utilisateur. Les actions disponibles incluent : + +* l'insertion d'un saut de page dans un tableau : + * commande [WP INSERER RUPTURE](../commands/wp-inserer-rupture) + * action standard *insertPageBreak* + * option **Insérer saut de page** du menu contextuel par défaut +* l'insertion d'un saut de colonne dans un tableau : + * commande [WP INSERER RUPTURE](../commands/wp-inserer-rupture) + * action standard *insertColumnBreak* + * option **Insérer saut de colonne** du menu contextuel par défaut + +Lorsqu'un saut de page ou de colonne est inséré via une action standard ou le menu contextuel, il est ajouté avant le contenu sélectionné : la première ligne de la sélection est déplacée au début de la page ou de la colonne suivante. Par exemple : + + \===>  + +**Notes :** + +* Seuls les tableaux situés dans le corps d'un document peuvent être rompus. Les ruptures insérées dans les tableaux, dans les en-têtes et les pieds, sont ignorées. +* Les tableaux ne peuvent pas être séparés dans des sections différentes. Insérer un saut de section dans un tableau déplacera la totalité du tableau dans la nouvelle section. +* Les saut de page à l'intérieur des lignes ne sont pas autorisés lorsque le *Carry-over rows (Lignes à reporter en bas)* est activé. + +#### Répétition des en-têtes + +4D Write Pro vous permet de définir jusqu'à cinq lignes d'en-tête par tableau. Les lignes d'en-tête sélectionnées seront répétées sur chaque colonne ou sur chaque page lorsqu'un saut de colonne ou un saut de page se produit. + + + +Les en-têtes de tableau sont la ou les premières lignes du tableau. Pour définir les lignes d'en-tête, vous pouvez : + +* utiliser l'action standard *headerRowCount* (voir *Utiliser les actions standard 4D Write Pro*), ou +* utiliser l'action [WP FIXER ATTRIBUTS](../commands/wp-fixer-attributs) avec wk header row count (sur un tableau, voir *Tableaux*), ou wk header (sur une ligne, voir *Lignes et colonnes*). + +Si vous désignez plus de cinq lignes comme en-tête (ou si cela résulte d'une insertion de lignes dans un en-tête existant), 4D Write Pro utilise uniquement les cinq premières lignes comme en-tête. Si vous supprimez la ou les lignes définies dans l'en-tête, le nombre de lignes d'en-tête est réduit. + +#### Datasource de tableau + +Vous pouvez assigner un objet formule comme source de données pour un tableau et accéder aux valeurs résultantes à travers le tableau en utilisant des *Expressions avec This* (voir ci-dessous). La formule de la source de données est évaluée par 4D Write Pro lors du calcul des formules (par exemple à l'ouverture du document, lors de l'appel de la commande [WP CALCULER FORMULES](../commands/wp-calculer-formules), etc.). Cette fonctionnalité bénéficie des contextes de données (voir [WP FIXER CONTEXTE DONNEES](../commands/wp-fixer-contexte-donnees)). + +Pour affecter une source de données à un tableau, utilisez la commande [WP FIXER ATTRIBUTS](../commands/wp-fixer-attributs) avec wk datasource et un objet [formule 4D](https://developer.4d.com/docs/fr/API/FunctionClass/) comme valeur. Par exemple, pour remplir un tableau avec une ligne pour chaque personne vivant en France : + +```4d + $formula:=Formula(ds.people.query("country = :1";"France")) + WP SET ATTRIBUTES($table;wk datasource;$formula) +``` + +* Si l'objet formule de la source de données renvoie une collection ou une sélection d'entités (non vide), le tableau est automatiquement rempli lorsque la formule est calculée : il contient au moins autant de lignes qu'il y a d'éléments dans la collection ou d'entités dans la sélection d'entités. La première ligne du tableau, appelée ligne de données, est utilisée comme ligne modèle (à l'exclusion de la ou des lignes d'en-tête et de la ou des lignes de rupture éventuelles). +* Dans la ligne de données (et la ou les lignes de rupture), vous pouvez insérer des expressions qui utilisent des mots-clés spéciaux tels que This.item.lastname. Les expressions sont remplacées au cours du traitement par les données de la collection ou de la sélection d'entités. La ligne de données sera dupliquée de manière à ce que le nombre de lignes d'éléments soit égal au nombre d'éléments de la collection ou de la sélection d'entités après le traitement des formules. +* Si la formule de la source de données ne renvoie pas de collection ou de sélection d'entités, ou si elle retourne une collection/sélection d'entités vide, les lignes du tableau ne sont pas créées automatiquement et toutes les lignes sont traitées comme des lignes normales. Vous pouvez définir une ligne de remplacement à afficher en cas de source de données vide. + +Pour supprimer une source de données d'un tableau, utilisez la commande [WP REINITIALISER ATTRIBUTS](../commands/wp-reinitialiser-attributs). La valeur de l'attribut de la source de données sera alors *null* : + +```4d + WP RESET ATTRIBUTES($table;wk datasource) +``` + +##### Créer un tableau avec une datasource + +Un tableau fondé sur une datasource peut être composé des lignes suivantes: + +| **icon** | **Lignes** | **Number** | **Mandatory** | **Conditions** | **Description** | +| ------------------------------------------------------------- | ----------------------- | ---------- | ------------- | -------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 
| Lignes d'en-tête | jusqu'à 5 | \- | \- | En-tête de tableau standard, voir *Répétition des en-têtes* | +| 
| Ligne de données | 1 | Oui | La formule de datasource doit retourner des éléments itérables | Si le tableau n'a pas de lignes d'en-tête et/ou ligne(s) de rupture, la ligne de données est la première ligne du tableau - sinon, c'est la première ligne après l'en-tête ou la (les) ligne(s) de rupture. Elle est généralement remplie d'expressions utilisant **This** (e.g. This.item.value) qui donnent accès aux données traitées lorsque le document est en mode *Display values* et que la ligne est dupliquée.. | +| 
| Lignes de rupture | jusqu'à 5 | \- | La formule de datasource doit retourner des éléments itérables | La (les) ligne(s) apparaissant avant ou après la ligne de données. Voir *Break rows (Lignes de rupture)* | +| 
| Ligne à reporter en bas | 1 | \- | La formule de datasource doit retourner des éléments itérables | La première ligne suivant la ligne de données ou la (les) ligne(s) de rupture. voir *Carry-over rows (Lignes à reporter en bas)* | +| 
| ligne de remplacement | 1 | \- | La source de données doit être définie | La ligne de remplacement doit être affichée à la place de la ligne de données et des lignes de rupture (le cas échéant) lorsque la source de données est vide et que l'attribut "Show placeholder row" est défini sur le tableau via l'action standard *emptyDatasource* ou la constante *wk empty datasource*. La ligne de remplacement précède immédiatement les autres lignes. | +| | Autres lignes | illimité | \- | \- | Lignes standard (non dupliquées) | | + +Exemple (*Mode d'affichage des références*): + + + +Lorsque les formules sont calculées, la ligne de données est automatiquement dupliquée si nécessaire pour correspondre à toutes les *entities* ou éléments de collection retournées par la formule du datasource : + + + +Dans tous les cas, l'instruction suivante retourne le véritable nombre de lignes : + +```4d + WP GET ATTRIBUTES($table;wk row count;$vcount) //31 pour l'exemple ci-dessus +``` + +##### Carry-over rows (Lignes à reporter en bas) + +Les tableaux basés sur des sources de données prennent en charge les **bottom carry-over rows (*lignes à reporter en bas*)** qui s'affichent automatiquement au bas de chaque page/colonne lorsque le tableau est réparti sur plusieurs pages/colonnes. + +Les carry-over rows peuvent afficher des informations supplémentaires basées sur les éléments précédemment affichés/imprimés, grâce à l'expression **This.previousItems** (voir *Expressions avec This*). Cette fonctionnalité vous permet, par exemple, d'ajouter des lignes de sous-total. + + + +Les carry-over rows sont affichées : + +* lorsqu'un tableau de source de données ne tient pas dans une seule page (ou colonne) +* au bas du tableau +* sur la première page (ou première colonne) et toutes les autres sauf la dernière. + +**Important:** Les carry-over rows ne sont disponibles que sur les tableaux remplis par une formule de source de données renvoyant une collection ou une entity selection non vide, et en mode d'affichage des valeurs. Dans tous les autres cas ou lorsque la formule de la source de données n'a pas été calculée, une ligne à reporter en bas est affichée comme une ligne normale. + +Pour créer des carry-over rows : + +1. Dans le template de tableau, ajoutez une ligne juste après la ligne de données ou la (les) ligne(s) de rupture et insérez-y les formules nécessaires, en utilisant par exemple **This.previousItems**. +2. Activer la fonctionnalité carry-over row pour votre document. Vous pouvez: +\- Utiliser l'action standard *bottomCarryOverRow* (voir *Utiliser les actions standard 4D Write Pro*), ou +\- Utiliser la commande [WP FIXER ATTRIBUTS](../commands/wp-fixer-attributs) avec le sélecteur d'attribut wk bottom carry over row *Tableaux*. + +**Remarque:** Les sauts de page à l'intérieur des lignes ne sont pas autorisés lorsque la fonctionnalité carry-over row est activée (voir *Pagination des tableaux*). Les options correspondantes, si elles sont définies, sont ignorées. + +##### Break rows (Lignes de rupture) + +Les tableaux basés sur des sources de données acceptent une ou plusieurs **Sort Break Rows** (lignes de rupture) qui peuvent être affichées avant ou après la ligne de données. Les lignes de rupture vous permettent de diviser visuellement vos éléments de source de données préalablement triés en différentes parties dans votre tableau selon la valeur d'une formule calculée. + + + +Chaque fois que la valeur de la formule change, une nouvelle ligne de rupture est insérée. Par conséquent, pour que votre tableau soit rendu correctement, l'entity selection (ou la collection) utilisée comme source de données du tableau **doit être triée en conséquence**. Par exemple, si on souhaite obtenir des ruptures par pays et par ville, la source de données doit être triée comme suit : *ds.people.all().orderBy("country asc, city asc")* + +La valeur de rupture est définie par l'attribut *wk break formula.* La valeur est généralement une formule basée sur une propriété d'élément comme "This.item.name", autrement la valeur calculée risque de ne jamais changer, ce qui rend la formule de rupture inutile. L'attribut *wk break formula* est ignoré si le tableau n'a pas de source de données ou si la ligne est un en-tête. Une ligne de rupture doit être adjacente à la ligne de données (avant ou après) ou à une autre ligne de rupture, sinon elle est ignorée. + +```4d + WP SET ATTRIBUTES($row_2;wk break formula;Formula(This.item.country)) +``` + +Grâce à l'expression **This.breakItems**, on peut par exemple afficher la moyenne totale des lignes de données à l'intérieur d'une ligne de rupture. breakItems est un sous-ensemble évalué de la source de données de la table, soit une entity selection si la source de données du tableau est une entity selection, soit une collection si la source de données est une collection. Vous pouvez donc taper à l'intérieur d'une ligne de rupture : *This.breakItems.sum("salary")* + +Pour créer des lignes de rupture : + +1. Ordonnez la source de données avec les niveaux correspondant aux ruptures que vous souhaitez afficher, par exemple, *ds.People.all().orderBy("continent asc, country asc, city asc")* +2. Tracer la ou les lignes de rupture dans le modèle de tableau. Si les ruptures sont situées après la ligne de données, elles doivent suivre **l'ordre de tri opposé** à celui de la source de données, et si elles sont situées avant la ligne de données, elles doivent suivre **le même ordre de tri** que celui de la source de données. +3. Définir la formule de rupture de l'attribut *wk break formula* pour la ou les ligne(s) sélectionnée(s) : + +```4d + $row:=WP Table get rows($table;2;1) //sélectionner la deuxième ligne comme rupture + WP SET ATTRIBUTES($row_2;wk break formula;Formula(This.item.country)) +``` + +##### Expressions avec This + +Lorsqu'il est utilisé dans une formule à l'intérieur du tableau, le mot-clé **This** donne accès à des données différentes selon le contexte : + +| **Contexte** | **Expression** | **Type** | **Retourne** | +| --------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------- | ------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| N'importe où | This.table | Objet | Tableau courant | +| | This.row | Objet | Elément de ligne ou de tableau courant | | +| | This.rowIndex | Numérique | Indice de ligne courante, commençant par 1 | | +| Lorsqu'un datasource a été défini pour un tableau | This.table.dataSource | Objet (formula) | Datasource en tant que formula | +| | This.tableData | Collection ou Entity selection (souvent) | Evaluated table.dataSource | | +| Dans chaque ligne de données lorsqu'une source de données du tableau retourne une collection ou une entity selection. | This.item.xxx | Tout type | Correspond à chaque élément de la collection de datasource du tableau ou à l'*entity selection*, par exemple **This.item.firstName** si *l'entity* associée possède l'attribut *firstName* | +| | This.itemIndex | Numérique | Indice de l'élément courant dans la collection ou l'*entity selection*, en commençant par 0 | | +| Dans n'importe quelle ligne (à l'exception des lignes d'en-tête), lorsqu'une source de données de type table renvoie une collection ou une sélection d'entités. | This.previousItems | Collection ou Entity selection | Éléments affichés sur les pages avant carry over row (le cas échéant) ou avant la ligne de l'expression, y compris la page où est affichée la ligne contenant l'expression. Cette expression renvoie le même type de valeur que l'expression **This.tableData**. | +| Dans une ligne de rupture | This.breakItems | Collection ou Entity selection | Les éléments de la collection ou de la entity selection affichés dans les lignes entre : la ligne de rupture actuelle et la ligne de rupture précédente du même niveau (ou le début du tableau) si la ou les lignes de rupture sont affichées après la ligne de données. la rupture actuelle et la ligne de rupture suivante du même niveau (ou la fin du tableau) si la ou les lignes de rupture sont affichées avant la ligne de données. | + +Dans tout autre contexte, ces expressions retourneront *undefined*. + +**Note** : Pour plus d'informations sur l'insertion de formules, voir [WP INSERER FORMULE](../commands/wp-inserer-formule). + +##### Travailler avec un tableau basé sur une datasource + +Lorsqu'un tableau est rempli à partir d'une datasource, les lignes sont automatiquement créées lorsque les références sont calculées. Vous pouvez insérer ou supprimer des lignes, modifier le contenu des cellules, changer le style, etc : + + + +A noter cependant que si la datasource du tableau est recalculée, toutes les modifications effectuées sur les lignes calculées (sauf sur la première ligne) sont perdues. Par contre, comme la première ligne est la ligne de données, toute modification apportée à cette ligne sera propagée à toutes les lignes si la datasource du tableau est recalculée. De même pour les lignes de rupture, toutes les modifications apportées aux lignes de rupture calculées sont perdues, à l'exception des lignes de rupture modèles (qui peuvent être situées soit à la fin, soit au début du tableau). + +Par exemple : + + + +Après le recalcul des expressions : + + + +Lorsque le curseur est inséré dans une cellule d'un tableau rempli avec une datasource, une icône d'avertissement s'affiche sur le côté gauche ainsi qu'une infobulle qui affiche des informations : + + + +Lorsque les formules sont affichées comme références ou lorsque vous enregistrez le document, seule la première ligne est affichée/enregistrée comme modèle (si les formules ne sont pas gelées). + +Lorsque les formules sont gelées, le tableau devient un tableau standard et la datasource du tableau est réinitialisée. + +**Note** : L'action standard *freezeExpressions* ne recalcule pas les formules. \ No newline at end of file diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/WritePro/user-legacy/importing-4d-write-documents.md b/i18n/fr/docusaurus-plugin-content-docs/current/WritePro/user-legacy/importing-4d-write-documents.md new file mode 100644 index 00000000000000..1dcfbbd8cd46aa --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/current/WritePro/user-legacy/importing-4d-write-documents.md @@ -0,0 +1,227 @@ +--- +id: importing-4d-write-documents +title: Import de documents 4D Write +displayed_sidebar: docs +--- + +#### + +Une des principales fonctions du nouvel objet 4D Write Pro est sa capacité à importer et à convertir les documents 4D Write existants. Ce principe vous permet de migrer les applications qui s'appuient actuellement sur le plug-in 4D Write. + +**Notes de compatibilité :** + +* Seuls les documents 4D Write de dernière génération ("4D Write v7") sont pris en charge. +* Le copier-coller d'un document 4D Write vers une zone 4D Write Pro n'est pour le moment pas pris en charge. L'importation d'un document 4D Write peut être uniquement effectuée via les commandes du langage de 4D Write Pro. +* Les retours chariots contenus dans les formules ont un comportement différent dans 4D Write et 4D Write Pro. Dans 4D Write, ils sont toujours interprétés comme des sauts de paragraphe, tandis que dans 4D Write Pro, ils sont interprétés par défaut comme des sauts de ligne. Afin de maintenir les retours chariots comme des sauts de paragraphe dans les formules des documents 4D Write importés, utilisez, après la conversion : +```4d + WP FIXER ATTRIBUTS(wp;wk break paragraphs in formulas;wk true) +``` + +Pour plus d'informations, reportez-vous à *Gérer des formules*. + +#### Comment importer un document 4D Write ? + +Les objets 4D Write Pro permettent d'importer des documents 4D Write de deux manières : + +* Pour les fichiers 4D Write stockés sur disque, vous pouvez utiliser la commande [WP Importer document](../commands/wp-importer-document), +* Pour les fichiers 4D Write stockés dans des champs BLOB, vous pouvez utiliser la commande [WP Nouveau](../commands/wp-nouveau). + +Pour plus d'informations, veuillez vous reporter aux descriptions de ces commandes. + +#### Quelles propriétés 4D Write sont importées ? + +Afin de faciliter votre migration du plug-in 4D Write vers 4D Write Pro, nous voulons conserver autant de fonctions 4D Write que possible dans les objets 4D Write Pro. + +Ce paragraphe liste les propriétés du plug-in 4D Write qui sont actuellement récupérées dans une zone 4D Write Pro après un import effectué à l'aide de la commande [WP Importer document](../commands/wp-importer-document) ou [WP Nouveau](../commands/wp-nouveau). + +Notez que quelques différences de rendu pourront apparaître, qui ne seront pas nécessairement considérées comme des bogues. Par exemple, des différences peuvent être liées à la police par défaut utilisée par 4D Write Pro pour les puces, ou aux conversions des caractères soulignés. + +##### Document info + +| **4D Write plug-in** | **4D Write Pro** | +| ---------------------------- | ------------------------------------------------------------ | +| Date & heure de création | Disponible | +| Date & heure de modification | Disponible | +| Verrouillé | Non disponible (utiliser la propriété d'objet lecture seule) | +| Titre | Disponible | +| Sujet | Disponible (texte brut uniquement) | +| Auteur | Disponible | +| Société | Disponible | +| Commentaire | Disponible | + +##### Paramètres de vue + +| **4D Write plug-in** | **4D Write Pro** | +| -------------------------- | -------------------------------------------------------------------------- | +| Mode affichage | Non importé (utiliser Document/Mode d'affichage dans le menu contextuel) | +| Règles | Non importé (utiliser propriété d'objet) | +| Cadres texte | Non importé (utiliser propriété d'objet) | +| En-têtes | Non importé (utiliser propriété d'objet) | +| Pieds de page | Non importé (utiliser propriété d'objet) | +| En-tête première page | Non disponible | +| Pied de page première page | Non disponible | +| Images | Non disponible | +| Barres défil horiz | Non importé (utiliser propriété d'objet Barre de défilement horiz) | +| Barres défil vert | Non importé (utiliser propriété d'objet Barre de défilement vert) | +| Caractères invisibles | Non importé (utiliser propriété d'objet) | +| Références | Non importé (utiliser [ST FIXER OPTIONS](../../commands/st-fixer-options)) | +| Séparateur de colonne | Disponible (à partir de 4D v17) | +| Séparateur horiz | Non disponible | +| Séparateur vert | Non disponible | +| Wysiwyg | Non disponible | +| Zoom | Non importé (utiliser Document/Zoom dans le menu contextuel) | + +##### Paramètres de document + +| **4D Write plug-in** | **4D Write Pro** | +| -------------------- | ---------------------------------------------------------------------- | +| Unité | Non importé (utiliser Document/Unité de mesuredans le menu contextuel) | +| Langage | Non disponible | +| Nombre de colonnes | Disponible (à partir de 4D v17) | +| Espacement colonnes | Disponible (à partir de 4D v17) | +| Veuves & orphelins | Disponible | +| Tabu défaut | Disponible | +| Tabu début | Disponible | +| Couleur lien | Non disponible | +| Couleur lien visité | Non disponible | + +Note : Le séparateur du système (comme retourné par [LIRE FORMATAGE SYSTEME](../../commands/lire-formatage-systeme)) est utilisé comme séparateur décimal pour les tabulations décimales. Vous pouvez modifier ce paramètre à l'aide de la commande [WP FIXER ATTRIBUTS](../commands/wp-fixer-attributs). + +##### Paramètres pagination document + +| **4D Write plug-in** | **4D Write Pro** | +| ----------------------------------------------- | ---------------- | +| Largeur page | Disponible | +| Hauteur page | Disponible | +| Numéro première page | Disponible | +| Première page en-tête pied différents | Disponible | +| Pages en-têtes pieds paires impaires différents | Disponible | +| Reliure | Disponible | +| Pages opposées | Disponible | +| Mages page | Disponible | +| En-tête marge haut | Disponible | +| En-tête marge bas | Disponible | +| Pied de page marge haut | Disponible | +| Pied de page marge bas | Disponible | +| Première page marge haut | Disponible | +| Première page marge bas | Disponible | +| En-tête première page marge haut | Disponible | +| En-tête première page marge bas | Disponible | +| Pied de page première page marge haut | Disponible | +| Pied de page première page marge bas | Disponible | +| Première page droite | Disponible | + +##### Paramètre impression document + +| **4D Write plug-in** | **4D Write Pro** | +| -------------------- | ---------------- | +| Papier | Non disponible | +| Orientation | Non disponible | +| Largeur | Non disponible | +| Hauteur | Non disponible | +| Marges utilisateur | Non disponible | +| Echelle | Non disponible | +| Résolution X | Non disponible | +| Résolution Y | Non disponible | + +##### Images + +**Note de compatibilité** : + +* Les modes d'affichage des images sont automatiquement importés à partir de 4D Write Pro v19 R2, à l'aide de [WP Importer document](../commands/wp-importer-document). Vous pouvez restaurer le comportement précédent (toutes les images sont redimensionnées pour s'adapter) à l'aide de l'attribut *importDisplayMode*. +* Sous Windows, les images au format PICT Mac OS insérées dans le document 4D Write sont importées mais ne peuvent pas être restituées dans 4D Write Pro. Si vous importez un document contenant ce type d'images, il sera nécessaire de les convertir. Le format PICT n'est plus pris en charge depuis 4D v18 et ne peut plus être utilisé. + +| **4D Write plug-in** | **4D Write Pro** | +| ------------------------------- | ------------------------------------------------------------ | +| X (gauche) | (& position :absolute) (uniquement images en page) | +| Y (haut) | (& position :absolute) (uniquement images en page) | +| Largeur | Disponible | +| Hauteur | Disponible | +| Numéro de page | Disponible (à partir de 4D v16 R6) | +| Devant | Disponible (à partir de 4D v16 R6) | +| Pas première page | Disponible (à partir de 4D v16 R6) | +| Mode d'affichage (rognée, etc.) | Disponible | +| Est une expression | Disponible pour images dans le texte (à partir de 4D v16 R5) | +| Conserver la taille | Non importé (automatique dans 4D Write Pro) | + +##### Propriétés de caractères + +| **4D Write plug-in** | **4D Write Pro (span)** | +| ------------------------------------------------ | ----------------------------------- | +| Italique | Disponible | +| Gras | Disponible | +| Barré | Disponible | +| Souligné | Disponible | +| Ombré | Disponible | +| Exposant ou indice | Disponible | +| Majuscules ou petites majuscules | Disponible | +| Famille de police | Disponible | +| Taille de police | Disponible | +| Couleur texte | Disponible | +| Couleur fond du texte | Disponible | +| Couleur soulignement | Disponible | +| Couleur barré | Disponible | +| Couleur ombré | Disponible | +| Propriété utilisateur | Non disponible | +| Correction orthographique (grammaire et syntaxe) | Non importée (propriété de la zone) | +| Aspect liens | Non disponible | +| Feuille de style | Disponible (à compter de 4D v18) | + +##### Propriétés paragraphes + +| **4D Write plug-in** | **4D Write Pro** | +| ------------------------------ | ---------------- | +| Justification | Disponible | +| Interligne | Disponible | +| Puces | Disponible | +| Marge gauche | Disponible | +| Marge droite | Disponible | +| Retrait alinéa | Disponible | +| Style encadrement | Disponible | +| Couleur encadrement | Disponible | +| Couleur fond encadrement | Disponible | +| Encadrement gauche | Disponible | +| Encadrement droit | Disponible | +| Encadrement haut et inter haut | Disponible | +| Encadrement bas et inter bas | Disponible | +| Espace encadrement | Disponible | +| Feuille de style | Disponible | +| Tabulations | Disponible | + +##### Liens hypertexte + +| **4D Write plug-in** | **4D Write Pro** | +| -------------------- | --------------------------------------------- | +| Lien URL | Disponible (\*) | +| Lien méthode 4D | Disponible (\*\*) (à partir de v17 R5) | +| Lien ouvrir document | Disponible (converti en URL de fichier local) | + +* (\*) À compter de 4D v16 R4, les liens URL sont convertis en attributs modifiables. Pour plus d'informations, veuillez vous reporter au paragraphe *Gestion des liens*. +* (\*\*) Les paramètres reçus dans les méthodes appelées doivent être adaptés : + +| **Paramètres** | **4D Write plug-in** | **4D Write Pro** | +| -------------- | ------------------- | ------------------------------- | +| $1 | Entier long - Référence de la zone 4D Write | Texte - Nom de la zone 4D Write Pro | +| $2 | Texte - Étiquette du lien | Objet - Description du lien :.method - Nom de la méthode du lien devant être autorisée par la commande [FIXER METHODES AUTORISEES](../../commands/fixer-methodes-autorisees). .parameter - Valeur du paramètre utilisateur passée à la méthode (le cas échéant).range - Plage de l'étiquette du lien. Voir *Gestion des plages* | +| $3 | Entier long - Paramètre utilisateur (methodRef) | \- | + +##### Expressions 4D + +| **4D Write plug-in** | **4D Write Pro** | +| -------------------- | ------------------ | +| Expression 4D | Disponible\* | +| Date & Heure | Disponible | +| Expression HTML | Non disponible\*\* | +| Expression RTF | Non disponible | + +\*Utilisez la commande [WP FIXER ATTRIBUTS](../commands/wp-fixer-attributs) avec l'attribut wk break paragraphs in formulas pour transformer les retours chariots retournés par les formules en sauts de paragraphe dans le document importé (sauts de ligne par défaut). Voir *Gérer des formules*). + +\*\*peut être importée en tant que texte dans les balises ***##htmlBegin##*** et ***##htmlEnd##*** si vous utilisez la constante wk import html expressions as text. + +##### Données texte + +| **4D Write plug-in** | **4D Write Pro** | +| -------------------------- | ---------------- | +| Données texte principal | Disponible | +| Données texte en-tête | Disponible | +| Données texte pied de page | Disponible | \ No newline at end of file diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/WritePro/user-legacy/importing-and-exporting-in-docx-format.md b/i18n/fr/docusaurus-plugin-content-docs/current/WritePro/user-legacy/importing-and-exporting-in-docx-format.md new file mode 100644 index 00000000000000..8ce2666bbd8ba9 --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/current/WritePro/user-legacy/importing-and-exporting-in-docx-format.md @@ -0,0 +1,193 @@ +--- +id: importing-and-exporting-in-docx-format +title: Exporter au format docx +displayed_sidebar: docs +--- + +#### + +4D Write Pro peut à la fois importer et exporter des documents au format .docx. Ce format est pris en charge par les applications de traitement de texte telles que Microsoft Word. + +**Note de compatibilité :** La prise en charge des documents 4D Write Pro exportés au format .docx est uniquement certifiée pour Microsoft Word 2010 et les versions plus récentes. Les anciennes versions, notamment Microsoft Word 2007, sont susceptibles de ne pas pouvoir ouvrir les documents. + +#### Comment importer au format .docx + +Les documents au format .docx peuvent être importés dans 4D Write Pro avec la commande [WP Importer document](../commands/wp-importer-document). Pour plus d'informations, reportez-vous à la description de cette commande. + +##### Changements de comportement + +Si la majorité des paramètres .docx sont conservés, certains paramètres sont connus pour être non pris en charge ou pour se comporter différemment dans 4D Write Pro. Il s'agit des paramètres suivants : + +###### Alignement / Configuration + +| **Paramètre** | **Description** | +| ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Anchored text areas | Les zones de texte ancrées sont importées par défaut en tant que zones de texte (elles peuvent également être ignorées ou importées en tant que texte en ligne, voir l'option de la commande [WP Importer document](../commands/wp-importer-document)). Seules les zones de texte simples peuvent être importées. Les zones de texte en ligne sont importées comme étant ancrées dans le premier niveau. Les zones de texte ancrées avec du texte autour sont importées avec leurs propriétés d'habillage (exception : l'option d'habillage .docx "tight" est importée en tant qu'habillage carré). | +| Paragraph layout | Seules les mises en page de texte occidental sont prises en charge. Les styles de paragraphe distribués, thaïlandais et asiatiques ne sont pas pris en charge. | +| Page Size | Les différentes tailles de page par section ne sont pas prises en charge. Seule la taille de la page de la première section est importée. | + +###### Arrière-plan + +| **Paramètre** | **Description** | +| ------------- | ------------------ | +| Watermark | Non pris en charge | + +###### Expressions + +| **Paramètre** | **Description** | +| ----------------- | ------------------------------------------------------ | +| MS Word equations | Non pris en charge. Les données ne sont pas importées. | +| MS Word charts | Non pris en charge. Les données ne sont pas importées. | + +###### Listes + +| **Paramètre** | **Description** | +| ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Hierarchical lists | Les listes à plusieurs niveaux ne sont pas prises en charge. Elles sont converties en listes à un seul niveau, de sorte que l'apparence et/ou la numérotation des listes puissent être différentes. | + +###### Images + +| **Paramètre** | **Description** | +| -------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- | +| DrawingML shapes | Seules les images DrawingML simples (en ligne ou ancrées) sont importées. Les formes DrawingML complexes ne sont pas prises en charge. | +| VML shapes or images | Non pris en charge. VML est obsolète dans MS Word et ne doit pas être utilisé dans des documents créés avec MS Word 2010 ou une version antérieure. | +| 3D models | Non pris en charge, mais la dernière image 2D rendue par le modèle 3D peut être importée si elle est présente dans le fichier .docx. | +| SmartArt | Non pris en charge. | + +###### Références + +| **Paramètre** | **Description** | +| ------------- | ---------------------------------------- | +| Comments | Non pris en charge. Contenu non importé. | +| Footnotes | Non pris en charge. Contenu non importé. | + +###### Espacement + +| **Paramètre** | **Description** | +| ----------------------- | --------------------------------------------------------------------------------------------------------- | +| "At least" line spacing | Non pris en charge. L'espacement "at least" entre les lignes est converti en un espacement fixe (simple). | +| Fit text | Non pris en charge. Le style 4D Write Pro normal est utilisé. | + +###### Tableaux + +| **Paramètre** | **Description** | +| ------------- | -------------------------------------------------------- | +| Tables | Les tableaux contigus ne fusionnent pas automatiquement. | + +###### Texte + +| **Paramètre** | **Description** | +| ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Themes | Les thèmes de texte ne sont pas importés. Si la définiton d'une couleur ou d'une police fait référence à une couleur ou à une police dans un thème, la dernière couleur ou police calculée sera utilisée. Sinon, la couleur ou la police définie dans le thème est utilisée. | + +##### Journal d'import + +Lors de l'import au format .docx dans 4D Write Pro, un objet journal est créé et inclus dans l'objet document importé. Cet objet peut être récupéré via l'attribut personnalisé "importLog" (ou la constante wk import log) : + +```4d + $myDoc:=WP Importer document("test.docx") + Si($myDoc#Null) + var $log : Objet + $log:=$myDoc[wk import log] + Fin de si +``` + +L'objet journal d'import contient les propriétés suivantes : + +| Constante | Comment | +| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| wk import log | Objet log contenant des informations sur l'opération d'import .docx. Les propriétés sont en lecture seule et ne peuvent pas être définies :
| **Propriété** | **Type** | **Description** | |
| status | Texte | Statut de l'import : successful - le document est importé dans 4D Write Pro failed - an empty 4D Write Pro document is returned | |
| developer | Collection | Collection d'objet(s) message pour les développeurs 4D Write Pro. | |
| \[ \].type | Texte | Le type de message enregistré : info warning error | |
| \[ \].message | Texte | Message concernant l'opération d'import. | |
| user | Collection | Collection d'objet(s) message pour les utilisateurs de 4D Write Pro.. | |
| \[ \].type | Texte | Le type de message enregistré : info warning | |
| \[ \].messageShort | Texte | Court message sur l'opération d'import. | |
| \[ \].messageLong | Texte | Long message sur l'opération d'import. |
- `wk type default` : Plage sans type défini
- `wk type paragraph` : Plage de type paragraphe
- `wk type image` : Image (ancrée ou en ligne)
- `wk type image anchored` : Image ancrée
- `wk type image inline` : Image en ligne
- `wk type container` : En-tête ou pied, par exemple
- `wk type table` : Référence de tableau
- `wk type table row` : Référence de ligne de tableau
- `wk type table cell` : Référence de cellule de tableau
- `wk type table column` : Référence de colonne de tableau (uniquement pour plage colonne)
- `wk type body` : Référence de corps (body) | + +Les plages de lignes, colonnes et cellules de [tables](./handling-tables.md) disposent d’attributs privés spécifiques permettant de les définir : + +| Constante | Valeur | Commentaire | +|------------------------|-------------------|-------------| +| `wk cell count` | `cellCount` | Nombre total de cellules dans la ligne.
**Type de valeur** : Entier long *(valeur pour `wk type table row`)* | +| `wk column count` | `columnCount` | *(Disponible pour les tableaux, les documents et les sections)* Nombre de colonnes.
**Type de valeur** : Entier long
Pour un tableau : attribut en lecture seule
Pour un document ou une section : attribut en lecture/écriture. Valeur par défaut = 1 (colonne unique). Valeur maximum = 20 | +| `wk first column` | `firstColumn` | *(Attribut en lecture seule)* Numéro de la première colonne du tableau incluse dans la plage.
**Valeur** : Entier long | +| `wk first row` | `firstRow` | *(Attribut en lecture seule)* Numéro de la première ligne du tableau incluse dans la plage.
**Valeur** : Entier long | +| `wk header row count` | `headerRowCount` | *(Lecture/Écriture)* Nombre de lignes du tableau pour lesquelles l’attribut `wk header` est défini sur True.
La valeur maximale est 5. Si vous indiquez une valeur supérieure à 5, `wk header` est défini sur True pour les cinq premières lignes uniquement *(voir [Répétition des en-têtes](./handling-tables.md#repeated-headers))* | +| `wk row count` | `rowCount` | *(Attribut en lecture seule)* Nombre total de lignes.
**Valeur** : Entier long | +| `wk table` | `table` | *(Attribut en lecture seule)* Le tableau parent.
**Type de valeur** : Objet | +| `wk table ID` | `tableID` | *(Attribut en lecture seule)* ID du tableau parent.
**Valeur** : Chaîne | + + + +Plusieurs commandes vous permettent de définir les plages d’un document : + +- [WP Text range](../commands-legacy/wp-text-range.md) retourne une nouvelle plage correspondant aux limites que vous avez passées en paramètres. +- [WP Selection range](../commands-legacy/wp-selection-range) retourne une nouvelle plage correspondant à la sélection utilisateur courante. +- [WP Picture range](../commands-legacy/wp-picture-range) retourne une nouvelle plage contenant uniquement les images. +- [WP Paragraph range](../commands-legacy/wp-paragraph-range) retourne une nouvelle plage contenant uniquement les paragraphes. +- [WP Table range](../commands-legacy/wp-table-range) retourne une nouvelle plage contenant uniquement les tableaux. + +Vous pouvez obtenir des informations sur la position d’une plage dans un document (numéro de page, numéro de colonne…) à l’aide de la commande [WP Get position](../commands-legacy/wp-get-position). diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/WritePro/user-legacy/storing-4d-write-pro-documents-in-4d-object-fields.md b/i18n/fr/docusaurus-plugin-content-docs/current/WritePro/user-legacy/storing-4d-write-pro-documents-in-4d-object-fields.md new file mode 100644 index 00000000000000..e6e9052fbdaf58 --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/current/WritePro/user-legacy/storing-4d-write-pro-documents-in-4d-object-fields.md @@ -0,0 +1,175 @@ +--- +id: 4d-write-pro-documents +title: Documents 4D Write Pro +displayed_sidebar: docs +--- + +## Format de document .4wp + +Vous pouvez sauvegarder des documents 4D Write Pro sur disque et les rouvrir sans aucune perte de données grâce au format natif **.4wp**. + +Le format **.4wp** est constitué d'un dossier zip dont le nom est le titre du document, et contenant du texte HTML et des images : + +* le texte HTML combine du HTML standard et des expressions 4D (non interprétées) ainsi que des balises 4D spécifiques, +* les images sont stockées dans un dossier du même nom que le document, situé à côté du fichier HTML. + +Comme les documents .4wp sont basés sur du HTML, ils peuvent être importés et ouverts dans toute application tierce qui prend en charge le format HTML. + +Le format interne des documents 4D Write Pro est du HTML étendu propriétaire, compatible HTML5/XHTML5, mais utilisant son propre sous-ensemble d'attributs et de balises HTML/CSS. Par conséquent, seuls les documents HTML exportés par 4D Write Pro peuvent être ouverts par 4D Write Pro sans risque de perte d'informations. Importer des documents HTML qui ont été créés par une source externe peut provoquer des erreurs. + +Pour plus d'informations, vous pouvez [**télécharger la liste des attributs de 4D Write pro avec la définition associée en tant que style CSS ou balise XHTML**](https://download.4d.com/Documents/Products%5FDocumentation/LastVersions/Line%5F19/4DWP-attributes-and-xhtml.pdf) dans le 4D Write Pro XHTML. + +### Rétrocompatibilité + +Vous pouvez toujours rouvrir un document .4wp avec une version antérieure de 4D Write Pro. S'il contient des attributs qui ont été ajoutés dans des versions plus récentes, ces attributs sont simplement ignorés. Cependant, si vous enregistrez le document, les attributs sont supprimés du document et seront perdus. + +## Stocker les documents 4D Write Pro dans des champs objet 4D + +Vous pouvez stocker automatiquement vos documents 4D Write Pro dans le fichier de données de 4D. Si vous avez créé une zone 4D Write Pro dans un formulaire ainsi qu'un champ de type Objet pour stocker le contenu de la zone, le texte saisi dans la zone est automatiquement sauvegardé dans les données au moment de la validation de l'enregistrement. Vous pouvez alors utiliser la commande [CHERCHER PAR ATTRIBUT](../../commands/chercher-par-attribut) afin de sélectionner des enregistrements en fonction de la valeur de leurs attributs internes. Vous pouvez également ajouter des attributs personnalisés aux zones 4D Write Pro et les utiliser pour des recherches. + +Cette section décrit les fonctionnalités suivantes : + +* Associer un champ objet 4D à une zone 4D Write Pro dans un formulaire. +* Fixer, lire et rechercher des attributs personnalisés dans les documents 4D Write Pro, à l'aide des commandes standard [OB FIXER](../../commands/ob-fixer), [OB Lire](../../commands/ob-lire) et [CHERCHER PAR ATTRIBUT](../../commands/chercher-par-attribut). + +### Associer un champ objet 4D à une zone 4D Write Pro + +Pour associer une zone 4D Write Pro à un champ 4D de type Objet, il vous suffit de référencer le champ dans la propriété "Nom de variable" de la zone. + +### Créer le champ objet en structure + +Dans la structure de votre base de données, tout champ objet 4D peut être utilisé pour stocker des documents 4D Write Pro. Vous devez simplement définir, en fonction de vos besoins, ses propriétés standard : + +* le nom du champ, +* ses attributs, tels que "Exposer avec REST resource" et son index, +* son option de stockage. + + + +### Affecter le champ objet à la zone 4D Write Pro + +Une fois que le champ objet destiné à stocker vos documents 4D Write Pro est défini, il vous suffit de le référencer dans le formulaire contenant la zone. Vous pouvez utiliser un formulaire table ou un formulaire projet. +Dans l'éditeur de formulaires, saisissez le nom du champ, en utilisant la notation standard "\[Table\]Champ", dans la zone **Nom de la variable** de la Liste des propriétés pour la zone 4D Write Pro : + + + +Votre zone 4D Write Pro est alors associée au champ, ce qui vous donne l'assurance que son contenu sera automatiquement sauvegardé avec chaque enregistrement. A noter que si vous n'utilisez pas les boutons à action automatique de 4D, vous devrez programmer vous-même la sauvegarde de la zone, à l'aide des commandes 4D. + +### Utiliser des attributs personnalisés + +Lorsque les zones 4D Write Pro sont stockées dans des champs de type Objet, vous pouvez écrire et lire des attributs personnalisés dans les documents 4D Write Pro, comme par exemple le nom de l'auteur, la catégorie du document, ou toute information supplémentaire qui vous serait utile. Vous pouvez effectuer des recherches parmi les attributs personnalisés afin de sélectionner des enregistrements en fonction de critères spécifiques. + +Les attributs personnalisés sont exportés avec les commandes [WP EXPORTER DOCUMENT](../commands/wp-exporter-document) et [WP EXPORTER VARIABLE](../commands/wp-exporter-variable). Ils sont également exportés lorsque vous convertissez un champ objet 4D Write Pro en JSON à l'aide de la commande [JSON Stringify](../../commands/json-stringify) (en plus des attributs principaux de document de 4D Write Pro). + +Pour écrire ou lire des attributs personnalisés, vous pouvez utiliser la notation objet ou les commandes [OB Lire](../../commands/ob-lire) et [OB FIXER](../../commands/ob-fixer). + +Par exemple, dans la méthode du formulaire, vous pouvez écrire : + +```4d + Si(Evenement formulaire code=Sur validation) + [MesDocuments]Mon4DWP["monatt_Dernière modif par"]:=Utilisateur courant + [MesDocuments]Mon4DWP.monatt_Catégorie:=Memo + [MesDocuments]Mon4DWP:=[MesDocuments]Mon4DWP //enregistrer la modification + Fin de si +``` + +ou : + +```4d + Si(Evenement formulaire code=Sur validation) + OB FIXER([MesDocuments]Mon4DWP;"monatt_Dernière modif par";Utilisateur courant) + OB FIXER([MesDocuments]Mon4DWP;"monatt_Catégorie";"Memo") + Fin de si +``` + +Vous pouvez bien entendu lire les attributs personnalisés des documents : + +```4d + vAttrib:=[MesDocuments]Mon4DWP.monatt_Catégorie +``` + +ou : + +```4d + vAttrib:=OB Lire([MesDocuments]Mon4DWP;"monatt_Catégorie") +``` + +Si vous avez stocké des attributs personnalisés avec les documents 4D Write Pro dans votre fichier de données, vous pouvez effectuer des recherches sur ces attributs afin de créer des sélections d'enregistrements contenant les valeurs recherchées. Exemple : + +```4d + CHERCHER PAR ATTRIBUT([MesDocuments];[MesDocuments]Mon4DWP;"monatt_Catégorie";=;"Memo") + //sélectionne tous les enregistrements de la table MesDocuments dont l'attribut personnalisé "monatt_Catégorie" contient la valeur "Memo" + //dans le champ objet Mon4DWP (associé à une zone 4D Write Pro) +``` + +:::warning Sur les noms des attributs personnalisés + +Comme les attributs personnalisés partagent le même espace de nommage que les attributs internes des documents 4D Write Pro, nous recommandons fortement l'utilisation de préfixes lorsque vous définissez les noms de vos attributs, afin d'éviter tout conflit entre les attributs internes et personnalisés. Les noms sans préfixe sont réservés aux attributs internes de 4D Write Pro. En revanche, la définition des préfixes est libre (nous utilisons par exemple le préfixe "monatt\_" dans les exemples ci-dessus). + +::: + +**Note** : Les attributs personnalisés ne peuvent pas être gérés par les commandes [WP FIXER ATTRIBUTS](../commands/wp-fixer-attributs), [WP LIRE ATTRIBUTS](../commands/wp-lire-attributs), et [WP REINITIALISER ATTRIBUTS](../commands/wp-reinitialiser-attributs) (ils ne supportent que les attributs internes de 4D Write Pro). + + +## Ouvrir et exporter des documents + +Dans les applications 4D, les documents 4D Write Pro sont créés, importés et/ou exportés via des commandes dédiées placées dans le thème **4D Write Pro** ([WP EXPORT DOCUMENT](../commands/wp-export-document), [WP EXPORT VARIABLE](../commands/wp-export-variable), [WP Import document](../commands/wp-import-document), [WP New](../commands/wp-new)). + +Vous pouvez également [associer une zone 4D Write Pro à un champ objet](../user-legacy/defining-a-4d-write-pro-area.md#storing-4d-write-pro-documents-in-4d-object-fields) de la base. De cette manière, chaque document 4D Write Pro est automatiquement sauvegardé avec l'enregistrement et est conservé dans les données de la base. + +## Imprimer des documents 4D Write Pro + +Les documents 4D Write Pro peuvent être imprimés de deux manières : + +* en tant que parties de formulaires 4D +* en tant que documents indépendants + +### Impression de documents dans des formulaires 4D + +Vous pouvez imprimer des objets 4D Write Pro inclus dans des [formulaires 4D](../../FormEditor/forms.md) de tout type (projet, table, entrée ou sortie), à l'aide des commandes d'impression standard de 4D telles que [IMPRIMER SELECTION](../../commands/imprimer-selection) ou [IMPRIMER ENREGISTREMENT](../../commands/imprimer-enregistrement). + +L'option standard *Impression taille variable* est également prise en charge(\*) pour les zones 4D Write Pro, vous permettant de gérer les variations de taille durant l'impression. Lorsque cette option est cochée, la marge (extérieure et intérieure) et la bordure hautes ne sont appliquées qu'à la première page. La marge (extérieure et intérieure) et la bordure basses ne sont appliquées qu'à la dernière page. Les propriétés de pagination du document sont ignorées : le contrôle des veuves et des orphelins est désactivé, et les sauts de page ne sont pas appliqués (ces propriétés sont utilisées uniquement pour le rendu des pages à l'écran ou l'impression autonome du document). Lorsque l'option **Impression taille variable** est sélectionnée, seuls les objets situés au-dessus de la zone dans le formulaire sont imprimés. Pour plus d'informations sur cette option, reportez-vous à la section "*Impression taille variable*" dans le manuel Mode Développement. + +(\*) Les commandes [Imprimer objet](../../commands/imprimer-objet) et [Imprimer ligne](../../commands/imprimer-ligne) ne sont pas compatibles avec cette option. + +#### Mode d'affichage et impression + +Quel que soit le **Mode d'affichage** défini pour la zone 4D Write Pro (cf. *Configurer les propriétés d'affichage*), elle est toujours imprimée en mode **Inclus** lorsque vous utilisez une commande d'impression 4D telle que [Imprimer ligne](../../commands/imprimer-ligne). Dans ce contexte, les propriétés d'Apparence ne sont pas prises en charge pour les objets de formulaire 4D Write Pro : Mode d'affichage (toujours "Inclus"), Montrer les entêtes, Montrer les pieds de page, Montrer le cadre de page (toujours "non") et Montrer les caractères cachés (toujours "non"). + +#### Exemple + +L'exemple suivant illustre l'effet de l'option **Impression taille variable** sur une zone 4D Write Pro incluse dans le formulaire de sortie par défaut. Le code suivant est exécuté : + +```4d + TOUT SELECTIONNER([Movies]) + TRIER([Movies]Title) + IMPRIMER SELECTION([Movies]) +``` + +* Avec l'option "Impression taille variable" **non cochée**, vous obtenez le résultat suivant : + +* Avec l'option "Impression taille variable" **cochée**, vous obtenez le résultat suivant : + +*(Source des texte d'exemple : wikipedia)* + +### Impression de documents indépendants + +A partir de 4D v15 R5, 4D Write Pro inclut des fonctionnalités d'impression vous permettant d'imprimer des documents 4D Write Pro indépendants et de contrôler les options standard d'impression comme le format, l'orientation ou les numéros de page. + +#### Commandes 4D Write Pro + +Essentiellement, deux commandes gèrent les fonctions d'impression avec 4D Write Pro : **WP IMPRIMER** et **WP UTILISER PARAMETRES IMPRESSION**. + +* [WP IMPRIMER](../commands/wp-imprimer) lance une tâche d'impression pour le document 4D Write Pro ou ajoute le document dans la tâche d'impression courante. +* [WP UTILISER PARAMETRES IMPRESSION](../commands/wp-utiliser-parametres-impression) modifie les options d'impression de la page courante, sur la base des attributs du document 4D Write Pro pour la taille de page et l'orientation. + +**Note :** Sur des machines avec Windows 7 ou Windows Server 2008 R2, vérifiez que le *Platform Update for Windows 7* a bien été installé pour que les fonctionnalités d'impression soient prises en charge. + +#### Commandes 4D standard + +Les commandes 4D suivantes prennent en charge les fonctionnalités d'impression de 4D Write Pro : + +* [SET PRINT OPTION](../../commands/set-print-option) et [GET PRINT OPTION](../../commands/get-print-option) : Toutes les options sont prises en charge pour les documents 4D Write Pro imprimés avec [WP PRINT](../commands/wp-print). +Pour Option papier et Option orientation, il sera généralement préférable d'appeler [WP USE PAGE SETUP](../commands/wp-use-page-setup) de façon à facilement synchroniser ces attributs avec les options du document 4D Write Pro. L'option Option intervalle de page (15) vous permet d'imprimer de la page *x* à la page *y* uniquement. +* [PRINT SETTINGS](../../commands/print-settings : permet de fixer les paramètres d'impression pour l'imprimante courante ; si la commande [WP PRINT](../commands/wp-print) est appelée par la suite, elle utilisera les paramètres d'impression modifiés si certains ont été modifiés au moyen des dialogues de paramétrage d'impression (excepté pour les options de marges qui prennent toujours en compte les options du document 4D Write Pro). +* [OPEN PRINTING JOB](../../commands/open-printing-job) et [CLOSE PRINTING JOB](../../commands/close-printing-job): [WP PRINT](../commands/wp-print) peut être appelée entre ces commandes de façon à insérer un ou plusieurs document(s) 4D Write Pro dans une tâche d'impression. \ No newline at end of file diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/WritePro/user-legacy/stylesheets.md b/i18n/fr/docusaurus-plugin-content-docs/current/WritePro/user-legacy/stylesheets.md new file mode 100644 index 00000000000000..4ff137938f5d37 --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/current/WritePro/user-legacy/stylesheets.md @@ -0,0 +1,138 @@ +--- +id: stylesheets +title: Feuilles de style +displayed_sidebar: docs +slug: /WritePro/user/stylesheets +--- + + +Une feuille de style est un objet composé d’un ensemble de paramètres d’attributs définis pour gérer l’apparence de vos documents 4D Write Pro. Ces paramètres peuvent s’appliquer aux paragraphes et aux caractères, tels que la police à afficher, sa taille, sa couleur et son poids. Une fois la feuille de style définie, elle est sauvegardée en tant qu’objet dans le document 4D Write Pro afin d’être réutilisée facilement. Les feuilles de style vous permettent de donner à vos documents un aspect unique et distinctif, tout en gagnant du temps et au moindre effort. + +## Style par défaut + +Tous les documents 4D Write Pro ont une feuille de style de paragraphe par défaut, nommée “Normal”. De nouvelles feuilles de style (créées à l’aide de la commande [WP New style sheet](../commands-legacy/wp-new-style-sheet)) sont héritées automatiquement du style Normal. Les attributs modifiés par une feuille de style ont uniquement une incidence sur les paragraphes auxquels ils s’appliquent, le reste du document conserve les paramètres par défaut (Normal). Si une feuille de style est supprimée, les attributs qui ont été modifiés reprennent le style Normal. + +Le style Normal définit une valeur par défaut à chaque feuille de style dans un document 4D Write Pro et peut être récupéré à l’aide de la commande [WP Get style sheet](../commands-legacy/wp-get-style-sheet). La feuille de style Normal peut être modifiée (mais ne peut pas être renommée) à l’aide de la commande [WP SET ATTRIBUTES](../commands/wp-set-attributes). Si les feuilles de style créées avec la commande [WP New style sheet](../commands-legacy/wp-new-style-sheet) sont supprimées avec la commande [WP DELETE STYLE SHEET](../commands-legacy/wp-delete-style-sheet), la feuille de style Normal ne peut pas être supprimée. + +## Attributs des feuilles de style de paragraphe et de caractère + +Les feuilles de style vous permettent de définir les attributs de paragraphes entiers ou de caractères spécifiques : + +- **Paragraphe** - La majorité des attributs pouvant être modifiés s’appliquent uniquement aux paragraphes. Les feuilles de style de paragraphe incluent les paramètres de style de caractère ainsi que les attributs de formatage qui ne peuvent s’appliquer qu’au niveau des paragraphes (ex : marges, bordures, tabulations, etc.). +- **Caractère** - Les feuilles de style de caractère utilisent uniquement les attributs appropriés pour distinguer le style du texte (un ou plusieurs caractères) du style du paragraphe (ex : en-têtes, titres, texte surligné, etc.). + +À noter que les styles de paragraphe s’appliquent à l’ensemble des paragraphes. Si vous souhaitez appliquer un style uniquement à une partie spécifique du paragraphe, vous devez utiliser une feuille de style de caractère. + +## Priorité des feuilles de style + +Plusieurs feuilles de style de paragraphe et de caractère peuvent être intégrées au même document 4D Write Pro. Il est important de noter que la priorité des feuilles de style est déterminée selon l’ordre dans lequel elles s’appliquent : + +- Si vous appliquez une feuille de style de paragraphe suivie d’une feuille de style de caractère, la feuille de style de caractère sera prioritaire par rapport à la feuille de style de paragraphe. Par exemple, vous pouvez appliquer une feuille de style de paragraphe au corps de votre document et créer ensuite une feuille de caractère “gras” et l’appliquer à certains mots. La feuille de paragraphe continuera de s’appliquer au reste du texte, mais la feuille de style de caractère sera prioritaire pour les mots qui avaient été désignés. +- Si vous appliquez une feuille de style de caractère suivie d’une feuille de style de paragraphe, la feuille de style de paragraphe s’appliquera à l’ensemble du texte et tous les styles de caractères liés à la feuille de style de caractère seront supprimés. + +## Appliquer les feuilles de style + +Les feuilles de style s’appliquent à l’aide de la commande [WP SET ATTRIBUTES](../commands/wp-set-attributes) et des constantes `wk style sheet` ou `wk new line style sheet` (ou à l’aide de la notation objets). + +## Récupérer les feuilles de style + +La commande [WP Get style sheets](../commands-legacy/wp-get-style-sheets) vous permet de récupérer toutes les feuilles de style d’un document en fonction de leur type. La commande [WP Get style sheet](../commands-legacy/wp-get-style-sheet) vous permet de récupérer une feuille de style via son nom. + +## Importer et exporter des feuilles de style + +Les feuilles de style étant stockées sous forme d’objets, elles peuvent être facilement importées dans d’autres documents 4D Write Pro ou maintenues lorsqu’elles sont exportées sous plusieurs formats. + +- **Import** - Vous pouvez obtenir tous les objets de la feuille de style d’un document 4D Write Pro spécifique et les utiliser dans un nouveau document à l’aide de la commande [WP IMPORT STYLE SHEETS](../commands-legacy/wp-import-style-sheets). +- **Export** - Les commandes [WP EXPORT DOCUMENT](../commands/wp-export-document) ou [WP EXPORT VARIABLE](../commands/wp-export-variable.md) exportent vos documents avec leurs feuilles de style. + +## Attributs des feuilles de style + +Les attributs de paragraphe et de caractère ci-dessous peuvent être modifiés à l’aide des commandes [WP SET ATTRIBUTES](../commands/wp-set-attributes) et [WP RESET ATTRIBUTES](../commands/wp-reset-attributes), ou récupérés à l’aide de la commande [WP GET ATTRIBUTES](../commands/wp-get-attributes). + +:::note + +Note : Certains attributs sont liés. Ainsi, lorsque vous ajoutez l’un de ces attributs, les autres attributs liés sont également créés avec les valeurs par défaut. La valeur par défaut des attributs liés peut être différente de la valeur définie dans la feuille de style Normal. Par exemple, si vous définissez uniquement une bordure gauche de couleur rouge, les autres bordures seront noires (valeur par défaut) même si les bordures du style Normal étaient précédemment définies comme violettes. + +::: + + +| Attributs | Paragraphe | Caractère | Lié à | +|----------------------------------|-----------|-----------|-------------| +| `wk avoid widows and orphans` | X | | | +| `wk background clip` | X | | | +| `wk background color` | X | X | | +| `wk background height` | X | | `wk background width` | +| `wk background image` | X | | | +| `wk background image url` | X | | | +| `wk background origin` | X | | | +| `wk background position horizontal` | X | | `wk background position vertical` | +| `wk background position vertical` | X | | `wk background position horizontal` | +| `wk background repeat` | X | | | +| `wk background width` | X | | `wk background height` | +| `wk border color` | X | | `wk border color bottom`, `wk border color left`, `wk border color right`, `wk border color top` | +| `wk border color bottom` | X | | `wk border color`, `wk border color left`, `wk border color right`, `wk border color top` | +| `wk border color left` | X | | `wk border color`, `wk border color bottom`, `wk border color right`, `wk border color top` | +| `wk border color right` | X | | `wk border color`, `wk border color bottom`, `wk border color left`, `wk border color top` | +| `wk border color top` | X | | `wk border color`, `wk border color bottom`, `wk border color left`, `wk border color right` | +| `wk border radius` | X | | | +| `wk border style` | X | | `wk border style bottom`, `wk border style left`, `wk border style right`, `wk border style top` | +| `wk border style bottom` | X | | `wk border style`, `wk border style left`, `wk border style right`, `wk border style top` | +| `wk border style left` | X | | `wk border style`, `wk border style bottom`, `wk border style right`, `wk border style top` | +| `wk border style right` | X | | `wk border style`, `wk border style bottom`, `wk border style left`, `wk border style top` | +| `wk border style top` | X | | `wk border style`, `wk border style bottom`, `wk border style left` | +| `wk border width` | X | | `wk border width bottom`, `wk border width left`, `wk border width right`, `wk border width top` | +| `wk border width bottom` | X | | `wk border width`, `wk border width left`, `wk border width right`, `wk border width top` | +| `wk border width left` | X | | `wk border width`, `wk border width bottom`, `wk border width right`, `wk border width top` | +| `wk border width right` | X | | `wk border width`, `wk border width bottom`, `wk border width left`, `wk border width top` | +| `wk border width top` | X | | `wk border width`, `wk border width bottom`, `wk border width left`, `wk border width right` | +| `wk direction` | X | | | +| `wk font` | X | X | `wk font bold`, `wk font italic`, `wk font size` | +| `wk font bold` | X | X | `wk font`, `wk font family`, `wk font italic`, `wk font size` | +| `wk font family` | X | X | `wk font`, `wk font bold`, `wk font italic`, `wk font size` | +| `wk font italic` | X | X | `wk font`, `wk font bold`, `wk font family`, `wk font size` | +| `wk font size` | X | X | `wk font`, `wk font bold`, `wk font family`, `wk font italic` | +| `wk line height` | X | | | +| `wk list font` | X | | | +| `wk list string format LTR` | X | | | +| `wk list string format RTL` | X | | | +| `wk list style image` | X | | | +| `wk list style image height` | X | | | +| `wk list style image url` | X | | | +| `wk list style type` | X | | | +| `wk margin` | X | | `wk margin bottom`, `wk margin left`, `wk margin right`, `wk margin top` | +| `wk margin bottom` | X | | `wk margin`, `wk margin left`, `wk margin right`, `wk margin top` | +| `wk margin left` | X | | `wk margin`, `wk margin bottom`, `wk margin right`, `wk margin top` | +| `wk margin right` | X | | `wk margin`, `wk margin bottom`, `wk margin left`, `wk margin top` | +| `wk margin top` | X | | `wk margin`, `wk margin bottom`, `wk margin left`, `wk margin right` | +| `wk min height` | X | | | +| `wk min width` | X | | | +| `wk name` | X | X | | +| `wk new line style sheet` | X | | | +| `wk owner` | X | X | | +| `wk padding` | X | | `wk padding bottom`, `wk padding left`, `wk padding right`, `wk padding top` | +| `wk padding bottom` | X | | `wk padding`, `wk padding left`, `wk padding right`, `wk padding top` | +| `wk padding box` | X | | | +| `wk padding left` | X | | `wk padding`, `wk padding bottom`, `wk padding right`, `wk padding top` | +| `wk padding right` | X | | `wk padding`, `wk padding bottom`, `wk padding left`, `wk padding top` | +| `wk padding top` | X | | `wk padding`, `wk padding bottom`, `wk padding left`, `wk padding right` | +| `_o_wk page break inside` | X | | | +| `wk tab default` | X | | `wk tabs`, `wk tab stop offsets`, `wk tab stop types`, `wk tab stop leadings` | +| `wk tabs` | X | | `wk tab default`, `wk tab stop offsets`, `wk tab stop types`, `wk tab stop leadings` | +| `wk tab stop offsets` | X | | `wk tabs`, `wk tab default`, `wk tab stop types`, `wk tab stop leadings` | +| `wk tab stop types` | X | | `wk tabs`, `wk tab default`, `wk tab stop offsets`, `wk tab stop leadings` | +| `wk tab stop leadings` | X | | `wk tabs`, `wk tab default`, `wk tab stop offsets`, `wk tab stop types` | +| `wk text align` | X | | | +| `wk text color` | X | X | | +| `wk text indent` | X | | | +| `wk text linethrough color` | X | X | | +| `wk text linethrough style` | X | X | `wk text underline style` | +| `wk text shadow color` | X | X | `wk text shadow offset` | +| `wk text shadow offset` | X | X | `wk text shadow color` | +| `wk text transform` | X | X | | +| `wk text underline color` | X | X | | +| `wk text underline style` | X | X | `wk text linethrough style` | +| `wk type` | X (read only) | X (read only) | | +| `wk vertical align` | X | X | | +| `wk width` | X | | | + + diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/WritePro/user-legacy/text-boxes.md b/i18n/fr/docusaurus-plugin-content-docs/current/WritePro/user-legacy/text-boxes.md new file mode 100644 index 00000000000000..d3c69429301977 --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/current/WritePro/user-legacy/text-boxes.md @@ -0,0 +1,54 @@ +--- +id: text-boxes +title: Text boxes +displayed_sidebar: docs +slug: /WritePro/user/text-boxes +--- + + +Les zones de texte sont des zones ancrées à une page ou à une section et qui peuvent contenir du texte, des images en ligne ou des tableaux. Les zones de texte peuvent être positionnées n'importe où sur la page et répondre à des besoins spécifiques, par exemple pour insérer le nom ou le logo d'une entreprise ou une zone d'adresse. + + + +**Note :** Une zone de texte ne peut pas contenir des en-têtes, des pieds de page, des colonnes, des images ancrées ou d'autres zones de texte. + +Les zones de texte sont ajoutées avec une position absolue, devant/derrière le texte, ainsi qu'ancrées à une page ou à des parties spécifiques d'un document en mode Page : en-tête, pied de page, une section, toutes les sections ou une sous-section. Les zones de texte peuvent également être utilisées en mode intégré (ancrées à la zone de calque). + +L'ajout d'une zone de texte à un document 4D Write Pro peut être réalisé de la manière suivante : + +* en utilisant la commande **WP New text box,** +* en utilisant l'action standard insertTextBox + +Pour sélectionner une zone de texte, l'utilisateur doit cliquer dessus (**Ctrl/Cmd+clic** si la zone de texte se trouve sur la couche de fond). Une fois sélectionnée, la zone de texte peut être déplacée ou redimensionnée à l'aide de la souris ou des flèches du clavier. + +Pour supprimer une zone de texte sélectionnée, vous pouvez appuyer sur la touche **Effacer** ou **Retour arrière**, utiliser l'action standard **textBox/remove** ou exécuter la commande **WP DELETE TEXT BOX**. + +Les attributs des zones de texte sont gérés par la commande [WP FIXER ATTRIBUTS](../commands/wp-fixer-attributs) ou la commande *Actions 4D Write Pro*. Les attributs et actions suivants sont disponibles : + +| **Propriété (constante)** | **Standard action** | **Commentaires** | +| ------------------------- | ------------------------- | --------------------------------------------------------------------------------------------------------------------------- | +| wk width | textBox/width | Si elle est réglée sur "auto", la largeur est convertie en 8 cm car la largeur de la zone de texte ne peut pas être "auto". | +| wk height | textBox/height | Si la valeur est "auto", la hauteur est ajustée en fonction du contenu. | +| wk padding | textBox/padding | | +| wk border \[...\] | textBox/border\[...\] | | +| wk background \[...\] | textBox/background\[...\] | | +| wk vertical align | textBox/verticalAlign | | +| wk id | \- | ne peut pas être vide pour une zone de texte | +| wk anchor \[...\] | textBox/anchor\[...\] | | +| wk owner | \- | en lecture uniquement | +| wk protected | \- | | +| wk style sheet | \- | en lecture uniquement et toujours "" (pas de feuille de style) | + +Les zones de texte supportent l'habillage automatique du texte lorsqu'elles sont ancrées dans un document avec des options telles que à gauche, à droite, sur le plus grand côté, au-dessus et au-dessous, ou tout autour, fournies par la propriété wk anchor layout ou l'action standard **anchorLayout**. Consultez cet [article de blog](https://blog.4d.com/fr/4d-write-pro-more-display-options-for-anchored-pictures-and-text-boxes/) pour plus de détails. + + + +Les zones de texte avec habillage ancrées dans le corps de la page n'affectent pas l'en-tête ou le pied de page (la zone de texte est affichée devant l'en-tête ou le pied de page) ; au contraire, les zones de texte ancrées dans l'en-tête et le pied de page affectent le corps de la page si elles le chevauchent. + +**Note :** Si vous souhaitez ancrer une zone de texte avec habillage de texte à l'en-tête ou au pied de page, vous devez également définir l'alignement vertical de la zone de texte sur le haut. + +Les zones de texte ne sont pas affichées si : + +* le mode d'affichage est Brouillon ; +* ils sont centrés ou ancrés à des sections et l'option **Show HTML WYSIWYG** est cochée ; +* l'option "fond visible" n'est pas activée. \ No newline at end of file diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/WritePro/user-legacy/using-a-4d-write-pro-area.md b/i18n/fr/docusaurus-plugin-content-docs/current/WritePro/user-legacy/using-a-4d-write-pro-area.md new file mode 100644 index 00000000000000..61e00c833a2000 --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/current/WritePro/user-legacy/using-a-4d-write-pro-area.md @@ -0,0 +1,424 @@ +--- +id: using-a-4d-write-pro-area +title: Utiliser une zone 4D Write Pro +displayed_sidebar: docs +--- + + + +## Notions de base + +Lorsqu'un document est en [mode d'affichage **Page**](./defining-a-4d-write-pro-area.md#selecting-the-view-mode), les propriétés de document suivantes sont apparentes pour l'utilisateur : + +* les contours des pages, qui représentent les limites d'impression +* la largeur et la hauteur des pages (21x29,7 cm par défaut) +* l'orientation des pages (portrait par défaut) +* les marges (2,5 cm par défaut) + +Vous pouvez également utiliser des commandes supplémentaires telles que Document.../Taille de la page ou Document.../Orientation de la page. + +**Note :** Lorsque le mode d'affichage d'un document est **Inclus** ou **Brouillon**, les propriétés de page peuvent être définies, même si leur effet n'est pas visible. En mode Brouillon, les effets des propriétés de paragraphe suivantes sont toutefois visibles : + +* Limites des hauteurs de pages (des lignes sont dessinées) +* Colonnes +* Propriété "Eviter les sauts de pages intérieurs" +* Propriété "Contrôle des veuves et des orphelins". + +## Sauts de paragraphe + +Lorsqu'ils sont affichés en mode Page ou Brouillon (ou dans le contexte de l'impression d'un document), les paragraphes de 4D Write Pro peuvent être rompus : + +* automatiquement, si la hauteur du paragraphe est supérieure à la hauteur de page disponible, +* en fonction des sauts de paragraphe définis par programmation ou par l'utilisateur. + +Les ruptures peuvent être ajoutées par programmation ou par l'utilisateur. Les actions disponibles sont les suivantes : + +* commande [WP INSERER RUPTURE](../commands/wp-inserer-rupture) +* action standard *insertPageBreak* +* l'option **Insérer un saut de page** du menu contextuel par défaut. + +### Contrôle des sauts de page automatiques + +Vous pouvez contrôler les sauts de paragraphe automatiques à l'aide des fonctions suivantes : + +* **Contrôle des veuves et des orphelins** : Lorsque cette option est définie pour un paragraphe, 4D Write Pro n'autorise pas les veuves (dernière ligne d'un paragraphe isolée en haut d'une page) ou les orphelins (première ligne d'un paragraphe isolée en bas d'une page) dans le document. Dans le premier cas, la ligne précédente du paragraphe est ajoutée en haut de la page de sorte que deux lignes y sont affichées. Dans le second cas, la première ligne isolée est déplacée sur la page suivante. +* **Éviter le saut de page à l'intérieur** : Lorsque cette option est définie pour un paragraphe, 4D Write Pro empêche ce paragraphe d'être divisé en parties sur deux pages ou plus. +* **Paragraphe solidaire :** Lorsque cette option est définie pour un paragraphe, ce paragraphe ne peut pas être séparé de celui qui le suit par un saut automatique. Voir wk keep with next et l'[action standard](./defining-a-4d-write-pro-area.md#standard-actions) correspondante *keepWithNext*. + +Ces options peuvent être définies à l'aide du menu contextuel, ou des [attributs](../commands-legacy/4d-write-pro-attributes.md) (`wk avoid widows and orphans`, `wk page break inside paragraph`, ou des [actions standard](./defining-a-4d-write-pro-area.md#standard-actions) *widowAndOrphanControlEnabled* et *avoidPageBreakInsidev*). + +## Fond + +L'arrière-plan (le fond) des documents et des éléments de documents de 4D Write Pro (tableaux, paragraphes, sections, en-têtes/pieds de pages, etc.) peut être défini à l'aide des attributs suivants : + +* couleurs +* bordures +* images +* positionnement horizontal, vertical et origine +* rectangle d'application +* répétition + +Ces [attributs](../commands-legacy/4d-write-pro-attributes.md) peuvent être définis par programmation pour le fond des éléments individuels dans la page et/ou de l'ensemble du document via la commande [WP FIXER ATTRIBUTS](../commands/wp-fixer-attributs) ou les [actions standard](./defining-a-4d-write-pro-area.md#standard-actions). + +Les utilisateurs peuvent modifier les attributs d'arrière-plan à l'aide du menu contextuel de la zone : + +  + +Pour un exemple d'ajout d'image d'arrière-plan en taille réelle, [téléchargez la base *How Do I* (HDI) dédiée](http://download.4d.com/Demos/4D%5Fv16%5FR5/HDI%5F4DWP%5FBackImagePaperBox.zip). + +## En-têtes, pieds de pages et sections + +Les documents 4D Write Pro peuvent contenir des en-têtes et des pieds de page. Les en-têtes et les pieds de page sont liés aux sections. + +Une section est une partie d'un document qui est définie par un intervalle de pages, et qui peut comporter des attributs de pagination et communs qui lui sont propres. Un document peut contenir de une à *N* sections, *N* étant le nombre total de pages. Chaque page ne peut appartenir qu'à une seule section, à l'exception des pages contenant des sauts de section continus (voir ci-dessous). + +Les documents 4D Write Pro peuvent contenir : + +- une ou plusieurs sections (une section par défaut) +- pour chaque section, jusqu'à trois sous-sections : + - sous-section première page + - sous-section page(s) gauche(s) + - sous-section page(s) droite(s) + +Vous pouvez définir un ensemble d'en-têtes et de pieds de page pour chaque section. + +### Définir une section + +Une section est un sous-ensemble de pages contiguës d'un document 4D Write Pro. Un document peut contenir une ou plusieurs sections, chaque section pouvant elle-même contenir un nombre variable de pages, depuis une page unique jusqu'au nombre total de pages du document. Une section peut contenir une seule colonne ou jusqu'à 20 colonnes par page. + +Par défaut, un document contient une seule section, nommée **Section 1**. Le menu contextuel de 4D Write Pro affiche ce numéro de section dans toutes les pages du document : + + + +Vous créez une nouvelle section en ajoutant un saut de section dans le texte : + + + +Lorsqu'un ou plusieurs sauts de section ont été ajoutés, le menu contextuel affiche un numéro incrémenté pour chaque section. Vous pouvez cependant renommer les sections : + + + +Le nom que vous saisissez est alors utilisé comme nom de section pour le document : + +  + +Notez que si vous avez défini une première page différente ou des pages droite/gauche différentes pour une section, le type de page est également affiché dans le menu (voir ci-dessous). + +### Insérer un saut de section continu + +Un saut de section continu crée une nouvelle section sur la même page. Cela vous permet de créer des pages avec des sections qui ont différents nombres de colonnes (voir *Créer une page avec des sections multi-colonnes et des section à une seule colonne*). + +Les sections créées avec des sauts de section continus sont comptées dans le document (elles possèdent des numéros de section), mais contrairement aux sections créées avec des sauts de section standard, leurs en-têtes, pieds, images ancrées, etc. sont pris en compte uniquement lorsqu'un saut de page physique s'est produit. + +**Note** : Si vous modifiez l'orientation de la page pour la nouvelle section après avoir inséré un saut de section continu, celui-ci se transforme en un saut de section standard. + +### Attributs de section + +Les sections héritent des attributs du document. Cependant, les attributs de documents communs, y compris les en-têtes et pieds de page, peuvent être modifiés séparément pour chaque section. Le menu contextuel affiche les propriétés et attributs disponibles au niveau des sections : + + + +* **Orientation de page** : permet de définir une orientation de page spécifique (portrait ou paysage) par section +* **Première page différente** : permet de définir des attributs spécifiques pour la première page de la section ; cette fonction peut être utilisée pour créer des pages de garde, par exemple. Lorsque cette option est cochée, la première page de la section est considérée elle-même comme une sous-section et peut disposer de ses propres attributs. + +* **Pages gauche et droite différentes** : permet de définir des attributs différents pour les pages gauches et droites de la section. Lorsque cette option est cochée, les pages gauches et droites de la section sont considérées comme des sous-sections et peuvent disposer de leurs propres attributs. + +* **Colonnes**: permet de définir le nombre et les propriétés des colonnes pour la section. Ces options sont détaillées ci-dessous. +* **Entête** et **Pied de page** : ces options vous permettent de définir des en-têtes et pieds de page spécifiques. Elles sont détaillées ci-dessous. +* **Marges extérieures** et **intérieures** / **Bordures** / **Fond** : ces attributs peuvent être définis séparément pour chaque section. Pour plus d'informations sur ces attributs, veuillez vous reporter à la page *Attributs 4D Write Pro*. + +### Insérer des en-têtes et des pieds de page + +Chaque section peut comporter un en-tête et un pied de page spécifiques. Les en-têtes et les pieds de page sont visibles uniquement lorsque le mode d'affichage du document est **Page**. + + A l'intérieur d'une section, vous pouvez définir jusqu'à trois en-têtes et pieds de page différents, en fonction des options activées : + +* première page, +* page(s) gauche(s), +* page(s) droite(s), + +Pour créer un en-tête ou un pied de page : + +1. Assurez-vous que le document est en mode d'affichage **Page**. +2. Double-cliquez dans la zone d'en-tête ou de pied de la section et de la page souhaitées afin de passer en édition. + * La zone d'en-tête est en haut de la page : +  + * La zone d'en-tête est en bas de la page : +  + +Vous pouvez ajouter tout contenu statique, qui sera automatiquement répété sur chaque page de la section (à l'exception de la première page, si l'option est activée). + + + +Vous pouvez ajouter du contenu dynamique tel que le numéro de page ou le nombre de pages, à l'aide de la commande [ST INSERER EXPRESSION](../../commands/st-inserer-expression) (pour plus d'informations, veuillez vous reporter au paragraphe *Insérer des expressions de page et de document*). + +**Note :** Vous pouvez également gérer les en-têtes et pieds de page par programmation à l'aide de commandes spécifiques telles que [WP Lire entete](../commands/wp-lire-entete) et [WP Lire pied](../commands/wp-lire-pied). + +Une fois qu'un en-tête ou un pied de page a été défini pour une section, vous pouvez configurer ses attributs communs à l'aide du menu contextuel : + + + +Pour plus d'informations sur les attributs **Marges extérieures**, **Marges intérieures**, **Bordures** et **Fond**, veuillez vous reporter à la section *Attributs 4D Write Pro*. + +Vous pouvez supprimer l'ensemble de la définition d'un en-tête ou d'un pied de page (contenu et attributs) en sélectionnant la commande **Retirer l'entête** ou **Retirer le pied de page** dans le menu contextuel. + +### Compatibilité + +4D Write Pro prend en charge les en-têtes et les pieds de page des documents convertis depuis le plug-in 4D Write dont la hauteur est fixe. + +Les expressions et propriétés suivantes sont également prises en charge et converties lorsqu'elles étaient présentes dans les en-têtes et pieds de page des documents du plug-in 4D Write : + +* variables numéros et nombre de pages +* première page différente +* pages gauche/droite différentes + +## Règles + +Les règles horizontales sont disponibles dans tous les modes d'affichage de 4D Write Pro et ont les caractéristiques suivantes : + +* Graduations en cm, mm, pouces ou pt en fonction de l'unité courante définie dans le document 4D Write Pro. Vous pouvez changer l'unité de mesure du document à l'aide du menu contextuel ou via l'attribut wk layout unit. +* Symbole de retrait première ligne +* Symbole de marge de paragraphe gauche +* Symbole de marge de paragraphe droite +* Tabulations affichées sur le bord inférieur de la règle +* Zones de couleur représentant les marges gauche et droite de la page + +Les règles verticales ne sont disponibles qu'en mode Page et ont les caractéristiques suivantes : + +* Graduations en cm, mm, pouces ou pt en fonction de l'unité courante définie dans le document 4D Write Pro. Vous pouvez changer l'unité de mesure du document à l'aide du menu contextuel ou via l'attribut wk layout unit. +* Zones de couleur représentant les marges haute et basse de la page + +Vous pouvez afficher ou masquer les règles via des actions standard (voir *Utiliser les actions standard 4D Write Pro*) ou en utilisant la ligne **Afficher la règle horizontale** ou **Afficher la règle verticale** dans le menu contextuel de la zone 4D Write Pro : + + + +**Note :** Une option des propriétés de la zone permet également de définir l'affichage par défaut des règles (cf. section *Configurer les propriétés d'affichage*). + +### Ajuster les marges et le retrait + +Vous pouvez modifier les marges, l'indentation (le retrait) des premières lignes et les positions des tabulations en déplaçant les symboles correspondants à l'aide de la souris : + + + +Lorsque vous survolez l'un de ces symboles avec la souris, le curseur est modifié pour indiquer qu'il peut être déplacé, et une ligne de repère verticale apparaît lorsque vous le déplacez : + + + +Lorsque plusieurs paragraphes sont sélectionnés, le déplacement d'un symbole de marge ou d'indentation est appliqué à tous les paragraphes sélectionnés. Si vous maintenez la touche **Majuscule** enfoncée pendant le déplacement, les intervalles existants entre les marges sont conservés dans les paragraphes sélectionnés. + +#### Règle horizontale + +Vous pouvez modifier les marges droites et gauches, les retraits et la position des tabulations en cliquant et en glissant les symboles correspondants sur la règle horizontale : + + + +Lorsque vous faites passer la souris sur l'un de ces symboles, le curseur change pour indiquer qu'il peut être déplacé, et une ligne verticale apparait au cours du déplacement : + + + +Lorsque plusieurs paragraphes sont sélectionnés, le fait de glisser les symboles de marge ou de retrait permet d'appliquer ces marges ou retraits à tous les paragraphes sélectionnés. En maintenant la touche Maj enfoncée tout en glissant ces symboles, vous conservez les intervalles existants entre les retraits ou les marges dans les paragraphes sélectionnés. + +#### Règle verticale + +Vous pouvez modifier les marges hautes et basses à l'aide de la règle verticale. Lorsque vous passez la souris sur la limite de la marge, le curseur change pour indiquer qu'il peut être déplacé, et une ligne horizontale apparait au cours du déplacement : + + + +Cette action peut être utilisée pour modifier l'espacement entre le haut et le bas de la page et le corps, l'en-tête et le pied d'un document. + +### Gestion des tabulations + +Vous pouvez utiliser le menu contextuel de la règle horizontale pour créer, modifier ou supprimer des tabulations : + + + +Pour créer une tabulation, cliquez sur la règle horizontale avec le bouton droit de la souris et choisissez son type depuis le menu contextuel ; un clic simple avec le bouton gauche de la souris crée automatiquement une tabulation gauche par défaut. Vous pouvez également effectuer un clic droit sur une tabulation existante pour modifier son type dans le menu contextuel. + +Le libellé **Retirer la tabulation** est disponible en cas de clic droit sur une tabulation existante. Vous pouvez également supprimer des tabulations en les faisant glisser hors de la zone de la règle horizontale. + +:::note Notes + +* Les tabulations peuvent également être définies par programmation à l'aide des commandes [WP FIXER ATTRIBUTS](../commands/wp-fixer-attributs), [WP LIRE ATTRIBUTS](../commands/wp-lire-attributs), et [WP REINITIALISER ATTRIBUTS](../commands/wp-reinitialiser-attributs) avec les sélecteurs wk tab default et wk tabs. +* Pour les tabulations décimales, 4D Write Pro considère le premier point ou la première virgule de droite comme un séparateur décimal ; ce paramètre par défaut peut être modifié avec le sélecteur wk tab decimal separator. + +::: + +#### Définir les caractères de conduite + +Vous pouvez définir les caractères qui précèdent les tabulations (caractères de conduite) en sélectionnant un caractère prédéfini ou en saisissant le caractère à utiliser. Les caractères prédéfinis sont : + +* Aucun (aucun caractère n'est affiché - *défaut*) +* .... (points) +* \--- (tirets) +* \_\_ (traits de soulignement) +* \*\*\* (astérisques) + +Les caractères de conduite apparaissent toujours avant la tabulation et suivent la direction du texte (gauche à droite ou droite à gauche). Ils peuvent être définis soit par programmation avec les commandes [WP FIXER ATTRIBUTS](../commands/wp-fixer-attributs), [WP LIRE ATTRIBUTS](../commands/wp-lire-attributs) ou [WP REINITIALISER ATTRIBUTS](../commands/wp-reinitialiser-attributs) à l'aide de `wk leading` et des sélecteurs `wk tab defaul`t ou `wk tabs`, soit via le menu contextuel de la règle horizontale (comme illustré ci-dessous) : + + + +L'option **Autre..** affiche une boîte de dialogue permettant de saisir un caractère de conduite personnalisé. + +### Règles multi-colonnes + +Lorsque deux ou plusieurs colonnes sont définies pour le document ou la section, la règle horizontale affiche une zone spécifique pour chaque colonne : + + + +**Note :** La fonctionnalité multi-colonnes n'est pas disponible en mode d'affichage **Inclus**. + +### Evénement Sur après modification + +Un [`On After Edit`](../../Events/onAfterEdit.md) (événement Sur après modification) est généré dans l'objet de formulaire 4D Write Pro à chaque déplacement d'une tabulation ou d'une marge, ainsi qu'à chaque ajout ou suppression d'une tabulation, que l'action ait été effectuée via le menu contextuel ou par glisser-déposer. + +## Colonnes + +4D Write Pro vous permet de créer des documents comportant plusieurs colonnes. Les colonnes sont chaînées depuis la colonne la plus à gauche jusqu'à la colonne la plus à droite. Autrement dit, lorsque vous saisissez du texte, le flux de texte commencera par remplir la colonne de gauche puis continuera dans la colonne à sa droite, puis ainsi de suite jusqu'à ce qu'il atteigne la fin de la page. Une fois que le bas de la page est atteint, le flux de texte est dirigé sur la page suivante. Pour que vous puissiez contrôler ce fonctionnement, 4D Write Pro permet d’insérer des sauts de colonnes. + + + +Les colonnes peuvent être définies au niveau du document (elles sont alors affichées dans l'ensemble du document) et/ou au niveau de la section (chaque section peut avoir sa propre configuration de colonne). + +**Note :** Les colonnes sont prises en charge uniquement dans les modes d'affichage **Page** et **Brouillon** (elles ne sont pas affichées en mode **Inclus),** et sont exportées en .docx à l'aide de [WP EXPORTER DOCUMENT](../commands/wp-exporter-document) mais pas aux formats HTML et MIME HTML (format wk page web complète). + +Les colonnes peuvent être définies via : + +* le sous-menu **Colonnes** du menu contextuel de la zone 4D Write Pro, +* les [attributes](../commands-legacy/4d-write-pro-attributes.md) 4D Write Pro, +* les [actions standard](./using-4d-write-pro-standard-actions.md) 4D Write Pro. + +Vous pouvez définir ou lire les propriétés et actions suivantes pour les colonnes : + +| **Propriétés** | **Description** | **Attributs de** *Document* | **Actions standard** | +| ---------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------- | ------------------------------------------------------- | +| Nombre de colonnes | Vous pouvez définir jusqu'à 20 colonnes par document/section | wk column count | *columnCount* | +| Espacement de colonne | Espacement entre les colonnes en pts, pouces ou cm. A noter que toutes les colonnes ont la même largeur. La largeur de chaque colonne est calculée automatiquement par 4D Write Pro en fonction du nombre de colonnes, de la largeur de la page et de l'espacement | wk column spacing | *columnSpacing* | +| Largeur de colonne | (attribut en lecture seule) Largeur actuelle de chaque colonne, i.e. largeur calculée | wk column width | \- | +| Style, couleur et épaisseur du séparateur de colonne | Vous pouvez ajouter un séparateur vertical (une ligne décorative) entre les colonnes. Ces options vous permettent de définir le style, la couleur et l'épaisseur de la ligne. Pour supprimer le séparateur vertical, choisissez **Aucun** comme style. | wk column rule style, wk column rule color, wk column rule width | *columnRuleStyle*, *columnRuleColor*, *columnRuleWidth* | +| Insérer saut | Insérer un saut de colonne | wk column break, voir aussi [WP INSERER RUPTURE](../commands/wp-inserer-rupture) | *insertColumnBreak* | +| Menu Colonnes | Créer un sous-menu Colonnes | \- | *columns* | + +### Créer une page avec des sections multi-colonnes et des section à une seule colonne + +*Insérer un saut de section continu* dans votre document vous permet d'avoir des sections à plusieurs colonnes et des sections à une seule colonne sur la même page. + +Par exemple : + + + +Vous pouvez insérer un saut de section continu et modifier le nombre de colonnes et le définir sur deux colonnes pour la première section : + + + + +## Signets + +4D Write Pro vous permet de créer et de manipuler des références dynamiques sur des parties de vos documents, appelées **signets**. Un signet est une référence nommée associée à une [plage](./ranges.md) spécifique dans un document 4D Write Pro. + +Les signets sont dynamiques, ce qui signifie que si l’utilisateur déplace, ajoute ou supprime du texte appartenant au signet, la plage associée sera automatiquement mise à jour et le signet continuera de référencer le même contenu dans le document. Par exemple : + +- Vous créez un signet nommé "MyBM" qui référence la plage de texte "Hello world" à la page 20 de votre document. +- Puis vous insérez 50 pages au début du document. +- Vous pouvez toujours accéder automatiquement au même contenu "Hello world", maintenant à la page 70 du document, par l’intermédiaire du signet "MyBM". + +Un document peut contenir un nombre illimité de signets. Plusieurs signets peuvent référencer la même plage, et les plages des signets peuvent être entrelacées. Cependant, chaque nom de signet doit être unique dans le document. Les signets ne sont pas importés lorsque la commande [WP INSERER DOCUMENT](../commands/wp-insert-document-body) est utilisée (les signets dans le document de destination ne peuvent pas être écrasés). + +Une fois créé, un signet est stocké dans le document. Il est enregistré avec le document, et peut être manipulé par différentes commandes. + +Les signets peuvent être utilisés pour référencer des parties d’un document modèle (*template*). Ces parties peuvent alors être automatiquement assemblées avec des données de la base afin de générer des documents finaux tels que des catalogues ou des factures. + +Plusieurs commandes vous permettent de créer, supprimer et utiliser les signets : + +* [WP NEW BOOKMARK](../commands-legacy/wp-new-bookmark.md) pour créer un signet à partir d’une plage +* [WP GET BOOKMARKS](../commands-legacy/wp-get-bookmarks.md) pour récupérer tous les signets définis dans le document, +* [WP Bookmark range](../commands-legacy/wp-bookmark-range.md) pour récupérer une plage depuis un signet existant, +* [WP DELETE BOOKMARK](../commands-legacy/wp-delete-bookmark.md) pour supprimer un signet + + +## Liens + +4D Write Pro vous permet d'associer des liens hypertexte à n'importe quel objet cible de votre document, y compris à des plages (texte, image, etc.), à des éléments (tableau, corps, pied, etc.), ou au document intégral. Par exemple, vous pouvez définir un hyperlien URL pour une plage de type image ; si le document 4D Write Pro est exporté en HTML, les utilisateurs pourront cliquer sur l'image et ouvrir la page Web qui correspond à l'adresse du lien. + +Les liens hypertexte peuvent également être activés directement depuis les documents 4D Write Pro à l'aide des raccourcis **Ctrl+clic** (Windows) ou **Commande+clic** (macOS). Dans un document 4D Write Pro non saisissable, un lien peut être activé par un simple clic. + +4D Write Pro prend en charge les types de liens suivants : + +| Type de lien | Description | +|--------------|-------------| +|`url` | Crée des liens vers des pages web ou à tout type de document, ou bien ouvre l'application associée lorsqu'il est activé (\*). L'activation d'un lien URL vers un document 4D Write Pro (`.4wp`, `.4w7`) remplace le document courant dans la zone 4D Write Pro.
(\*) tout comme la commande [OPEN URL](../../commands-legacy/open-url.md). | +| `signet` | Crée des liens vers les signets du document | +| `méthode` | L'association d'un lien à une méthode 4D exécute la méthode (sous réserve d'être enregistrée par la méthode [SET ALLOWED METHODS](../../commands/set-allowed-methods.md)).| + +Les liens hypertexte sont gérés via les commandes suivantes : + +* [WP FIXER LIEN](../commands-legacy/wp-set-link.md) pour insérer un lien à l'aide de l'objet cible +* [WP Lire liens](../commands-legacy/wp-get-links.md) pour lire la collection de tous les liens dans un objet cible. + +:::note + +Les liens sont gérés en tant qu'attributs, ils peuvent donc être définis ou lus à l'aide des commandes [WP SET ATTRIBUTES](../commands/wp-set-attributes) et [WP GET ATTRIBUTES](../commands/wp-get-attributes) associées à la constante `wk link url`. Toutefois, il est recommandé d'utiliser les commandes [WP SET LINK](../commands-legacy/wp-set-link.md) et [WP Get links](../commands-legacy/wp-get-links.md, puisqu'elles encodent/décodent automatiquement les liens hypertexte sous forme d'URL. Lorsque les liens sont lus à l'aide de la commande [WP GET ATTRIBUTES](../commands/wp-get-attributes), si l'objet cible contient plusieurs liens, la commande retourne la chaîne du premier lien. + +::: + +Par exemple, si vous souhaitez transformer le texte sélectionné par l'utilisateur en URL : + + + +Vous pouvez écrire : + +```4d + $range:=WP Lire selection(*;"WParea") + WP FIXER LIEN($range;Creer objet("url";"http://www.4d.com")) +``` + + + +Pour supprimer un lien dans un objet cible, vous pouvez écrire : + +```4d + WP REINITIALISER ATTRIBUTS($range;wk link url) +``` + +ou + +```4d + WP FIXER ATTRIBUTS($range;wk link url;"") +``` + +**Note :** Si *\$range* ne contient pas le lien complet, ce dernier est tronqué mais n'est pas entièrement supprimé. + +## Utiliser les commandes du thème Objets (Formulaires) + +Les commandes 4D suivantes du thème [Objets (Formulaires)](../../commands/theme/Objects_Forms.md) prennent en charge les objets de formulaire 4D Write Pro : + +| Commande | Commentaire | +| ------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------- | +| `OBJECT DUPLICATE` | | +| `OBJECT Get auto spellcheck` / `OBJECT SET AUTO SPELLCHECK` | | +| `OBJECT Get border style` / `OBJECT SET BORDER STYLE` | | +| `OBJECT Get context menu` / `OBJECT SET CONTEXT MENU` | | +| `OBJECT GET COORDINATES` / `OBJECT SET COORDINATES` | | +| `OBJECT Get data source` / `OBJECT SET DATA SOURCE` | | +| `OBJECT GET DRAG AND DROP OPTIONS` / `OBJECT SET DRAG AND DROP OPTIONS` | | +| `OBJECT Get enabled` / `OBJECT SET ENABLED` | | +| `OBJECT Get enterable` / `OBJECT SET ENTERABLE` | | +| `OBJECT GET EVENTS` / `OBJECT SET EVENTS` | | +| `OBJECT Get focus rectangle invisible` / `OBJECT SET FOCUS RECTANGLE INVISIBLE` | | +| `OBJECT Get font` / `OBJECT SET FONT` | Appliqué à la sélection (si présente) | +| `OBJECT Get font size` / `OBJECT SET FONT SIZE` | Appliqué à la sélection (si présente) | +| `OBJECT Get font style` / `OBJECT SET FONT STYLE` | Appliqué à la sélection (si présente) | +| `OBJECT Get horizontal alignment` / `OBJECT SET HORIZONTAL ALIGNMENT` | Appliqué à la sélection (si présente). Support de la constante `wk justify` pour les zones Write Pro | +| `OBJECT GET RESIZING OPTIONS` / `OBJECT SET RESIZING OPTIONS` | | +| `OBJECT GET RGB COLORS` / `OBJECT SET RGB COLORS` | Appliqué à la sélection (si présente) | +| `OBJECT Get type` | | +| `OBJECT Get vertical alignment` / `OBJECT SET VERTICAL ALIGNMENT` | Alignement vertical des paragraphes : n’a d’effet que si la hauteur du paragraphe dépasse celle du texte | +| `OBJECT Get visible` / `OBJECT SET VISIBLE` | | +| `OBJECT Is styled text` | Retourne vrai | +| `OBJECT MOVE` | | +| `OBJECT GET SUBFORM CONTAINER SIZE` | | +| `OBJECT Get name` | | +| `OBJECT Get pointer` | | + +Les commandes OBJET non listées ci-dessus ne sont pas applicables aux zones 4D Write Pro. + + diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/ak_400.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/ak_400.png new file mode 100644 index 00000000000000..03ddd799fa0a3a Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/ak_400.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/ak_700.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/ak_700.png new file mode 100644 index 00000000000000..67de2c6ccbeac1 Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/ak_700.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/comment.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/comment.png new file mode 100644 index 00000000000000..7bc9233ea63c89 Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/comment.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/header_title_olv.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/header_title_olv.png new file mode 100644 index 00000000000000..96e9102ce17d7b Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/header_title_olv.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/link1.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/link1.png new file mode 100644 index 00000000000000..37389843e8f050 Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/link1.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/link2.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/link2.png new file mode 100644 index 00000000000000..a49860493ce8e7 Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/link2.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2584929.fr.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2584929.fr.png new file mode 100644 index 00000000000000..2551a14acf72c9 Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2584929.fr.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2584938.fr.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2584938.fr.png new file mode 100644 index 00000000000000..dd7c1585969601 Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2584938.fr.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2646292.en.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2646292.en.png new file mode 100644 index 00000000000000..2f6dd9ff7667f9 Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2646292.en.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2646294.en.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2646294.en.png new file mode 100644 index 00000000000000..c5706f5b23244e Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2646294.en.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994900.fr.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994900.fr.png new file mode 100644 index 00000000000000..04661077e5f01e Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994900.fr.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994904.fr.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994904.fr.png new file mode 100644 index 00000000000000..04464a3690782c Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994904.fr.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994907.fr.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994907.fr.png new file mode 100644 index 00000000000000..49c9700bf8cca8 Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994907.fr.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994910.fr.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994910.fr.png new file mode 100644 index 00000000000000..e1aefecc96e852 Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994910.fr.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994913.fr.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994913.fr.png new file mode 100644 index 00000000000000..7ae88092d0b352 Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994913.fr.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994942.fr.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994942.fr.png new file mode 100644 index 00000000000000..937812b44c387e Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994942.fr.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994945.fr.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994945.fr.png new file mode 100644 index 00000000000000..d71683bb6a3fb4 Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994945.fr.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994956.fr.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994956.fr.png new file mode 100644 index 00000000000000..7f065f03e17a24 Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994956.fr.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994958.fr.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994958.fr.png new file mode 100644 index 00000000000000..c314b882326d51 Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994958.fr.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994965.fr.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994965.fr.png new file mode 100644 index 00000000000000..9f3163f3e7dac1 Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994965.fr.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2995027.fr.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2995027.fr.png new file mode 100644 index 00000000000000..74b38f03e77784 Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2995027.fr.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3033006.en.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3033006.en.png new file mode 100644 index 00000000000000..ad7e034e246705 Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3033006.en.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3033008.en.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3033008.en.png new file mode 100644 index 00000000000000..51f1aa5c128b59 Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3033008.en.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3071271.en.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3071271.en.png new file mode 100644 index 00000000000000..e7f020cc979f5e Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3071271.en.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3071271.fr.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3071271.fr.png new file mode 100644 index 00000000000000..47a27c5e58b718 Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3071271.fr.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3106228.fr.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3106228.fr.png new file mode 100644 index 00000000000000..31fa063efe1885 Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3106228.fr.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3133340.en.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3133340.en.png new file mode 100644 index 00000000000000..36424d5d26322e Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3133340.en.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3254912.fr.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3254912.fr.png new file mode 100644 index 00000000000000..adf083fca61d7c Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3254912.fr.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3307937.en.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3307937.en.png new file mode 100644 index 00000000000000..fb12b681bed355 Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3307937.en.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3307941.en.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3307941.en.png new file mode 100644 index 00000000000000..0016bc2e11049d Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3307941.en.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3308424.en.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3308424.en.png new file mode 100644 index 00000000000000..17c545dcd5e7cc Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3308424.en.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3513503.en.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3513503.en.png new file mode 100644 index 00000000000000..eddf97544e0575 Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3513503.en.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3513505.en.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3513505.en.png new file mode 100644 index 00000000000000..5e8669f5c2aace Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3513505.en.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3514201.fr.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3514201.fr.png new file mode 100644 index 00000000000000..7e39ce8a8d993a Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3514201.fr.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3541581.en.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3541581.en.png new file mode 100644 index 00000000000000..8d2321c8b19748 Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3541581.en.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3632556.fr.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3632556.fr.png new file mode 100644 index 00000000000000..23443680094556 Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3632556.fr.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3650607.fr.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3650607.fr.png new file mode 100644 index 00000000000000..5bcf2e225bdd6a Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3650607.fr.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3687425.fr.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3687425.fr.png new file mode 100644 index 00000000000000..1bf4249f234ec3 Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3687425.fr.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3690153.fr.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3690153.fr.png new file mode 100644 index 00000000000000..40f1560fe8454e Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3690153.fr.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3751849.fr.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3751849.fr.png new file mode 100644 index 00000000000000..59f3b47ad6e07e Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3751849.fr.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3751870.en.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3751870.en.png new file mode 100644 index 00000000000000..3e884da6e3c89d Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3751870.en.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3752166.en.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3752166.en.png new file mode 100644 index 00000000000000..40ec61e14638df Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3752166.en.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3752176.en.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3752176.en.png new file mode 100644 index 00000000000000..1b09211ea8ac30 Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3752176.en.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3893246.en.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3893246.en.png new file mode 100644 index 00000000000000..84c289b866e8e6 Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3893246.en.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3893248.en.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3893248.en.png new file mode 100644 index 00000000000000..c21d5b60eeb195 Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3893248.en.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101161.fr.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101161.fr.png new file mode 100644 index 00000000000000..191b37db304c7a Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101161.fr.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101210.fr.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101210.fr.png new file mode 100644 index 00000000000000..1007d4aef0838b Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101210.fr.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101242.fr.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101242.fr.png new file mode 100644 index 00000000000000..5d72f83cc2be19 Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101242.fr.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101252.fr.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101252.fr.png new file mode 100644 index 00000000000000..104bbb131d6773 Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101252.fr.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101267.fr.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101267.fr.png new file mode 100644 index 00000000000000..b3ae1038a51d7b Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101267.fr.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101278.fr.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101278.fr.png new file mode 100644 index 00000000000000..039813ae8a6ad7 Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101278.fr.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101328.en.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101328.en.png new file mode 100644 index 00000000000000..b3af7a68001554 Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101328.en.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4619596.en.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4619596.en.png new file mode 100644 index 00000000000000..0c0a886b53349f Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4619596.en.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4619694.fr.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4619694.fr.png new file mode 100644 index 00000000000000..b36404e9437f68 Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4619694.fr.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4619865.fr.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4619865.fr.png new file mode 100644 index 00000000000000..bd85b39dd6ef81 Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4619865.fr.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5562054.en.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5562054.en.png new file mode 100644 index 00000000000000..dee167c5ccf7c3 Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5562054.en.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5562058.en.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5562058.en.png new file mode 100644 index 00000000000000..f84f46638756cb Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5562058.en.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5859437.en.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5859437.en.png new file mode 100644 index 00000000000000..8a546866502013 Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5859437.en.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5907013.en.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5907013.en.png new file mode 100644 index 00000000000000..e233c502a77cb2 Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5907013.en.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5907021.en.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5907021.en.png new file mode 100644 index 00000000000000..bcbe548297f87d Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5907021.en.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5907023.en.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5907023.en.png new file mode 100644 index 00000000000000..6eba7f2baedff6 Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5907023.en.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5907026.en.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5907026.en.png new file mode 100644 index 00000000000000..d526c51578eb27 Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5907026.en.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5907030.en.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5907030.en.png new file mode 100644 index 00000000000000..964245707b6717 Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5907030.en.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6013182.en.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6013182.en.png new file mode 100644 index 00000000000000..c5b95111dd2fc2 Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6013182.en.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6014414.en.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6014414.en.png new file mode 100644 index 00000000000000..1454f02b49f34c Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6014414.en.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6014426.en.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6014426.en.png new file mode 100644 index 00000000000000..5430cc882d6f13 Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6014426.en.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6014429.en.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6014429.en.png new file mode 100644 index 00000000000000..12cb8442c5f68c Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6014429.en.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6022144.en.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6022144.en.png new file mode 100644 index 00000000000000..ab1d4670b16d55 Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6022144.en.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6131919.en.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6131919.en.png new file mode 100644 index 00000000000000..d8b2b0f013f901 Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6131919.en.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6236360.en.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6236360.en.png new file mode 100644 index 00000000000000..8a1ada936554a5 Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6236360.en.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6260026.en.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6260026.en.png new file mode 100644 index 00000000000000..25b899cdd7ca87 Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6260026.en.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6260033.en.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6260033.en.png new file mode 100644 index 00000000000000..d8271cd06a6220 Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6260033.en.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6260036.en.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6260036.en.png new file mode 100644 index 00000000000000..a93bbc2deb6580 Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6260036.en.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6421031.en.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6421031.en.png new file mode 100644 index 00000000000000..f338bd44caeb38 Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6421031.en.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6421340.en.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6421340.en.png new file mode 100644 index 00000000000000..a00a64fa003fe5 Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6421340.en.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6421342.en.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6421342.en.png new file mode 100644 index 00000000000000..e7bbdb0445e7dc Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6421342.en.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6421344.en.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6421344.en.png new file mode 100644 index 00000000000000..b1da7d4f717589 Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6421344.en.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6421356.en.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6421356.en.png new file mode 100644 index 00000000000000..e19848f65d2951 Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6421356.en.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6434575.en.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6434575.en.png new file mode 100644 index 00000000000000..b98b7a71deb16b Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6434575.en.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6434579.en.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6434579.en.png new file mode 100644 index 00000000000000..232ad5653b5bdf Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6434579.en.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6434721.en.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6434721.en.png new file mode 100644 index 00000000000000..199e62f81ef736 Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6434721.en.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6434723.en.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6434723.en.png new file mode 100644 index 00000000000000..480da0bfc5f80f Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6434723.en.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6434756.en.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6434756.en.png new file mode 100644 index 00000000000000..ffdcce4bd30899 Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6434756.en.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6441966.fr.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6441966.fr.png new file mode 100644 index 00000000000000..cc384a43d07e28 Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6441966.fr.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6856159.en.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6856159.en.png new file mode 100644 index 00000000000000..18f093b69da71c Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6856159.en.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6856163.en.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6856163.en.png new file mode 100644 index 00000000000000..0c3c6665e834d8 Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6856163.en.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict7014959.en.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict7014959.en.png new file mode 100644 index 00000000000000..a667cee2e6696a Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict7014959.en.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict7148443.en.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict7148443.en.png new file mode 100644 index 00000000000000..ab64da522a20a6 Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict7148443.en.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict7148495.en.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict7148495.en.png new file mode 100644 index 00000000000000..499af8e3737b08 Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict7148495.en.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/poweredby4D_web.png b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/poweredby4D_web.png new file mode 100644 index 00000000000000..fbb7fefffac38d Binary files /dev/null and b/i18n/fr/docusaurus-plugin-content-docs/current/assets/en/WritePro/poweredby4D_web.png differ diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-20-R10/API/SessionClass.md b/i18n/fr/docusaurus-plugin-content-docs/version-20-R10/API/SessionClass.md index c5c66b26785e60..ab161ca0f9a6a5 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-20-R10/API/SessionClass.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-20-R10/API/SessionClass.md @@ -136,7 +136,7 @@ La fonction `.createOTP()` crée u Pour plus d'informations sur les tokens OTP, veuillez consulter [cette section](../WebServer/sessions.md#session-token-otp). -Par défaut, si le paramètre *lifespan* est omis, le token est créé avec la même durée de vie que le [`.idleTimeOut`](#idletimeout) de la session. Vous pouvez définir un délai personnalisé en passant une valeur en secondes dans *lifespan* (la valeur minimale est de 10 secondes, *lifespan* est réinitialisé à 10 si une valeur inférieure est passée). Si un token expiré est utilisé pour restaurer la session d'un utilisateur web, il est ignoré. +Par défaut, si le paramètre *lifespan* est omis, le token est créé avec la même durée de vie que le [`.idleTimeOut`](#idletimeout) de la session. You can set a custom timeout by passing a value in seconds in *lifespan*. Si un token expiré est utilisé pour restaurer la session d'un utilisateur web, il est ignoré. Le token retourné peut ensuite être utilisé lors d'échanges avec des applications tierces ou des sites Web pour identifier la session de manière sécurisée. Par exemple, le token OTP de session peut être utilisé avec une application de paiement. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-20-R10/Concepts/operators.md b/i18n/fr/docusaurus-plugin-content-docs/version-20-R10/Concepts/operators.md index 82e97a3608a5d2..509c501a59b6a7 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-20-R10/Concepts/operators.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-20-R10/Concepts/operators.md @@ -90,7 +90,10 @@ Les opérateurs d'affectation composés suivants sont pris en charge : | | Time \*= Number | Number | `$t1*=5 //$t1:=$t1*5` | | | Picture \*= Number | Picture | `$p1*=5 //$p1:=$p1*5 (redimensionner $p1 de 5)` | -Ces opérateurs s'appliquent à toutes les [expressions assignables](quick-tour.md#assignable-vs-non-assignable-expressions) (à l'exception des images en tant que propriétés d'objet ou éléments de collection). +These operators apply on any [assignable expressions](quick-tour.md#assignable-vs-non-assignable-expressions) except: + +- pictures as object properties or collection elements, +- array index variables. L'opération "source `operator` value" n'est pas strictement équivalente à "source := source `operator` valeur" car l'expression désignant la source (variable, champ, propriété d'objet, élément de collection) n'est évaluée qu'une seule fois. Par exemple, dans une expression telle que `getPointer()->+=1`, la méthode `getPointer` n'est appelée qu'une seule fois. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-20-R9/API/SessionClass.md b/i18n/fr/docusaurus-plugin-content-docs/version-20-R9/API/SessionClass.md index bfc9aa1dc0893f..c33e25597bda50 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-20-R9/API/SessionClass.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-20-R9/API/SessionClass.md @@ -133,7 +133,7 @@ La fonction `.createOTP()` crée u Pour plus d'informations sur les tokens OTP, veuillez consulter [cette section](../WebServer/sessions.md#session-token-otp). -Par défaut, si le paramètre *lifespan* est omis, le token est créé avec la même durée de vie que le [`.idleTimeOut`](#idletimeout) de la session. Vous pouvez définir un délai personnalisé en passant une valeur en secondes dans *lifespan* (la valeur minimale est de 10 secondes, *lifespan* est réinitialisé à 10 si une valeur inférieure est passée). Si un token expiré est utilisé pour restaurer la session d'un utilisateur web, il est ignoré. +Par défaut, si le paramètre *lifespan* est omis, le token est créé avec la même durée de vie que le [`.idleTimeOut`](#idletimeout) de la session. You can set a custom timeout by passing a value in seconds in *lifespan*. Si un token expiré est utilisé pour restaurer la session d'un utilisateur web, il est ignoré. Le token retourné peut ensuite être utilisé lors d'échanges avec des applications tierces ou des sites Web pour identifier la session de manière sécurisée. Par exemple, le token OTP de session peut être utilisé avec une application de paiement. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-20-R9/Concepts/operators.md b/i18n/fr/docusaurus-plugin-content-docs/version-20-R9/Concepts/operators.md index 82e97a3608a5d2..509c501a59b6a7 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-20-R9/Concepts/operators.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-20-R9/Concepts/operators.md @@ -90,7 +90,10 @@ Les opérateurs d'affectation composés suivants sont pris en charge : | | Time \*= Number | Number | `$t1*=5 //$t1:=$t1*5` | | | Picture \*= Number | Picture | `$p1*=5 //$p1:=$p1*5 (redimensionner $p1 de 5)` | -Ces opérateurs s'appliquent à toutes les [expressions assignables](quick-tour.md#assignable-vs-non-assignable-expressions) (à l'exception des images en tant que propriétés d'objet ou éléments de collection). +These operators apply on any [assignable expressions](quick-tour.md#assignable-vs-non-assignable-expressions) except: + +- pictures as object properties or collection elements, +- array index variables. L'opération "source `operator` value" n'est pas strictement équivalente à "source := source `operator` valeur" car l'expression désignant la source (variable, champ, propriété d'objet, élément de collection) n'est évaluée qu'une seule fois. Par exemple, dans une expression telle que `getPointer()->+=1`, la méthode `getPointer` n'est appelée qu'une seule fois. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-20/Concepts/operators.md b/i18n/fr/docusaurus-plugin-content-docs/version-20/Concepts/operators.md index 81e21488a20873..a12e7d110dd0e5 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-20/Concepts/operators.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-20/Concepts/operators.md @@ -93,7 +93,9 @@ Les opérateurs d'affectation composés suivants sont pris en charge : | | Time *= Number | Number | `$t1*=5 //$t1:=$t1*5` | | | Picture *= Number | Picture | `$p1*=5 //$p1:=$p1*5 (redimensionner $p1 de 5)` | -Ces opérateurs s'appliquent à toutes les [expressions assignables](quick-tour.md#assignable-vs-non-assignable-expressions) (à l'exception des images en tant que propriétés d'objet ou éléments de collection). +These operators apply on any [assignable expressions](quick-tour.md#assignable-vs-non-assignable-expressions) except: +- pictures as object properties or collection elements, +- array index variables. L'opération "source `operator` value" n'est pas strictement équivalente à "source := source `operator` valeur" car l'expression désignant la source (variable, champ, propriété d'objet, élément de collection) n'est évaluée qu'une seule fois. Par exemple, dans une expression telle que `getPointer()->+=1`, la méthode `getPointer` n'est appelée qu'une seule fois. diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/API/SessionClass.md b/i18n/ja/docusaurus-plugin-content-docs/current/API/SessionClass.md index ce405ef6e802c8..c2e2ee1c8a12bc 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/API/SessionClass.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/API/SessionClass.md @@ -136,7 +136,7 @@ $isGuest:=Session.isGuest() // $isGuest は true OTP トークンについてのより詳細な情報については、[こちらの章](../WebServer/sessions.md#セッショントークンotp)を参照して下さい。 -デフォルトで、*lifespan* 引数が省略された場合、トークンはセッションの[`.idleTimeOut`](#idletimeout) と同じ有効期限を持って作成されます。 *lifespan* 引数に秒単位の値を渡すことで、カスタムのタイムアウトを設定することができます(最小値は10秒間で、それより小さい値が渡された場合には*lifespan* は10にリセットされます)。 Web ユーザーセッションを復元するために失効したトークンを使用した場合、それは無視されます。 +デフォルトで、*lifespan* 引数が省略された場合、トークンはセッションの[`.idleTimeOut`](#idletimeout) と同じ有効期限を持って作成されます。 You can set a custom timeout by passing a value in seconds in *lifespan*. Web ユーザーセッションを復元するために失効したトークンを使用した場合、それは無視されます。 返されたトークンは、サードパーティアプリケーションや他のWebサイトとのやり取りで使用することでセッションを安全に特定することができます。 例えば、セッションOTP トークンは支払いアプリケーションなどにおいて使用することができます。 diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/Admin/data-collect.md b/i18n/ja/docusaurus-plugin-content-docs/current/Admin/data-collect.md index f2994bbeb28c92..2c231599a26ca3 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/Admin/data-collect.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/Admin/data-collect.md @@ -54,7 +54,8 @@ title: データ収集 | encrypted | Boolean | データファイルが暗号化されていれば true | | encryptedConnections | Boolean | クライアント/サーバー接続が暗号化されている場合は True | | externalPHP | Boolean | クライアントが `PHP execute` を呼び出して、独自のバージョンの php を使用した場合は True。 | -| hasDataChangeTracking | Boolean | True if a "__DeletedRecords" table exists | +| hasDataChangeTracking | Boolean | "__DeletedRecords" テーブルが存在する場合にはTrue | + | headless | Boolean | アプリケーションがヘッドレスモードで実行されている場合は true | | id | Text (ハッシュ文字列) | データベースに関連付けられた一意の id (*データベース名の多項式ローリングハッシュ*) | | indexSegment.diskReadBytes | Number | インデックスファイルから読み取ったバイト数 | @@ -64,7 +65,7 @@ title: データ収集 | indexesSize | Number | インデックスのサイズ (バイト単位) | | isEngined | Boolean | アプリケーションに 4D Volume Desltop が組み込まれている場合は true | | isRosetta | Boolean | macOS の Rosetta で 4D がエミュレートされている場合は True、そうでない場合は False (エミュレートされていない、または Windows の場合)。 | -| LDAPLogin | Number | Number of calls to `LDAP LOGIN` | +| LDAPLogin | Number | `LDAP LOGIN` の呼び出し回数 | | license | Object | 製品ライセンスの名称と説明 | | maximum4DClientConnections | Number | サーバーへのクライアントの最大接続数 | | maximumNumberOfWebProcesses | Number | 最大同時Webプロセス数 | diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/Concepts/operators.md b/i18n/ja/docusaurus-plugin-content-docs/current/Concepts/operators.md index 6797c5d2ea76b5..bd6ca82039610d 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/Concepts/operators.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/Concepts/operators.md @@ -90,7 +90,10 @@ $a+=2 // $a=3 | | Time \*= Number | Number | `$t1*=5 //$t1:=$t1*5` | | | Picture \*= Number | Picture | `$p1*=5 //$p1:=$p1*5 ($p1 を 5倍にリサイズします)` | -これらの演算子は、あらゆる [代入可能な式](quick-tour.md#代入可-vs-代入不可の式) に適用できます (オブジェクトのプロパティやコレクション要素としてのピクチャーを除く)。 +These operators apply on any [assignable expressions](quick-tour.md#assignable-vs-non-assignable-expressions) except: + +- pictures as object properties or collection elements, +- array index variables. "代入先 複合代入演算子 値" と "代入先 := 代入先 演算子 値" は、厳密には等価ではありません。なぜなら、前者の場合、代入先 (変数・フィールド・オブジェクトプロパティ・コレクション要素) は一度しか評価されないからです。 たとえば、`getPointer()-+=1` のような式では、`getPointer` メソッドは一度だけ呼び出されます。 diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/Notes/updates.md b/i18n/ja/docusaurus-plugin-content-docs/current/Notes/updates.md index 13ce6fa0be80f7..7b04828f6bd56b 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/Notes/updates.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/Notes/updates.md @@ -42,11 +42,6 @@ Read [**What’s new in 4D 21**](https://blog.4d.com/en-whats-new-in-4d-21/), th - Web server: the support of deprecated `4DSYNC/` and `4DCGI/` URLs is removed. No specific processing is done on these URLs anymore. - Web user sessions are now returned by [`Process activity`](../commands/process-activity.md). -#### 動作の変更 - - - Web services (SOAP): when [scalable sessions](../WebServer/sessions.md#enabling-web-sessions) are enabled, web services now run in [**preemptive processes**](../Develop/preemptive.md) in compiled mode. Make sure your SOAP code is thread-safe. - - Web server: the support of deprecated `4DSYNC/` and `4DCGI/` URLs is removed. No specific processing is done on these URLs anymore. - - Web user sessions are now returned by [`Process activity`](../commands/process-activity.md). ## 4D 20 R10 diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/WritePro/user-legacy/defining-a-4d-write-pro-area.md b/i18n/ja/docusaurus-plugin-content-docs/current/WritePro/user-legacy/defining-a-4d-write-pro-area.md new file mode 100644 index 00000000000000..9ecfc2d3317e64 --- /dev/null +++ b/i18n/ja/docusaurus-plugin-content-docs/current/WritePro/user-legacy/defining-a-4d-write-pro-area.md @@ -0,0 +1,257 @@ +--- +id: defining-a-4d-write-pro-area +title: Defining a 4D Write Pro area +displayed_sidebar: docs +--- + + +## Drag and Drop + +ご自分の4D Write Proエリアでのドラッグ＆ドロップ機能の設定をするためには、プロパティリストの"アクション"テーマ内にて適切なオプションを選択する必要があります: + + + +4D Write Proエリアは、二つのドラッグ＆ドロップモードをサポートします: + +* **カスタムモード:** "ドラッグ可"と"ドロップ可"のオプションのみチェックされています。 +このモードでは、テキストを選択し、移動させる事ができます。On Begin Drag Overイベントのオブジェクトメソッドが呼び出され、このカスタムモードを使用してドロップ時の挙動を定義する事ができます。 +* **自動モード**: "ドラッグ可"、"ドロップ可"、そして"自動ドラッグ"と"自動ドロップ"のオプションがチェックされています。 +このモードでは、選択したテキストを移動または(**Alt/Option**キーを押しながら)コピーすることができます。On Begin Drag Overイベントはトリガーされません。 + +**注:** "自動ドラッグ"と"自動ドロップ"のオプションしか選択していなかった場合、4D Write Proエリアには何の影響もありません。 + +## View properties + +ドキュメントビュープロパティは、4D Write Pro エリアのプロパティリストで直接設定可能です。これを使用することで4D Write Pro エリアにおいて4D Wrie Pro ドキュメントがデフォルトでどのように表示されるかを指定することができます。これらのプロパティを使って、例えば 4D Write Pro ドキュメントを印刷されるとおりに表示するか、それともブラウザーで見たときと同じように表示するかを設定することができます。同一のフォーム上で、同じ 4D Write Pro ドキュメントの異なるビューを表示させることも可能です。 + +**注:** ビュー設定は[WP SET VIEW PROPERTIES](../commands/wp-set-view-properties) および [WP Get view properties](../commands/wp-get-view-properties) コマンドを使用することで動的に管理することも可能です。 + +ドキュメントビューの設定は、4D Write Pro フォームオブジェクトのプロパティリストにおいて、**アピアランス**テーマの項目で指定します: + + + +* **解像度**: 4D Write Pro エリアの画面解像度を設定します。デフォルト値は **72 dpi (Mac OS)** で、これはすべてのプラットフォームにおける 4D フォームの標準解像度です。この項目を**自動**に設定すると、Mac OS と Windows 間でドキュメントのレンダリングが異なることになります。特定の dpi 値を指定すると、両プラットフォームでのレンダリングを同じになります。 +* **ズーム**: 4D Write Pro エリアのコンテンツ表示に使用するズーム率を設定します。 +* **ビューモード**: フォームエリア内の 4D Write Pro ドキュメントの表示モードを設定します。次の値が提供されています: + * **ページ**: もっとも完全といえるビューモードで、ページの枠、余白、改ページ、ヘッダー & フッターなどを含みます。詳細については *ページビュー機能* を参照ください。 + * **下書き**: 基本のドキュメントプロパティを含む下書きモードです。 + * **埋め込み**: 埋め込みエリアに適切なビューモードです。余白や、ヘッダー & フッター、ページフレームなどは表示されません。 + このモードは Web に似た出力をするのに使用することもできます (この場合には、解像度を 96 dpi に設定のうえ、**HTML WYSIWYG を表示**オプションを有効にします)。 + + **注:** **ビューモード**プロパティは画面上のレンダリングにのみ使用されます。印刷設定については、特定のレンダリングルールが自動的に適用されます (*4D Write Pro ドキュメントの印刷* 参照)。 +* **ページ枠を表示**: ページビューモードが "ページ" に設定されている場合に、ページのフレームを表示 / 非表示にします。 +* **参照を表示**: ドキュメントに*参照* として挿入された 4Dフォーミュラ(または式)をすべて表示します(*フォーミュラの管理* 参照)。このオプションがチェックされていない場合、4D フォーミュラは全て*値* として表示されます。 +**注意:** フォーミュラ参照は 記号として表示することもできます(以下参照)。 +* **ヘッダー / フッターを表示**: ページビューモードが "ページ" に設定されている場合に、ページのヘッダー & フッターを表示 / 非表示にします。ヘッダー & フッターについての詳細は を参照ください。 +* **背景とアンカーされた要素を表示**: ページの背景画像、背景色、アンカーされた画像およびテキストボックスを表示 / 非表示にします。 +* **非表示文字を表示**: 非表示の文字を表示 / 非表示にします。 +* **HTML WYSIWYG を表示**: HTML WYSIWYG ビューを有効 / 無効にします。このビューでは、すべてのブラウザーに対応していない 4D Write Pro の属性が取り除かれます。 +* **水平ルーラーを表示**: ルーラーを表示/非表示にします(デフォルトでは表示)。4D Write Proエリアでのルーラーについてのより詳細な情報については、*ルーラーの管理* の章を参照してください。 +* **垂直** **ルーラーを表示**: ドキュメントがページモードの時の垂直ルーラーを表示 / 非表示にします。4D Write Pro エリアでのルーラーについての詳細な情報については、*ルーラーの管理* の章を参照してください。 +* **空またはサポートされていない画像を表示**: 読み込めない、あるいは計算できない画像(空の画像またはサポートされていないフォーマットの画像)に対して表示する黒い四角形を表示/非表示にします。詳細な情報については*空のピクチャー* の章を参照して下さい。 +* **フォーミュラのソースを記号として表示**: 4D式を参照として表示(上記参照)している場合、フォーミュラのソーステキストを 記号として表示します。フォーミュラを記号として表示することで、テンプレートのドキュメントをよりコンパクトに、より*wysiwyg* にすることができます。 + +****互換性に関する注記:** + +* 4D v15 R5 までのバージョンで作成された 4D Write Pro ドキュメントは、これらのプロパティはデフォルト値に設定されますが、例外として解像度のみ自動に設定されます。 +* 水平ルーラーは、4D v16 R2以降で作成されたデータベースについてはデフォルトで利用可能です。それ以前のバージョンから変換されたデータベースについては、このセッティングはデフォルトではチェックされていません。 + +## コンテキストメニュー + +4D Write Pro エリア内にて**コンテキストメニュー**プロパティがチェックされている場合(*4D Write Pro エリアを定義する*を参照して下さい)、ランタイムでフォームが実行された時に、ユーザーは包括的なコンテキストメニューを使用することができます: + + + +このメニューを通して、提供されているすべての4D Write Pro 機能へとアクセスすることができます。 + +## ビューモードの選択 + +4D Write Proドキュメントは三種のページビューモードで表示することができます: + +* **下書き**: 基本的なプロパティを持つ下書きモード +* **ページ** (デフォルト): "印刷ビュー" モード +* **埋め込み**: 埋め込みエリアに最適なビューモードです。このモードでは余白、フッター、ヘッダー、カラム、ページフレーム等は表示されません。 +このモードはWeb風のビュー出力を作成するのにも使用できます (96 dpi解像度と **HTML WYSIWYG** オプションを選択した場合)。 + +ページビューモードはエリアポップアップメニューを使用することで設定が可能です: + + + +**注:** ページビューモードはドキュメントには保存されません。 + +4Dフォームに埋め込まれたエリアについては、プロパティリストを使用してデフォルトのビューモードを設定することができます。この場合、ビューモードは 4D Write Proフォームオブジェクトのプロパティとして保存されます (より詳細な情報については、*ビュープロパティの設定* の章を参照してください)。 + + +## 標準アクション + +4D Write Proエリアのユーザーインターフェースは、多様な**標準アクション**を使用して管理することができます。標準アクションは次のようなものに割り当てることが可能です: + +* **メニューバー**あるいは[Dynamic pop up menu](../../commands/dynamic-pop-up-menu) コマンドを通して利用可能なメニューコマンド +* ポップアップ・ドロップダウンリストや階層ポップアップメニューを通して利用可能なリスト項目 +* ボタン、チェックボックス +* あるいは[INVOKE ACTION](../../commands/invoke-action) コマンドによって実行 + +インターフェースオブジェクトに割り当てた場合、標準アクションはコンテキストに応じてオブジェクトの有効化/無効化を管理します。詳細な情報については*標準アクション* の章を参照してください。 + +4D Write Proエリアでは二種類のアクションが利用可能です: + +* 4D Write Pro 特有の、4D Write Proエリアに対してのみ使用可能なアクション +* フォント、式、スペルチェック、編集アクションを含む、4D Write Proエリアと他の4Dエリアで使用可能な*その他のアクション*(*標準アクション*参照)。 + +### 4D Write Pro アクション + +4D Write Proエリアでは以下の標準アクションが利用可能です。 + +**注:** + +* 自動メニュー/リストを表示するアクションは、メニューコマンド、ポップアップ/ドロップダウンリスト、あるいは階層ポップアップメニューオブジェクトにのみ割り当て可能です(*サブメニュー* 参照)。 +* チェックボックスと3Dチェックボックスはステータスアクション("section/differentFirstPage" あるいは "visibleHorizontalRuler"など)を割り当てて下さい。スリーステートオプションは標準のチェックボックスでのみサポートされます。 +* セクションのアクションステータスは、常にその選択されたセクションの実際のステータスと一致します(属性が親セクションあるいはデフォルト属性から継承される場合にはステータスが継承されます)。選択されたセクションのステータス(セクションに現在適用されているステータス)を反映する必要があるからです。しかしながら標準アクションを使用してセクション属性を変更した場合には、選択されたセクションの属性のみが上書きされます。 +* *サブメニュー*: 引数を渡さず、メニューコマンド、ポップアップ/ドロップダウンリスト、あるいは階層ポップアップメニューに割り当てて使用した場合、これらのアクションは自動サブメニュー/リストを表示します。例えば、"backgroundColor"アクションをメニューコマンドに割り当てた場合、このメニューコマンドをランタイムで選択するとBackground color サブメニュー項目が表示されます。"zoom"アクションを階層ポップアップメニューに割り当てた場合、このメニューには既定のズーム値の一覧が自動的に含まれます。これらのアクションはボタンに対しては割り当てられない点に注意してください。 +* *showDialog*: アクション名に"/showDialog " の文字列を追加することで、アクションに割り当てられた標準のダイアログボックスを表示します。例えば、"paragraph/styleSheet/showDialog"と入力することで新しいスタイルシート名を入力する入力ダイアログを開くことができます。 + +| アクション名 | シンタックス | 割り当て可能オブジェクト | 詳細 | +|---|---|---|---| +| anchorHorizontalAlign | {image \| textBox}/anchorHorizontalAlign?value={left \| center \| right} | Image, Textbox, Submenu | Defines the horizontal alignment of the element, relative to the anchorOrigin for images/text boxes in page, or to the layout box for images/text box in embedded mode. This action will reset the horizontal offset to 0. (not enabled for inline images). | +| anchoring | {image \| textBox}/anchoring | Submenu | Default submenu with anchor settings actions for images or text boxes | +| anchorLayout | image/anchorLayout?value={front \| behind \| wrapTopBottom \| wrapSquareLeft \| wrapSquareRight \| wrapSquareLargest \| wrapSquare \| inline}
textBox/anchorLayout?value={front \| behind \| wrapTopBottom \| wrapSquareLeft \| wrapSquareRight \| wrapSquareLargest \| wrapSquare} | Image, Textbox, Submenu | Defines the anchor layout type for an image or a text box. Can be used to transform an inline image to an anchored image, or the reverse. Note: If an image is moved from an anchored mode to inline, the image is inserted at the beginning of the current selected text. "inline" value is not supported for text boxes | +| anchorOrigin | {image \| textBox}/anchorOrigin?value={paper-box \| header-box \| footer-box} | Image, TextBox, Submenu | Defines the area relative to the absolute position of an anchored image or text box. If the element is relative to the header-box/footer-box which is not visible on a page, the element is not displayed. This action will reset horizontal and vertical offsets to 0. Page mode only, not enabled for inline images. | +| anchorPage | {image \| textBox}/anchorPage?value={all \| current \| currentSubSection} | Image, TextBox, Submenu | Defines the page(s) where the selected image or text box is displayed (not enabled for inline images). Page mode only. | +| anchorSection | {image \| textBox}/anchorSection?value={all \| current} | Image, TextBox, Submenu | Defines the section(s) where the selected image or text box is displayed. (not enabled for inline images). Page mode only. | +| anchorVerticalAlign | {image \| textBox}/anchorVerticalAlign?value={top \| center \| bottom} | Image, TextBox Submenu | Defines the vertical alignment of the image or text box, relative to the anchorOrgin for an image or text box in page, or to the layout box for an image or text box in embedded mode. This action will reset the vertical offset to 0 (not enabled for inline images). Note: See "verticalAlign" action for the vertical alignment inside the text box | +| avoidPageBreakInside | {paragraph/}avoidPageBreakInside | Paragraph | | +| background | {doc \| paragraph \| image \| textBox \| section \| header \| footer \| table \| row \| column \| cell/}background | Document, Paragraph, Image, TextBox, Section, Header, Footer, Table, Row, Column, Cell, Submenu | For menu commands only. Default submenu for all background attributes. | +| backgroundClip | {doc \| paragraph \| image \| textBox \| section \| header \| footer \| table \| row \| column \| cell/}backgroundClip?value={paper-box \| border-box \| padding-box \| content-box} | Document, Paragraph, Image, TextBox, Section, Header, Footer, Table, Row, Column, Cell, Submenu | Changes target background clipping box (default target is paragraph). Paper-box targets document and section only. | +| backgroundColor | {doc \| paragraph \| image \| textBox \| section \| header \| footer \| table \| row \| column \| cell/}backgroundColor?value={
cell/merge | Paragraph, Cell | Used with paragraphs: merges paragraphs. Used with cells: merges the selected cells. | +| minHeight | {paragraph \| image/}minHeight?value=
cell/split | Paragraph, Cell | Used with paragraph: splits paragraph. Used with cells: splits the selected cells (only cells that have been already merged may be split). | +| styleSheet | {paragraph \| image/}styleSheet?value={1<=number<=number of target style sheets} | Paragraph, Image, Submenu, showDialog | Applies Nth stylesheet to the selected target elements. With dialog, new stylesheet will use current attributes from the first selected target. (default target is paragraph) Ex: styleSheet?value=1 //apply first paragraph style sheet to the selected paragraphs and set it as paragraph stylesheets. | +| styleSheets | {paragraph \| image/}styleSheets | Paragraph, Image, Submenu | Default submenu for editing target stylesheets. | +| tabDecimalSeparator | tabDecimalSeparator?value={point \| comma \| pointOrComma \| system} | Document, Submenu | Defines the character used as decimal separator by decimal tabulations. | +| tableAlign | tableAlign?value={left \| center \| right}
or
table/tableAlign?value={left \| center \| right} | Table, Submenu | Specifies horizontal alignment for a table. | +| table/avoidPageBreakInside | table/avoidPageBreakInside | Table | Allows/disallows page breaks inside tables. Disabled if: the current selection does not contain at least one table the table is in a header or a footer | +| table/bottomCarryOverRow | table/bottomCarryOverRow | Table | Toggles between display/not display of carry-over rows (see Carry-over rows). | +| textAlign | textAlign?value={left \| right \| center \| justify \| initial} | Paragraph | Paragraph text alignment (initial=use right for rtl or left for ltr direction). | +| textBox | textBox | Submenu | Submenu with all actions available for the focused/selected text box | +| textBox/remove | textBox/remove | TextBox | Removes the selected text box | +| textIndent | textIndent?value=
** | **数** | **必須** | **条件** | **説明** | +| ------------------------------------------------------------- | ------------------- | ----- | ------ | --------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +|  | ヘッダー行 | 最大5 | \- | \- | 標準の表ヘッダー、*繰り返し表示されるヘッダー行* 参照 | +| 
| データ行 | 1 | 必須 | データソースフォーミュラは必ず繰り返される要素を返す必要があります | 表にヘッダー行またはブレーク行がない場合、データ行が表の最初の行となります。それ以外の場合には、ヘッダー行の後の最初の行がこの行となります。一般的には**This** を使用した式(例: *This.item.value* )が記述されています。ドキュメントが*値を表示*モードで行が複製されているとき、この式を通して処理されたデータへとアクセスすることができます。 | +| 
| ソートブレーク行 | 最大5 | \- | データソースフォーミュラは必ず繰り返される要素を返す必要があります | データ行の前または後に表示される行。 *ブレーク行* 参照 | +| 
| 下部キャリーオーバー行 | 1 | \- | データソースフォーミュラは必ず繰り返される要素を返す必要があります | データ行またはブレーク行のあとに最初に表示される行。*キャリーオーバー行* 参照 | +|  | プレースホルダー行 | 1 | \- | データソースが定義されている必要があります | プレースホルダ行は、表に対してデータソースが空でかつ"プレースホルダー行を表示"属性が*emptyDatasource* 標準アクションまたは*wk empty datasource* 定数を通して設定されていた場合に、データ行の代わりに表示される行です。プレースホルダー行はその他の行の直前に表示されます。 | +| | その他の行 | 無制限 | \- | \- | 標準の行(複製されません) | | + +表示例(*参照を表示* モード): + + + +フォーミュラが計算されると、繰り返される行は、データソースフォーミュラから返される全エンティティ数またはコレクション項目数と合致するまで自動的に複製されます: + + + +いずれの場合にしても、以下の宣言を使用することで実際の行数を得ることができます: + +```4d + WP GET ATTRIBUTES($table;wk row count;$vcount) // 上記の例の場合には31 +``` + +##### キャリーオーバー行 + +データソースに基づいた表は**下部キャリー行**をサポートします。これは表が複数のページ/カラムに分割される場合に各ページ/カラムの下部に自動的に表示される行です。キャリーオーバー行は**This.previousItems** という式を使用することで、ここまで表示/印刷された項目に基づいた追加の情報を表示することができます(*This を使用した式* 参照)。この機能を使用することで、例えば小計行を追加することなどができます。 + + + +キャリーオーバー行は以下のように表示されます: + +* データソース表が単一のページ(またはカラム)に収まらない場合に表示されます +* 表の下部に表示されます +* 最初のページ(または最初のカラム)を含め、他の全てのページ/カラムに表示されますが、最後のページ/カラムには表示されません。 + +**重要:** キャリーオーバー行は、空でないコレクションまたはエンティティセレクションを返すデータソースフォーミュラで埋められた表において、値を表示モードのときにのみ利用できます。それ以外の場合、またはデータソースフォーミュラが計算されていない場合には、キャリーオーバー行は通常の行として表示されます。 + +キャリーオーバー行は以下のように作成できます: + +1. 表のテンプレートに、データ行またはブレーク行のすぐ後に行を追加し、例えば**This.previousItems** のように必要なフォーミュラを中に入力します。 +2. ドキュメントにおいてキャリーオーバー行を有効化します。以下の2つの方法があります: +\- *bottomCarryOverRow* 標準アクションを使用する(*4D Write Pro標準アクションの使用* 参照) +\- [WP SET ATTRIBUTES](../commands/wp-set-attributes) コマンドに wk bottom carry over row *表* 属性セレクターを組み合わせて使用する + +**注意:** キャリーオーバー行機能が有効化されている場合、行内の改ページは許可されません(*表のページ分け* 参照)。対応するオプションが設定されてい場合には、無視されます。 + +##### ブレーク行 + +データソースに基づいた表では1つまたは複数の**並べ替えブレーク行**をサポートします。これはデータ行の前または後に表示することができます。**並べ替えブレーク行**を使用すると、表内で既に並べ替えられているデータソースの項目を、計算されたフォーミュラの値に基づいて複数の部分に区分けすることができます。 + + + +フォーミュラの値が変わるたびに、新しいブレーク行が挿入されます。そのため、表が正確にレンダリングされるためには、表のデータソースとして使用されているエンティティセレクション(またはコレクション)は**適切にソートされている必要があります**。例えば、国ごとおよび都市ごとにブレーク行を挿入したい場合、データソースは以下のように指定されている必要があります: *ds.people.all().orderBy("country asc, city asc")* + +ブレーク値は、*wk break formula* 属性を通して定義されます。値は通常、"This.item.name'' のような、項目のプロパティに基づいたフォーミュラです。そうでない場合には値は全く変化しないことがあり、これではブレークフォーミュラは意味のないものになってしまいます。*wk break formula* 属性は、表に何のデータソースもない場合、あるいは行がヘッダー行の場合には無視されます。ブレーク行はデータ行と(前か後ろに)隣り合うか、他のブレーク行と隣り合うように配置されなければなりません。そうでない場合にはこれは無視されます。 + +```4d + WP SET ATTRIBUTES($row_2;wk break formula;Formula(This.item.country)) +``` + +この機能で使用することができる**This.breakItems** 式を使用することで、例えば、データ行全体の平均を1つのブレーク行で表示することができます。breakItems は、表のデータソースがエンティティセレクションならエンティティセレクションの、表のデータソースがコレクションならコレクションの、データソースの評価されたサブセットです。そのため、ブレーク行内には、以下のように書くことができます: *This.breakItems.sum("salary")* + +ブレーク行を作成するには、以下の手順に従って下さい: + +1. データソースを、表示したいブレークに対応したレベルで並べ替えして下さい。例: *ds.People.all().orderBy("continent asc, country asc, city asc")* +2. ブレーク行を表のテンプレート内に追加します。ブレーク行をデータ行の後に配置したい場合、ブレークはデータソースとは**逆順のソート**と合致する必要があり、繰り替えされる行の前に配置したい場合、ブレークはデータソースと**同じソート順**と合致する必要があります。 +3. 選択された行に対して*wk break formula* 属性を設定します: + +```4d + $row:=WP Table get rows($table;2;1) //2行目をブレークとして選択 + WP SET ATTRIBUTES($row_2;wk break formula;Formula(This.item.country)) +``` + +##### This を使用した式 + +表内のフォーミュラ内で使用された場合、**This** キーワードはコンテキストに応じて異なるデータへのアクセスを提供します: + +| **コンテキスト** | **式
** | **型** | **返されるもの** | +| ----------------------------------------------------- | -------------------------- | ----------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 全て | This.table | オブジェクト | カレントの表 | +| | This.row | オブジェクト | カレントの表の行要素 | | +| | This.rowIndex | 数値 | カレント行のインデックス、1から数え始める | | +| 表に対してデータソースが定義されている場合 | This.table.dataSource | オブジェクト (formula) | データソースをフォーミュラとして取得 | +| | This.tableData | (通常は)コレクションまたはエンティティセレクション | 評価された table.dataSource | | +| 表のデータソースがコレクションまたはエンティティセレクションを返す場合のそれぞれのデータ行内 | This.item.xxx | 不定 | 表のデータソースのコレクションまたはエンティティセレクションにマップされたそれぞれの項目。例えば、割り当てられたエンティティに*firstName* 属性がある場合には**This.item.firstName** でアクセス可能 | +| | This.itemIndex | 数値 | コレクションまたはエンティティセレクション内でのカレントの項目のインデックス、0から数え始める | | +| データソースがコレクションまたはエンティティセレクションを返す表における任意の行(ただしヘッダー行を除く) | This.previousItems | コレクションまたはエンティティセレクション | 下部キャリーオーバー行の前まで、あるいは式の行の前までのページに表示された要素。これには式を格納している行を表示しているページも含まれます。
この式は **This.tableData** の式と同じ型の値を返します。 | +| ブレーク行内 | This.breakItems | コレクションまたはエンティティセレクション | コレクションまたはエンティティセレクションの項目が以下の場所に表示されます: ブレーク行が、データ行の後に表示される場合には、現在のブレーク行とその同レベルの前のブレーク行(もしくは表のスタート)との間 ブレーク行が、データ行の前に表示される場合には、現在のブレーク行とその同レベルの後のブレーク行(もしくは表の終わり)との間 | + +その他のコンテキストにおいては、これらの式は*undefined* を返します。 + +**注意:** フォーミュラの挿入についてのより詳しい情報については、[WP INSERT FORMULA](../commands/wp-insert-formula) を参照してください。 + +##### 表のデータソースを扱う + +表がデータソースからのデータが表示されている場合、参照が計算されると行が自動的に作成されます。行を挿入または削除したり、セルのコンテンツを削除したり、スタイルを変えたり、といったことができます: + + + +しかしながら、表のデータソースが再計算された場合、計算された行への変更は(最初の行以外)全て失われてしまうという点に注意して下さい。その一方で、最初の行はデータ行であるため、この行に対して行われた変更は、表のデータソースが再計算された際に全ての行へと伝搬していきます。同じことはブレーク行にも適用され、計算されたブレーク行に対して行われた編集はテンプレートブレーク行を除いて全て失われてしまいます(テンプレートのブレーク行は表の最初または最後に配置されます)。 + +例えば、以下の表は、: + + + +式が再計算されたあとは以下のようになります: + + + +カーソルが、データソースが割り当てられている表のセル内に挿入された時、以下の情報を表示する警告アイコンが左上角に表示されます: + + + +フォーミュラが参照として表示されている場合、あるいはドキュメントを保存した時、最初の行のみがテンプレート行として表示/保存されます(フォーミュラが固定化されていなかった場合)。 + +フォーミュラが固定化されると、表は標準の表となり、表のデータソースはリセットされます。 + +**注意:** *freezeExpressions* 標準アクションを使用しても、フォーミュラは再計算されません。 \ No newline at end of file diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/WritePro/user-legacy/importing-4d-write-documents.md b/i18n/ja/docusaurus-plugin-content-docs/current/WritePro/user-legacy/importing-4d-write-documents.md new file mode 100644 index 00000000000000..9cbd9672d87859 --- /dev/null +++ b/i18n/ja/docusaurus-plugin-content-docs/current/WritePro/user-legacy/importing-4d-write-documents.md @@ -0,0 +1,227 @@ +--- +id: importing-4d-write-documents +title: Importing 4D Write documents +displayed_sidebar: docs +--- + +#### + +新しい4D Write Proオブジェクトの主要な機能の一つとして、既存の4D Writeドキュメントの読み込みと変換機能が挙げられます。これによって4D Write プラグインに依存しているアプリケーションを移行させることができます。 + +****互換性に関する注意:** + +* サポートされるのは、4DWite ドキュメントのうち最後の世代 ("4D Write v7") のドキュメントに限られます。 +* 4D Write ドキュメントから 4D Write Pro エリアへのコピー・ペーストは現時点ではまだサポートされていません。4D Writeドキュメントの読み込みは 4D Write Pro ランゲージコマンドの使用によってのみ可能です。 +* キャリッジリターン(CR)は4D Write と4D Write Pro とで振る舞いが異なります。4D Write では、CRは常に段落ブレークとして解釈されましたが、4D Write Pro ではデフォルトでは改行として解釈されます。読み込まれた4D Write ドキュメントでフォーミュラ内のCRを段落ブレークとして扱うためには、変換後に以下のコードを実行してください: +```4d + WP SET ATTRIBUTES(wp;wk break paragraphs in formulas;wk true) +``` + +詳細な情報については、*フォーミュラの管理* を参照してください。 + +#### 4D Write ドキュメントを読み込むには + +4D Write Proオブジェクトに 4D Writeドキュメントを読み込む方法は二つあります: + +* ディスク上に保存されている 4D Write ファイルに関しては、[WP Import document](../commands/wp-import-document) コマンドを使用してください。 +* BLOBフィールドに格納されている 4D Write エリアに関しては、[WP New](../commands/wp-new) コマンドを使用してください。 + +より詳細な情報に関しては、それぞれのコマンドの詳細を参照してください。 + +#### 4D Write のプロパティで復元されるもの + +4D Write プラグインから4D Write Proへの移行を簡単にするために、4D Write の機能のうち、出来る限り多くのものが4D Write Proオブジェクトでサポートされようとしています。 + +以下の段落では、4D Write プラグインのプロパティのうち、[WP Import document](../commands/wp-import-document) または [WP New](../commands/wp-new) コマンドを使用して4D Write Proエリアへと読み込んだときに復元されるプロパティについてまとめています。 + +しかしながら一部の機能において、バグとはみなされない小さな差異が生じることがあります。これらは例えば、4D Write Proで使用されるデフォルトの行頭の記号や、下線のタイプの小さな変化などによるものです。 + +##### ドキュメント情報 + +| **4D Write プラグイン** | **4D Write Pro** | +| ------------------ | ------------------------------- | +| 作成日時 | 利用可能 | +| 修正日時 | 利用可能 | +| ロック | 利用不可(読み込み専用オブジェクトプロパティを使用して下さい) | +| タイトル | 利用可能 | +| 件名 | 利用可能(標準テキストのみ) | +| 作者 | 利用可能 | +| 会社名 | 利用可能 | +| 注記 | 利用可能 | + +##### ドキュメントの表示の引数 + +| **4D Writeプラグイン** | **4D Write Pro** | +| ----------------- | ------------------------------------------------------------- | +| ページモード | 読み込まれません(コンテキストメニューの、ドキュメント/ページモードを使用して下さい) | +| ルーラー | 読み込まれません(オブジェクトプロパティを使用して下さい) | +| 枠 | 読み込まれません(オブジェクトプロパティを使用して下さい) | +| ヘッダー | 読み込まれません(オブジェクトプロパティを使用して下さい) | +| フッター | 読み込まれません(オブジェクトプロパティを使用して下さい) | +| 最初のページのヘッダー | 利用不可 | +| 最初のページのフッター | 利用不可 | +| 画像 | 利用不可 | +| 縦スクロールバー | 読み込まれません(オブジェクトプロパティの縦スクロールバーを使用して下さい) | +| 横スクロールバー | 読み込まれません(オブジェクトプロパティの横スクロールバーを使用して下さい) | +| 非表示文字 | 読み込まれません(オブジェクトプロパティを使用して下さい) | +| 参照 | 利用不可([ST SET OPTIONS](../../commands/st-set-options)を参照して下さい) | +| カラム分割 | 利用可能(v17以降) | +| 縦スプリッター | 利用不可 | +| 横スプリッター | 利用不可 | +| Wysiwyg | 利用不可 | +| ズーム | 読み込まれません(コンテキストメニューの、ドキュメント/ズームを使用して下さい) | + +##### ドキュメントの引数 + +| **4D Write プラグイン** | **4D Write Pro** | +| ------------------ | ---------------------------------------- | +| 単位 | 読み込まれません(コンテキストメニューのドキュメント/計測単位を使用して下さい) | +| 言語 | 利用不可 | +| カラム数 | 利用可能(v17以降) | +| カラム間隔 | 利用可能(v17以降) | +| ウィンドウ&オーファン | 利用可能 | +| デフォルトのタブ | 利用可能 | +| 先頭のタブ | 利用可能 | +| URLカラー | 利用不可 | +| アクセス済みのURLカラー | 利用不可 | + +**注:** 小数点区切りには([GET SYSTEM FORMAT](../../commands/get-system-format)で返される)システムの小数点が使用されます。この引数は[WP SET ATTRIBUTES](../commands/wp-set-attributes) コマンドを使用することで変更できます。 + +##### ドキュメントのページ付の引数 + +| **4D Writeプラグイン** | **4D Write Pro** | +| --------------------- | ---------------- | +| ページ幅 | 利用可能 | +| ページの高さ | 利用可能 | +| 最初のページ番号 | 利用可能 | +| 最初のページのヘッダーとフッターを別にする | 利用可能 | +| 左右のページでヘッダーとフッターが異なる | 利用可能 | +| ページバインディング | 利用可能 | +| 反対側のページ | 利用可能 | +| ページマージン | 利用可能 | +| ヘッダーの上マージン | 利用可能 | +| ヘッダーの下マージン | 利用可能 | +| フッターの上マージン | 利用可能 | +| フッターの下マージン | 利用可能 | +| 最初のページの上マージン | 利用可能 | +| 最初のページの下マージン | 利用可能 | +| 最初のページのヘッダーの上マージン | 利用可能 | +| 最初のページのヘッダーの下マージン | 利用可能 | +| 最初のページのフッターの上マージン | 利用可能 | +| 最初のページのフッターの下マージン | 利用可能 | +| 最初のページを右側にする | 利用可能 | + +##### ドキュメントの印刷引数 + +| **4D Write プラグイン** | **4D Write Pro** | +| ------------------ | ---------------- | +| 用紙の種類 | 利用不可 | +| 横向きに印刷 | 利用不可 | +| 幅 | 利用不可 | +| 高さ | 利用不可 | +| ユーザー設定マージン | 利用不可 | +| 倍率 | 利用不可 | +| X 解像度 | 利用不可 | +| Y 解像度 | 利用不可 | + +##### 画像 + +**互換性に関する注意:** + +* 4D v19 R2 のWrite Pro 以降、[WP Import document](../commands/wp-import-document) を使用するとピクチャーの表示モードは自動的に読み込まれます。*importDisplayMode* 属性を使用することで以前の振る舞い(全ての画像は合致するように縮小する)を復活させることができます。 +* Windows では、Mac OS PICT フォーマットの画像は読み込まれますが4D Write Pro ではレンダリングされません。このタイプの画像を格納しているドキュメントを読み込んだ場合、それらの画像を他のフォーマットへと変換する必要があります。PICT フォーマットのサポートは4D v18 以降削除されており、今後使用することはできません。 + +| **4D Write プラグイン** | **4D Write Pro** | +| ---------------------- | ---------------------------------- | +| X (左) | (& position :absolute) (ページ内の画像のみ) | +| Y (上) | (& position :absolute) (ページ内の画像のみ) | +| 幅 | 利用可能 | +| 高さ | 利用可能 | +| ページ番号 | 利用可能(v16 R6 以降) | +| 背景画像 | 利用可能(v16 R6 以降) | +| 最初のページには含めない | 利用可能(v16 R6 以降) | +| ビューポートモード(縮小して画像を入れる等) | 利用可能 | +| 式である | インライン画像で利用可能(v16 R5 以降) | +| サイズを保持 | 読み込まれません(4D Write Proでは自動) | + +##### 文字プロパティ + +| **4D Write プラグイン** | **4D Write Pro (span プロパティ)** | +| ----------------------------- | ----------------------------- | +| イタリック | 利用可能 | +| ボールド | 利用可能 | +| 取り消し線 | 利用可能 | +| 下線 | 利用可能 | +| シャドウ | 利用可能 | +| 指数(上付きまたは下付き) | 利用可能 | +| 大文字(英大文字または小型英大文字) | 利用可能 | +| フォントファミリー | 利用可能 | +| フォントサイズ | 利用可能 | +| テキストカラー | 利用可能 | +| テキスト背景カラー | 利用可能 | +| 下線カラー | 利用可能 | +| 取り消し線カラー | 利用可能 | +| シャドウカラー | 利用可能 | +| ユーザープロパティ | 利用不可 | +| スペルチェック(シンタックス&グラマー onまたはoff) | 読み込まれません(エリアプロパティ) | +| 表示 | 利用不可 | +| スタイルシート | 利用可能(4D v18以降) | + +##### 段落プロパティ + +| **4D Write プラグイン** | **4D Write Pro** | +| ------------------ | ---------------- | +| 均等位置 | 利用可能 | +| Interline | 利用可能 | +| 箇条書き | 利用可能 | +| 左マージン | 利用可能 | +| 右マージン | 利用可能 | +| テキストインデント | 利用可能 | +| 境界線スタイル | 利用可能 | +| 境界線カラー | 利用可能 | +| 境界線の背景カラー | 利用可能 | +| 左境界線 | 利用可能 | +| 右境界線 | 利用可能 | +| 上境界線&上の内側の境界線 | 利用可能 | +| 下の境界線&下の内側の境界線 | 利用可能 | +| 境界線間隔 | 利用可能 | +| スタイルシート | 利用可能 | +| タブ | 利用可能 | + +##### ハイパーリンク + +| **4D Write プラグイン** | **4D Write Pro** | +| ------------------ | ------------------------- | +| URL リンク | 利用可能 (\*) | +| 4D メソッドリンク | 利用可能 (\*\*) (v17 R5 以降) | +| ドキュメントを開くリンク | 利用可能(ローカルファイルのURLに変換されます) | + +* (\*) 4D v16 R4以降、URLリンクは編集可能な属性に変換されます。詳細については *リンクコマンド* を参照ください。 +* (\*\*) 呼び出されたメソッド内で受け取った引数を調整する必要があります: + +| **引数** | **4D Write プラグイン** | **4D Write Pro** | +| ------ | --------------------- | ------------------------------------- | +| $1 | 倍長整数 - 4D Write エリア参照 | テキスト - 4D Write Pro エリア名 | +| $2 | テキスト - リンクラベル | オブジェクト - リンク詳細:.method - リンクのメソッドの名前。[SET ALLOWED METHODS](../../commands/set-allowed-methods) コマンドで許可されている必要があります。.parameter - メソッドに渡されたユーザー引数値(使用されていれば).range - リンクのラベルのレンジ*セレクションレンジコマンド*参照。 | +| $3 | 倍長整数 - ユーザー引数(メソッド参照) | \- | + +##### 4D 式 + +| **4D Write プラグイン** | **4D Write Pro** | +| ------------------ | ---------------- | +| 4D 式 | 利用可能\* | +| 日付と時間 | 利用可能 | +| HTML 式 | 利用不可\*\* | +| RTF 式 | 利用不可 | + +\*読み込まれたドキュメント内においてフォーミュラから返されたCR を段落ブレークへと変換するためには[WP SET ATTRIBUTES](../commands/wp-set-attributes) コマンドとwk break paragraphs in formulas 属性を使用してください(デフォルトでは改行として扱われます)。詳細は*フォーミュラの管理* を参照してください。 + +\*ただしwk import html expressions as text 定数を使用した場合には**##htmlBegin##** および **##htmlEnd##** タグに挟まれたテキストとして読み込み可能 + +##### テキストデータ + +| **4D Write プラグイン** | **4D Write Pro** | +| ------------------ | ---------------- | +| メインテキストデータ | 利用可能 | +| ヘッダーテキストデータ | 利用可能 | +| フッターテキストデータ | 利用可能 | \ No newline at end of file diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/WritePro/user-legacy/importing-and-exporting-in-docx-format.md b/i18n/ja/docusaurus-plugin-content-docs/current/WritePro/user-legacy/importing-and-exporting-in-docx-format.md new file mode 100644 index 00000000000000..2cbd05b3a5b4b7 --- /dev/null +++ b/i18n/ja/docusaurus-plugin-content-docs/current/WritePro/user-legacy/importing-and-exporting-in-docx-format.md @@ -0,0 +1,193 @@ +--- +id: importing-and-exporting-in-docx-format +title: Importing and Exporting in docx format +displayed_sidebar: docs +--- + +#### + +4D Write Pro は.docx フォーマットでの読み込みと書き出しの両方ができます。このフォーマットはMicrosof Word などのワープロアプリケーションでサポートされているものです。 + +**互換性に関する注意:** 4D Write Pro ドキュメントの.docx フォーマットの読み込み/書き出しに関するサポートは、Microsoft Word 2010 以降にしか認定されていません。それより古いバージョン、具体的にはMicrosoft Word 2007 などは、ドキュメントを開けない可能性があります。 + +#### .docx フォーマットのファイルの読み込み方 + +.docx フォーマットのドキュメントは、[WP Import document](../commands/wp-import-document) コマンドで4D Write Pro に読み込むことができます。詳細な情報については、このコマンドの説明を参照してください。 + +##### 振る舞いの変化 + +大部分の.docx のパラメーターは保存される一方、一部のパラメーターは4D Write Pro ではサポートされないか振る舞いが異なることが知られています。これらのパラメーターは以下にまとめてあります: + +###### 揃え / レイアウト + +| **設定** | **詳細** | +| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| アンカーされたテキストエリア | アンカーされたテキストエリアはデフォルトではテキストボックスとして読み込まれます(あるいはそれらを無視するか、インラインテキストとして読み込むこともできます。詳細は[WP Import document](../commands/wp-import-document) のオプションを参照してください)。シンプルなテキストエリアのみが読み込まれます。インラインテキストエリアは前面レイヤーにアンカーされたテキストとして読み込まれます。テキストの周りにアンカーされたテキストエリアはそれぞれの折り返しプロパティで読み込まれます(例外: .docx の"tight" 折り返しオプションはスクェア折り返しとして読み込まれます)。 | +| 段落レイアウト | 西欧テキストレイアウトのみがサポートされます。均等段落スタイル、タイ/アジア段落スタイルはサポートされません。 | +| ページサイズ | セクションごとの異なるページサイズはサポートされません。最初のセクションのページサイズのみが読み込まれます。 | + +###### 背景 + +| **設定** | **詳細** | +| ------ | ---------- | +| 透かし画像 | サポートされません。 | + +###### 式 + +| **設定** | **詳細** | +| ------------ | ----------------------- | +| MS Word 演算式 | サポートされません。データは読み込まれません。 | +| MS Word チャート | サポートされません。データは読み込まれません。 | + +###### リスト + +| **設定** | **詳細** | +| ----------- | --------------------------------------------------------------------- | +| 階層リスト | 複数階層のリストはサポートされません。これらは単一階層のリストへと変換されるので、リストの見た目/ナンバリングは変化する可能性があります。 | +| 読み込みオペレーション | | + +###### ピクチャー/画像 + +| **設定** | **詳細** | +| -------------- | ----------------------------------------------------------------------------- | +| DrawingML シェイプ | 単純なDrawingML 画像(インラインまたはアンカーされた画像)のみが読み込まれます。複雑なDrawingML シェイプはサポートされません。 | +| VML シェイプまたは画像 | サポートされません。VML はMS Word では廃止予定となっており、MS Word 2010 以降で作成されたドキュメント内では使用してはいけません。 | +| 3D モデル | サポートされませんが、3D モデルをレンダーした最後の2D 画像は、.docx ファイル内に存在すれば読み込まれます。 | +| SmartArt | サポートされません。 | + +###### 参照 / レビュー + +| **設定** | **詳細** | +| ------ | ------------------------- | +| コメント | サポートされません。コンテンツは読み込まれません。 | +| 脚注 | サポートされません。コンテンツは読み込まれません。 | + +###### 行間隔 + +| **設定** | **詳細** | +| ------------ | ----------------------------------------- | +| "最低限" 行間隔 | サポートされません。"最低限"行間隔は固定された(単一の)行間隔へと変換されます。 | +| テキストをフィットさせる | サポートされません。通常の4D Write Pro スタイルがしようされます。 | + +###### 表 + +| **設定** | **詳細** | +| ------ | --------------------- | +| 表 | 隣接している表は自動的には結合されません。 | + +###### テキスト + +| **Paramètre** | **Description** | +| ------------- | ---------------------------------------------------------------------------------------------------------------- | +| テーマ | テキストテーマは読み込まれません。カラーまたはフォントの定義がテーマのカラーやフォントを参照している場合、最後に計算されたカラーまたはフォントが使用されます。そうでない場合、テーマで定義されたカラーやフォントが使用されます。 | + +##### 読み込みログ + +.docx フォーマットを4D Write Pro へと読み込む際、ログオブジェクトが作成され、読み込まれたドキュメントオブジェクトに含まれます。このオブジェクトは、"importLog" カスタム属性(あるいは wk import log 定数)を通して取得することができます: + +```4d + $myDoc:=WP Import document("test.docx") + if($myDoc#Null) + var $log : Object + $log:=$myDoc[wk import log] + End if +``` + +読み込みログオブジェクトには、以下のプロパティが格納されています : + +| 定数 | コメント | +| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| wk import log | ログオブジェクトには.docx 読み込みオペレーションについての情報が格納されています。プロパティは読み出し専用で設定することはできません:
| **プロパティ** | **型** | **詳細** | |
| status | テキスト | 読み込みステータス: successful - ドキュメントは4D Write Proへと読み込まれました。 failed - 空の4D Write Proドキュメントが返されます。 | |
| developer | コレクション | 4D Write Pro デベロッパーのためのメッセージオブジェクトのコレクション | |
| \[ \].type | テキスト | 記録されたメッセージの種類: info warning error | |
| \[ \].message | テキスト | 読み込みオペレーションについてのメッセージ | |
| user | コレクション | 4D Write Pro ユーザーのためのメッセージオブジェクトのコレクション | |
| \[ \].type | テキスト | 記録されたメッセージの種類: info warning | |
| \[ \].messageShort | テキスト | 読み込みオペレーションについての短いメッセージ | |
| \[ \].messageLong | テキスト | 読み込みオペレーションについての詳細なメッセージ |
- `wk type default`: 定義のないレンジ
- `wk type paragraph`: 段落のレンジ
- `wk type image`: 画像（アンカー付き画像およびインライン画像）
- `wk type image anchored`: アンカー画像
`wk type image inline`: インライン画像
`wk type container`: ヘッダーやフッターなど
`wk type table`: 表の参照
`wk type table row`: 表の行参照
`wk type table cell`: 表のセル参照
`wk type table column`: 複数のカラム参照（カラム透明行カラムレンジに対してのみ）
`wk type body`: 本文のレンジ | + +行、カラムとセルのレンジには、それらを定義するための非公開の属性が存在します： [tables](./handling-tables.md) を参照してください。 + +| 定数 | 値 | コメント| +|-------------------------|------------------|------------------------| +| `wk column count` | `columnCount` | （テーブル、ドキュメント、セクション用の属性）カラムの数。
**値の型**：整数（long）
- テーブルの場合：読み込みのみの属性
- ドキュメントおよびセクションの場合：読み込み／書き込み可能属性。デフォルト値は 1（単一の行）、最大値は 20 | +| `wk first column` | `firstColumn` | *(読み込みのみの属性)* テーブル内にある最初のカラムの数。
**値の型**：整数（long） | +| `wk first row` | `firstRow` | *(読み込みのみの属性)* テーブル内の最初の行の数。
**値の型**：整数（long） | +| `wk row count` | `rowCount` | *(読み込みのみの属性)* レンジ内の行数。
**値の型**：整数（long） | +| `wk table` | `table` | *(読み出しのみの属性)* 親テーブル。
**値の型**：オブジェクト | +| `wk table ID` | `tableID` | *(読み込みのみの属性)* 親テーブルのID。
**値の型**：文字列 | + + + +ドキュメントのレンジは次のように定義できます： + +- [WP Text range](../commands-legacy/wp-text-range.md) `(wpArea ; startRange ; endRange) -> rangeObj`: 範囲として渡した境界値に基づく新しいレンジを返します。 +- [WP Selection range](../commands-legacy/wp-selection-range) `({*} wpArea) -> rangeObj`: 現在のユーザーセレクションに対応した新しいレンジを返します。 +- [WP Picture range](../commands-legacy/wp-picture-range) `(rangeObj) -> rangeObj`: 新しい画像のみのレンジを返します。 +- [WP Paragraph range](../commands-legacy/wp-paragraph-range) `(rangeObj) -> rangeObj`: 新しい段落のみのレンジを返します。 +- [WP Table range](../commands-legacy/wp-table-range) `(rangeObj) -> rangeObj`: 新しい表のみのレンジを返します。 + +ドキュメント内でのレンジの位置情報（ページ番号、カラム番号など）を取得するには、[`WP Get position`](../commands-legacy/wp-get-position) コマンドを使用してください。 + + + diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/WritePro/user-legacy/storing-4d-write-pro-documents-in-4d-object-fields.md b/i18n/ja/docusaurus-plugin-content-docs/current/WritePro/user-legacy/storing-4d-write-pro-documents-in-4d-object-fields.md new file mode 100644 index 00000000000000..3631cad7f45f46 --- /dev/null +++ b/i18n/ja/docusaurus-plugin-content-docs/current/WritePro/user-legacy/storing-4d-write-pro-documents-in-4d-object-fields.md @@ -0,0 +1,172 @@ +--- +id: 4d-write-pro-documents +title: 4D Write Pro documents +displayed_sidebar: docs +--- + +## .4wp ドキュメントフォーマット + +**.4wp** を使用する事によって 4D Write Proドキュメントをロスなくディスク上に保存したりディスクから開いたりすることができます。 + +**.4wp** フォーマットはドキュメント名と同じ名前を持つ ZIPフォルダーと、その中に格納された HTMLテキストと画像から構成されます: + +* HTMLテキストは、通常の HTML と (計算されていない) 4D式に加え、4D特有のタグを組み合わせます。 +* 画像は、HTMLファイルの隣にある、ドキュメント名と同じ名前を持つフォルダー内に保存されています。 + +.4wp ドキュメントは HTML に基づいているので、HTMLをサポートしているものであればどんな外部アプリケーションでもそれを読み込んだり開いたりすることができます。 + +4D Write Pro の内部ドキュメントは HTML に 4D独自の拡張を加えたもので、HTML5/XHTML5 に準拠していながら、独自の HTML/CSS属性のサブセットとタグもサポートしています。したがってデータ損失のリスクなく 4D Write Pro で開けるのは、4D Write Pro で書き出された HTMLドキュメントに限られます。外部で作成された HTMLドキュメントの読み込みはエラーを生成する可能性があります。 + +より詳細な情報については、[**4D Write Pro 属性およびCSSスタイルとしての関連した定義、および4D Write Pro XHTML で使用できるXHTMLタグの一覧**](https://download.4d.com/Documents/Products%5FDocumentation/LastVersions/Line%5F19/4DWP-attributes-and-xhtml.pdf) をダウンロードしてください。 + +### 後方互換性 + +.4wp ドキュメントはいつでも以前のバージョンの4D Write Pro で開くことができます。開いたバージョンより後のバージョンで追加された属性が含まれていた場合、それらの属性は単に無視されるだけです。ただし、その状態でドキュメントを保存した場合、それらの属性はドキュメントから削除され失われてしまいます。 + +## Storing 4D Write Pro documents in 4D Object fields + +4D Write Proドキュメントを自動的に4Dデータファイルに保存できるようになりました。フォーム内に4D Write Proエリアを作成し、そのエリアの中身を保存するオブジェクトフィールドを作成すれば、エリア内に入力したテキストはレコードが評価されるごとにそれぞれのレコードへと自動的に保存されます。その後[QUERY BY ATTRIBUTE](../../commands/query-by-attribute)コマンドを使用して内部属性の値に基づいてレコードを選択する事ができます。また独自の属性を4D Write Proエリアに追加しクエリすることができます。 + +この章では以下の機能について説明しています: + +* フォーム内の4D Write Proエリアを4D オブジェクトフィールドへと結びつける +* 標準のオブジェクトコマンド[OB SET](../../commands/ob-set)、[OB Get](../../commands/ob-get)および[QUERY BY ATTRIBUTE](../../commands/query-by-attribute)を使用して、保存されている4D Write Proドキュメントのカスタムの属性を設定、取得、そしてクエリする + +### 4D オブジェクトフィールドを4D Write Proエリアへと割り当てる + +4D Write Proエリアを4Dオブジェクトフィールドに割り当てるためには、エリアの変数名プロパティにフィールド名を入力するだけです。 + +### ストラクチャー内にオブジェクトフィールドを作成 + +データベースのストラクチャー内において、4Dオブジェクトフィールドであればどれでも4D Write Proドキュメントを保存するのに使用する事ができます。他のオブジェクトフィールドと同様、必要に応じて以下のフィールドの標準のプロパティを定義する必要があります: + +* フィールド名 +* "REST resourceに公開"などの属性とインデックス +* 保存オプション. + + + +### オブジェクトフィールドを4D Write Proエリアに割り当て + +4D Write Proドキュメントを保存するオブジェクトフィールドを決めたら、あとはそのエリアを含んでいるフォーム内で参照するだけです。どのようなテーブルフォームもプロジェクトフォームも使用する事ができます。フォームエディター内において、4D Write Proエリアのプロパティリスト内の、**変数名**の欄に標準の"\[Table\]Field"表記を使用してフィールド名を入力して下さい: + + + +これで4D Write Proエリアはフィールドと関連付けがなされ、エリアの中身はレコード毎に自動的に保存されるようになりました。4D自動アクションボタンを使用しない場合、4Dコマンドを使用してエリアを手動で保存しなければならない点に注意して下さい。 + +### カスタムの属性を使用 + +4D Write Proエリアがオブジェクトフィールド内に保存されているとき、4D Write Proドキュメントにはカスタムの属性を保存または読み出しすることができます。例えば作者名、ドキュメントのカテゴリーなど、どんな追加情報でも有用だと思えるものは使用する事ができます。そしてカスタムの属性をクエリし、条件に合致したレコードを選択することができます + +カスタムの属性は [WP EXPORT DOCUMENT](../commands/wp-export-document) または [WP EXPORT VARIABLE](../commands/wp-export-variable) コマンドで書き出されます。カスタムの属性は[JSON Stringify](../../commands/json-stringify)コマンドを使用して4D Write Pro オブジェクトフィールドをJSONに変換する際にも書き出されます(同時に4D Write Pro のメインドキュメント属性も書き出されます)。 + +カスタムの属性を設定または取得するためには、オブジェクト記法を使用するか、[OB Get](../../commands/ob-get) と [OB SET](../../commands/ob-set)コマンドを使用するだけです。 + +たとえばフォームメソッドにおいて、以下のように書くことがでカスタムの属性を設定できます: + +```4d + If(Form event code=On Validate) + [MyDocuments]My4DWP["myatt_Last edition by"]:=Current user + [MyDocuments]My4DWP.myatt_Category:="Memo" + [MyDocuments]My4DWP:=[MyDocuments]My4DWP //編集を記録 + End if +``` + +あるいは: + +```4d + If(Form event code=On Validate) + OB SET([MyDocuments]My4DWP;"myatt_Last edition by";Current user) + OB SET([MyDocuments]My4DWP;"myatt_Category";"Memo") + End if +``` + +また、以下のように書いて、ドキュメントのカスタムの属性を読み出すことができます: + +```4d + vAttrib:=[MyDocuments]My4DWP.myatt_Category +``` + +あるいは: + +```4d + vAttrib:=OB Get([MyDocuments]My4DWP;"myatt_Last edition by") +``` + +カスタムの4D Write Pro属性をデータファイルに保存していた場合、これらの属性をクエリして適切な属性の値を含むレコードのセレクションを作成することができます。以下の例では、レコードを選択するためにオブジェクトフィールドを含んでいるテーブルをクエリします: + +```4d + QUERY BY ATTRIBUTE([MyDocuments];[MyDocuments]My4DWP;"myatt_Category";=;"Memo") + //MyDocuments内の、(4D Write Proエリアに割り当てられている)My4DWPオブジェクトフィールド内で + //"myatt_Category"というカスタム属性が"Memo"という値を含んでいるレコードを全て選択します +``` + +:::warning カスタム属性の名前についての注意 + +カスタム属性は4D Write Pro内部属性と同じ名前空間を共有するため、内部属性とカスタム属性との衝突を避けるために、独自の属性を定義するときには必ず接頭辞をつけた名前を定義する事が強く推奨されます。接頭辞がついていない名前は4D Write Proの内部属性のために予約されているからです。接頭辞であればどのような独自の接頭辞であっても使用する事ができます(上記の例では"myatt\_" を接頭辞として使用しました)。 + +::: + +**注意:** カスタム属性は[WP SET ATTRIBUTES](../commands/wp-set-attributes)、[WP GET ATTRIBUTES](../commands/wp-get-attributes) および [WP RESET ATTRIBUTES](../commands/wp-reset-attributes) コマンドで管理することはできません(これらのコマンドは4D Write Pro の内部属性のみをサポートします)。 + +## Opening and exporting documents + +4D アプリケーションでは、4D Write Proテーマ内にある特定のコマンドを使用することによって、4D Write Proドキュメントを作成、読み込み、書き出しすることができます ([WP EXPORT DOCUMENT](../commands/wp-export-document), [WP EXPORT VARIABLE](../commands/wp-export-variable), [WP Import document](../commands/wp-import-document), [WP New](../commands/wp-new)))。 + +[4D Write Proエリアをデータベースの内のオブジェクトフィールドと関連づけることができます](../user-legacy/defining-a-4d-write-pro-area.md#storing-4d-write-pro-documents-in-4d-object-fields)。これにより、各 4D Write Proドキュメントはレコードとともに自動的に保存され、データベースのデータ内に保存されます。 + +## Printing 4D Write Pro documents + +4D Write Pro ドキュメントの印刷には次の方法があります: + +* 4D フォームの一部として +* 独立したドキュメントとして + +### 4D フォーム内ドキュメントの印刷 + +[PRINT SELECTION](../../commands/print-selection) や [PRINT RECORD](../../commands/print-record) などの標準の 4D印刷コマンドを使用して、どのような 4Dフォームでも (プロジェクトフォーム、テーブルフォーム、入力フォーム、出力フォーム)、その中に埋め込まれた 4D Write Pro オブジェクトを印刷することができます。 + +標準の *印刷時可変* オプションは 4D Write Pro エリアでもサポートされている (\*) ため、印刷時にサイズを操作することができます。このオプションがチェックされているとき、マージン (内側・外側) と上マージンは先頭のページにのみ適用されます。マージン (内側・外側) と下マージンは最終ページにのみ適用されます。ドキュメントのページ付けプロパティは無視されます。ウィドウ・オーファンコントロールは無効化され、改ページは適用されません (これらのプロパティはスクリーン上でのページレンダリングとドキュメントのスタンドアロン印刷においてのみ使用されます)。**印刷時可変**オプションが選択されていた場合、フォームエリアより上に位置しているオブジェクトのみが印刷されます。このオプションについてのより詳細な情報については、デザインリファレンスマニュアルの "*印刷時可変*" を参照してください。 + +(\*) [Print object](../../commands/print-object) と [Print form](../../commands/print-form) コマンドは、このオプションと併用できません。 + +#### 印刷とビューモード + +4D Write Pro エリアに設定した**ビューモード** (*ビュープロパティの設定* 参照) にかかわらず、[Print form](../../commands/print-form) などの 4D 印刷コマンドをしようすると、常に **埋め込み** モードで印刷されます。つまり、4D Write Pro フォームオブジェクトの次のアピアランス設定が無視されます: ページビューモード (常に **埋め込み**)、 ヘッダーを表示、フッターを表示、ページ枠を表示 (常に "No")、非表示の文字を表示 (常に "No")。 + +#### 例題 + +以下の例は、デフォルト出力フォームに埋め込まれた4D Write Proエリアにおける**印刷時可変**オプションの効果を示したものです。ここでは以下のコードが実行されています: + +```4d + ALL RECORDS([Movies]) + ORDER BY([Movies]Title) + PRINT SELECTION([Movies]) +``` + +* 以下は印刷時可変のオプションがチェック**されていない** (off) 場合の結果です: + +* 以下は印刷時可変のオプションがチェック**されている** (on) 場合の結果です: + +*(Sample text source: Wikipedia)* + +### 独立したドキュメントの印刷 + +4D v15 R5以降、4D Write Pro に含まれる新機能によって、独立した 4D Write Pro ドキュメントを印刷できるようになったのに加え、フォーマット、ページの向き、ページ番号と言った標準の印刷オプションの操作が可能になりました。 + +#### 4D Write Pro コマンド + +4D Write Proの印刷機能は、主に次の二つのコマンドによって管理されます。**WP PRINT** と **WP USE PAGE SETUP**です。 + +* [WP PRINT](../commands/wp-print) は 4D Write Pro ドキュメントの印刷ジョブをローンチするか、ドキュメントをカレントの印刷ジョブに追加します。 +* [WP USE PAGE SETUP](../commands/wp-use-page-setup) はカレントプリンターのページ設定を、4D Write Proドキュメント属性のページサイズとページの向きに変更します。 + +**注**: Windows 7 あるいは Windows Server 2008 R2のマシン上では、*Platform Update for Windows 7* がインストールされており、印刷機能がサポートされていることを確認してください。 + +#### 標準の 4D コマンド + +以下の 4Dコマンドは 4D Write Pro 印刷機能をサポートします: + +* [SET PRINT OPTION](../../commands/set-print-option) と [GET PRINT OPTION](../../commands/get-print-option): すべてのオプションが、[WP PRINT](../commands/wp-print) によって印刷される 4D Write Proドキュメントに対してサポートされています。Paper option と Orientation optionに関しては、[WP USE PAGE SETUP](../commands/wp-use-page-setup) を呼び出してページサイズと向きの属性を 4D Write Pro ドキュメントの設定と同期させる方が効率的な場合もあります。Page range option (15) を使って、印刷するページ範囲を指定することができます。 +* [PRINT SETTINGS](../../commands/print-settings): カレントのプリンターに対して印刷設定を設定します。[WP PRINT](../commands/wp-print) がこの後に呼び出された場合、プリンター設定が PRINT SETTINGS ダイアログで変更されていれば、その設定を使用します (ただし余白ページ設定だけは常に4D Write Proドキュメントの設定を使用します) +* [OPEN PRINTING JOB](../../commands/open-printing-job) と [CLOSE PRINTING JOB](../../commands/close-printing-job): これらのコマンドの間に [WP PRINT](../commands/wp-print) を呼び出すことによって、一つ以上の4D Write Proドキュメントを一件の印刷ジョブに挿入することができます。 \ No newline at end of file diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/WritePro/user-legacy/stylesheets.md b/i18n/ja/docusaurus-plugin-content-docs/current/WritePro/user-legacy/stylesheets.md new file mode 100644 index 00000000000000..a4489127d89fa5 --- /dev/null +++ b/i18n/ja/docusaurus-plugin-content-docs/current/WritePro/user-legacy/stylesheets.md @@ -0,0 +1,138 @@ +--- +id: stylesheets +title: スタイルシート +displayed_sidebar: docs +slug: /WritePro/user/stylesheets +--- + + +スタイルシートとは、定義された属性設定のセットのオブジェクトであり、4D Write Pro ドキュメントの見た目をコントロールすることができます。これらの設定は段落または文字に適用することができます（例: は表示するフォント、フォントのサイズ、カラー、ウェイトなどです）。スタイルシートを定義すると、それはオブジェクトとして 4D Write Pro ドキュメントに保存されるため、再利用することができます。スタイルシートを使用することで、文書に独自性を持たせつつ、時間を節約することもできます。 + +## デフォルト スタイル + +すべての 4D Write Pro ドキュメントにはデフォルトの段落スタイルシート「Normal」が含まれます。新しいスタイルシートは、[WP New style sheet](../commands-legacy/wp-new-style-sheet) コマンドで作成すると、自動的にこの標準スタイルを継承します。スタイルシートによって変更された属性は、そのスタイルシートが適用されている段落にのみ影響し、ドキュメントの残りの部分はデフォルトの Normal 設定を保持します。スタイルシートを削除すると、変更された属性は Normal スタイルに戻されます。 + +通常スタイル Normal は、4D Write Pro ドキュメント内のすべてのスタイル属性のデフォルト値を定義します。これは [WP Get style sheet](../commands-legacy/wp-get-style-sheet) コマンドで取得することができます。通常スタイルは [WP SET ATTRIBUTES](../commands/wp-set-attributes) コマンドで編集可能ですが（ただし名前の変更はできません）。[WP New style sheet](../commands-legacy/wp-new-style-sheet) コマンドで作成されたスタイルシートは [WP DELETE STYLE SHEET](../commands-legacy/wp-delete-style-sheet) コマンドで削除できますが、Normal スタイルシートは削除することができません。 + +## 段落スタイルシートと文字スタイルシートの属性 + +スタイルシートには次の属性があり、段落または文字の属性を定義することができます: + +- **段落** - 段落の大部分の属性は段落にのみ適用されます。段落スタイルシートは文字スタイル属性も含み、かつ段落にのみ適用可能なフォーマット属性（例:余白、境界線、タブなど）に対しての適用可能なフォーマット属性も含んでいます。 +- **文字** - 文字スタイルシートは、文字スタイル属性のみを使用して、段落スタイルと区別するテキスト（1文字または複数）の形式（例: 見出し、強調、下線など）を定義します。 + +段落スタイルは段落全体に適用されることに注意してください。段落の特定の一部にのみ適用したい場合は、文字スタイルシートを使用する必要があります。 + +## スタイルシート優先順位 + +1つの 4D Write Pro ドキュメントに複数の段落スタイル/文字スタイルシートの優先順位が存在し、それが適用された順番によって決定されるという点に注意してください。 + +- 例えば、最初に段落スタイルシートを適用し、その後で文字スタイルシートを適用すると、文字スタイルシートが優先されます。例えば、段落スタイルシートをドキュメントの本文に適用し、その後に「太字」文字スタイルシートを作成し、特定の単語の箇所に対してのみ適用することができます。段落スタイルシートは他の箇所に対して引き続き適用されますが、指定された単語には文字スタイルシートが優先されます。 +- 反対に、先に文字スタイルシートを適用し、その後に段落スタイルシートを適用すると、段落スタイルシートがすべてのテキストに適用され、文字スタイルシートのスタイルは削除されます。 + +## スタイルシートの適用 + +スタイルシートは [WP SET ATTRIBUTES](../commands/wp-set-attributes) コマンドに `wk style sheet` または `wk new line style sheet` 定数を使うことで適用されます（オブジェクト記法を使っても適用されます）。 + +## スタイルシートの取得 + +[WP Get style sheets](../commands-legacy/wp-get-style-sheets) コマンドを使うと、指定されたタイプに基づいてすべてのスタイルシートを取得することができます。[WP Get style sheet](../commands-legacy/wp-get-style-sheet) コマンドを使用するとスタイルシート名を指定して取得することができます。 + +## スタイルシートの読み込みと書き出し + +スタイルシートはオブジェクトとして保存されるので、他の 4D Write Pro ドキュメントへ簡単に読み込んだり、書き出しても容易に維持できます。 + +- 書き込み – [WP IMPORT STYLE SHEETS](../commands-legacy/wp-import-style-sheets) コマンドを使用すれば、指定4Dドキュメントのスタイルシートオブジェクトを取得し、新規ドキュメントで使用することが可能です。 +- 書き出し – [WP EXPORT DOCUMENT](../commands/wp-export-document) または [WP EXPORT VARIABLE](../commands/wp-export-variable.md) コマンドでスタイル付きの文書をエクスポートすることができます。 + +## スタイルシート属性 + +以下の属性はスタイルシートにより変更可能で、[WP SET ATTRIBUTES](../commands/wp-set-attributes) および [WP RESET ATTRIBUTES](../commands/wp-reset-attributes) コマンドで保存すること、[WP GET ATTRIBUTES](../commands/wp-get-attributes) コマンドで取得することが可能です。 + +:::note + +注: 一部の属性はリンクされています。そのため、これらのうち一つの属性を追加すると、リンクされた他の属性もデフォルト値で作成されます。リンクされた属性については、デフォルトの値は通常スタイルシートで定義された値とは異なる場合があります。例えば、赤の左境界線だけを定義した場合、他の境界線はたとえ通常スタイルが紫で事前に定義されていたとしても黒でデフォルト値が設定されます。 + +::: + + +| 属性 | 段落 | 文字 | リンクして連動する属性 | +|----------------------------------|-----------|-----------|-------------| +| `wk avoid widows and orphans` | X | | | +| `wk background clip` | X | | | +| `wk background color` | X | X | | +| `wk background height` | X | | `wk background width` | +| `wk background image` | X | | | +| `wk background image url` | X | | | +| `wk background origin` | X | | | +| `wk background position horizontal` | X | | `wk background position vertical` | +| `wk background position vertical` | X | | `wk background position horizontal` | +| `wk background repeat` | X | | | +| `wk background width` | X | | `wk background height` | +| `wk border color` | X | | `wk border color bottom`, `wk border color left`, `wk border color right`, `wk border color top` | +| `wk border color bottom` | X | | `wk border color`, `wk border color left`, `wk border color right`, `wk border color top` | +| `wk border color left` | X | | `wk border color`, `wk border color bottom`, `wk border color right`, `wk border color top` | +| `wk border color right` | X | | `wk border color`, `wk border color bottom`, `wk border color left`, `wk border color top` | +| `wk border color top` | X | | `wk border color`, `wk border color bottom`, `wk border color left`, `wk border color right` | +| `wk border radius` | X | | | +| `wk border style` | X | | `wk border style bottom`, `wk border style left`, `wk border style right`, `wk border style top` | +| `wk border style bottom` | X | | `wk border style`, `wk border style left`, `wk border style right`, `wk border style top` | +| `wk border style left` | X | | `wk border style`, `wk border style bottom`, `wk border style right`, `wk border style top` | +| `wk border style right` | X | | `wk border style`, `wk border style bottom`, `wk border style left`, `wk border style top` | +| `wk border style top` | X | | `wk border style`, `wk border style bottom`, `wk border style left` | +| `wk border width` | X | | `wk border width bottom`, `wk border width left`, `wk border width right`, `wk border width top` | +| `wk border width bottom` | X | | `wk border width`, `wk border width left`, `wk border width right`, `wk border width top` | +| `wk border width left` | X | | `wk border width`, `wk border width bottom`, `wk border width right`, `wk border width top` | +| `wk border width right` | X | | `wk border width`, `wk border width bottom`, `wk border width left`, `wk border width top` | +| `wk border width top` | X | | `wk border width`, `wk border width bottom`, `wk border width left`, `wk border width right` | +| `wk direction` | X | | | +| `wk font` | X | X | `wk font bold`, `wk font italic`, `wk font size` | +| `wk font bold` | X | X | `wk font`, `wk font family`, `wk font italic`, `wk font size` | +| `wk font family` | X | X | `wk font`, `wk font bold`, `wk font italic`, `wk font size` | +| `wk font italic` | X | X | `wk font`, `wk font bold`, `wk font family`, `wk font size` | +| `wk font size` | X | X | `wk font`, `wk font bold`, `wk font family`, `wk font italic` | +| `wk line height` | X | | | +| `wk list font` | X | | | +| `wk list string format LTR` | X | | | +| `wk list string format RTL` | X | | | +| `wk list style image` | X | | | +| `wk list style image height` | X | | | +| `wk list style image url` | X | | | +| `wk list style type` | X | | | +| `wk margin` | X | | `wk margin bottom`, `wk margin left`, `wk margin right`, `wk margin top` | +| `wk margin bottom` | X | | `wk margin`, `wk margin left`, `wk margin right`, `wk margin top` | +| `wk margin left` | X | | `wk margin`, `wk margin bottom`, `wk margin right`, `wk margin top` | +| `wk margin right` | X | | `wk margin`, `wk margin bottom`, `wk margin left`, `wk margin top` | +| `wk margin top` | X | | `wk margin`, `wk margin bottom`, `wk margin left`, `wk margin right` | +| `wk min height` | X | | | +| `wk min width` | X | | | +| `wk name` | X | X | | +| `wk new line style sheet` | X | | | +| `wk owner` | X | X | | +| `wk padding` | X | | `wk padding bottom`, `wk padding left`, `wk padding right`, `wk padding top` | +| `wk padding bottom` | X | | `wk padding`, `wk padding left`, `wk padding right`, `wk padding top` | +| `wk padding box` | X | | | +| `wk padding left` | X | | `wk padding`, `wk padding bottom`, `wk padding right`, `wk padding top` | +| `wk padding right` | X | | `wk padding`, `wk padding bottom`, `wk padding left`, `wk padding top` | +| `wk padding top` | X | | `wk padding`, `wk padding bottom`, `wk padding left`, `wk padding right` | +| `_o_wk page break inside` | X | | | +| `wk tab default` | X | | `wk tabs`, `wk tab stop offsets`, `wk tab stop types`, `wk tab stop leadings` | +| `wk tabs` | X | | `wk tab default`, `wk tab stop offsets`, `wk tab stop types`, `wk tab stop leadings` | +| `wk tab stop offsets` | X | | `wk tabs`, `wk tab default`, `wk tab stop types`, `wk tab stop leadings` | +| `wk tab stop types` | X | | `wk tabs`, `wk tab default`, `wk tab stop offsets`, `wk tab stop leadings` | +| `wk tab stop leadings` | X | | `wk tabs`, `wk tab default`, `wk tab stop offsets`, `wk tab stop types` | +| `wk text align` | X | | | +| `wk text color` | X | X | | +| `wk text indent` | X | | | +| `wk text linethrough color` | X | X | | +| `wk text linethrough style` | X | X | `wk text underline style` | +| `wk text shadow color` | X | X | `wk text shadow offset` | +| `wk text shadow offset` | X | X | `wk text shadow color` | +| `wk text transform` | X | X | | +| `wk text underline color` | X | X | | +| `wk text underline style` | X | X | `wk text linethrough style` | +| `wk type` | X (read only) | X (read only) | | +| `wk vertical align` | X | X | | +| `wk width` | X | | | + + diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/WritePro/user-legacy/text-boxes.md b/i18n/ja/docusaurus-plugin-content-docs/current/WritePro/user-legacy/text-boxes.md new file mode 100644 index 00000000000000..13d92ae87a1139 --- /dev/null +++ b/i18n/ja/docusaurus-plugin-content-docs/current/WritePro/user-legacy/text-boxes.md @@ -0,0 +1,55 @@ +--- +id: text-boxes +title: Text boxes +displayed_sidebar: docs +slug: /WritePro/user/text-boxes +--- + + + +テキストボックスはページまたはセクションに対してアンカーされるエリアで、その中にテキスト、インライン画像、または表を格納することができます。テキストボックスはページ上のどこにでも配置可能で、例えば会社名やロゴ、住所エリアを挿入するなど、幅広い用途に応じて使用できます。 + + + +**注意:** テキストボックスには、ヘッダー、フッター、カラム、アンカーされた画像、あるいは他のテキストボックスを格納することはできません。 + +テキストボックスは絶対位置で追加され、テキストの前面/背面のどちらにも配置可能です。またページにアンカーすることもできる他、ページモードでのドキュメントの特定のパーツ(ヘッダー、フッター。セクション、全セクション、サブセクション)へとアンカーすることも可能です。テキストボックスはまた埋め込みモードで使用することもできます(レイヤーボックスへとアンカーされます)。 + +4D Write Pro ドキュメントにテキストボックスを追加するためには、以下の方法があります: + +* **WP New text box** コマンドを使用する +* *insertTextBox* 標準アクションを使用する + +テキストボックスを選択するためには、ユーザーはそれをクリックする必要があります(テキストボックスが背面レイヤーにある場合には**Ctrl/Cmd+クリック** で選択します)。テキストボックスが選択されると、マウスまたは矢印キーを使用してそれを移動させたり、リサイズすることができます。 + +テキストボックスを削除するためには、**Delete** または **Backspace** キーを押すか、**textBox/remove** 標準アクションを使用するか、あるいは**WP DELETE TEXT BOX** コマンドを実行します。 + +テキストボックス属性は、[WP SET ATTRIBUTES](../commands/wp-set-attributes) コマンドまたは *4D Write Pro アクション*によって管理できます。以下の属性とアクションが利用可能です: + +| **プロパティ(定数)** | **標準アクション** | **補足** | +| --------------------- | ------------------------- | -------------------------------------------------------------------- | +| wk width | textBox/width | "auto" に設定されている場合、幅は8cm へと変換されます。テキストボックスの幅を"auto" に設定することはできないからです。 | +| wk height | textBox/height | "auto" に設定されている場合、高さはコンテンツに合わせて調整されます。 | +| wk padding | textBox/padding | | +| wk border \[...\] | textBox/border\[...\] | | +| wk background \[...\] | textBox/background\[...\] | | +| wk vertical align | textBox/verticalAlign | | +| wk id | \- | テキストボックスに対しては空にすることはできません。 | +| wk anchor \[...\] | textBox/anchor\[...\] | | +| wk owner | \- | 読み出し専用 | +| wk protected | \- | | +| wk style sheet | \- | 読み出し専用かつ、必ず"" (スタイルシートはありません) | + +テキストボックスは、左側/右側/大きい側/上と下またはwk anchor layout プロパティまたは**anchorLayout** 標準アクションを通して提供されるオプションでドキュメントにアンカーされた場合、自動テキスト折り返しをサポートします。詳細については [こちらのblog記事](https://blog.4d.com/4d-write-pro-more-display-options-for-anchored-pictures-and-text-boxes/) を参照してください。 + + + +テキスト折り返しが設定されているテキストボックスがページの本文に対してアンカーされている場合、それらはヘッダーまたはフッターには影響しません(テキストボックスはヘッダーまたはフッターの前面に表示されます)。その反対に、ヘッダーまたはフッターにアンカーされたテキストボックスは、ページの本文と重なった場合にはそちらに影響します。 + +**注意**: テキスト折り返しが設定されているテキストボックスをヘッダーまたはフッターにアンカーしたい場合、テキストボックスの横方向揃えを上揃えに設定する必要があります。 + +テキストボックスは、以下の場合には表示されません: + +* ビューモードが下書きモードである +* テキストボックスが中央揃えになっているかセクションにアンカーされていて、**HTML WYSIWYGに表示** オプションがチェックされている。 +* "背景を表示"オプションが有効化されていない \ No newline at end of file diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/WritePro/user-legacy/using-a-4d-write-pro-area.md b/i18n/ja/docusaurus-plugin-content-docs/current/WritePro/user-legacy/using-a-4d-write-pro-area.md new file mode 100644 index 00000000000000..1c3d7cbe4c53ae --- /dev/null +++ b/i18n/ja/docusaurus-plugin-content-docs/current/WritePro/user-legacy/using-a-4d-write-pro-area.md @@ -0,0 +1,427 @@ +--- +id: using-a-4d-write-pro-area +title: Using a 4D Write Pro area +displayed_sidebar: docs +--- + + + + + +## 基本概念 + +ドキュメントが[ページビューモード](./defining-a-4d-write-pro-area.md#selecting-the-view-mode)のとき、以下のドキュメントプロパティがユーザーに表示されます: + +* 印刷範囲を示すページのアウトライン +* ページ幅とページの高さ (デフォルトは21x29.7 cm) +* ページの向き (デフォルト: 縦向き) +* ページの余白 (デフォルト: 2.5cm) + +また、**改ページを挿入/カラムを挿入/セクションブレークを挿入**、**文書.../ページサイズ**、**文書.../ページの向き**、といったページ関連の追加のコマンドを使用する事もできます。 + +**注:** ドキュメントが **埋め込み**モードまたは**下書き**モードのときにページプロパティを変更しても見た目上は変化ありませんが、それでも設定は可能です。以下の段落プロパティは、**下書き**モードでも見た目上の変化があります: + +* ページの高さ制限 (線が引かれます) +* カラム +* 内側での改ページを避けるプロパティ +* ウィドウ&オーファンコントロール + +## 段落ブレーク + +ページモードまたは下書きモードで表示された時(あるいはドキュメント印刷のコンテキストにおいて)、4D Write Pro の段落は、以下のようなときにブレークを行うことがあります: + +* 段落の高さが利用可能なページの高さより高いときには自動的に段落ブレークが挿入されます。 +* プログラミングによって、またはユーザーによって設定されていた場合、段落ブレークが挿入されます。 + +ブレークはプログラミングによって、またはユーザーの操作で追加することが可能です。利用可能なアクションとしては以下のようなものが含まれます: + +* [WP INSERT BREAK](../commands/wp-insert-break) コマンド +* *insertPageBreak* 標準アクション +* デフォルトのコンテキストメニューの、**段落ブレーク挿入**オプション + +### 自動ブレークを管理する + +以下の機能を使用することで、段落内の自動ブレークを管理することができます: + +* **ウィドウ&オーファンコントロール**: このオプションが段落に対して設定されているとき、4D Write Pro はドキュメント内にてウィドウ (段落の最終行がページ上部に取り残される状態) とオーファン (段落の先頭行がページ下部に取り残される状態) を許可しません。前者の場合には、最終行の一つ前の行を加えた 2行がページ上部に表示されます。後者の場合には、単一の先頭行は次ページへと送られます。 +* **段落内の改ページを避ける**: このオプションが段落に対してチェックされている場合、4D Write Pro はその段落が 2枚以上のページに分割されないようにします。 +* **次の段落につなげる:** このオプションが段落に対して設定されている場合、その段落は、その後に続く段落と自動ブレークでは分割されなくなります。詳細に関しては`wk keep with next` とそれに対応する[標準アクション](./defining-a-4d-write-pro-area.md#standard-actions)を参照して下さい*keepWithNext*. + +これらのオプションはコンテキストメニューを使用するか、あるいは[属性](../commands-legacy/4d-write-pro-attributes.md)(`wk avoid widows and orphans`、`wk page break inside paragraph`、または[標準アクション](./defining-a-4d-write-pro-area.md#standard-actions)(*widowAndOrphanControlEnabled*、 *avoidPageBreakInside*。 + +## 背景 + +4D Write Pro ドキュメントの背景とドキュメント要素(表、段落、セクション、ヘッダー/フッター等)には、以下のエフェクトを設定することができます: + +* カラー +* 境界線 +* 画像 +* 原点、水平および垂直位置 +* 塗りエリア +* 繰り返し + +これらの[属性](../commands-legacy/4d-write-pro-attributes.md)は、[WP SET ATTRIBUTES](../commands/wp-set-attributes) コマンドあるいは[標準アクション](./defining-a-4d-write-pro-area.md#standard-actions)によってによって、プログラムによってページ上のそれぞれの要素に対して、あるいはドキュメントの背景全体に対して定義することが可能です。 + +ユーザーは以下のように、コンテキストメニューを通じて背景属性を変更することが可能です: + + + + +背景画像にフルサイズの画像を追加する例については、*[How Do I (HDI) 例題 4DWrite Pro: フチなし全面の背景画像](https://github.com/4D-JP/HDI/releases/download/16r5/HDI%5F4DWP%5FBackImagePaperBox.zip)* にて紹介しています。 + +## Headers, footers, and sections + +4D Write Pro ドキュメントはヘッダーとフッターをサポートします。ヘッダーとフッターはセクションと関連しています。 + +セクションとは、ページレンジによって定義されたドキュメントの一部分で、ページングと属性の設定を独自に持つことができます。ドキュメントには複数のセクションを含めることができます (1から合計のページ数まで)。それぞれのページには、継続したセクションブレークを持つページを除き(以下参照)、1ページにつき1セクションのみ含めることができます, except pages with continuous section breaks (see below). + +4D Write Pro documents can contain: + +- one or more sections (one section by default) +- for each section, up to three subsections: + - first page subsection + - left page(s) subsection + - right page(s) subsection + +各セクションに対して、ヘッダーとフッターのセットを定義することができます。 + +### セクションの定義 + +セクションとは4D Write Proドキュメント内の継続したページのサブセットです。ドキュメントは1つ以上のセクションを含むことができます。ひとつのセクションには何ページでも (単一のページからドキュメント内の総ページ数まで) 含めることができます。また、ひとつのセクションにはカラムを1個から最大20個まで含めることができます。 + +デフォルトで、ドキュメントは**セクション1**と名付けられたひとつのセクションを持ちます。ドキュメント内のどこをクリックしても、4D Write Proコンテキストメニューにそのセクション番号を表示します: + + + +テキストの中にセクションブレークを追加することで新しいセクションを作成することができます: + + + +セクションブレークが追加されたとき、コンテキストメニューはそれぞれのセクションに対しインクリメントされた数字を表示します。セクション名は任意に改名することも可能です: + + + +入力した名前はそのセクションの名前として、ドキュメント全体で使用されます: + +  + +セクションに対し、異なる最初のページ、異なる左/右ページを定義していた場合、そのページタイプもまたメニューに表示されるというに点に注意して下さい (後述参照)。 + +### 継続したセクションブレークの挿入 + +継続したセクションブレークは、同一ページ内に新しいセクションを作成します。これを使用することで、異なる数のカラムのセクションを持つページを作成することができます(*複数カラムと単一カラムのセクションを持ったページの作成* 参照)。 + +継続したセクションブレークで作成されたセクションはドキュメント内でカウントされます(セクション番号を持ちます)。ただし通常のセクションブレークで作成されたセクションとは異なり、ヘッダー、フッター、アンカーされた画像などは実際の改ページが発生したときにのみ考慮されます。 + +**注:** 継続したセクションブレークを挿入したあとに新しいセクションに対してページの方向を変更した場合には、そのセクションブレークは通常のセクションブレークへと変換されます。 + +### セクション属性 + +セクションはドキュメント属性を継承しますが、ヘッダーとフッターを含むドキュメント属性は、セクションごとに個別に編集することも可能です。コンテキストポップアップメニューは、セクションレベルで利用可能なプロパティと属性を表示します: + + + +* **ページの向き**: セクションごとに特定のページの向き (横向き/縦向き)を設定することができます。 +* **最初のページを個別に設定**: セクションの最初のページに対して異なる属性を設定することができます。この機能は例えば、余白を作成するのに使用することができます。この属性がチェックされている場合、セクションの最初のページはセクションのサブセクションとして管理され、独自の属性を持つことができます。 + + +* **左右のページを個別に設定**: セクションの左ページと右ページで異なる属性を設定することができます。この属性がチェックされていると、セクションの左ページ/右ページはサブセクションとして管理され、それぞれ独自の属性を持つことができます。 + + +* **カラム**コマンド: セクションに対してカラムの数とプロパティを定義することができます。これらのオプションは以下に詳細な説明があります。 +* **ヘッダー** と **フッター** コマンド: これらのオプションを使用すると個別のヘッダーとフッターを定義することができます。これらのオプションは以下に詳細な説明があります。 +* **マージン** / **パッディング** / **境界線** / **背景**: これらの属性は各セクションに対して個別に設定が可能です。これらの属性のより詳細な情報については、*4D Write Pro属性*の記事を参照してください。 + +### ヘッダーとフッターの挿入 + +それぞれのセクションには固有のヘッダーとフッターをつけることができます。ヘッダーとフッターはページビューモードが**ページ**のときのみ表示されます。 + +有効化されたオプションによって、ひとつのセクションにつき最大3つまでヘッダーとフッターを定義することが可能です: + +* 最初のページ +* 左ページ +* 右ページ + +ヘッダーまたはフッターを作成する手順は以下の通りです: + +1. まずドキュメントが**ページ**ビューモードであることを確認してください。 +2. 目的のセクションのヘッダーまたはフッターエリアをダブルクリックして、編集モードに入ります。 + * ヘッダーエリアはページの上部にあります: +  + * フッターエリアはページの下部にあります: +  + +スタティックなコンテンツが入力すると、その入力した内容は各ページのセクションにて自動的に繰り返されます (ただし最初のページが別設定の場合には、そこには反映されません)。 + + + +[ST INSERT EXPRESSION](../../commands/st-insert-expression) コマンドを使用することで、ページ番号やページ数などの動的なコンテンツを挿入することができます (より詳細な情報については、*式の挿入*の段落を参照してください)。 + +**注:** [WP Get header](../commands/wp-get-header) と [WP Get footer](../commands/wp-get-footer) といった特定のコマンドを使用することで、フッターやヘッダーのをプログラミングによって管理することができます。 + +セクションのヘッダーとフッターが定義できたら、コンテキストメニューを使用してそれらの属性を設定することができます: + + + +**マージン**、**パッディング**、**境界線**、そして**背景**属性についてのより詳細な情報については、*4D Write Pro属性*の章を参照してください。 + +コンテキストメニューの**ヘッダーを削除**あるいは**フッターを削除**コマンドを選択すると、ヘッダーまたはフッターの定義全体 (コンテンツと属性) を削除することができます。 + +### 互換性 + +4D Write Proは、4D Writeプラグインから変換されたドキュメントのヘッダーとフッターも(固定長の高さで)扱うことができます。 + +4D Writeプラグインのヘッダーとフッターから引き続きサポートされ変換される式とプロパティは、以下の通りです: + +* ページ番号とページ数変数 +* 個別の最初のページ +* 個別の左/右ページ + +## Rulers + +水平ルーラーは、4D Write Proの全てのビューモードで利用可能で、以下のような特徴を持ちます: + +* メモリはcm、mm、inch、あるいはptのうち、4D Write Proドキュメント内で定義されているカレントのレイアウト単位に応じたものになります。単位は、コンテキストメニュー、あるいは wk layout unit 属性を使用して変更することができます。 +* 最初の行のインデント記号 +* 左の段落マージン記号 +* 右の段落マージン記号 +* タブはルーラーの下の端に表示 +* 左と右のページマージンを表す視覚的なカラーコントラスト + +垂直ルーラーはページモードでのみ利用可能で、以下のような特徴を持ちます: + +* メモリはcm、mm、inch、あるいはptのうち、4D Write Proドキュメント内で定義されているカレントのレイアウト単位に応じたものになります。単位は、コンテキストメニュー、あるいは wk layout unit 属性を使用して変更することができます。 +* 上と下のページマージンを表す視覚的なカラーコントラスト + +ルーラーの表示状態は、標準アクション(*4D Write Pro標準アクションの使用* 参照)か、あるいは4D Write Proエリアのコンテキストメニュー内の**水平ルーラーを表示**あるいは**垂直ルーラーを表示**をチェックする/チェックを外すことで変更可能です: + + + +**注:** 特定の4D Write Pro エリアプロパティを使用することで、ルーラーのデフォルトの表示状態を定義することができます(*ビュープロパティの設定* の章を参照してください)。 + +### テキストのマージンとインデントを調整する + +マージン、インデント、そしてタブの位置は、それぞれに対応する記号をクリックしてドラッグすることで変更することができます: + + + +これらの記号の上にマウスをホバーさせたとき、カーソルは変わってそれが移動できることを表します。ドラッグ中は垂直のガイドラインが表示されます: + + + +複数の段落が選択されているとき、マージンあるいはインデント記号をドラッグした場合にはそのマージンとインデントは選択されている全ての段落に適用されます。これらの記号をShiftキーを押しながらドラッグした場合には、選択された段落内でのインデント間・マージン間の現在の間隔を維持します。 + +#### 水平ルーラー + +水平ルーラーの、対応する記号をクリックしたりドラッグしたりすることで、左右のマージン、インデント、タブ位置などを変更することができます: + + + +これらの記号の上をマウスでホバーすると、カーソルは形を変えてそれが移動可能であることを示し、またドラッグ中は水平なガイドラインが表示されます: + + + +複数の段落が選択されている時、マージンあるいはインデントの記号をドラッグすると、そのマージンあるいはインデントは選択された段落全体に対して適用されます。**Shift** キーを押しながら記号をドラッグすると、選択されている段落でのインデントとマージンの間の既存の距離が維持されます。 + +#### 垂直ルーラー + +垂直ルーラーを使用すると、上と下のマージンを変更することができます。マウスをマージンの端にホバーすると、カーソルは形を変えてそれが移動可能であることを示し、またドラッグ中は垂直なガイドラインが表示されます: + + + +このアクションを使用すると、ページの上と下の余白、またはドキュメントの本文とヘッダーとフッターの間の間隔を変更することができます。 + +### タブの管理 + +水平ルーラーのコンテキストメニューを使用して、タブの作成、変更、削除をすることができます: + + + +タブを作成するには、水平ルーラーを右クリックしてそのタイプをコンテキストメニューから選択してください。単一の左クリックは自動的にデフォルトの左タブを作成します。既存のタブを右クリックすることで、コンテキストメニューを使用してそのタブのタイプを変えることもできます。 + +**タブを削除**は既存のタブを右クリックした場合にのみ使用可能です。また、タブを水平ルーラーエリアの外へとドラッグすることで削除することもできます。 + +:::note 注 + +* タブは、[WP SET ATTRIBUTES](../commands/wp-set-attributes)、[WP GET ATTRIBUTES](../commands/wp-get-attributes)、あるいは[WP RESET ATTRIBUTES](../commands/wp-reset-attributes) コマンドとwk tab default および wk tabs セレクターを使用することでプログラムで定義することも可能です。 +* 小数点揃えに関しては、4D Write Pro は右からみて最初のドットまたはカンマ文字を小数点区切りとして認識します。このデフォルトの設定はwk tab decimal separator セレクターを使用して変更することができます。 + +::: + +#### タブリーダー文字を定義する + +タブの前にくる文字(リーダー文字)は、既定の5つの文字から選択するか、使用する特定の文字を指定することで定義する事ができます。既定の文字とは以下のとおりです: + +* なし (何も文字が表示されない - *デフォルト*) +* .... (点) +* \--- (破線) +* \_\_ (アンダースコア) +* \*\*\* (アスタリスク) + +リーダー文字は必ずタブの前に表示され、テキストの方向(左から右、あるいは右から左)に従います。[WP SET ATTRIBUTES](../commands/wp-set-attributes) 、[WP GET ATTRIBUTES](../commands/wp-get-attributes) 、および[WP RESET ATTRIBUTES](../commands/wp-reset-attributes) コマンドと`wk leading` と `wk tab default` または `wk tabs` セレクターを使用することでプログラミングによる定義も可能ですし、水平ルーラーのコンテキストメニューからユーザーインターフェース経由で定義することも可能です(以下参照)。 + + + +**その他...**が選択された場合、カスタムのリーダー文字を定義可能なダイアログが表示されます。 + +### マルチカラムルーラー + +ドキュメントあるいはセクションに対して二つ以上のカラムが定義されている時、水平ルーラーは各カラムに対するそれぞれの特定のエリアを表示します: + + + +**注:** マルチカラム機能は、**埋め込み**ビューモードでは利用できません。 + +### On After Edit イベント + +どの種類のタブやマージンコントロールでも、それらが(ドラッグあるいはコンテキストメニューを使用して)移動、追加、削除されたときには、4D Write Proエリアフォームオブジェクトに対して[`On After Edit`](../../Events/onAfterEdit.md) フォームイベントがトリガーされます。 + +## Columns + +4D Write Pro ではドキュメント内にカラムを管理することができます。カラムは最も左のカラムから最も右のカラムへと順番につながっています。言い換えると、テキストを入力していくとき、テキストは左にあるカラムを埋めていき、そのあとすぐ右にあるカラムへと続き、それがページの終わりに達するまで続いていきます。ページの終わりまで達すると、テキストは次のページへと続いていきます。ページ設定のバランスをとるために、4D Write Pro ではかカラムブレークを挿入することができます。 + + + +カラムはドキュメントレベル(ドキュメント全体に表示される)、あるいはセクションレベル(各セクションはそれぞれ独自のカラム設定を持つことができる)において定義することができます。 + +**注:** カラムは**ページビュー**モードと**下書きビュー**モードにおいてのみサポートされます(**埋め込み**ビューモードでは表示されません)。また[WP EXPORT DOCUMENT](../commands/wp-export-document) コマンドを使用して.docx フォーマットへと書き出すことができますが、HTML またはMIME HTML フォーマット(wk web page complete フォーマット)への書き出しはできません。 + +カラムは以下の方法を用いて設定することも可能です: + +* 4D Write Pro エリアコンテキストメニューの**カラム**サブメニュー +* 4D Write Pro [属性](../commands-legacy/4d-write-pro-attributes.md) +* 4D Write Pro [標準アクション](./using-4d-write-pro-standard-actions.md) + +カラムに対しては、以下のプロパティを設定/取得することができます: + +| **プロパティ** | **詳細** | *ドキュメント* **属性** | **標準アクション** | +| -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------- | ----------------------------------------------------- | +| カラム数 | ドキュメント/セクションに対して最大20個までカラムを定義可能です | wk column count | *columnCount* | +| カラム間隔 | カラム間の間隔をpt、インチ、cm単位で指定。全てのカラムに同じ間隔が適用されることに注意してください。各カラムの幅は、カラム数、ページ幅、そしてカラム間隔に応じて、4D Write Proによって自動的に算出されます。 | wk column spacing | *columnSpacing* | +| カラム幅 | (読込のみ属性) 各カラムのカレントの(自動算出された)幅。 | wk column width | \- | +| 区切り線スタイル、カラー、幅 | カラムの間には垂直のセパレーター(区切り線)を追加することができます。これらのオプションを使用すると、その区切り線のスタイル、カラー、幅をデザインすることができます。区切り線を削除するためには、スタイルから**なし**を選んでください。 | wk column rule style、wk column rule color、wk column rule width | *columnRuleStyle*、*columnRuleColor*、*columnRuleWidth* | +| ブレークを挿入 | カラムブレークを挿入 | wk column break、[WP INSERT BREAK](../commands/wp-insert-break)も参照してください | *insertColumnBreak* | +| カラムメニュー | カラムのサブメニューを作成します | \- | *columns* | + +### 複数カラムと単一カラムのセクションを持ったページの作成 + +ドキュメント内で*継続したセクションブレークの挿入* を使用することで、同じページ上に複数カラムのセクションと単一カラムのセクションを載せることができます。 + +例えば以下のようなドキュメントがある場合: + + + +継続したセクションブレークを挿入し、最初のセクションに対してカラムの数を2つに変更することができます: + + + +## ブックマーク + +4D Write Pro ではブックマークと呼ばれる、ドキュメントの一部において動的な参照を作成、使用することができます。ブックマークは、4D Write Pro ドキュメント内の特定の[範囲](./ranges.md)に名前付きで関連付けられる参照です。 + +ブックマークは動的なものであり、ユーザーにより範囲が移動、追加、または削除されると、ブックマークは自動的に更新され、ドキュメント内の同じ内容を継続して参照することができます。たとえば： + +- ドキュメント内のページ20にある "Hello world" を参照する"MyBM" という名前のブックマークを作成します。 +- 次に、ドキュメントの先頭に50ページを挿入します。 +- "MyBM" ブックマークを使用すると、今度はドキュメント内の70ページにある "Hello world" に自動的にアクセスできます。 + +ドキュメント内には無制限のブックマークを含むことができます。複数のブックマークが同じ範囲を参照することができ、ブックマークの範囲は重なり合うことがあります。ただし、ドキュメント内の各ブックマーク名は一意である必要があります。ブックマークは、[WP INSERER DOCUMENT](../commands/wp-insert-document-body) コマンドが使用されるとインポートされません（移行先のドキュメント内のブックマークは上書きされません）。 + +一度作成されたブックマークはドキュメント内に保存されます。ブックマークはドキュメントと共に保存され、複数のコマンドで操作することができます。 + +また、テンプレートドキュメントの一部としてブックマークを使用することができます。これらのパーツは、データベース内のデータを使用して自動的に組み立てられ、請求書やカタログなどの最終的なドキュメントを生成するのに役立ちます。 + +複数のコマンドを使用して、ブックマークを作成、削除、使用することができます： + +- [WP NEW BOOKMARK](../commands-legacy/wp-new-bookmark.md) はレンジから新しいブックマークを作成します。 +- [WP GET BOOKMARKS](../commands-legacy/wp-get-bookmarks.md) はドキュメント内で定義されている全てのブックマークを取得します。 +- [WP Bookmark range](../commands-legacy/wp-bookmark-range.md) は既存のブックマークからレンジを取得します。 +- [WP DELETE BOOKMARK](../commands-legacy/wp-delete-bookmark.md) はブックマークを削除します。 + +## Links + +4D Write Pro では、レンジ（テキスト、ピクチャーなど）や要素（表、本文、フッターなど）を含めるほぼすべてを含むドキュメント全体にハイパーリンクを割り当てることができます。たとえば、ドキュメントの画像に対してハイパーリンクを設定できます。4D Write Pro ドキュメントが HTML にエクスポートされた場合、ユーザーはその画像をクリックして、リンク先のページを開くことができます。 + +ハイパーリンクは、4D Write Pro ドキュメント内で **Ctrl+クリック**（Windows）または **Cmd+クリック**（macOS）操作をすることで簡単にアクティブ化できます。 + +4D Write Pro は以下のリンクタイプをサポートします: + +| リンクのタイプ | 詳細 | +|----------------|------| +| `url` | Web ページあるいは任意のドキュメントのリンク。実行時には関連づけられたアプリケーションが開始されます。4D Write Pro ドキュメント (`.4wp`, `.4w7`) への URL リンクを活性化すると、エリアの 4D Write Pro ドキュメントが置き換えられます。
(*) [OPEN URL](../../commands-legacy/open-url.md) コマンドと同じ動作です。 | +| `bookmark` | ドキュメント内のブックマークへのリンクです | +| `method` | リンクがアクティブになると 4D メソッドが実行されます（実行されるのはあらかじめ登録されているメソッド [SET ALLOWED METHODS](../../commands/set-allowed-methods.md) に限られます）。 | + +ハイパーリンクは以下のコマンドで管理することができます: + +- [WP SET LINK](../commands-legacy/wp-set-link.md) を使用して、ターゲットオブジェクトの指定用にリンクを挿入 +- [WP Get links](../commands-legacy/wp-get-links.md) を使用して、ターゲットオブジェクト内のすべてのリンクのコレクションとして取得 + +:::note + +注: リンクは属性として扱われるため、`wk link url` 定数を用いて [WP SET ATTRIBUTES](../commands/wp-set-attributes) および [WP GET ATTRIBUTES](../commands/wp-get-attributes) コマンドで定義・取得することができます。けれども、通常は [WP SET LINK](../commands-legacy/wp-set-link.md) や [WP Get links](../commands-legacy/wp-get-links.md) の使用が推奨されます。これらは自動的に URL としてリンクをエンコード／デコードします。[WP GET ATTRIBUTES](../commands/wp-get-attributes) コマンドを使用してリンクを読み取るとき、ターゲットオブジェクトが複数のリンクを含む場合は、最初のリンク文字列のみが返されます。 + +::: + +たとえば、ユーザーが選択したテキストを Web サイトへの URL リンクに変換したい場合: + + + +次のように書きます: + +```4d +$range:=WP Get selection(*;"WParea") +WP SET LINK($range;New object("url";"http://www.4d.com")) +``` + + + +ターゲットオブジェクトからリンクを除去するためには、以下のように書きます: + +```4d +$range:=WP Get selection(*;"WParea") +WP SET LINK($range;New object("url";"http://www.4d.com")) +``` +または + +```4d +$range:=WP Get selection(*;"WParea") +WP SET LINK($range;New object("url";"http://www.4d.com")) +``` + +**注:** *$range* がリンク全体を含んでいない場合、リンクは短縮されますが完全に削除されるわけではありません。 + +## オブジェクト(フォーム)テーマのコマンドの使用 + +以下の[オブジェクト（フォーム）](../../commands/theme/Objects_Forms.md)テーマの4Dコマンドは、4D Write Proのフォームオブジェクトをサポートします： + +| コマンド | 補足 | +|---------|------| +| OBJECT DUPLICATE | | +| OBJECT Get auto spellcheck / OBJECT SET AUTO SPELLCHECK | | +| OBJECT Get border style / OBJECT SET BORDER STYLE | | +| OBJECT Get context menu / OBJECT SET CONTEXT MENU | | +| OBJECT GET COORDINATES / OBJECT SET COORDINATES | | +| OBJECT Get data source / OBJECT SET DATA SOURCE | | +| OBJECT GET DRAG AND DROP OPTIONS / OBJECT SET DRAG AND DROP OPTIONS | | +| OBJECT Get enabled / OBJECT SET ENABLED | | +| OBJECT Get enterable / OBJECT SET ENTERABLE | | +| OBJECT GET EVENTS / OBJECT SET EVENTS | | +| OBJECT Get focus rectangle invisible / OBJECT SET FOCUS RECTANGLE INVISIBLE | | +| OBJECT Get font / OBJECT SET FONT | カレントセレクションがあればそこに適用 | +| OBJECT Get font size / OBJECT SET FONT SIZE | カレントセレクションがあればそこに適用 | +| OBJECT Get font style / OBJECT SET FONT STYLE | カレントセレクションがあればそこに適用 | +| OBJECT Get horizontal alignment / OBJECT SET HORIZONTAL ALIGNMENT | カレントセレクションがあればそこに適用。4D Write Proエリアの [wk justify](../../constants.md#wk-justify) 定数をサポート | +| OBJECT GET RESIZING OPTIONS / OBJECT SET RESIZING OPTIONS | | +| _o OBJECT SET COLOR | カレントセレクションがあればそこに適用 | +| OBJECT GET RGB COLORS / OBJECT SET RGB COLORS | カレントセレクションがあればそこに適用 | +| OBJECT Get type | | +| OBJECT Get vertical alignment / OBJECT SET VERTICAL ALIGNMENT | 段落の垂直方向の行揃え。段落の高さが段落のテキストの高さより高い場合にのみ効力を発揮します。 | +| OBJECT Get visible / OBJECT SET VISIBLE | | +| OBJECT Is styled text | trueを返します | +| OBJECT MOVE | | +| OBJECT GET SUBFORM CONTAINER SIZE | | +| OBJECT Get name | | +| OBJECT Get pointer | | + +上記にないOBJECTコマンドはそれぞれ Write Proエリアに対しては使用できません。 diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/ak_400.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/ak_400.png new file mode 100644 index 00000000000000..03ddd799fa0a3a Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/ak_400.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/ak_700.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/ak_700.png new file mode 100644 index 00000000000000..67de2c6ccbeac1 Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/ak_700.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/comment.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/comment.png new file mode 100644 index 00000000000000..7bc9233ea63c89 Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/comment.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/header_title_olv.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/header_title_olv.png new file mode 100644 index 00000000000000..96e9102ce17d7b Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/header_title_olv.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/link1.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/link1.png new file mode 100644 index 00000000000000..37389843e8f050 Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/link1.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/link2.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/link2.png new file mode 100644 index 00000000000000..a49860493ce8e7 Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/link2.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2584929.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2584929.en.png new file mode 100644 index 00000000000000..03a90f0aa6ff33 Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2584929.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2584938.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2584938.en.png new file mode 100644 index 00000000000000..45c3f9773eea02 Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2584938.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2646292.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2646292.en.png new file mode 100644 index 00000000000000..2f6dd9ff7667f9 Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2646292.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2646294.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2646294.en.png new file mode 100644 index 00000000000000..c5706f5b23244e Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2646294.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2878453.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2878453.en.png new file mode 100644 index 00000000000000..8d0366c92cd553 Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2878453.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994900.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994900.en.png new file mode 100644 index 00000000000000..cae8f054a00ad2 Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994900.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994904.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994904.en.png new file mode 100644 index 00000000000000..cd70790beb1915 Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994904.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994907.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994907.en.png new file mode 100644 index 00000000000000..2623c1d996e42d Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994907.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994910.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994910.en.png new file mode 100644 index 00000000000000..320ddf239ac86c Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994910.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994913.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994913.en.png new file mode 100644 index 00000000000000..61613bf845f8c9 Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994913.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994942.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994942.en.png new file mode 100644 index 00000000000000..01f531e6cb591c Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994942.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994945.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994945.en.png new file mode 100644 index 00000000000000..07c3f9f10eb2d5 Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994945.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994956.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994956.en.png new file mode 100644 index 00000000000000..78bbcbb797cc5c Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994956.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994958.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994958.en.png new file mode 100644 index 00000000000000..75d6dd97fc625c Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994958.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994965.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994965.en.png new file mode 100644 index 00000000000000..276bf3df53d508 Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994965.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2995027.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2995027.en.png new file mode 100644 index 00000000000000..1aa8745413d65b Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2995027.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3033006.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3033006.en.png new file mode 100644 index 00000000000000..ad7e034e246705 Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3033006.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3033008.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3033008.en.png new file mode 100644 index 00000000000000..51f1aa5c128b59 Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3033008.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3071271.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3071271.en.png new file mode 100644 index 00000000000000..e7f020cc979f5e Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3071271.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3106228.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3106228.en.png new file mode 100644 index 00000000000000..230e44dbbb561b Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3106228.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3133340.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3133340.en.png new file mode 100644 index 00000000000000..36424d5d26322e Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3133340.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3307937.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3307937.en.png new file mode 100644 index 00000000000000..fb12b681bed355 Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3307937.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3307941.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3307941.en.png new file mode 100644 index 00000000000000..0016bc2e11049d Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3307941.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3308424.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3308424.en.png new file mode 100644 index 00000000000000..17c545dcd5e7cc Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3308424.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3513503.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3513503.en.png new file mode 100644 index 00000000000000..eddf97544e0575 Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3513503.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3513505.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3513505.en.png new file mode 100644 index 00000000000000..5e8669f5c2aace Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3513505.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3514201.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3514201.en.png new file mode 100644 index 00000000000000..cfcd01019f70bb Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3514201.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3541581.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3541581.en.png new file mode 100644 index 00000000000000..8d2321c8b19748 Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3541581.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3626363.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3626363.en.png new file mode 100644 index 00000000000000..823fcf7c97fbcb Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3626363.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3751849.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3751849.en.png new file mode 100644 index 00000000000000..df240b64e8c0c9 Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3751849.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3752166.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3752166.en.png new file mode 100644 index 00000000000000..40ec61e14638df Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3752166.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3752176.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3752176.en.png new file mode 100644 index 00000000000000..1b09211ea8ac30 Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3752176.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3893246.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3893246.en.png new file mode 100644 index 00000000000000..84c289b866e8e6 Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3893246.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3893248.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3893248.en.png new file mode 100644 index 00000000000000..c21d5b60eeb195 Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3893248.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101161.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101161.en.png new file mode 100644 index 00000000000000..661c944356118b Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101161.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101210.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101210.en.png new file mode 100644 index 00000000000000..52d6d286b37274 Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101210.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101242.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101242.en.png new file mode 100644 index 00000000000000..b72796fcb066a9 Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101242.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101252.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101252.en.png new file mode 100644 index 00000000000000..596879ef24e051 Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101252.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101267.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101267.en.png new file mode 100644 index 00000000000000..0d3e10a91e6847 Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101267.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4619596.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4619596.en.png new file mode 100644 index 00000000000000..0c0a886b53349f Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4619596.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4619694.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4619694.en.png new file mode 100644 index 00000000000000..4ace1703dab061 Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4619694.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4619865.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4619865.en.png new file mode 100644 index 00000000000000..e708853ddf2c4c Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4619865.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4687892.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4687892.en.png new file mode 100644 index 00000000000000..d6702bd121d3bc Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4687892.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5562054.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5562054.en.png new file mode 100644 index 00000000000000..dee167c5ccf7c3 Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5562054.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5562058.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5562058.en.png new file mode 100644 index 00000000000000..f84f46638756cb Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5562058.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5761667.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5761667.en.png new file mode 100644 index 00000000000000..a6e16bcd3e31bf Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5761667.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5761669.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5761669.en.png new file mode 100644 index 00000000000000..6f56866e06cff7 Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5761669.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5761671.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5761671.en.png new file mode 100644 index 00000000000000..d2b933e6253bd5 Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5761671.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5761673.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5761673.en.png new file mode 100644 index 00000000000000..eef0da9b30d61f Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5761673.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5761675.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5761675.en.png new file mode 100644 index 00000000000000..f21fa89866c9ef Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5761675.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5761677.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5761677.en.png new file mode 100644 index 00000000000000..b6b82029e3bdaa Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5761677.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5859437.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5859437.en.png new file mode 100644 index 00000000000000..8a546866502013 Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5859437.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5907013.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5907013.en.png new file mode 100644 index 00000000000000..e233c502a77cb2 Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5907013.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5907021.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5907021.en.png new file mode 100644 index 00000000000000..bcbe548297f87d Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5907021.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5907023.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5907023.en.png new file mode 100644 index 00000000000000..6eba7f2baedff6 Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5907023.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5907026.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5907026.en.png new file mode 100644 index 00000000000000..d526c51578eb27 Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5907026.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5907030.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5907030.en.png new file mode 100644 index 00000000000000..964245707b6717 Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5907030.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5941073.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5941073.en.png new file mode 100644 index 00000000000000..66f10af3210774 Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5941073.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6013182.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6013182.en.png new file mode 100644 index 00000000000000..c5b95111dd2fc2 Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6013182.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6014414.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6014414.en.png new file mode 100644 index 00000000000000..1454f02b49f34c Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6014414.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6014426.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6014426.en.png new file mode 100644 index 00000000000000..5430cc882d6f13 Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6014426.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6014429.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6014429.en.png new file mode 100644 index 00000000000000..12cb8442c5f68c Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6014429.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6022144.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6022144.en.png new file mode 100644 index 00000000000000..ab1d4670b16d55 Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6022144.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6131919.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6131919.en.png new file mode 100644 index 00000000000000..d8b2b0f013f901 Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6131919.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6236360.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6236360.en.png new file mode 100644 index 00000000000000..8a1ada936554a5 Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6236360.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6260026.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6260026.en.png new file mode 100644 index 00000000000000..25b899cdd7ca87 Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6260026.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6260033.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6260033.en.png new file mode 100644 index 00000000000000..d8271cd06a6220 Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6260033.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6260036.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6260036.en.png new file mode 100644 index 00000000000000..a93bbc2deb6580 Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6260036.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6421031.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6421031.en.png new file mode 100644 index 00000000000000..f338bd44caeb38 Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6421031.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6421340.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6421340.en.png new file mode 100644 index 00000000000000..a00a64fa003fe5 Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6421340.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6421342.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6421342.en.png new file mode 100644 index 00000000000000..e7bbdb0445e7dc Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6421342.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6421344.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6421344.en.png new file mode 100644 index 00000000000000..b1da7d4f717589 Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6421344.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6421356.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6421356.en.png new file mode 100644 index 00000000000000..e19848f65d2951 Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6421356.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6434575.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6434575.en.png new file mode 100644 index 00000000000000..b98b7a71deb16b Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6434575.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6434579.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6434579.en.png new file mode 100644 index 00000000000000..232ad5653b5bdf Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6434579.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6434721.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6434721.en.png new file mode 100644 index 00000000000000..199e62f81ef736 Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6434721.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6434723.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6434723.en.png new file mode 100644 index 00000000000000..480da0bfc5f80f Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6434723.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6434756.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6434756.en.png new file mode 100644 index 00000000000000..ffdcce4bd30899 Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6434756.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6441966.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6441966.en.png new file mode 100644 index 00000000000000..e6b76b3b690664 Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6441966.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6856159.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6856159.en.png new file mode 100644 index 00000000000000..18f093b69da71c Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6856159.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6856163.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6856163.en.png new file mode 100644 index 00000000000000..0c3c6665e834d8 Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6856163.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict7014959.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict7014959.en.png new file mode 100644 index 00000000000000..a667cee2e6696a Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict7014959.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict7148443.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict7148443.en.png new file mode 100644 index 00000000000000..ab64da522a20a6 Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict7148443.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict7148495.en.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict7148495.en.png new file mode 100644 index 00000000000000..499af8e3737b08 Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict7148495.en.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/poweredby4D_web.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/poweredby4D_web.png new file mode 100644 index 00000000000000..fbb7fefffac38d Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/poweredby4D_web.png differ diff --git a/i18n/ja/docusaurus-plugin-content-docs/version-20-R10/API/SessionClass.md b/i18n/ja/docusaurus-plugin-content-docs/version-20-R10/API/SessionClass.md index 316a8c305181c2..c0cea72e07c162 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/version-20-R10/API/SessionClass.md +++ b/i18n/ja/docusaurus-plugin-content-docs/version-20-R10/API/SessionClass.md @@ -136,7 +136,7 @@ $isGuest:=Session.isGuest() // $isGuest は true OTP トークンについてのより詳細な情報については、[こちらの章](../WebServer/sessions.md#セッショントークンotp)を参照して下さい。 -デフォルトで、*lifespan* 引数が省略された場合、トークンはセッションの[`.idleTimeOut`](#idletimeout) と同じ有効期限を持って作成されます。 *lifespan* 引数に秒単位の値を渡すことで、カスタムのタイムアウトを設定することができます(最小値は10秒間で、それより小さい値が渡された場合には*lifespan* は10にリセットされます)。 Web ユーザーセッションを復元するために失効したトークンを使用した場合、それは無視されます。 +デフォルトで、*lifespan* 引数が省略された場合、トークンはセッションの[`.idleTimeOut`](#idletimeout) と同じ有効期限を持って作成されます。 You can set a custom timeout by passing a value in seconds in *lifespan*. Web ユーザーセッションを復元するために失効したトークンを使用した場合、それは無視されます。 返されたトークンは、サードパーティアプリケーションや他のWebサイトとのやり取りで使用することでセッションを安全に特定することができます。 例えば、セッションOTP トークンは支払いアプリケーションなどにおいて使用することができます。 diff --git a/i18n/ja/docusaurus-plugin-content-docs/version-20-R10/Concepts/operators.md b/i18n/ja/docusaurus-plugin-content-docs/version-20-R10/Concepts/operators.md index 6797c5d2ea76b5..bd6ca82039610d 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/version-20-R10/Concepts/operators.md +++ b/i18n/ja/docusaurus-plugin-content-docs/version-20-R10/Concepts/operators.md @@ -90,7 +90,10 @@ $a+=2 // $a=3 | | Time \*= Number | Number | `$t1*=5 //$t1:=$t1*5` | | | Picture \*= Number | Picture | `$p1*=5 //$p1:=$p1*5 ($p1 を 5倍にリサイズします)` | -これらの演算子は、あらゆる [代入可能な式](quick-tour.md#代入可-vs-代入不可の式) に適用できます (オブジェクトのプロパティやコレクション要素としてのピクチャーを除く)。 +These operators apply on any [assignable expressions](quick-tour.md#assignable-vs-non-assignable-expressions) except: + +- pictures as object properties or collection elements, +- array index variables. "代入先 複合代入演算子 値" と "代入先 := 代入先 演算子 値" は、厳密には等価ではありません。なぜなら、前者の場合、代入先 (変数・フィールド・オブジェクトプロパティ・コレクション要素) は一度しか評価されないからです。 たとえば、`getPointer()-+=1` のような式では、`getPointer` メソッドは一度だけ呼び出されます。 diff --git a/i18n/ja/docusaurus-plugin-content-docs/version-20-R10/WritePro/commands/wp-get-attributes.md b/i18n/ja/docusaurus-plugin-content-docs/version-20-R10/WritePro/commands/wp-get-attributes.md index 381411a7e83020..2d2100d89d3e36 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/version-20-R10/WritePro/commands/wp-get-attributes.md +++ b/i18n/ja/docusaurus-plugin-content-docs/version-20-R10/WritePro/commands/wp-get-attributes.md @@ -20,7 +20,8 @@ displayed_sidebar: docs ## 説明 -**WP Get attributes** コマンドは、4D Write Pro レンジ、ヘッダー、本文、フッター、表、あるいはドキュメント内の、任意の属性の値を返します。 このコマンドを使用することで、4D Write Pro の次のようなあらゆる内部属性にアクセスすることができます: 文字、段落、ドキュメント、表、画像。 +**WP Get attributes** コマンドは、4D Write Pro レンジ、ヘッダー、本文、フッター、表、あるいはドキュメント内の、任意の属性の値を返します。 このコマンドを使用することで、4D Write Pro の次のようなあらゆる内部属性にアクセスすることができます: 文字、段落、ドキュメント、表、画像。 + *targetObj* 引数には、以下のいずれかを渡すことができます: diff --git a/i18n/ja/docusaurus-plugin-content-docs/version-20-R9/API/SessionClass.md b/i18n/ja/docusaurus-plugin-content-docs/version-20-R9/API/SessionClass.md index ec900578af50ef..3782ec993a7381 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/version-20-R9/API/SessionClass.md +++ b/i18n/ja/docusaurus-plugin-content-docs/version-20-R9/API/SessionClass.md @@ -133,7 +133,7 @@ $isGuest:=Session.isGuest() // $isGuest は true OTP トークンについてのより詳細な情報については、[こちらの章](../WebServer/sessions.md#セッショントークンotp)を参照して下さい。 -デフォルトで、*lifespan* 引数が省略された場合、トークンはセッションの[`.idleTimeOut`](#idletimeout) と同じ有効期限を持って作成されます。 *lifespan* 引数に秒単位の値を渡すことで、カスタムのタイムアウトを設定することができます(最小値は10秒間で、それより小さい値が渡された場合には*lifespan* は10にリセットされます)。 Web ユーザーセッションを復元するために失効したトークンを使用した場合、それは無視されます。 +デフォルトで、*lifespan* 引数が省略された場合、トークンはセッションの[`.idleTimeOut`](#idletimeout) と同じ有効期限を持って作成されます。 You can set a custom timeout by passing a value in seconds in *lifespan*. Web ユーザーセッションを復元するために失効したトークンを使用した場合、それは無視されます。 返されたトークンは、サードパーティアプリケーションや他のWebサイトとのやり取りで使用することでセッションを安全に特定することができます。 例えば、セッションOTP トークンは支払いアプリケーションなどにおいて使用することができます。 diff --git a/i18n/ja/docusaurus-plugin-content-docs/version-20-R9/Concepts/operators.md b/i18n/ja/docusaurus-plugin-content-docs/version-20-R9/Concepts/operators.md index 6797c5d2ea76b5..bd6ca82039610d 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/version-20-R9/Concepts/operators.md +++ b/i18n/ja/docusaurus-plugin-content-docs/version-20-R9/Concepts/operators.md @@ -90,7 +90,10 @@ $a+=2 // $a=3 | | Time \*= Number | Number | `$t1*=5 //$t1:=$t1*5` | | | Picture \*= Number | Picture | `$p1*=5 //$p1:=$p1*5 ($p1 を 5倍にリサイズします)` | -これらの演算子は、あらゆる [代入可能な式](quick-tour.md#代入可-vs-代入不可の式) に適用できます (オブジェクトのプロパティやコレクション要素としてのピクチャーを除く)。 +These operators apply on any [assignable expressions](quick-tour.md#assignable-vs-non-assignable-expressions) except: + +- pictures as object properties or collection elements, +- array index variables. "代入先 複合代入演算子 値" と "代入先 := 代入先 演算子 値" は、厳密には等価ではありません。なぜなら、前者の場合、代入先 (変数・フィールド・オブジェクトプロパティ・コレクション要素) は一度しか評価されないからです。 たとえば、`getPointer()-+=1` のような式では、`getPointer` メソッドは一度だけ呼び出されます。 diff --git a/i18n/ja/docusaurus-plugin-content-docs/version-20-R9/WritePro/commands/wp-get-attributes.md b/i18n/ja/docusaurus-plugin-content-docs/version-20-R9/WritePro/commands/wp-get-attributes.md index 381411a7e83020..2d2100d89d3e36 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/version-20-R9/WritePro/commands/wp-get-attributes.md +++ b/i18n/ja/docusaurus-plugin-content-docs/version-20-R9/WritePro/commands/wp-get-attributes.md @@ -20,7 +20,8 @@ displayed_sidebar: docs ## 説明 -**WP Get attributes** コマンドは、4D Write Pro レンジ、ヘッダー、本文、フッター、表、あるいはドキュメント内の、任意の属性の値を返します。 このコマンドを使用することで、4D Write Pro の次のようなあらゆる内部属性にアクセスすることができます: 文字、段落、ドキュメント、表、画像。 +**WP Get attributes** コマンドは、4D Write Pro レンジ、ヘッダー、本文、フッター、表、あるいはドキュメント内の、任意の属性の値を返します。 このコマンドを使用することで、4D Write Pro の次のようなあらゆる内部属性にアクセスすることができます: 文字、段落、ドキュメント、表、画像。 + *targetObj* 引数には、以下のいずれかを渡すことができます: diff --git a/i18n/ja/docusaurus-plugin-content-docs/version-20/Concepts/operators.md b/i18n/ja/docusaurus-plugin-content-docs/version-20/Concepts/operators.md index a22ff94edb91a5..82d858e3c5095b 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/version-20/Concepts/operators.md +++ b/i18n/ja/docusaurus-plugin-content-docs/version-20/Concepts/operators.md @@ -93,7 +93,9 @@ $a+=2 // $a=3 | | Time *= Number | Number | `$t1*=5 //$t1:=$t1*5` | | | Picture *= Number | Picture | `$p1*=5 //$p1:=$p1*5 ($p1 を 5倍にリサイズします)` | -これらの演算子は、あらゆる [代入可能な式](quick-tour.md#代入可-vs-代入不可の式) に適用できます (オブジェクトのプロパティやコレクション要素としてのピクチャーを除く)。 +These operators apply on any [assignable expressions](quick-tour.md#assignable-vs-non-assignable-expressions) except: +- pictures as object properties or collection elements, +- array index variables. "代入先 複合代入演算子 値" と "代入先 := 代入先 演算子 値" は、厳密には等価ではありません。なぜなら、前者の場合、代入先 (変数・フィールド・オブジェクトプロパティ・コレクション要素) は一度しか評価されないからです。 たとえば、`getPointer()->+=1` のような式では、`getPointer` メソッドは一度だけ呼び出されます。 diff --git a/i18n/ja/docusaurus-plugin-content-docs/version-20/Project/architecture.md b/i18n/ja/docusaurus-plugin-content-docs/version-20/Project/architecture.md index bc6ad77523edab..97a6d67fbe791b 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/version-20/Project/architecture.md +++ b/i18n/ja/docusaurus-plugin-content-docs/version-20/Project/architecture.md @@ -15,7 +15,7 @@ title: プロジェクトのアーキテクチャー - `Project` - `DerivedData` - `Sources` - - `Trash` + - `ゴミ箱` - `Resources` - `Settings` - `userPreferences.username` @@ -117,7 +117,7 @@ title: プロジェクトのアーキテクチャー **注:** 拡張子 .4dm のファイルは、4Dメソッドのコードをテキスト形式で格納しており、 ソース管理ツールに対応しています。 ソース管理ツールに対応しています。 -### `Trash` +### `ゴミ箱` プロジェクトから削除されたメソッドやフォームがあれば、Trash フォルダーにはそれらが格納されます。 たとえば、つぎのフォルダーが格納されている場合があります: diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/API/SessionClass.md b/i18n/pt/docusaurus-plugin-content-docs/current/API/SessionClass.md index eee345529baf43..eb3431c0ae30be 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/API/SessionClass.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/API/SessionClass.md @@ -136,7 +136,7 @@ A função `.createOTP()` cria um Para mais informações sobre os tokens OTP, consulte [esta seção](../WebServer/sessions.md#session-token-otp). -Por padrão, se o parâmetro *lifespan* for omitido, o token será criado com o mesmo tempo de vida que o [`.idleTimeOut`](#idletimeout) da sessão. Você pode definir um tempo limite personalizado passando um valor em segundos em *lifespan* (o valor mínimo é 10 segundos, *lifespan* é redefinido para 10 se um valor menor for passado). Se um token expirado for usado para restaurar uma sessão de usuário Web, ele será ignorado. +Por padrão, se o parâmetro *lifespan* for omitido, o token será criado com o mesmo tempo de vida que o [`.idleTimeOut`](#idletimeout) da sessão. You can set a custom timeout by passing a value in seconds in *lifespan*. Se um token expirado for usado para restaurar uma sessão de usuário Web, ele será ignorado. O token retornado pode então ser usado em trocas com aplicativos ou sites de terceiros para identificar a sessão com segurança. Por exemplo, o token de sessão OTP pode ser usado com um aplicativo de pagamento. diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/Concepts/operators.md b/i18n/pt/docusaurus-plugin-content-docs/current/Concepts/operators.md index 5dbb7ed4bddc3f..9494e03c367619 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/Concepts/operators.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/Concepts/operators.md @@ -90,7 +90,10 @@ São suportados os seguintes operadores de atribuição compostos: | | Time \*= Number | Number | `$t1*=5 //$t1:=$t1*5` | | | Picture \*= Number | Imagem | `$p1*=5 //$p1:=$p1*5 (redimensionar $p1 por 5)` | -Esses operadores se aplicam a quaisquer [expressões atribuíveis](quick-tour.md#assignable-vs-non-assignable-expressions) (exceto imagens como propriedades de objetos ou elementos de coleções). +These operators apply on any [assignable expressions](quick-tour.md#assignable-vs-non-assignable-expressions) except: + +- pictures as object properties or collection elements, +- array index variables. A operação "source `operator` value" não é estritamente equivalente a "source := source `operator` value" porque a expressão que designa a fonte (variável, campo, propriedade de objeto, elemento de coleção) é avaliada apenas uma vez. Por exemplo, em expressões como `getPointer()->+=1` o método `getPointer` é chamado apenas uma vez. diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/Notes/updates.md b/i18n/pt/docusaurus-plugin-content-docs/current/Notes/updates.md index 597fa3302173f6..52bb9597209d8f 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/Notes/updates.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/Notes/updates.md @@ -29,7 +29,6 @@ Leia [**O que há de novo no 4D 21**](https://blog.4d.com/en-whats-new-in-4d-21/ - Web user sessions are now returned by [`Process activity`](../commands/process-activity.md). - The [`HIGHLIGHT TEXT`](../commands/highlight-text) command is now supported in the context of subforms. - #### Mudanças de comportamento :::caution Index rebuild @@ -42,11 +41,6 @@ Leia [**O que há de novo no 4D 21**](https://blog.4d.com/en-whats-new-in-4d-21/ - Web server: the support of deprecated `4DSYNC/` and `4DCGI/` URLs is removed. No specific processing is done on these URLs anymore. - Web user sessions are now returned by [`Process activity`](../commands/process-activity.md). -#### Mudanças de comportamento - - - Web services (SOAP): when [scalable sessions](../WebServer/sessions.md#enabling-web-sessions) are enabled, web services now run in [**preemptive processes**](../Develop/preemptive.md) in compiled mode. Make sure your SOAP code is thread-safe. - - Web server: the support of deprecated `4DSYNC/` and `4DCGI/` URLs is removed. No specific processing is done on these URLs anymore. - - Web user sessions are now returned by [`Process activity`](../commands/process-activity.md). ## 4D 20 R10 diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/WritePro/user-legacy/defining-a-4d-write-pro-area.md b/i18n/pt/docusaurus-plugin-content-docs/current/WritePro/user-legacy/defining-a-4d-write-pro-area.md new file mode 100644 index 00000000000000..1b96419cd61912 --- /dev/null +++ b/i18n/pt/docusaurus-plugin-content-docs/current/WritePro/user-legacy/defining-a-4d-write-pro-area.md @@ -0,0 +1,258 @@ +--- +id: defining-a-4d-write-pro-area +title: Criar uma area 4D Write Pro +displayed_sidebar: docs +--- + + + +## Arrastar e Soltar + +Para configurar as propriedades arrastar e soltar para suas áreas 4D Write Pro, é necessário seleciar as opções apropriadas no tema "Action" na lista de Propriedades: + + + +Áreas 4D Write Pro suporta dois modos arrastar e soltar: + +* **Modo personalisado:** apenas as opções "Arrastável" e "Soltável" estão marcadas. +Neste modo, pode selecionar texto e começar a movê-lo. O método objeto é chamado com o evento On Begin Drag Over , e assim pode definir a ação soltar usando o modo personalisado. +* **Modo Automatico**: as opções "Arrastável", "Soltável", "Arraste automático" e "Soltado automático" estão marcadas +Neste modo, pode automativamente mover ou copiar (aperte a tecla **Alt/Option**) o texto selecionado. O evento On Begin Drag Over não é ativado. + +**Nota:** Selecionar apenas as opções "Arraste automático" e "Soltado automático" não terá efeito na área 4D Write Pro area. + +## Propriedades de Vista + +As propriedades de vista do documento estão diretamennte disponíveis na lista Propriedades das áreas 4D Write pro para permitier que defina como um documento 4D Write será exibido como padrão nesta área. Estas propriedades permitem que personalise, por exemplo, se os documentos 4D Write Pro são exibidos da mesma maneira que serão impressos, ou como gerados pelo navegador. Pode estabelecer diferentes vistas do mesmo documento 4D Write Pro no mesmo formulário. + +**Nota:** Configurações de Vista podem ser gerenciadas dinamicamente usando os comandos [WP SET VIEW PROPERTIES](../commands/wp-set-view-properties) e [WP Get view properties](../commands/wp-get-view-properties). + +Configurações de vista de documento são gerenciadas através de itens específicos no tema **Aparência** da lista de propriedades de objetos de formulário 4D Write Pro.: + + + +* **Resolução**: Estabelece a resolução de tela para os conteúdos de área 4D Write Pro. Como padrão, é estabelecido em **72 dpi (Mac OS)**, que é a resolução padrão para formulários 4D em todas as plataformas. Estabelecer esta propriedade para Automático faz com que oa geração do documento seja diferente entre as plataformas Mac Os e Windows. Estabelecer um valor de dpi específico faz com que a geração do documento seja a mesma nas plataformas Mac OS e Windows. +* **Zoom**: Estabelece a porcentagem do zoom para exibir os conteúdos da área 4D Write Pro. O normal é 100%. +* **Modo de Vista**: Estabelece o modo para exibir o documento 4D Write Pro na área formulário. Três valores estão disponíveis: + * **Página** (padrão): o modo de vista mais completo que inclui limites de página, orientação, margens, quebra de página, cabeçalhos, rodapés, etc. Para saber mais veja o parágrafo *Propriedades de visualização de página*. + * **Rascunho**: modo rascunho com propriedades de documento básicas + * **Embebido**: modo de vista adequado para áreas embebidas. Não exibe margens, cabeçalhos, rodapés, bordas de página, etc. + Este modo também pode ser usado para produzir uma vista de página do tipo Web (se também selecionar a resolução de 96 dpi e a opção **Show HTML WYSIWYG**). + + **Nota:** A propriedade **Modo de vista** é usada apenas para geração na tela. Em quanto a configurações de impressão, regras específicas de geração são usadas automaticamente (ver *Imprimir documentos 4D Write Pro*). +* **Mostrar page frame**: Exibe ou esconde a borda da página quando o modo de vista for estabelecido como "Página". O normal é escondido. +* **Mostrar referências**: Exibe todas as expressões 4D inseridas no documento como referências. Quando esta opção não estiver marcada (padrão) as expressões 4D são exibidas como valores. Quando inserir um campo ou expressão 4D, 4D Write Pro computa e exibe o valor atual. Se quiser saber que campos ou expressões estão sendo exibidas, marque esta opção. As referências do campo ou expressão vão aparecer em seu documento, com um fundo cinza. +Por exemplo, se inserir a data atual junto com o formato, a data é exibida: + +Se marcar a opção **Mostrar referências**, a referência é exibida: + +**Nota:** expressões 4D podem ser inseridas usando o comando [ST INSERT EXPRESSION](../../commands/st-insert-expression). +* **Mostrar cabeçalhos e rodapés**: Exibe ou esconde os cabeçalhos e rodapés quando o modo de página estiver estabelecido como "Página" (exibido como padrão). Para saber mais, veja . +* ****Mostrar fundo**: Exibe/esconde tanto as imagens de fundo quando a cor de fundo (padrão é exibido) +* ****Mostrar caracteres escondidos**: Exibe ou esconde caracteres invisíveis (padrão é escondido). +* ****Mostrar HTML WYSIWYG**: Ativa ou desativa a vista HTML WYSIWYG, na qual qualquer atributo avançado 4D Write Pro que não forem compatíveis com todos os navegadores serão removidos (padrão é desaqtivado). +* **Mostrar régua horizonta**l: horizontal. Para saber mais sobre as réguas nas áreas 4D Write Pro, consulte *Manejar réguas*. +* **Mostrar régua vertical**: mostra/oculta a régua vertical quando o documento estiver em modo Página. Para saber mais sobre as réguas nas áreas 4D Write Pro, consulte *Manejar réguas*. +* Mostrar imágens vaziaws ou não compatíveis: mostra/oculta um retângulo negro para s imagens que não podem ser carregadas ou calculadas (imagens vazias ou em um formato não compatível). Para saber mais veja *Imagens vazias*. +* Mostrar a fonte da fórmula como símbolo: mostra o texto fonte das formulas como  símbolos quando as expressões são mostradas como referencias (ver acima). Mostrar as fórmulas como símbolos faz com que os documentos de modelo sejam mais compactos e mais wysiwyg. + + +## Menu contextual + +Se a propriedade **Menu contextual** está selecionada por uma área 4D Write Pro (ver *Criar uma área 4D Write Pro*), um menu contextual completo está disponível para os usuários em modo Aplicação: + + + +Este menu oferece acesso a todas as funcionalidades de 4D Write Pro. + +## Selecionar o modo de visualização + +Os documentos 4D Write Pro podem ser visualizados em três modos de vista de página: + +* **Rascunho**: modo rascunho com propriedades básicas +* **Página**: modo "vista imprimir" (novo em 4D v15 R5) +* **Embebido**: modo adequado para áreas embebidas, não exibe margens, cabeçalhos, rodapés, bordas de página, etc +Este modo pode ser usado para produzir output do tipo Web (se selecionar também a resolução de 96 dpi e a opção **HTML WYSIWYG**). + +O modo de visualização pode ser configurardo utilizando a área de menu pop-up: + + + +**Nota:** o modo de visualização da página não são armazenadas com o documento. + +Para áreas embebidas em formulários 4D, o modo vista pode ser também definido como padrão usando a lista Propriedades. Neste caso, o modo de vista é armazenado como uma propriedade do objeto de formulário 4D Write Pro (para saber mais, veja o parágrafo *Configurar propriedades de Vista*). + + + + +## Ações padrão + +A interface de usuário de áreas 4D Write Pro pode ser manejada através de um amplo conjunto de **ações padrão**. As ações padrão podem ser atribuidas a: + +* comandos de menu, disponíveis através da **barra de menu** ou do comando [Dynamic pop up menu](../../commands/dynamic-pop-up-menu) +* list items, listas pop up ou drop down, menus pop up hierárquicos +* botões, check boxes +* ou executados pelo comando [INVOKE ACTION](../../commands/invoke-action). + +Quando são atribuidos aos objetos de interface, as ações padrão manejam a ativação/desativação de objeto em função de contexto. Para mais informação, consulte a seção *Ações padrões*. + +Dois tipos de ações estão disponíveis para áreas 4D Write Pro: + +* As ações específicas 4D Write Pro, que só podem ser utilizadas com áreas 4D Write Pro, +* *[Outras ações](#other-actions)*, incluido as fontes, expressões, corretor ortográfico e ações de edição, que podem ser utilizadas com as áreas 4D Write Pro e as outras áreas 4D (ver [*Ações padrões*](#standard-actions)). + +### Ações 4D Write Pro + +**Notas:** + +* As ações que mostram um menu/lista só podem ser associadas aos comandos de menu ou aos objetos pop-up/listas suspensas e menus pop-up hierárquicos (ver *Submenu*). +* Check boxes e 3D check boxes devem ser associadas com ações de estado, tais como "section/differentFirstPage" ou "visibleHorizontalRuler". Três opções de estado são suportadas com check boxes padrão apenas. +* um status de ação de seção é sempre igual ao status atual de seção selecionada (estado herdado se o atributo for herdado da seção pai ou de um atributo padrão) já que deve refletir o status de seção selecionada (o status que é aplicado atualmente para a seção). Entretanto, modificar o atributo de seção com uma ação padrão vai sobrepujar o atributo de seção selecionado. +* *Submenu*: Quando usado sem parâmetros e associados ao comando menu, um pop-up/lista drop down ou um objeto de menu hierárquico pop-up, essas ações exibem um submenu/lista automática. Por exemplo, se atribuir a ação "backgroundColor" a um comando de menu, selecionando este comando de menu na execução vai exibir os itens de submenu de Cor de Fundo. Se atribuir a ação "zoom" a um menu hierárquico pop-up menu, vai conter automaticamente conter uma lista de valores pré-definidos de zoom. Note que essas ações não podem ser atribuídas aos botões. +* *showDialog*:Adicionar a string "/showDialog" ao nome de ação permite a exibição da caixa de diálogo padrão associada para a ação. Por exemplo, pode ser usado "paragraph/styleSheet/showDialog" para abrir o diálogo de input que permite a entrada de um novo nome de folha de estilo. . + +| Ação | Sintaxe | Disponível com | Descrição | +|---|---|---|---| +| anchorHorizontalAlign | {image \| textBox}/anchorHorizontalAlign?value={left \| center \| right} | Image, Textbox, Submenu | Defines the horizontal alignment of the element, relative to the anchorOrigin for images/text boxes in page, or to the layout box for images/text box in embedded mode. This action will reset the horizontal offset to 0. (not enabled for inline images). | +| anchoring | {image \| textBox}/anchoring | Submenu | Default submenu with anchor settings actions for images or text boxes | +| anchorLayout | image/anchorLayout?value={front \| behind \| wrapTopBottom \| wrapSquareLeft \| wrapSquareRight \| wrapSquareLargest \| wrapSquare \| inline}
textBox/anchorLayout?value={front \| behind \| wrapTopBottom \| wrapSquareLeft \| wrapSquareRight \| wrapSquareLargest \| wrapSquare} | Image, Textbox, Submenu | Defines the anchor layout type for an image or a text box. Can be used to transform an inline image to an anchored image, or the reverse. Note: If an image is moved from an anchored mode to inline, the image is inserted at the beginning of the current selected text. "inline" value is not supported for text boxes | +| anchorOrigin | {image \| textBox}/anchorOrigin?value={paper-box \| header-box \| footer-box} | Image, TextBox, Submenu | Defines the area relative to the absolute position of an anchored image or text box. If the element is relative to the header-box/footer-box which is not visible on a page, the element is not displayed. This action will reset horizontal and vertical offsets to 0. Page mode only, not enabled for inline images. | +| anchorPage | {image \| textBox}/anchorPage?value={all \| current \| currentSubSection} | Image, TextBox, Submenu | Defines the page(s) where the selected image or text box is displayed (not enabled for inline images). Page mode only. | +| anchorSection | {image \| textBox}/anchorSection?value={all \| current} | Image, TextBox, Submenu | Defines the section(s) where the selected image or text box is displayed. (not enabled for inline images). Page mode only. | +| anchorVerticalAlign | {image \| textBox}/anchorVerticalAlign?value={top \| center \| bottom} | Image, TextBox Submenu | Defines the vertical alignment of the image or text box, relative to the anchorOrgin for an image or text box in page, or to the layout box for an image or text box in embedded mode. This action will reset the vertical offset to 0 (not enabled for inline images). Note: See "verticalAlign" action for the vertical alignment inside the text box | +| avoidPageBreakInside | {paragraph/}avoidPageBreakInside | Paragraph | | +| background | {doc \| paragraph \| image \| textBox \| section \| header \| footer \| table \| row \| column \| cell/}background | Document, Paragraph, Image, TextBox, Section, Header, Footer, Table, Row, Column, Cell, Submenu | For menu commands only. Default submenu for all background attributes. | +| backgroundClip | {doc \| paragraph \| image \| textBox \| section \| header \| footer \| table \| row \| column \| cell/}backgroundClip?value={paper-box \| border-box \| padding-box \| content-box} | Document, Paragraph, Image, TextBox, Section, Header, Footer, Table, Row, Column, Cell, Submenu | Changes target background clipping box (default target is paragraph). Paper-box targets document and section only. | +| backgroundColor | {doc \| paragraph \| image \| textBox \| section \| header \| footer \| table \| row \| column \| cell/}backgroundColor?value={
cell/merge | Paragraph, Cell | Used with paragraphs: merges paragraphs. Used with cells: merges the selected cells. | +| minHeight | {paragraph \| image/}minHeight?value=
cell/split | Paragraph, Cell | Used with paragraph: splits paragraph. Used with cells: splits the selected cells (only cells that have been already merged may be split). | +| styleSheet | {paragraph \| image/}styleSheet?value={1<=number<=number of target style sheets} | Paragraph, Image, Submenu, showDialog | Applies Nth stylesheet to the selected target elements. With dialog, new stylesheet will use current attributes from the first selected target. (default target is paragraph) Ex: styleSheet?value=1 //apply first paragraph style sheet to the selected paragraphs and set it as paragraph stylesheets. | +| styleSheets | {paragraph \| image/}styleSheets | Paragraph, Image, Submenu | Default submenu for editing target stylesheets. | +| tabDecimalSeparator | tabDecimalSeparator?value={point \| comma \| pointOrComma \| system} | Document, Submenu | Defines the character used as decimal separator by decimal tabulations. | +| tableAlign | tableAlign?value={left \| center \| right}
or
table/tableAlign?value={left \| center \| right} | Table, Submenu | Specifies horizontal alignment for a table. | +| table/avoidPageBreakInside | table/avoidPageBreakInside | Table | Allows/disallows page breaks inside tables. Disabled if: the current selection does not contain at least one table the table is in a header or a footer | +| table/bottomCarryOverRow | table/bottomCarryOverRow | Table | Toggles between display/not display of carry-over rows (see Carry-over rows). | +| textAlign | textAlign?value={left \| right \| center \| justify \| initial} | Paragraph | Paragraph text alignment (initial=use right for rtl or left for ltr direction). | +| textBox | textBox | Submenu | Submenu with all actions available for the focused/selected text box | +| textBox/remove | textBox/remove | TextBox | Removes the selected text box | +| textIndent | textIndent?value=
Esta expressão retorna o mesmo tipo de valor que a expressão **This.tableData**. | +| Em uma quebra de linha | This.breakItems | Collection or Entity selection | Itens da coleção ou seleção de entidade exibida nas linhas entre: a quebra de linha atual e a quebra de linha no mesmo nível (no inicio da página) se as quebras forem exibidas antes da linha repetida. a quebra atual e a quebra no mesmo nivel (ou o final da tabela) se a quebra de linha for exibida na mesma linah repetida. | + +Em outros contextos, essas expresões retornam *undefined*. + +**Nota:** Para saber mais, veja inserção de fórmula [WP INSERT FORMULA](../commands/wp-insert-formula). + +##### Trabalhar com uma tabela de datasource + +Quando preencher uma tabela desde uma fonte de dados, as filas são criadas automaticamente quando calcular as referências. As linhas podem ser inseridas ou eliminadas, editar o conteúdo das células, mudar o estilo, etc: + + + +Entretanto, lembre que se a fonte de dados da tabela voltar a ser calculada, qualquer modificação realizada nas linhas calculadas (exceto na primeira linha, ver a seguir) é perdida. Por outro lado, como a primeira linha é a linha da planilha, qualquer modificação realizada nesta linha se propagará a todas as linhas se voltar a calcular a fonte de dados da tabela. O mesmo é válido para quebra de linhas, qualquer modificação feita em quebras de linhas é perdida, exceto para quebras de linha template (que estao localizadas no final ou começo da tabela). + +Por exemplo + + + +Depois de voltar a calcular as expressões: + + + +Quando o cursor se inserir em uma célula de uma tabela preenchida com uma fonte de dados, aparece um ícone no canto esquerdo junto com um conselho que mostra a informação: + + + +Quando as fórmulas são mostradas como referências ou quando se guarda o documento, só são mostradas/salvas a primeira fila como planilha (se as fórmulas não estiverem congeladas). + +Quando congelar as fórmulas, a tabela se converte em uma tabela padrão se restabelece a fonte de dados da tabela. + +**Nota:** a ação padrão *freezeExpressions* não recalcula as fórmulas. \ No newline at end of file diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/WritePro/user-legacy/importing-4d-write-documents.md b/i18n/pt/docusaurus-plugin-content-docs/current/WritePro/user-legacy/importing-4d-write-documents.md new file mode 100644 index 00000000000000..8cee5749bfef5c --- /dev/null +++ b/i18n/pt/docusaurus-plugin-content-docs/current/WritePro/user-legacy/importing-4d-write-documents.md @@ -0,0 +1,227 @@ +--- +id: importing-4d-write-documents +title: Importar documentos 4D Write +displayed_sidebar: docs +--- + +#### + +Uma das principais funcionalidades do novo 4D Write Pro é a capacidade de importar e converter documentos 4D Write Pro existentes. Isto lhe permitirá migrar as aplicações que se baseiam no plug-in 4D Write. + +**Nota de compatibilidade**: + +* só os documentos 4D Write da última geração ("4D Write v7") são suportados. +* Copiar-colar de um documento 4D Write document para uma área 4D Write Pro não é suportada no momento. Importar um documento 4D Write pode apenas ser feito usando os comandos de linguagem 4D Write Pro. +* Retornos de carro (CR) em fórmulas se comportam diferente em 4D Write do que em 4D Write Pro. Em 4D Write, eles sempre são interpretados como quebras de parágrafo, mas em 4D Write Pro são interpretados como quebras de linha por padrão. Para manter CR em fórmulas como quebras de parágrafos em documentos importados 4D Write, depois da conversão, use: +```4d + WP SET ATTRIBUTES(wp;wk break paragraphs in formulas;wk true) +``` + +Para saber mais veja *Gestão de fórmulas*. + +#### Como importar um documento 4D Write + +Os objetos 4D Write Pro oferecem duas maneiras de importar documentos 4D Write: + +* Para os arquivos 4D Write Pro armazenados no disco, se utiliza o comando [WP Import document](../commands/wp-import-document), +* Para as áreas 4D Write armazenadas em campos BLOB, se utiliza o comando [WP New](../commands/wp-new). + +Para mais informação, consulte a descrição destes comandos. + +#### Que propriedades se conservam de 4D Write? + +Para facilitar a migração desde o plug-in 4D Write a 4D Write Pro, queremos suportar tantas funcionalidades 4D Write como seja possível em objetos 4D Write Pro. + +Este parágrafo mostra as propriedades do plug-in 4D Write que se recuperam em uma área 4D Write Pro depois de uma importação com os comandos [WP Import document](../commands/wp-import-document) ou [WP New](../commands/wp-new). + +Tenha em conta no entanto, que há algumas diferenças, que não se consideram como bugs. Isto deve ser, por exemplo, a fonte pré determinada utilizada em 4D Write Pro para vinhetas, ou pequenas conversões no tipo Sublinhado. + +##### Informação do documento + +| **Plug-in** **4D Write** | **4D Write Pro** | +| ------------------------ | --------------------------------------------------------- | +| Criação data e hora | Disponível | +| Modificação data e hora | Disponível | +| Bloqueado | Não disponível (utilizar a propriedade objeto só leitura) | +| Título | Disponível | +| Tema | Disponível (só texto plano) | +| Autor | Disponível | +| Empresa | Disponível | +| Notas | Disponível | + +##### Parâmetros de visualização do documento + +| **Plug-in** **4D Write** | **4D Write Pro** | +| ---------------------------------- | ---------------------------------------------------------------------------- | +| Vista modo página | Não importado (utilizar o modo de vista Documento/Página no menu contextual) | +| Vista regras | Não disponível | +| Vista marcos | Não disponível | +| Vista cabeçalho | Não disponível | +| Vista rodapé | Não disponível | +| Vista cabeçalho de primeira página | Não disponível | +| Vista rodapé de primeira página | Não disponível | +| Vista imagens | Não disponível | +| Vista HScrollbar | Não importado (utilize a propriedade de objeto deslocável hor.) | +| Vista VScrollbar | Não importado (utilize a propriedade de objeto deslocável vert.) | +| Vista invisible characters | Não disponível | +| Vista referências | Não importado (utilize [ST SET OPTIONS](../../commands/st-set-options)) | +| Vista separadores de coluna | Não disponível | +| Vista H Splitter | Não disponível | +| Vista V Splitter | Não disponível | +| Vista Wysiwyg | Não disponível | +| Vista zoom | Não importado (utilize Document/Zoom no menu contextual) | + +##### Parâmetros do documento + +| **Plug-in** **4D Write** | **4D Write Pro** | +| ------------------------ | -------------------------------------------------------------------- | +| Unidade | Não importado (use unidades de documento/medidas no menu contextual) | +| Linguagem | Não disponível | +| Contagem de colunas | disponível (a partir de v17) | +| Espaço entre colunas | disponível (a partir de v17) | +| Viúvas e órfãos | disponível | +| Aba por padrão | Disponível | +| Aba Líder | Disponível | +| Cor URL | Não disponível | +| Cor de URL visitado | Não disponível | + +**Nota:** O separador do sistema (como retornado por [GET SYSTEM FORMAT](../../commands/get-system-format)) é usado como separador decimal para tabulação decimal. Pode mudar esse parâmetro usando o comando [WP SET ATTRIBUTES](../commands/wp-set-attributes). + +##### Parâmetros de paginação de documentos + +| **Plug-in** **4D Write** | **4D Write Pro** | +| ----------------------------------------------------------------- | ---------------- | +| Largura de página | disponível | +| Altura página | disponível | +| Número primeira página | disponível | +| Primeira página cabeçalho rodapés diferentes | disponível | +| Página cabeçalho Esquerda e direita e rodapé de página diferentes | disponível | +| Encadernação | disponível | +| Páginas opostas | disponível | +| Margens página | Disponível | +| Cabeçalho margem superior | disponível | +| Cabeçalho margem inferior | disponível | +| Rodapé de página margem superior | disponível | +| Rodapé de página margem inferior | disponível | +| Primeira página margem superior | disponível | +| Primeira página margem inferior | disponível | +| Cabeçalho primeira página margem superior | disponível | +| Cabeçalho primeira página margem inferior | disponível | +| Rodapé de página primeira página margem superior | disponível | +| Rodapé de página primeira página margem inferior | disponível | +| Primeira página é correta | disponível | + +##### Parâmetros de impressão de documentos + +| **Plug-in 4D Write** | **4D Write Pro** | +| -------------------- | ---------------- | +| Classe de papel | Não disponível | +| Paisagem | Não disponível | +| Largura | Não disponível | +| Altura | Não disponível | +| Margens de usuário | Não disponível | +| Escala | Não disponível | +| Resolução X | Não disponível | +| Resolução Y | Não disponível | + +##### Imagens + +**Notas de compatibilidade**: + +Os modos de visualização de imagens são importadas automaticamente a partir de 4D Write Pro v19 R2, utilizando [WP Import document](../commands/wp-import-document). Pode restaurar o comportamento anterior (todas as imagens se escalam para ajuste) utilizando o atributo importDisplayMode. + + Windows imagens com o formato PICT de Mac OS são importadas mas não podem ser geradas em 4D Write Pro . Se quiser importar documentos que contenham imagens desse tipo, deve primeiro converter as imagens para outro formato, Lembre que o formato PICT é obsoleto e não deve mais ser usado (ver ). + +| **Plug-in** **4D Write** | **4D Write Pro** X (esquerda) | (& position :absolute) (para imagens em página unicamente) | +| --------------------------------------------- | ---------------------------------------------------------- | ---------------------------------------------------------- | +| Y (acima) | (& position :absolute) (para imagens em página unicamente) | | +| Largura | Disponível | | +| Altura | Disponível | | +| Número de página | Disponível (a partir de v16 R6) | | +| Atrás | Disponível (a partir de v16 R6) | | +| Não em primeira página | Disponível (a partir de v16 R6) | | +| Modo de visualização (escala a ajustar, etc.) | Disponível | | +| É uma expressão | Disponível para imagens inline(a partir de v16 R5) | | +| Conservar o tamanho | \]Não importado (automático em 4D Write Pro)l | | + +##### Propriedades de caracteres + +| **Plug-in** **4D Write** | **4D Write Pro (span)** | +| ------------------------------------------ | -------------------------------- | +| Itálica | Disponível | +| Negrita | Disponível | +| Tachado | Disponível | +| Sublinhado | Disponível | +| Sombra | Disponível | +| Exponente (superscript ou subscript) | Disponível | +| Maiúsculas ou pequenas maiúsculas | Disponível | +| Família de fonte | Disponível | +| Tamanho de fonte | Disponível | +| Cor texto | Disponível | +| Cor fundo de texto | Disponível | +| Cor sublinhado | Disponível | +| Cor tachado | Disponível | +| Cor sombra | Disponível | +| Propriedade usuário | Não disponível | +| Correção ortográfica (sintaxe e gramática) | Não importada (propriedade área) | +| Aparência | Não disponível | +| Folha de estilo | Disponível a partir de 4D v18) | + +##### Propriedades parágrafos + +| **Plug-in** **4D Write** | **4D Write Pro** | +| ---------------------------------------- | ---------------- | +| Justificação | Disponível | +| Interlinear | Disponível | +| Vinhetas | Disponível | +| Margem esquerda | Disponível | +| Margem direita | Disponível | +| Indentar texto | Disponível | +| Estilo borde linha | Disponível | +| Cor borde linha | Disponível | +| Cor fundo borde | Disponível | +| Borde esquerdo | Disponível | +| Borde direito | Disponível | +| Borde superior e borde interior acima | Disponível | +| Borde inferior e borde interior inferior | Disponível | +| Espaço de borde | Disponível | +| Folha de estilo | Disponível | +| Tabulações | Disponível | + +##### Hyperlinks + +| **4D Write plug-in** | **4D Write Pro** | +| -------------------- | ------------------------------------------- | +| URL link | Disponível (\*) | +| 4D method link | disponível (\*\*) (a partir de v17 R5) | +| Open document link | Disponível (convertido a URL arquivo local) | + +* (\*) A partir de 4D v16 R4, URL links são convertidos a atributos editáveis. Para saber mais, veja *Manejar URLs*. +* (\*\*) Precisa adaptar os parâmetros recebidos dentro dos métodos chamados: + +| **Parâmetros** | **4D Write plug-in** | **4D Write Pro** | +| -------------- | ------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| $1 | Longint - 4D Write area reference | Text - nome área 4D Write Pro | +| $2 | Text - Link label | Object - Link description:.método - Nome do link de método. Deve ser permitido com o comando [SET ALLOWED METHODS](../../commands/set-allowed-methods). .parâmetro - valor de parâmetro de usuário passado ao método (se usado).range - Range da etiqueta de link. ver *Comandos de seleção de faixa* | +| $3 | Longint - User parameter (methodRef) | \- | + +##### Expressões 4D + +| **Plug-in** **4D Write** | **4D Write Pro** | +| ------------------------ | ---------------- | +| Expressão 4D | Disponível | +| Data e hora | Disponível | +| Expressão HTML | Não disponível\* | +| Expressão RTF | Não disponível | + +\*Use o comando [WP SET ATTRIBUTES](../commands/wp-set-attributes) com o atributo wk break paragraphs in formulas para transformar CR (retorno de carro) retornado pelas fórmulas em quebras de parágrafo no documento importado (quebra de linha como padrão). (Ver *Gestão de fórmulas*) + +\*\*pode ser importado como texto entre as tags **##htmlBegin##** e **##htmlEnd##** se usar a constante wk import html expressions as text. + +##### Dados de texto + +| **Plug-in** **4D Write** | **4D Write Pro** | +| ------------------------- | ---------------- | +| Dados de texto principais | Disponível | +| Dados de texto cabeçalho | Disponível | +| Dados de texto Rodapé | Disponível | \ No newline at end of file diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/WritePro/user-legacy/importing-and-exporting-in-docx-format.md b/i18n/pt/docusaurus-plugin-content-docs/current/WritePro/user-legacy/importing-and-exporting-in-docx-format.md new file mode 100644 index 00000000000000..30760203de7182 --- /dev/null +++ b/i18n/pt/docusaurus-plugin-content-docs/current/WritePro/user-legacy/importing-and-exporting-in-docx-format.md @@ -0,0 +1,191 @@ +--- +id: importing-and-exporting-in-docx-format +title: Exportar em formato docx +displayed_sidebar: docs +--- + +#### + +4D Write Pro pode importar e exportar documentos no formato .docx. Esse formato é compatível com aplicações de processamento de texto como Microsoft Word. + +**Nota de compatibilidade:** a compatibilidade para documentos 4D Write Pro exportados em formato .docx só está certificado para Microsoft Word 2010 e versões posteriores. As versões anteriores, em particular Microsoft Word 2007, podem ter problemas para abrir os documentos. + +#### Como importar .docx + +Os documentos no formato .docx podem ser importados com 4D Write Pro com o comando [WP Import document](../commands/wp-import-document). Para mais informações veja a descrição do comando. + +##### Mudanças de comportamenot + +Se a maioria dos parâmetros .docx são conservados, certos parâmetros são conhecidos por não terem compatibilidade ou por se comportarem diferentemente que em 4D Write Pro. Estes são os seguintes parâmetros: + +###### Alinhamento / Layout + +| **Configuração** | **Descrição** | +| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| Anchored text areas | áreas de texto ancoradas não são compatíveis. O conteúdo pode ser ignorado ou importado como texto inline (opção a estabelecer quando usar o comando [WP Import document](../commands/wp-import-document)). Só áreas de texto simples podem ser importadas. Áreas de texto ancoradas com texto ao redor ou com texto inline são ancoradas na layer superior. | +| Paragraph layout | Só layouts de texto ocidental são compatíveis. Estilo de parágrafos distribuidos, tailandês e asiático não são compatíveis. | +| Page Size | Tamanhos de página diferentes não são compatíveis. Só o tamanho da página da primeira seção é importado. | + +###### Background/Fundo + +| **Configurações** | **Descrição** | +| ----------------- | -------------- | +| Watermark | Não compatível | + +###### Expressões + +| **Configuração** | **Descrição** | +| ----------------- | -------------------------------------------- | +| MS Word equations | Não compatível. Os datos não são importados. | +| MS Word charts | Não compatível. Os dados não são importados. | + +###### Listas + +| **Configuração** | **Descrição** | +| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Listas hierárquicas | As listas multiniveles não são suportadas. As listas multinível são convertidas em listas de um só nível, por isso o aspecto da lista ou a numeração podem ser diferentes | + +###### Pictures / Imagens + +| **Configuração** | **Descrição** | +| -------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | +| DrawingML shapes | Só imagens simples DrawingML (inline ou ancoradas) são importadas. Formas complexas DrawingML não são compatíveis. | +| VML shapes or images | Não compatível. VML está obsoleto em MS Word e não deveria ser usado em documentos criados com MS Word 2010 ou anteriores. | +| 3D models | Não compatível, entretando a última imagem 2D renderizada ou o último modelo 3D renderizado podem ser importados se presentes no .docx. | +| SmartArt | Não compatível. | + +###### Referências/ Review + +| **Configuração** | **Descrição** | +| ---------------- | ----------------------------------------- | +| Comments | Não compatível. Conteúdo não é importado. | +| Footnotes | Não compatível. Conteúdo não é importado. | + +###### Spacing + +| **Configuração** | **Descrição** | +| ----------------------- | ------------------------------------------------------------------------------------------------------ | +| "At least" line spacing | Não compativel. Espaçamento de linha "At least" é converitdo para espaçamento de linha fixo (simples). | +| Fit text | Não compativel.. O estilo normal 4D Write Pro é usado. | + +###### Tabelas + +| **Configurações** | **Descrição** | +| ----------------- | ----------------------------------------------------- | +| Tables | Tabelas contíguas não são fusionadas automaticamente. | + +###### Texto + +| **Configuração** | **Descrição** | +| ---------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Themes | Temas texto não são importados. Se uma definição de cor ou fonte referenciar uma cor ou fonte em um tema, a última cor ou fonte computada serão usadas. Senão, a cor ou fonte definida no tema será usada. | + +##### Importar histórico + +Quando importar o formato .docx em um 4D Write Pro, um objeto log histórico é criado e incluido com o objeto documentos importados. Esse objeto pode ser encontrado com o atributo "importLog" (ou a constante wk import log) + +```4d + $myDoc:=WP Import document("test.docx") + if($myDoc#Null) + var $log : Object + $log:=$myDoc[wk import log] + End if +``` + +O objeto import log contém as propriedades abaixo: + +| Constante | Comentário | +| ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| wk import log | Objeto Log contendo informação sobre a operação de importação .docx. Propriedades são de apenas leitura e não podem ser estabelecidas:
| **Propriedade** | **Tipo** | **Descrição** | |
| status | Text | Estado da importação: successo - o documento é importado em 4D Write Pro erro - um documento 4D Write Pro é retornado | |
| developer | Collection | Coleção de objetos mensagem para desenvolvedores 4D Write Pro. | |
| \[ \].type | Text | O tipo de mensagem arquivada: informação avisos erros | |
| \[ \].message | Text | Mensagem sobre a operação de importação. | |
| user | Collection | Coleção de objetos mensagem para usuários 4D Write Pro. | |
| \[ \].type | Text | O tipo de mensagem arquivada: informação aviso | |
| \[ \].messageShort | Text | Mensagem curta sobre a operação de importação. | |
| \[ \].messageLong | Text | Mensagem longa sobre a operação de importação. |
**Tipo de Valor**: Inteiro longo *(valor para `wk type table row`)* | +| `wk column count` | `columnCount` | *(Atributo de faixa somente leitura)* Número total de colunas na faixa.
**Valor**: inteiro longo | +| `wk first column` | `firstColumn` | *(Atributo de faixa somente leitura)* Número da primeira coluna na faixa.
**Valor**: inteiro longo | +| `wk first row` | `firstRow` | *(Atributo de faixa somente leitura)* Número da primeira linha na faixa.
**Valor**: inteiro longo | +| `wk header row count` | `headerRowCount` | *(Leitura/Escrita)* Número de linhas da tabela com o atributo `wk header` definido como True.
O valor máximo é 5. Se passar um valor superior a 5, `wk header` se define como True só para as cinco primeiras linhas *(ver [Cabeçalho repetido](./handling-tables.md#repeated-headers))* | +| `wk row count` | `rowCount` | *(Atributo de faixa somente leitura)* Número total de linhas na faixa.
**Valor**: inteiro longo | +| `wk table` | `table` | *(Atributo apenas Leitura)* Tabela pai.
**Valor tipo**: Objeto | +| `wk table ID` | `tableID` | *(Atributo de faixa somente leitura)* ID da faixa da tabela pai.
**Valor**: String | + + + +Vários comandos lhe permitem definir faixas: + +- [WP Text range](../commands-legacy/wp-text-range.md): devolve uma nova faixa correspondente aos limites que passam como parâmetros. +- [WP Selection range](../commands-legacy/wp-selection-range): devolve uma nova faixa que corresponde à seleção usuário atual. +- [WP Picture range](../commands-legacy/wp-picture-range): devolve uma nova faixa que contém só as imagens. +- [WP Paragraph range](../commands-legacy/wp-paragraph-range): devolve uma nova faixa que contém só os parágrafos. +- [WP Table range](../commands-legacy/wp-table-range): devolve uma nova faixa que contém só as tabelas. + +Você pode obter informações sobre a posição de uma faixa em um documento (número da página, número da coluna…) usando o comando [WP Get position](../commands-legacy/wp-get-position). + + diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/WritePro/user-legacy/storing-4d-write-pro-documents-in-4d-object-fields.md b/i18n/pt/docusaurus-plugin-content-docs/current/WritePro/user-legacy/storing-4d-write-pro-documents-in-4d-object-fields.md new file mode 100644 index 00000000000000..c97a6f5a39d1c1 --- /dev/null +++ b/i18n/pt/docusaurus-plugin-content-docs/current/WritePro/user-legacy/storing-4d-write-pro-documents-in-4d-object-fields.md @@ -0,0 +1,180 @@ +--- +id: 4d-write-pro-documents +title: Documentos 4D Write Pro +displayed_sidebar: docs +--- + +## Formato de documento .4wp + +É possível salvar e reabrir documentos 4D Write Pro em disco e a partir de disco sem qualquer perda usando o formato nativo **.4wp**. + +O formato **.4wp** consiste de uma pasta zip cujo nome é o título do documento e cujos conteúdos são texto HTML e imagens: + +* texto HTML combina HTML normal com expressões 4D (que não são computadas) assim como etiquetas 4D especificas, +* imagens são armazenadas em uma pasta com o mesmo nome que o título do documento, do lado do arquivo HTML. + +Já que documentos .4wp são baseados em HTML, podem ser importados ou abertos em qualquer aplicação externa que suporta HTML. + +O formato de documento interno 4D Write Pro é uma extensão HTML proprietária, compatível comHTML5/XHTML5, mas que suporta um subconjunto de atributos HTML/CSS e etiquetas. Como resultado, apenas documentos HTML exportados por 4D Write Pro podem ser abertos por 4D Write Pro sem risco de perda de dados. Importar documentos HTML que foram criados externamente pode produzir erros. + +Para saber mais, [**baixe a lista de atributos 4D Write pro com definição associada como CSS style ou XHTML tag**](https://download.4d.com/Documents/Products%5FDocumentation/LastVersions/Line%5F19/4DWP-attributes-and-xhtml.pdf) em 4D Write Pro XHTML. + +### Compatibilidade com versões anteriores + +Sempre pode reabrir um documento .4wp com uma versão anterior de 4D Write Pro. Se conter atributos que foram adicionados em versões mais recentes, esses atribuos são apenas ignorados. Entretanto se salvar o documento, os atributos são removidos do documento e serão perdidos. + +## Armazenar os documentos 4D Write Pro nos campos objeto 4D + +Pode armazenar seus documentos 4D Write Pro automaticamente no arquivo de dados 4D. Se criar uma área 4D Write Pro em um formulário e criar um campo Objeto para armazenar os conteúdos da área, qualquer texto digitado na área é salvado automaticamente com cada registro quando o registro for validado. Pode então usar o comando [QUERY BY ATTRIBUTE](../../commands/query-by-attribute) para selecionar registros baseados no valor dos atributos internos. Pode também adicioanr e pesquisar seus próprios atributos com áreas 4D Write Pro. + +Esta seção descreve as seguintes propriedades: + +* Ligar o campo 4D Object à área 4D Write Pro em um formulário +* Configurar, obter e pesquisar atributos personalizados dos documentos 4D Write Pro armazenados usando os comandos de objeto padrão [OB SET](../../commands/ob-set), [OB Get](../../commands/ob-get), e [QUERY BY ATTRIBUTE](../../commands/query-by-attribute). + +### Atribuindo um campo 4D Object para uma área 4D Write Pro + +Para ligar uma área 4D Write Pro com um campo 4D Object, só precisa referenciar o campo na propriedade Variable Name da área. + +### Criar o campo Objeto na Estrutura + +Em sua estrutura de banco de dados, qualquer campo de Objeto 4D Object pode ser usado para armazenar documentos 4D Write Pro. Assim como qualquer campo Object, tem que definir, dependendo de suas necessidades: + +* o nome do campo, +* os atributos, tais como "Expose as REST resource," assim como o índice, +* a opção de armazenamento + + + +Estes parâmetros são padrão para campos Objeto. + +### Atribuindo a área 4D Write Pro para o campo + +Quando tiver definido um campo Objeto para armazenar seu documento 4D Write Pro, só precisa referenciar ele no formulário contendo a área. Pode usar qualquer tabela ou um formulário projeto. +No editor Formulário, entre o nome do campo usando a notação padrão "\[Table\]Field" na área **Variable Name** da lista de Propriedade para a área 4D Write Pro: + + + +Sua área 4D Write Pro é então associada com o campo, assegurando que seus conteudos serão salvados automaticamente com cada registro. Note que se não usar os botões automáticos 4D, terá que salvar a área manualmente usando os comandos 4D. + +### Usar atributos personalizáveis + +Quando as áreas 4D Write Pro forem armazenadas nos campos Objeto, pode salvar e ler qualquer atributo personalizado com o documento 4D Write Pro, tais como o nome do escritor, a categoria do documento ou qualquer informação adicional que achar útil. Pode então pesquisar qualquer atributo personalizável para selecionar registros que se enquadrem nos critérios. + +* Atributos personalizados não serão exportados com os comandos [WP EXPORT DOCUMENT](../commands/wp-export-document) ou [WP EXPORT VARIABLE](../commands/wp-export-variable). Eles tambèm seráo quando converter um campo de objeto 4D Write Pro para JSON com o comando [JSON Stringify](../../commands/json-stringify) (junto com os principais atributos de documento 4D Write Pro). + +Para estabelecer ou conseguir atributos personalizados, precisa usar os comandos padrão [OB Get](../../commands/ob-get) e [OB SET](../../commands/ob-set). + +Por exemplo, no método de formulário pode escrever: + +```4d + If(Form event code=On Validate) + [MyDocuments]My4DWP["myatt_Last edition by"]:=Current user + [MyDocuments]My4DWP.myatt_Category:="Memo" + [MyDocuments]My4DWP:=[MyDocuments]My4DWP //to record the edit + End if +``` + +ou: + +```4d + If(Form event code=On Validate) + OB SET([MyDocuments]My4DWP;"myatt_Last edition by";Current user) + OB SET([MyDocuments]My4DWP;"myatt_Category";"Memo") + End if +``` + +Também pode ler atributos personalizados de documentos: + +```4d + vAttrib:=[MyDocuments]My4DWP.myatt_Category +``` + + +ou: + +```4d + vAttrib:=OB Get([MyDocuments]My4DWP;"myatt_Category") +``` + +Se tiver salvo atributos personalizados 4D Write Pro em seu arquivo de dados, pode pesquisar estes atributos para criar uma seleção de registros contendo o valor apropriado do atributo. No exemplo abaixo, pode pesquisar a tabela contendo o campo Objeto para selecionar registros: + +```4d + QUERY BY ATTRIBUTE([MyDocuments];[MyDocuments]My4DWP;"myatt_Category";=;"Memo") + //seleciona todos os registros em MyDocuments cujo atributo personalizável "myatt_Category" tenha o valor "Memo" + //no campo de objeto My4DWP (ligado à área 4D Write Pro) +``` + +:::warning Sobre nomes de atributos personalizados + +Já que atributos personalizados têm o mesmo espaço de nomeação que atributos internos 4D Write Pro, recomenda-se que se use prefixo quando definir seus próprios nomes de atributo, para evitar conflitos entre atributos internos e personalizados. Nomes não prefixados são reservados para os atributos internos 4D Write Pro. Pode usar qualque prefixo personalizável (no exemplo acima foi usado "myatt\_" como prefixo). + +::: + +**Nota:** a partir de 4D v15 R4, os atributos internos de 4D Write Pro também são acessíveis por programação utilizando os comandos padrão [OB Get](../../commands/ob-get) e [OB SET](../../commands/ob-set), mas também utilizando [WP SET ATTRIBUTES](../commands/wp-set-attributes), [WP GET ATTRIBUTES](../commands/wp-get-attributes) e [WP RESET ATTRIBUTES](../commands/wp-reset-attributes). + +## Abrir e exportar documentos + +Nas aplicações 4D, os documentos, 4D Write Pro são criados importados e exportados por meio de comandos específicos que se encontram no tema **4D Write Pro** ([WP EXPORT DOCUMENT](../commands/wp-export-document), [WP EXPORT VARIABLE](../commands/wp-export-variable), [WP Import document](../commands/wp-import-document), [WP New](../commands/wp-new)). + +Também é possível [associar uma área 4D Write Pro com um campo Objeto](../user-legacy/defining-a-4d-write-pro-area.md#storing-4d-write-pro-documents-in-4d-object-fields) em um banco de dados. Desta maneira, cada documento 4D Write Pro é automaticamente salvo com o registro e armazenado nos dados do banco de dados. + +## Imprimir documentos 4D Write Pro + +Os documentos 4D Write Pro podem ser impressos de duas formas + +* como partes de formulários 4D +* como documentos independentes + +### Imprimindo documentos + +Imprimir uma área 4D Write Pro embebida em um formulário 4D é respaldada pelo sistema + +Pode imprimir objetos 4D Write Pro incluidos em qualquer tipo de [formulário 4D](../../FormEditor/forms.md) (projeto, tabela, input ou output) usando comandos de impressão comuns de 4D tais como [PRINT SELECTION](../../commands/print-selection) ou [PRINT RECORD](../../commands/print-record). + +A opção padronizada *Impressão tamanho variável* também é compatível (\*) com áreas 4D Write Pro, pérmitindo que maneje tamanho durante impressão. Quando esta opção for marcada, a margem (interior ou exterior) e margem superior são aplicadas apenas para a primeira página. As margens (interior e exterior) e a margem inferior são aplicadas apenas na última página. Propriedades de paginação do documento são ignoradas: controle de linhas viúvas e órfãs é desativado e quebras de página não são aplicadas (estas propriedades são usadas apenas para renderização na tela ou impressão do documento página por página. Quando a opção **Print Variable Frame** for selecionada, apenas objetos localizados acima da área de formulário serão impressos. Para saber mais, veja "*Impressão tamanho variável*" no manual Design Reference. + +(\*) Os comandos [Print object](../../commands/print-object) e [Print form](../../commands/print-form) não são compatíveis com esta opção. + +#### Modo de vista para impressão + +Qualquer que seja o modo de Vista para a área 4D Write Pro (ver *Configurar propriedades de Vista*), sempre será impresso no modo Embebido quanod usar um comando de impressão 4D tal como [Print form](../../commands/print-form). Neste caso, as configurações de aparência abaixo não são levadas em conta para os objetos de formulário 4D Write Pro: modo de vista Página (sempre "Embebido"), Mostrar cabeçalho, Mostra rodapé, mostrar borda da página (sempre "Não"), Mostrar caracteres ocultos (sempre "Não"). + +#### Exemplo + +O exemplo abaixo mostra o efeito da opção **Print Variable Frame** numa área 4D Write Pro area embebida no formulário de output padrão. O seguinte código é executado: + +```4d + ALL RECORDS([Movies]) + ORDER BY([Movies]Title) + PRINT SELECTION([Movies]) +``` + +* Com a opção Print Variable Frame **desmarcada** (off), terá o resultado abaixo: + +* Com a opção Print Variable Frame **marcada** (on), terá o resultado abaixo: + +*(sample text source: wikipedia)* + +### Imprimir documentos independentes + +A partir de 4D v15 R5, 4D Write Pro inclui novas funcionalidades de impressão. Utilizando estas funcionalidades padrão, poderá imprimir documentos 4D Write Pro independentes, assim como também controlar as opções de impressão padrão tais como formato, orientação ou números de página. + +#### Novos comandos 4D Write Pro + +Basicamente, dois comandos manejam a função de impressão 4D Write Pro: [WP PRINT](../commands/wp-print) e [WP USE PAGE SETUP](../commands/wp-use-page-setup). + +* [WP PRINT](../commands/wp-print) inicia um trabalho de impressão0 para o documento 4D Write Pro ou agrega o documento ao trabalho de impressão atual. +* [WP USE PAGE SETUP](../commands/wp-use-page-setup) modifica a configuração de página da impressora atual dos atributos de documento 4D Write Pro para o tamanho e orientação. + +**Notas** + +* Nas máquinas com Windows 7 ou Windows Server 2008 R2, tenha certeza de que a *atualização de plataforma para Windows 7* tenha sido instalado de maneira a que as funcionalidades de impressão sejam compatíveis. + +#### Comandos 4D atualizados + +Os comandos abaixo 4D suportam as funcionalidades de impressão 4D Write Pro: + +* [SET PRINT OPTION](../../commands/set-print-option) e [GET PRINT OPTION](../../commands/get-print-option): todas as opções são suportadas para documentos 4D Write Pro impressos por [WP PRINT](../commands/wp-print). Para Paper option e Orientation option, é mais eficiente chamar a [WP USE PAGE SETUP](../commands/wp-use-page-setup) para sincronizar facilmente estes atributos com a configuração do documento 4D Write Pro. Page range option (15) lhe permite definir a faixa de página a imprimir. +* [PRINT SETTINGS](../../commands/print-settings): permite estabelecer os ajustes de impressão para a impressora atual; se [WP PRINT](../commands/wp-print) for chamado depois, será utilizada a configuração de impressora modificada se foram modificados por diálogos de configuração de impressão (com exceção das márgens de diálogo de configuração de página que sempre se baseiam no documento 4D Write Pro). +* [OPEN PRINTING JOB](../../commands/open-printing-job) e [CLOSE PRINTING JOB](../../commands/close-printing-job): [WP PRINT](../commands/wp-print) pode ser chamada entre estes comandos para inserir um ou mais documentos 4D Write Pro em um trabalho de impressão. \ No newline at end of file diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/WritePro/user-legacy/stylesheets.md b/i18n/pt/docusaurus-plugin-content-docs/current/WritePro/user-legacy/stylesheets.md new file mode 100644 index 00000000000000..7f4211565d7ffc --- /dev/null +++ b/i18n/pt/docusaurus-plugin-content-docs/current/WritePro/user-legacy/stylesheets.md @@ -0,0 +1,138 @@ +--- +id: stylesheets +title: Folhas de estilo +displayed_sidebar: docs +slug: /WritePro/user/stylesheets +--- + + +Uma folha de estilo é um objeto de um conjunto definido de configurações de atributos utilizadas para controlar a aparência de seus documentos 4D Write Pro. Esta configuração pode ser aplicada a parágrafos e caracteres, como a fonte a mostrar, assim como o tamanho, a cor e o peso da fonte. Quando tiver definido uma folha de estilo, é guardada como um objeto no documento 4D Write Pro para que possa ser reutilizada facilmente. As folhas de estilo lhe permitem dar a seus documentos um aspecto diferente e único, enquanto poupa tempo e esforço. + +## Estilo “normal” + +Todos os documentos 4D Write Pro têm uma folha de estilo de parágrafo definida por padrão, “Normal”. As novas folhas de estilo (criadas com o comando [WP New style sheet](../commands-legacy/wp-new-style-sheet)) se herdam automaticamente do estilo Normal. Os atributos modificados por uma folha de estilo só afetam aos parágrafos aos que forem aplicados, o resto de documento conserva a configuração Normal por padrão. Se for eliminada uma folha de estilo, os atributos modificados voltarão ao estilo Normal. + +O estilo Normal define um valor predeterminado para cada atributo de folha de estilo em um documento 4D Write Pro e pode ser recuperado com o comando [WP Get style sheet](../commands-legacy/wp-get-style-sheet). A folha de estilo Normal pode ser modificada (mas não renomeada) com o comando [WP SET ATTRIBUTES](../commands/wp-set-attributes). Apesar das folhas de estilo criadas com o comando [WP New style sheet](../commands-legacy/wp-new-style-sheet) poderem ser eliminadas com o comando [WP DELETE STYLE SHEET](../commands-legacy/wp-delete-style-sheet), a folha de estilo Normal não pode ser reliminada. + +## Folhas de estilo de atributos de parágrafo e de caracteres + +As folhas de estilo lhe permitem definir os atributos de parágrafos completos ou caracteres específicos: + +- **Parágrafo** - a grande maioria dos atributos que podem ser modificados se aplicam aos parágrafos. As folhas de estilo de parágrafo incluem configurações de estilo de caracteres, assim como atributos de formato que apenas podem ser aplicados a nível de parágrafo (por exemplo, margens, bordas, abas, etc.). +- **Caracteres** - as folhas de estilo de caracteres utilizam apenas os atributos apropriados para diferenciar o texto (um ou mais caracteres) do estilo de parágrafo (por exemplo, cabeçalhos, títulos, texto sublinhado, etc.). + +Lembre que os estilos de parágrafo se aplicam a parágrafos completos. Para aplicar um estilo apenas a uma parte específica de um parágrafo, deve utilizar uma folha de estilo de caracteres. + +## Precedência de folha de estilo + +Podem ser combinadas várias folhas de estilo de parágrafos e caracteres dentro do mesmo documento 4D Write Pro. É importante lembrar que a prioridade da folha de estilo estiver determinada pela ordem em que se aplicam. + +- Se aplicar uma folha de estilo de parágrafo e depois aplicar uma folha de estilo de caracteres, a folha de estilo de caracteres terá prioridade sobre a folha de estilo de parágrafo. Por exemplo, poderia aplicar uma folha de estilo de parágrafo ao corpo de seu documento, depois poderia criar uma folha de estilo de caracteres “em negrito” e aplicá-la a palavras específicas. A folha de estilo de parágrafo se aplicará ao resto del texto, sin embargo, a folha de estilo de caracteres terá prioridade para as palavras designadas. +- Se aplicar uma folha de estilo de caracteres e depois aplicar uma folha de estilo de parágrafo, a folha de estilo de parágrafo se aplicará a todo o texto e se eliminarão todos os estilos de caracteres da folha de estilos de caracteres. + +## Aplicando folhas de estilo + +As folhas de estilo se aplicam com o comando [WP SET ATTRIBUTES](../commands/wp-set-attributes) utilizando as constantes `wk style sheet` ou `wk new line style sheet` (utilizando notação de objetos). + +## Recuperando folhas de estilo + +O comando [WP Get style sheets](../commands-legacy/wp-get-style-sheets) lhe permite recuperar todas as folhas de estilo de um documento de acordo com seu tipo específico. O comando [WP Get style sheet](../commands-legacy/wp-get-style-sheet) lhe permite recuperar uma única folha de estilo por seu nome. + +## Importar e exportar folhas de estilo + +Devido a que as folhas de estilo se armazenam como objetos, podem ser facilmente importadas entre a outros documentos 4D Write Pro ou ser mantidas quando são exportadas em múltiplos formatos. + +- **Importar** - pode obter todos os objetos de folha de estilo de um documento 4D Write Pro designado e usá-los em um novo documento com o comando [WP IMPORT STYLE SHEETS](../commands-legacy/wp-import-style-sheets). +- **Exportar** - os comandos [WP EXPORT DOCUMENT](../commands/wp-export-document) ou [WP EXPORT VARIABLE](../commands/wp-export-variable.md) exportam seus documentos com suas folhas de estilo. + +## Atributos de folhas de estilo + +Os atributos abaixo de folha de estilo de parágrafos e caracteres se podem modificar com os comandos [WP SET ATTRIBUTES](../commands/wp-set-attributes) e [WP RESET ATTRIBUTES](../commands/wp-reset-attributes), ou se recuperam com o comando [WP GET ATTRIBUTES](../commands/wp-get-attributes). + +:::note + +Nota: alguns atributos estão vinculados entre si. Por lo tanto, ao agregar apenas um desses atributos, os outros atributos vinculados também se criarão com os valores predeterminados. Para os atributos vinculados, o valor predeterminado pode ser diferente do valor definido na folha de estilo Normal. Por exemplo, se definir apenas uma borda esquerda vermelha, os outros bordas serão pretas (valor por defeito) mesmo se as bordas na folha de estilo Normal tinham sido previamente definidas como púrpura. + +::: + + +| Atributos | Parágrafo | Caractere | Associado com | +|----------------------------------|-----------|-----------|-------------| +| `wk avoid widows and orphans` | X | | | +| `wk background clip` | X | | | +| `wk background color` | X | X | | +| `wk background height` | X | | `wk background width` | +| `wk background image` | X | | | +| `wk background image url` | X | | | +| `wk background origin` | X | | | +| `wk background position horizontal` | X | | `wk background position vertical` | +| `wk background position vertical` | X | | `wk background position horizontal` | +| `wk background repeat` | X | | | +| `wk background width` | X | | `wk background height` | +| `wk border color` | X | | `wk border color bottom`, `wk border color left`, `wk border color right`, `wk border color top` | +| `wk border color bottom` | X | | `wk border color`, `wk border color left`, `wk border color right`, `wk border color top` | +| `wk border color left` | X | | `wk border color`, `wk border color bottom`, `wk border color right`, `wk border color top` | +| `wk border color right` | X | | `wk border color`, `wk border color bottom`, `wk border color left`, `wk border color top` | +| `wk border color top` | X | | `wk border color`, `wk border color bottom`, `wk border color left`, `wk border color right` | +| `wk border radius` | X | | | +| `wk border style` | X | | `wk border style bottom`, `wk border style left`, `wk border style right`, `wk border style top` | +| `wk border style bottom` | X | | `wk border style`, `wk border style left`, `wk border style right`, `wk border style top` | +| `wk border style left` | X | | `wk border style`, `wk border style bottom`, `wk border style right`, `wk border style top` | +| `wk border style right` | X | | `wk border style`, `wk border style bottom`, `wk border style left`, `wk border style top` | +| `wk border style top` | X | | `wk border style`, `wk border style bottom`, `wk border style left` | +| `wk border width` | X | | `wk border width bottom`, `wk border width left`, `wk border width right`, `wk border width top` | +| `wk border width bottom` | X | | `wk border width`, `wk border width left`, `wk border width right`, `wk border width top` | +| `wk border width left` | X | | `wk border width`, `wk border width bottom`, `wk border width right`, `wk border width top` | +| `wk border width right` | X | | `wk border width`, `wk border width bottom`, `wk border width left`, `wk border width top` | +| `wk border width top` | X | | `wk border width`, `wk border width bottom`, `wk border width left`, `wk border width right` | +| `wk direction` | X | | | +| `wk font` | X | X | `wk font bold`, `wk font italic`, `wk font size` | +| `wk font bold` | X | X | `wk font`, `wk font family`, `wk font italic`, `wk font size` | +| `wk font family` | X | X | `wk font`, `wk font bold`, `wk font italic`, `wk font size` | +| `wk font italic` | X | X | `wk font`, `wk font bold`, `wk font family`, `wk font size` | +| `wk font size` | X | X | `wk font`, `wk font bold`, `wk font family`, `wk font italic` | +| `wk line height` | X | | | +| `wk list font` | X | | | +| `wk list string format LTR` | X | | | +| `wk list string format RTL` | X | | | +| `wk list style image` | X | | | +| `wk list style image height` | X | | | +| `wk list style image url` | X | | | +| `wk list style type` | X | | | +| `wk margin` | X | | `wk margin bottom`, `wk margin left`, `wk margin right`, `wk margin top` | +| `wk margin bottom` | X | | `wk margin`, `wk margin left`, `wk margin right`, `wk margin top` | +| `wk margin left` | X | | `wk margin`, `wk margin bottom`, `wk margin right`, `wk margin top` | +| `wk margin right` | X | | `wk margin`, `wk margin bottom`, `wk margin left`, `wk margin top` | +| `wk margin top` | X | | `wk margin`, `wk margin bottom`, `wk margin left`, `wk margin right` | +| `wk min height` | X | | | +| `wk min width` | X | | | +| `wk name` | X | X | | +| `wk new line style sheet` | X | | | +| `wk owner` | X | X | | +| `wk padding` | X | | `wk padding bottom`, `wk padding left`, `wk padding right`, `wk padding top` | +| `wk padding bottom` | X | | `wk padding`, `wk padding left`, `wk padding right`, `wk padding top` | +| `wk padding box` | X | | | +| `wk padding left` | X | | `wk padding`, `wk padding bottom`, `wk padding right`, `wk padding top` | +| `wk padding right` | X | | `wk padding`, `wk padding bottom`, `wk padding left`, `wk padding top` | +| `wk padding top` | X | | `wk padding`, `wk padding bottom`, `wk padding left`, `wk padding right` | +| `_o_wk page break inside` | X | | | +| `wk tab default` | X | | `wk tabs`, `wk tab stop offsets`, `wk tab stop types`, `wk tab stop leadings` | +| `wk tabs` | X | | `wk tab default`, `wk tab stop offsets`, `wk tab stop types`, `wk tab stop leadings` | +| `wk tab stop offsets` | X | | `wk tabs`, `wk tab default`, `wk tab stop types`, `wk tab stop leadings` | +| `wk tab stop types` | X | | `wk tabs`, `wk tab default`, `wk tab stop offsets`, `wk tab stop leadings` | +| `wk tab stop leadings` | X | | `wk tabs`, `wk tab default`, `wk tab stop offsets`, `wk tab stop types` | +| `wk text align` | X | | | +| `wk text color` | X | X | | +| `wk text indent` | X | | | +| `wk text linethrough color` | X | X | | +| `wk text linethrough style` | X | X | `wk text underline style` | +| `wk text shadow color` | X | X | `wk text shadow offset` | +| `wk text shadow offset` | X | X | `wk text shadow color` | +| `wk text transform` | X | X | | +| `wk text underline color` | X | X | | +| `wk text underline style` | X | X | `wk text linethrough style` | +| `wk type` | X (read only) | X (read only) | | +| `wk vertical align` | X | X | | +| `wk width` | X | | | + + diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/WritePro/user-legacy/text-boxes.md b/i18n/pt/docusaurus-plugin-content-docs/current/WritePro/user-legacy/text-boxes.md new file mode 100644 index 00000000000000..3af7c121235015 --- /dev/null +++ b/i18n/pt/docusaurus-plugin-content-docs/current/WritePro/user-legacy/text-boxes.md @@ -0,0 +1,46 @@ +--- +id: text-boxes +title: Text boxes +displayed_sidebar: docs +slug: /WritePro/user/text-boxes +--- + + +As caixas de texto são áreas que se ancoram a uma página ou seção e podem ser preenchidas com texto, imagens online ou tabelas. As caixas de texto podem ser colocadas em qualquer parte da página e responder à necessidades específicas, por exemplo, para inserir o nome ou logotipo de uma empresa ou uma área de endereços. + + + +**Nota:** uma caixa de texto não pode conter cabeçalhos, rodapés, colunas, imagens ancoradas ou outras caixas de texto. + +As caixas de texto são adicionadas com uma posição absoluta, na frente/atrás do texto, assim como ancoradas a uma página ou a partes específicas de um documento no modo Página: cabeçalho, rodapé, seção, todas as seções ou uma subseção. As caixas de texto também podem ser usadas em modo aninhado (ancoradas à layer box). + +Pode adicionar uma caixa de texto a um documento 4D Write Pro das maneiras abaixo: + +* utilizando o comando **WP New text box**, +* utilizando a ação padrão *insertTextBox* + +Para selecionar uma caixa de texto, o usuário tem que clicar nela (**Ctrl/Cmd+clique** se a caixa de texto estiver na camada de fundo). Uma vez selecionado, a caixa de texto pode ser movida ou redimensionada usando o mouse ou as teclas de flecha. + +Para eliminar uma caixa de texto selecionada, pode pressionar a tecla **Delete** ou **Retrocesso**, utilizar a ação padrão **textBox/eliminar**, ou executar o comando **WP DELETE TEXT BOX**. + +Os atributos das caixas de texto são manejadas com o comando [WP SET ATTRIBUTES](../commands/wp-set-attributes) ou *ações 4D Write Pro*. Estão disponíveis os seguintes atributos e ações: + +| **Propriedade (constante)** | **Ação padrão** | **Comentários** | +| --------------------------- | --------------------- | ----------------------------------------------------------------------------------------------------------------- | +| wk width | textBox/ancho | Se forem definidas em "auto", a largura se converte a 8cm já que a largura da caixa de texto não pode ser "auto". | +| wk height | textBox/alto | Se estiver em "auto", a altura se ajusta ao conteúdo. | +| wk padding | textBox/relleno | | +| wk border \[...\] | textBox/borde\[...\] | | +| wk background \[...\] | textBox/fondo\[...\] | | +| wk vertical align | textBox/verticalAlign | | +| wk id | \- | não pode estar vazio para uma caixa de texto | +| wk anchor \[...\] | textBox/anchor\[...\] | | +| wk owner | \- | só leitura | +| wk protected | \- | | +| wk style sheet | \- | só leitura e sempre "" (sem folha de estilo) | + +As caixas de texto não são mostradas se: + +* o modo de vista é Rascunho; +* estão centrados ou ancorados a seções e a opção **Mostrar HTML WYSIWYG** está marcada; +* a opción "fundo visível" não estiver ativada. \ No newline at end of file diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/WritePro/user-legacy/using-a-4d-write-pro-area.md b/i18n/pt/docusaurus-plugin-content-docs/current/WritePro/user-legacy/using-a-4d-write-pro-area.md new file mode 100644 index 00000000000000..3abcf6f77a15ad --- /dev/null +++ b/i18n/pt/docusaurus-plugin-content-docs/current/WritePro/user-legacy/using-a-4d-write-pro-area.md @@ -0,0 +1,421 @@ +--- +id: using-a-4d-write-pro-area +title: Utilizar uma area 4D Write Pro +displayed_sidebar: docs +--- + + + +## Noções básicas + +Quando o documento está no [modo de vista **Página**](./defining-a-4d-write-pro-area.md#selecting-the-view-mode), as seguintes propriedades do documento são mostradas ao usuário: + +* Traços de página para representar os limites de impressão +* Largura de página e Altura da página (normal: 21x29.7 cm) +* Orientação da página (normal: retrato) +* Margem da página (normal: 2.5 cm) + +Você também pode usar comandos adicionais, como **Documento.../Tamanho da página** ou **Documento.../Orientação da página**. + +**Nota:** quando o documento está em modo Web ou Rascunho, as propriedades da página se podem definir, ainda que seu efeito não for visível. No modo Rascunho, os seguintes efeitos propriedad de parágrafo são visíveis: + +* Limitação de altura página (línhas desenhadas) +* Colunas +* Evitar salto de página dentro da propriedade +* Controle de viúdas e órfãs. + +## Quebras de parágrafo + +Quando exibido em modo Page ou Draft (no contexto de impressão de documento), Parágrafos 4D Write Pro pode quebrar: + +* automaticamente, se a altura de parágrafo for maior que a altura disponível de página +* dependendo de quebras de parágrafo estabelecidos por programação ou pelo usuário. + +Quebras podem ser adicionadas por programação ou pelo usuário. Ações disponíveis incluem: + +* [WP INSERT BREAK](../commands/wp-insert-break) comando +* *insertPageBreak* ação padrão +* **Insert page break** opção do menu contextual padrão + +### Controle de Quebra automática + +Pode controlar quebras automáticas em parágrafos usando as funcionalidades abaixo: + +* **Widow and orphan control**: Quando essa opção for estabelecida para um parágrafo. 4D Write Pro não permite linhas viúvas (a última linha de um parágrafo isolada no topo da próxima página) ou órfãs (a primeira linha de um parágrafo isolada no fundo da página anterior) em um documento. No primeiro caso, a linha anterior do parágrafo é adicionada ao topo da página de forma que duas linhas são exibidas lá. No segundo caso, a primeira linha isolada é movida para a próxima página.. +* **Avoid page break inside**: Quando essa opção for estabelecida para um parágrafo, 4D Write Pro previne que esse parágrafo seja quebrada em partes ou em duas ou mais páginas. +* **Manter com o próximo**: quando se estabelece esta opção para um parágrafo, esse parágrafo não pode separar-se do que lhe segue por uma quebra automática. Ver `wk keep with next` e a [ação padrão](./defining-a-4d-write-pro-area.md#standard-actions) correspondente *keepWithNext*. + +Essas opções podem ser estabelecidas usando o menu contextual, ou [atributos](../commands-legacy/4d-write-pro-attributes.md) (`wk avoid widows and orphans`, `wk page break inside paragraph`, ou [ações padrão](./defining-a-4d-write-pro-area.md#standard-actions) *widowAndOrphanControlEnabled*, *avoidPageBreakInside*. + +## Fundo + +O fundo de documentos 4D Write e elementos de documentos (tabelas, parágrafos, seções, cabeçalhos/rodapés, etc) podem ser estabelecidos com os efeitos abaixo: + +* cores +* bordas +* imagens +* origem, posicionamento horizontal e vertical +* área de pintura +* repetir + +Esses [atributos](../commands-legacy/4d-write-pro-attributes.md) podem ser definidos programaticamente para os elementos indivíduos ou uma página ou fundos de documentos inteiros com o comando [WP SET ATTRIBUTES](../commands/wp-set-attributes) ou por [ações padrão](./defining-a-4d-write-pro-area.md#standard-actions). + +Usuários podem modificar atributos de fundo via o menu contextual como mostrado abaixo: + + + + +Como exemplo de adicionar uma imagem de tamanho inteiro como fundo, veja *How Do I* (HDI) demo [aqui](http://download.4d.com/Demos/4D%5Fv16%5FR5/HDI%5F4DWP%5FBackImagePaperBox.zip). + +## Cabeçalhos, rodapés e seções + +Documentos 4D Write Pro são compatíveis com cabeçalhos e rodapés. Cabeçalhos e rodapés são relacionadas à seções + +Uma seção é uma parte do documento definida por uma faixa de páginas e pode ter seu próprio paginamento e atributos comuns. Um documento pode conter qualquer número de seções (de uma seção ao número total de páginas). Cada página pode conter apenas uma seção, exceto páginas com quebras de secção contínuas (ver abaixo). + +Os documentos 4D Write Pro podem conter: + +- uma ou mais secções (uma secção por predefinição) +- para cada secção, até três subsecções: + - subsecção da primeira página + - subsecção da(s) página(s) esquerda(s) + - subsecção da(s) página(s) direita(s) + +Pode definir um conjunto de cabeçalhos e rodapés para cada seção + +### Definir uma seção + +Uma seção é um subconjunto de páginas contínuas em um documento 4D Write Pro. Um documento pode conter uma ou mais seções. Uma seção pode conter qualquer número de páginas, de uma página única ao número total de páginas do documento. Uma seção pode conter de uma coluna até 20 colunas. + +Como padrão, um documento contém apenas uma seção, chamada **Seção 1**. O menu contextual 4D Write Pro exibe este número de seção sempre que clicar no documento. + + + +Pode criar uma nova seção adicionado uma quebra de sessão no fluxo do texto : + + + +Quando uma quebra de seção for adicionada, o menu contextual exibe um número incrementado para cada seção. No entanto, pode renomear qualquer seção: + + + +O nome que digitar será usado como nome da seção em qualquer ponto do documento + +  + +Note que se tiver definido uma primeira página diferente ou a opção de páginas da esquerda e da direita diferentes para a seção, o tipo de página também é exibido no menu (ver abaixo) + +### Inserir uma quebra de seção contínua + +Uma quebra de seção contínua cria uma nova seção na mesma página. Isso permite criar páginas com seções que tenham diferentes números de colunas (vet *Criar uma página com seções múltiplas-colunas e únicas colunas*). + +As seções criadas com saltos de seção continuos são contadas no documento (têm números de seção), mas diferente das seções criadas com quebras de seção normal, seus cabeçalhos, rodapés, imagens ancoradas, etc, só são levadas em consideração quando for produzido uma quebra de página física. + +**Nota:** se mudar a orientação da página da nova seção depois de inserir uma quebra de seção contínua, se converte em uma quebra de seção padrão. + +### Atributos de seção + +Seções são herdadas de atributos de documentos. Entretanto atributyos comuns de documentos, incluindo cabeçalhos e rodapés podem ser modificados separadamente para cada seção. O menu contextual pop up exibe as propriedades e atributos disponíveis ao nível de seção: + + + +* **Orientação de Página**: permite que estabeleça uma orientação de página específica (Orientação vertical ou horizontal) por seção +* **Primeira página diferente**: permite que estabeleça atributos diferentes para a primeira página da seção. Esta propriedade pode ser usada para criar páginas em branco no começo do texto, por exemplo. Quando este atributo estiver marcado, a primeira página da seção é manejada como uma subseção e pode ter seus próprios atributos. + +* **Páginas da esquerda e da direita diferentes**: permite que estabelece atributos diferentes para páginas que estão à esquerda e à direita na seção. Quando este atributo for marcado, páginas da esquerda e da direita na seção serão manejadas como subseções e terão seus próprios atributos. + +* Comandos **Cabeçalho** e **Rodapé**: estas opções permitem que defina cabeçalhos e rodapé separados. Estas opções são detalhadas abaixo +* **Margens** / **preenchimento** / **Bordas** / **Fundo**: estes atributos podem ser definidos separadamente para cada seção. Para saber mais, veja o artigo *Atributos 4D Write Pro*. + +### Inserir cabeçalhos e rodapés + +Cada seção pode ter cabeçalhos e rodapés específicos. São exibidos apenas quando o modo de vista da página do documento for **Page**. + + Dentro de uma seção, pode definir até três diferentes cabeçalhos ou rodapés, dependendo das opções ativadas: + +* primeira página, +* páginas esquerda, +* páginas direita. + +Para criar um cabeçalho ou rodapé: + +1. Veja se o documento está no modo de vista **Page**. +2. Dê duplo clique na área de cabeçalho ou rodapé da seção desejada para começar o modo editar. + * A área cabeçalho está no topo da página: +  + * A área rodapé está no fundo da página: +  + +Pode entrar qualquer conteúdo estático, que será automaticamente repetido em cada página da seção (exceto para a primeira página, se ativado) + + + +Pode inserir conteúdos dinâmicos tais como número de página ou contador de página usando o comando [ST INSERT EXPRESSION](../../commands/st-insert-expression) (para saber mais, veja o parágrafo *Inserir documentos e expressões de página*). + +Nota: TAmbém é possível manejar cabeçalhos e rodapés por programação, usando comandos específicos como [WP Get header](../commands/wp-get-header) ou [WP Get footer](../commands/wp-get-footer) + +Quando um cabeçalho ou rodapé tiver sido definido para uma seção, pode configurar seus atributos comuns usando o menu contextual: + + + +Para saber mais sobre **Margens**, **Preenchimento**, **Bordas**, e atributos **Fundo**, veja a seção *Atributos 4D Write Pro*. + +Pode remover a definição total do cabeçalho ou rodapé (conteúdos e atributos) selecionando os comandos **Remove header** ou **Remove footer** no menu contextual. + +### Compatibilidade + +4D Write Pro maneja cabeçalhos e rodapés de documentos convertidos do plug-in 4D Write com uma altura fixa + +A expressão abaixo e propriedades também são compatíveis e convertidas do plugin 4D Write em cabeçalhos e rodapés: + +* número de página e variáveis de contador de página +* primeira página diferenciada +* páginas esquerda/direita diferenciadas + +## Réguas + +As réguas estão disponíveis em todos os modos de visualização de 4D Write Pro e têm as seguintes características: + +* Graduações em cm, mm, polegadas ou pt de acordo com a unidade de desenho atual definida no documento 4D Write Pro. Pode mudar as unidades de medida mediante o menu contextual ou modificando o atributo wk layout unit. +* Símbolo de indentação de primeira linha +* Símbolo de margem de parágrafo esquerdo +* Símbolo de margem de parágrafo direito +* Tabulações mostradas ao longo da borda inferior da régua +* O contraste de cor visível representa as margens de página esquerda e direita + +As réguas verticais estão disponíveis só no modo Página e possuem as características abaixo: + +* Graduações em cm, mm, polegadas ou pt segundo a unidade de desenho atual definida no documento 4D Write Pro. Pode mudar as unidades de medida utilizando o menu contextual ou modificando o atributo wk layout unit. +* Contraste de cor visível que representa as margens superior e inferior da página. + +Pode mudar o estado de visualização da régua marcando ou desmarcando a opção **Mostrar régua horizontal** ou **Mostrar régua vertical** no menu contextual da área 4D Write Pro: + + + +**Nota:** uma propriedade específica da área 4D Write Pro permite definir a visualização predeterminada para as réguas (ver a seção *Configurar propriedades de Vista*). + +### Ajustar margens de texto e indentação + +Pode modificar margens, indentações e posições de abas clicando e arrastando os símbolos correspondentes: + + + +Quando colocar o mouse sobre um destes símbolos, o cursor muda para indicar que pode ser movido e aparece uma linha de guia vertical enquanto for arrastado: + + + +Quando forem selecionados vários parágrafos, arrastar margens ou símbolos de indentação aplica estes margens ou indentações a todos os parágrafos selecionados. Mantendo pressionada a tecla Maiúsc Enquanto arrasta estes símbolos mantém os intervalos existentes entre indentações ou margens nos parágrafos selecionados. + +#### Régua Horizontal + +Pode modificar margens esquerda e direita, indentações e posições de tabulação clicando e arrastando os símbolos correspondentes na régua horizontal: + + + +Quando colocar o mouse sobre um desses símbolos, o cursor muda para indicar que pode ser movido e aparece uma linha de guia vertical enquanto for arrastado: + + + +Quando vários parágrafos forem selecionados, arrastar margens ou símbolos de indentação aplica a estas margens ou indentações a todos os parágrafos selecionados. Mantendo pressionada a tecla Maiúscula (Shift) enquanto arrasta estes símbolos mantém os intervalos existentes entre as identações ou margens nos parágrafos selecionados. + +#### Régua Vertical + +Pode modificar as margens superior e inferior com a régua vertical. Quando mover o mouse sobre o limite da margem, o cursor muda para indicar que é possível mover, e aparece uma linha de guia horizontal enquanto for arrastado: + + + +Esta ação pode ser usada para modificar o espaço entre a parte superior e inferior da página e o corpo e o cabeçalho e rodapé de um documento. + +### Gerenciar tabulações + +É possível usar o menu contextual de regua para criar, modificar ou apagar tabulações: + + + +Para criar uma tabulação, dê um clique direito diretamente na régua e escolha seu tipo do menu contextual; um clique esquerdo automaticamente cria uma aba esquerda padrão. Pode também dar um clique direito em tabulações existentes para modificar seu tipo usando o menu contextual. + +**Remover tabulação** só está disponível quando der clique direito diretamente numa tabulação existente; também pode remover tabulações ao arrastar as tabulações fora da área de régua. + +:::note Notas + +* Abas também podem ser definidas por programação com os comandos [WP SET ATTRIBUTES](../commands/wp-set-attributes), [WP GET ATTRIBUTES](../commands/wp-get-attributes), e [WP RESET ATTRIBUTES](../commands/wp-reset-attributes) com os seletores wk tab default e wk tabs +* Para separações decimais, 4D Write Pro consida o primeiro caractere ponto ou vírgula da direita como um separador decimal; essa configuração padrão pode ser modificada com o seletor wk tab decimal separator + +::: + +#### Definir o signo inicial + +Os caracteres precedendo as tabulações (signos iniciais) podem ser definidos ao selecionar entre cinco caracteres pré-definidos ou definindo um caractere específico a usar. Os caracteres pré-definidos são: + +* Nenhum (nenhum caractere é exibido - padrão) +* .... (pontos) +* \--- (traços) +* \_\_ (subscritos) +* \*\*\* (asteriscos) + +Signos iniciais sempre aparecem antes da aba e seguem a direção do texto (da esquerda para direita ou direita para esquerda). Podem ser definidos por programação com os comandos [WP SET ATTRIBUTES](../commands/wp-set-attributes), [WP GET ATTRIBUTES](../commands/wp-get-attributes), e [WP RESET ATTRIBUTES](../commands/wp-reset-attributes) usando `wk leading` com os seletores `wk tab default` ou `wk tabs` , ou através do menu contextual da régua horizontal (mostrado abaixo). + + + +Quando **Outro...** for selecionado, um diálogo é exibido onde um caractere inicial personalizado pode ser definido. + +### Réguas Multi-coluna + +Quando duas ou mais colunas forem definidas para o documento ou seção, a régua exibe uma área específica para cada coluna: + + + +**Nota:** propriedade Multi-coluna não está disponível em modo **Embedded**. + +### Evento On After Edit + +Um evento de formulário [`On After Edit`](../../Events/onAfterEdit.md) é ativado para objeto de área de formulário 4D Write Pro sempre que uma aba ou controle de margem for movido, adicionado ou apagado, seja arrastando ou usando o menu contextual + +## Colunas + +4D Write Pro permite que maneje colunas em seus documentos. Colunas são conectadas da coluna mais à esquerda até a mais à direita. Ou seja, quando digitar texto, o fluxo de texto vai começar preenchendo a coluna mais à esquerda e continuar com a coluna diretamente à direita até chegar ao final da página. Quando o final da página tiver sido alcançado, o fluxo de texto vai para a próxima página. Para poder balancear as configurações de páginas, 4D Write Pro permite que insira quebras de coluna. + + + +Colunas podem ser definidas ao nível de documento (são exibidos no documento inteiro) ou no nível da seção (cada seção pode ter sua própria configuração de coluna). + +**Nota:** Colunas só são compatíveis nos modos **Vista de página** e **Vista rascunho** (não são exibidos em modo **Embedded** e são exportados a .docx por [WP EXPORT DOCUMENT](../commands/wp-export-document) , mas não aos formato HTML e MIME HTML wk web page complete ). + +Colunas podem ser estabelecidas usando: + +* o submenu **Colunas** do menu contextual de área 4D Write Pro, +* [atributos](../commands-legacy/4d-write-pro-attributes.md) 4D Write Pro, +* [ações padrão](./using-4d-write-pro-standard-actions.md) 4D Write Pro. + +Pode estabelecer ou obter as propriedades abaixo e ações para colunas: + +| **Propriedade** | **Descrição** | *Documento* **atributos** | **Ações padrão** | +| ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------- | ------------------------------------------------------- | +| Número de colunas | Pode definir até 20 colunas para o documento/seção | wk column count | *columnCount* | +| Espaçamento de coluna | Espaço entre colunas em pts, polegadas, ou cm. Note que todas as colunas vão ter o mesmo tamanho. Cada largura de coluna é automaticamente calculada por 4D Write Pro de acordo com o número de colunas, a largura de página e o espaçamento | wk column spacing | *columnSpacing* | +| Largura de coluna | (atributo apenas leitura) Largura atual de cada coluna, ou seja, largura computada | wk column width | \- | +| Estilo, cor e largura de coluna | Pode adicionar um separadador vertical (uma linha decorativa) entre as collunas. Essas opções permitem planejar o estilo de separador, cor e largura. Para remover o separador vertical, selecione **None** como estilo. | wk column rule style, wk column rule color, wk column rule width | *columnRuleStyle*, *columnRuleColor*, *columnRuleWidth* | +| Inserir break | Insere uma quebra de coluna | wk column break, veja também [WP INSERT BREAK](../commands/wp-insert-break) | *insertColumnBreak* | +| Menu de Colunas | Crie um sub-menu Colunas | \- | *colunas* | + +### Criar uma página com seções múltiplas-colunas e únicas colunas + +*Inserir uma quebra de seção contínua* em seu documento lhe permite ter seções de várias colunas e seções de uma coluna na mesma página. + +Por exemplo: + + + +Pode inserir uma quebra de seção continua e mudar o número de colunas a duas para a primeira seção: + + + +## Bookmarks + +4D Write Pro permite criar e trabalhar com referências dinâmicas para faixas, chamadas **bookmarks**. Uma bookmark é uma referência de nome anexada à [faixa](./ranges.md) específica em um documento 4D Write Pro. + +Bookmarks são dinâmicas, o que significa que se suas faixas associadas são modificadas, estendidas ou reduzidas, a bookmark ainda vai referenciar a mesma faixa dentro do documento. Por exemplo: + +- Se criar uma bookmark chamada "MyBM" que referencia o texto "Hello world" na página 20 do seu documento. +- Se então inserir 50 páginas no começo do documento. +- Mesmo assim ainda poderá acessar o mesmo texto "Hello world" automaticamente, agora na página 70 do documento, através do bookmark "MyBM". + +Um documento pode conter um número ilimitado de bookmarks. Diversas bookmarks podem referenciar a mesma faixa, e faixas de bookmarks podem ser intercaladas. Entretanto, cada nome de bookmark deve ser único no documento. Bookmarks não são importadas quando usar o comando [WP INSERT DOCUMENT](../commands/wp-insert-document-body) (bookmarks no documento de destino não podem ser gravadas por cima). + +Ao ser criada, uma bookmark é armazenada dentro do documento. A bookmark é salva com o documento e pode ser manejada através de diversos comandos. Também pode ser usada para referenciar partes de um documento modelo. Estas partes podem então ser juntadas automaticamente com dados do banco de dados para produzir documentos output dinâmicos tais como faturas ou catálogos. + +Diversos comandos permitem que se crie, remova ou use bookmarks: + +- [WP NEW BOOKMARK](../commands-legacy/wp-new-bookmark.md) para criar uma nova bookmark de uma faixa, +- [WP GET BOOKMARKS](../commands-legacy/wp-get-bookmarks.md) para obter todas as bookmarks definidas em um documento, +- [WP Bookmark range](../commands-legacy/wp-bookmark-range.md) para recuperar uma faixa de uma bookmark existente, +- [WP DELETE BOOKMARK](../commands-legacy/wp-delete-bookmark.md) para apagar uma bookmark. + + +## Links + +4D Write Pro permite que atribua hyperlinks para qualquer faixa de seleção do documento, incluindo faixas de texto, parágrafos, imagens, linhas de tabela ou células. Por exemplo, pode estabelecer um hyperlink para uma imagem, quando o documento 4D Write Pro for exportado a HTML, usuários podem clicar a imagem para abrir uma página num endereço específico. + +Hyperlinks podem ser ativados em documentos 4D Write Pro usando os atalhos **Ctrl+clique** (Windows) ou **Cmd+clique** (macOS). + +Em um documento 4D Write Pro, um link pode ser ativado utilizando um simples clique. + +4D Write Pro é compatível com links dos seguintes tipos: + +| Tipo de link | Descrição | +|--------------|-----------| +| `url` | Links a páginas web ou a qualquer documento, abre a aplicação associada quando se ativar (\*). A ativação de um link URL ao documento 4D Write Pro (`.4wp`, `.4w7`) substitui ao documento atual na área de 4D Write Pro.
(\*) Igual que o comando [OPEN URL](../../commands-legacy/open-url.md). | +| `bookmark` | Links a bookmarks no documento | +| `method` | Ativando um link a um método 4D executa o método (sempre que esteja registrado pelo método [SET ALLOWED METHODS](../../commands/set-allowed-methods.md)). | + +Os hyperlinks são manejados através dos comandos abaixo: + +- [WP SET LINK](../commands-legacy/wp-set-link.md) para inserir um link utilizando um objeto de destino. +- [WP Get links](../commands-legacy/wp-get-links.md) para obter a coleção de todos os links em um objeto de destino. + +:::note + +Nota: os links são manejados como atributos, portanto podem ser definidos ou obtidos utilizando os comandos [WP SET ATTRIBUTES](../commands/wp-set-attributes) e [WP RESET ATTRIBUTES](../commands/wp-reset-attributes) assim como a constante `wk link url`. Entretanto, recomendamos utilizar [WP SET LINK](../commands-legacy/wp-set-link.md) e [WP Get links](../commands-legacy/wp-get-links.md) porque automaticamente codificam/decodificam links como URLs. Quando são lidos links utilizando o comando [WP GET ATTRIBUTES](../commands/wp-get-attributes), se a range conter vários hyperlinks, o comando devolve a primeira string de url. + +::: + +Por exemplo, se quiser transformar o texto selecionado pelo usuário em uma URL em um site web: + + + +Se pode escrever: + +```4d + $range:=WP Get selection(*;"WParea") + WP SET LINK($range;New object("url";"http://www.4d.com")) +``` + + + +Para eliminar um link da range, pode escrever: + +```4d + WP RESET ATTRIBUTES($range;wk link url) +``` +ou +```4d + WP SET ATTRIBUTES($range;wk link url;"") +``` + +**Nota:** se *$range* não incluir o link todo, o link é truncado mas não é eliminado completamente. + + +## Utilizar os comandos do tema Objeto (Formulários) + +Os seguintes comandos 4D do tema [Objetos (Formulários)](../../commands/theme/Objects_Forms.md) suportam objetos de formulário do 4D Write Pro: + +| Comando | Comentários | +|--------|-------------| +| OBJECT DUPLICATE | | +| OBJECT Get auto spellcheck / OBJECT SET AUTO SPELLCHECK | | +| OBJECT Get border style / OBJECT SET BORDER STYLE | | +| OBJECT Get context menu / OBJECT SET CONTEXT MENU | | +| OBJECT GET COORDINATES / OBJECT SET COORDINATES | | +| OBJECT Get data source / OBJECT SET DATA SOURCE | | +| OBJECT GET DRAG AND DROP OPTIONS / OBJECT SET DRAG AND DROP OPTIONS | | +| OBJECT Get enabled / OBJECT SET ENABLED | | +| OBJECT Get enterable / OBJECT SET ENTERABLE | | +| OBJECT GET EVENTS / OBJECT SET EVENTS | | +| OBJECT Get focus rectangle invisible / OBJECT SET FOCUS RECTANGLE INVISIBLE | | +| OBJECT Get font / OBJECT SET FONT | Aplicado a seleção atual (se houver) | +| OBJECT Get font size / OBJECT SET FONT SIZE | Aplicado a seleção atual (se houver) | +| OBJECT Get font style / OBJECT SET FONT STYLE | Aplicado a seleção atual (se houver) | +| OBJECT Get horizontal alignment / OBJECT SET HORIZONTAL ALIGNMENT | Aplicado a seleção atual (se houver) | +| OBJECT GET RESIZING OPTIONS / OBJECT SET RESIZING OPTIONS | | +| OBJECT SET COLOR | Aplicado a seleção atual (se houver) | +| OBJECT GET RGB COLORS / OBJECT SET RGB COLORS | Aplicado a seleção atual (se houver) | +| OBJECT Get type | | +| OBJECT Get vertical alignment / OBJECT SET VERTICAL ALIGNMENT | Alinhamento vertical de parágrafos: só tem efeito quando a altura do parágrafo é maior a altura do texto do parágrafo | +| OBJECT Get visible / OBJECT SET VISIBLE | | +| OBJECT Is styled text | Devolve true | +| OBJECT MOVE | | +| OBJECT GET SUBFORM CONTAINER SIZE | | +| OBJECT Get name | | +| OBJECT Get pointer | | + +Todos os comandos OBJECT não enumerados anteriormente não são aplicáveis às áreas 4D Write Pro. diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/ak_400.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/ak_400.png new file mode 100644 index 00000000000000..03ddd799fa0a3a Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/ak_400.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/ak_700.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/ak_700.png new file mode 100644 index 00000000000000..67de2c6ccbeac1 Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/ak_700.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/comment.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/comment.png new file mode 100644 index 00000000000000..7bc9233ea63c89 Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/comment.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/header_title_olv.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/header_title_olv.png new file mode 100644 index 00000000000000..96e9102ce17d7b Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/header_title_olv.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/icon-f.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/icon-f.png new file mode 100644 index 00000000000000..c5b95111dd2fc2 Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/icon-f.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/link1.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/link1.png new file mode 100644 index 00000000000000..37389843e8f050 Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/link1.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/link2.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/link2.png new file mode 100644 index 00000000000000..a49860493ce8e7 Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/link2.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2584929.en.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2584929.en.png new file mode 100644 index 00000000000000..03a90f0aa6ff33 Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2584929.en.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2584938.en.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2584938.en.png new file mode 100644 index 00000000000000..45c3f9773eea02 Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2584938.en.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2646292.en.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2646292.en.png new file mode 100644 index 00000000000000..2f6dd9ff7667f9 Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2646292.en.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2646294.en.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2646294.en.png new file mode 100644 index 00000000000000..c5706f5b23244e Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2646294.en.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994900.pt.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994900.pt.png new file mode 100644 index 00000000000000..708a312878111a Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994900.pt.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994904.pt.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994904.pt.png new file mode 100644 index 00000000000000..32d32278668fbf Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994904.pt.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994907.pt.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994907.pt.png new file mode 100644 index 00000000000000..e54fc7a054c53b Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994907.pt.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994910.pt.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994910.pt.png new file mode 100644 index 00000000000000..b2ea9aba525bec Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994910.pt.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994913.pt.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994913.pt.png new file mode 100644 index 00000000000000..861b15c9ad2ed3 Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994913.pt.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994942.pt.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994942.pt.png new file mode 100644 index 00000000000000..26808f376ba6b5 Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994942.pt.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994945.pt.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994945.pt.png new file mode 100644 index 00000000000000..4671e43aa7f7e4 Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994945.pt.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994956.pt.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994956.pt.png new file mode 100644 index 00000000000000..7ebcaf114bf45d Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994956.pt.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994958.pt.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994958.pt.png new file mode 100644 index 00000000000000..e393291f33a7c5 Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994958.pt.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994965.pt.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994965.pt.png new file mode 100644 index 00000000000000..b3c0a322d39936 Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2994965.pt.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2995027.pt.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2995027.pt.png new file mode 100644 index 00000000000000..da5f44dbf50030 Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict2995027.pt.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3033006.EN.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3033006.EN.png new file mode 100644 index 00000000000000..ad7e034e246705 Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3033006.EN.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3033008.EN.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3033008.EN.png new file mode 100644 index 00000000000000..51f1aa5c128b59 Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3033008.EN.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3071271.en.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3071271.en.png new file mode 100644 index 00000000000000..e7f020cc979f5e Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3071271.en.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3106228.en.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3106228.en.png new file mode 100644 index 00000000000000..230e44dbbb561b Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3106228.en.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3133340.en.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3133340.en.png new file mode 100644 index 00000000000000..36424d5d26322e Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3133340.en.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3254912.pt.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3254912.pt.png new file mode 100644 index 00000000000000..30126c1aa783ec Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3254912.pt.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3307937.EN.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3307937.EN.png new file mode 100644 index 00000000000000..fb12b681bed355 Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3307937.EN.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3307941.EN.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3307941.EN.png new file mode 100644 index 00000000000000..0016bc2e11049d Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3307941.EN.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3308424.en.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3308424.en.png new file mode 100644 index 00000000000000..17c545dcd5e7cc Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3308424.en.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3513503.EN.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3513503.EN.png new file mode 100644 index 00000000000000..eddf97544e0575 Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3513503.EN.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3513505.en.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3513505.en.png new file mode 100644 index 00000000000000..5e8669f5c2aace Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3513505.en.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3514201.pt.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3514201.pt.png new file mode 100644 index 00000000000000..1d76c9adeda15d Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3514201.pt.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3541581.EN.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3541581.EN.png new file mode 100644 index 00000000000000..8d2321c8b19748 Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3541581.EN.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3626363.EN.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3626363.EN.png new file mode 100644 index 00000000000000..823fcf7c97fbcb Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3626363.EN.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3751849.pt.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3751849.pt.png new file mode 100644 index 00000000000000..ef6729c52ad9db Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3751849.pt.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3751870.en.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3751870.en.png new file mode 100644 index 00000000000000..3e884da6e3c89d Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3751870.en.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3752166.en.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3752166.en.png new file mode 100644 index 00000000000000..40ec61e14638df Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3752166.en.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3752176.en.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3752176.en.png new file mode 100644 index 00000000000000..1b09211ea8ac30 Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3752176.en.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3893246.EN.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3893246.EN.png new file mode 100644 index 00000000000000..84c289b866e8e6 Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3893246.EN.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3893248.EN.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3893248.EN.png new file mode 100644 index 00000000000000..c21d5b60eeb195 Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict3893248.EN.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101161.pt.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101161.pt.png new file mode 100644 index 00000000000000..a61f10b1d52bb7 Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101161.pt.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101210.pt.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101210.pt.png new file mode 100644 index 00000000000000..a844f0958549c7 Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101210.pt.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101242.pt.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101242.pt.png new file mode 100644 index 00000000000000..6bcbfc4d44a26e Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101242.pt.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101252.pt.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101252.pt.png new file mode 100644 index 00000000000000..a1e5ec76a2bd82 Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101252.pt.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101267.pt.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101267.pt.png new file mode 100644 index 00000000000000..be0d97a26d24a3 Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4101267.pt.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4619596.en.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4619596.en.png new file mode 100644 index 00000000000000..0c0a886b53349f Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4619596.en.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4619694.en.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4619694.en.png new file mode 100644 index 00000000000000..4ace1703dab061 Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4619694.en.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4619865.en.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4619865.en.png new file mode 100644 index 00000000000000..e708853ddf2c4c Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict4619865.en.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5562054.EN.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5562054.EN.png new file mode 100644 index 00000000000000..dee167c5ccf7c3 Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5562054.EN.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5562058.EN.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5562058.EN.png new file mode 100644 index 00000000000000..f84f46638756cb Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5562058.EN.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5761667.en.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5761667.en.png new file mode 100644 index 00000000000000..a6e16bcd3e31bf Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5761667.en.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5761669.en.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5761669.en.png new file mode 100644 index 00000000000000..6f56866e06cff7 Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5761669.en.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5761671.en.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5761671.en.png new file mode 100644 index 00000000000000..d2b933e6253bd5 Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5761671.en.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5761675.en.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5761675.en.png new file mode 100644 index 00000000000000..f21fa89866c9ef Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5761675.en.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5761677.en.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5761677.en.png new file mode 100644 index 00000000000000..b6b82029e3bdaa Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5761677.en.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5859437.EN.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5859437.EN.png new file mode 100644 index 00000000000000..8a546866502013 Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5859437.EN.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5907013.EN.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5907013.EN.png new file mode 100644 index 00000000000000..e233c502a77cb2 Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5907013.EN.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5907021.EN.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5907021.EN.png new file mode 100644 index 00000000000000..bcbe548297f87d Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5907021.EN.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5907023.EN.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5907023.EN.png new file mode 100644 index 00000000000000..6eba7f2baedff6 Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5907023.EN.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5907026.EN.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5907026.EN.png new file mode 100644 index 00000000000000..d526c51578eb27 Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5907026.EN.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5907030.EN.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5907030.EN.png new file mode 100644 index 00000000000000..964245707b6717 Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5907030.EN.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5941073.EN.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5941073.EN.png new file mode 100644 index 00000000000000..66f10af3210774 Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict5941073.EN.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6014414.EN.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6014414.EN.png new file mode 100644 index 00000000000000..1454f02b49f34c Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6014414.EN.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6014426.EN.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6014426.EN.png new file mode 100644 index 00000000000000..5430cc882d6f13 Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6014426.EN.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6014429.EN.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6014429.EN.png new file mode 100644 index 00000000000000..12cb8442c5f68c Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6014429.EN.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6021229.EN.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6021229.EN.png new file mode 100644 index 00000000000000..6a2beadade9fd0 Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6021229.EN.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6022144.EN.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6022144.EN.png new file mode 100644 index 00000000000000..ab1d4670b16d55 Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6022144.EN.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6131919.EN.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6131919.EN.png new file mode 100644 index 00000000000000..d8b2b0f013f901 Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6131919.EN.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6421031.EN.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6421031.EN.png new file mode 100644 index 00000000000000..f338bd44caeb38 Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6421031.EN.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6421340.EN.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6421340.EN.png new file mode 100644 index 00000000000000..a00a64fa003fe5 Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6421340.EN.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6421342.EN.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6421342.EN.png new file mode 100644 index 00000000000000..e7bbdb0445e7dc Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6421342.EN.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6421344.EN.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6421344.EN.png new file mode 100644 index 00000000000000..b1da7d4f717589 Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6421344.EN.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6421356.EN.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6421356.EN.png new file mode 100644 index 00000000000000..e19848f65d2951 Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6421356.EN.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6434575.en.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6434575.en.png new file mode 100644 index 00000000000000..b98b7a71deb16b Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6434575.en.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6434579.EN.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6434579.EN.png new file mode 100644 index 00000000000000..232ad5653b5bdf Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6434579.EN.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6434721.EN.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6434721.EN.png new file mode 100644 index 00000000000000..199e62f81ef736 Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6434721.EN.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6434723.EN.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6434723.EN.png new file mode 100644 index 00000000000000..480da0bfc5f80f Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6434723.EN.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6434756.en.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6434756.en.png new file mode 100644 index 00000000000000..ffdcce4bd30899 Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6434756.en.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6441966.EN.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6441966.EN.png new file mode 100644 index 00000000000000..e6b76b3b690664 Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6441966.EN.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6856159.en.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6856159.en.png new file mode 100644 index 00000000000000..18f093b69da71c Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6856159.en.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6856163.en.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6856163.en.png new file mode 100644 index 00000000000000..0c3c6665e834d8 Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict6856163.en.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict7014959.en.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict7014959.en.png new file mode 100644 index 00000000000000..a667cee2e6696a Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict7014959.en.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict7148443.en.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict7148443.en.png new file mode 100644 index 00000000000000..ab64da522a20a6 Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict7148443.en.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict7148495.en.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict7148495.en.png new file mode 100644 index 00000000000000..499af8e3737b08 Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/pict7148495.en.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/poweredby4D_web.png b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/poweredby4D_web.png new file mode 100644 index 00000000000000..fbb7fefffac38d Binary files /dev/null and b/i18n/pt/docusaurus-plugin-content-docs/current/assets/en/WritePro/poweredby4D_web.png differ diff --git a/i18n/pt/docusaurus-plugin-content-docs/version-20-R10/API/SessionClass.md b/i18n/pt/docusaurus-plugin-content-docs/version-20-R10/API/SessionClass.md index cd45cc5a556635..02c3bb6af40dfa 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/version-20-R10/API/SessionClass.md +++ b/i18n/pt/docusaurus-plugin-content-docs/version-20-R10/API/SessionClass.md @@ -136,7 +136,7 @@ A função `.createOTP()` cria um Para mais informações sobre os tokens OTP, consulte [esta seção](../WebServer/sessions.md#session-token-otp). -Por padrão, se o parâmetro *lifespan* for omitido, o token será criado com o mesmo tempo de vida que o [`.idleTimeOut`](#idletimeout) da sessão. Você pode definir um tempo limite personalizado passando um valor em segundos em *lifespan* (o valor mínimo é 10 segundos, *lifespan* é redefinido para 10 se um valor menor for passado). Se um token expirado for usado para restaurar uma sessão de usuário Web, ele será ignorado. +Por padrão, se o parâmetro *lifespan* for omitido, o token será criado com o mesmo tempo de vida que o [`.idleTimeOut`](#idletimeout) da sessão. You can set a custom timeout by passing a value in seconds in *lifespan*. Se um token expirado for usado para restaurar uma sessão de usuário Web, ele será ignorado. O token retornado pode então ser usado em trocas com aplicativos ou sites de terceiros para identificar a sessão com segurança. Por exemplo, o token de sessão OTP pode ser usado com um aplicativo de pagamento. diff --git a/i18n/pt/docusaurus-plugin-content-docs/version-20-R10/Concepts/operators.md b/i18n/pt/docusaurus-plugin-content-docs/version-20-R10/Concepts/operators.md index 5dbb7ed4bddc3f..9494e03c367619 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/version-20-R10/Concepts/operators.md +++ b/i18n/pt/docusaurus-plugin-content-docs/version-20-R10/Concepts/operators.md @@ -90,7 +90,10 @@ São suportados os seguintes operadores de atribuição compostos: | | Time \*= Number | Number | `$t1*=5 //$t1:=$t1*5` | | | Picture \*= Number | Imagem | `$p1*=5 //$p1:=$p1*5 (redimensionar $p1 por 5)` | -Esses operadores se aplicam a quaisquer [expressões atribuíveis](quick-tour.md#assignable-vs-non-assignable-expressions) (exceto imagens como propriedades de objetos ou elementos de coleções). +These operators apply on any [assignable expressions](quick-tour.md#assignable-vs-non-assignable-expressions) except: + +- pictures as object properties or collection elements, +- array index variables. A operação "source `operator` value" não é estritamente equivalente a "source := source `operator` value" porque a expressão que designa a fonte (variável, campo, propriedade de objeto, elemento de coleção) é avaliada apenas uma vez. Por exemplo, em expressões como `getPointer()->+=1` o método `getPointer` é chamado apenas uma vez. diff --git a/i18n/pt/docusaurus-plugin-content-docs/version-20-R9/API/SessionClass.md b/i18n/pt/docusaurus-plugin-content-docs/version-20-R9/API/SessionClass.md index 2a60234db4134e..7f50a117cbcb58 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/version-20-R9/API/SessionClass.md +++ b/i18n/pt/docusaurus-plugin-content-docs/version-20-R9/API/SessionClass.md @@ -133,7 +133,7 @@ A função `.createOTP()` cria um Para mais informações sobre os tokens OTP, consulte [esta seção](../WebServer/sessions.md#session-token-otp). -Por padrão, se o parâmetro *lifespan* for omitido, o token será criado com o mesmo tempo de vida que o [`.idleTimeOut`](#idletimeout) da sessão. Você pode definir um tempo limite personalizado passando um valor em segundos em *lifespan* (o valor mínimo é 10 segundos, *lifespan* é redefinido para 10 se um valor menor for passado). Se um token expirado for usado para restaurar uma sessão de usuário Web, ele será ignorado. +Por padrão, se o parâmetro *lifespan* for omitido, o token será criado com o mesmo tempo de vida que o [`.idleTimeOut`](#idletimeout) da sessão. You can set a custom timeout by passing a value in seconds in *lifespan*. Se um token expirado for usado para restaurar uma sessão de usuário Web, ele será ignorado. O token retornado pode então ser usado em trocas com aplicativos ou sites de terceiros para identificar a sessão com segurança. Por exemplo, o token de sessão OTP pode ser usado com um aplicativo de pagamento. diff --git a/i18n/pt/docusaurus-plugin-content-docs/version-20-R9/Concepts/operators.md b/i18n/pt/docusaurus-plugin-content-docs/version-20-R9/Concepts/operators.md index d5412569234e89..97a515a76d4a4f 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/version-20-R9/Concepts/operators.md +++ b/i18n/pt/docusaurus-plugin-content-docs/version-20-R9/Concepts/operators.md @@ -90,7 +90,10 @@ São suportados os seguintes operadores de atribuição compostos: | | Time \*= Number | Number | `$t1*=5 //$t1:=$t1*5` | | | Picture \*= Number | Imagem | `$p1*=5 //$p1:=$p1*5 (redimensionar $p1 por 5)` | -Esses operadores se aplicam a quaisquer [expressões atribuíveis](quick-tour.md#assignable-vs-non-assignable-expressions) (exceto imagens como propriedades de objetos ou elementos de coleções). +These operators apply on any [assignable expressions](quick-tour.md#assignable-vs-non-assignable-expressions) except: + +- pictures as object properties or collection elements, +- array index variables. A operação "source `operator` value" não é estritamente equivalente a "source := source `operator` value" porque a expressão que designa a fonte (variável, campo, propriedade de objeto, elemento de coleção) é avaliada apenas uma vez. Por exemplo, em expressões como `getPointer()->+=1` o método `getPointer` é chamado apenas uma vez. diff --git a/i18n/pt/docusaurus-plugin-content-docs/version-20/Concepts/operators.md b/i18n/pt/docusaurus-plugin-content-docs/version-20/Concepts/operators.md index 8f7fbe36152e43..935a3d60282c3a 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/version-20/Concepts/operators.md +++ b/i18n/pt/docusaurus-plugin-content-docs/version-20/Concepts/operators.md @@ -93,7 +93,9 @@ São suportados os seguintes operadores de atribuição compostos: | | Time *= Number | Number | `$t1*=5 //$t1:=$t1*5` | | | Picture *= Number | Imagem | `$p1*=5 //$p1:=$p1*5 (redimensionar $p1 por 5)` | -Estes operadores aplicam-se a quaisquer [expressões atribuíveis](quick-tour.md#assignable-vs-non-assignable-expressions) (exceto imagens como propriedades de objecto ou elementos de colecções). +These operators apply on any [assignable expressions](quick-tour.md#assignable-vs-non-assignable-expressions) except: +- pictures as object properties or collection elements, +- array index variables. A operação "source `operator` value" não é estritamente equivalente a "source := source `operator` value" porque a expressão que designa a fonte (variável, campo, propriedade de objeto, elemento de coleção) só é avaliada uma vez. Por exemplo, numa expressão como `getPointer()->+=1` o método `getPointer` é chamado apenas uma vez. diff --git a/sidebars.js b/sidebars.js index 8072dbade8a4f2..0f0a7149439ff0 100644 --- a/sidebars.js +++ b/sidebars.js @@ -15,40 +15,52 @@ module.exports = }, items: [ "GettingStarted/installation", - "GettingStarted/creating", + "Project/overview", "Notes/updates" ] }, { type: "category", - label: "Core Development", + label: "Project & IDE", link: { type: "generated-index", - title: "Core Development", - slug: "/category/core-development", + title: "Project & IDE", + slug: "/category/project-ide", keywords: [ - "core" + "ide" ], image: "/img/docusaurus.png" }, items: [ + "GettingStarted/creating", + "Project/architecture", + { + type: "category", + label: "Dababase structure", + items: [ + "Develop/field-properties" + ] + }, + { + type: "category", + label: "Code & Methods", + items: [ + "Project/code-overview", + "code-editor/write-class-method", + "Project/project-method-properties", + "Project/documentation" + ] + }, + "Project/components", + "Project/compiler", { type: "category", - label: "Project Management", + label: "Settings", link: { - type: "doc", - id: "Project/overview" + type: "doc", + id: "settings/overview" }, items: [ - "Project/architecture", - { - type: "category", - label: "Settings", - link: { - type: "doc", - id: "settings/overview" - }, - items: [ "settings/general", "settings/interface", "settings/compiler", @@ -61,88 +73,34 @@ module.exports = "settings/security", "settings/compatibility" ] - }, - "Project/components", - "Project/date-time-formats", - "Project/documentation", - { - type: "category", - label: "Dababase structure", - items: [ - "Develop/field-properties", - ] - } - ] - }, - { - type: "category", - label: "Development Environment", - items: [ - "Project/code-overview", - "code-editor/write-class-method", - "Project/compiler", - { - type: "category", - label: "Debugging", - link: { - type: "doc", - id: "Debugging/basics" - }, - items: [ + }, + "Desktop/building", + { + type: "category", + label: "Debugging", + link: { + type: "doc", + id: "Debugging/basics" + }, + items: [ "Debugging/debugger", "Debugging/breakpoints", "Debugging/debugging-remote" ] - }, - "Debugging/debugLogFiles", - { - type: "category", - label: "Preferences", - link: { - type: "doc", - id: "Preferences/overview" - }, - items: [ - "Preferences/general", - "Preferences/structure", - "Preferences/forms", - "Preferences/methods", - "Preferences/shortcuts" - ] - } - - ] - }, - { - type: "category", - label: "ORDA", - link: { - type: "doc", - id: "ORDA/overview" }, - items: [ - "ORDA/dsmapping", - "ORDA/ordaClasses", - "ORDA/orda-events", - "ORDA/entities", - "ORDA/global-stamp", - "ORDA/datastores", - "ORDA/privileges", - "ORDA/client-server-optimization", - "ORDA/glossary" - ] - }, - { - type: "category", - label: "Processes", - items: [ - "Develop/processes", - "Develop/preemptive-processes" - ] - }, - "Develop-legacy/transactions", - "Tags/transformation-tags" - ] + { + type: "category", + label: "Application Preferences", + items: [ + "Preferences/overview", + "Preferences/general", + "Preferences/structure", + "Preferences/forms", + "Preferences/methods", + "Preferences/shortcuts" + ] + } + ] }, { type: "category", @@ -152,7 +110,7 @@ module.exports = title: "4D Language", slug: "/category/4d-language", keywords: [ - "language" + "language","orda" ], image: "/img/docusaurus.png" }, @@ -201,12 +159,13 @@ module.exports = "Concepts/paths" ] }, + "commands/command-index", { type: "category", - label: "Commands", + label: "Commands by theme", link: { type: "generated-index", - title: "Commands", + title: "Commands by theme", slug: "/category/commands", keywords: [ "commands" @@ -214,7 +173,6 @@ module.exports = image: "/img/docusaurus.png" }, items: [ - "commands/command-index", { type: "category", label: "4D Environment", @@ -483,34 +441,6 @@ module.exports = "commands-legacy/register-data-key" ] }, - { - type: "category", - label: "Database Methods", - link: { - type: "doc", - id: "commands/theme/Database_Methods_theme" - }, - items: [ - "commands-legacy/on-backup-shutdown-database-method", - "commands-legacy/on-backup-startup-database-method", - "commands-legacy/on-drop-database-method", - "commands-legacy/on-exit-database-method", - "commands-legacy/on-host-database-event-database-method", - "commands-legacy/on-mobile-app-action-database-method", - "commands-legacy/on-mobile-app-authentication-database-method", - "commands-legacy/on-rest-authentication-database-method", - "commands-legacy/on-server-close-connection-database-method", - "commands-legacy/on-server-open-connection-database-method", - "commands-legacy/on-server-shutdown-database-method", - "commands-legacy/on-server-startup-database-method", - "commands-legacy/on-sql-authentication-database-method", - "commands-legacy/on-startup-database-method", - "commands-legacy/on-system-event-database-method", - "commands-legacy/on-web-authentication-database-method", - "commands-legacy/on-web-connection-database-method", - "commands-legacy/on-web-legacy-close-session-database-method" - ] - }, { type: "category", label: "Date and Time", @@ -2278,7 +2208,6 @@ module.exports = type: "category", label: "Classes", items: [ - "API/overview", "API/BlobClass", "API/ClassClass", "API/CollectionClass", @@ -2321,7 +2250,7 @@ module.exports = ], link: { type: "generated-index", - title: "Class Functions", + title: "Classes", description: "List of built-in 4D classes", slug: "/category/class-API-reference", keywords: [ @@ -2333,1030 +2262,1132 @@ module.exports = ] }, { - type: "category", - label: "Administration", - link: { - type: "generated-index", - title: "Administration", - description: "How to monitor your 4D applications", - keywords: [ - "administration" - ], - image: "/img/docusaurus.png" - }, - items: [ - { type: "category", - label: "4D Server Administration Window", + label: "Core Development", link: { - type: "doc", - id: "ServerWindow/overview" + type: "generated-index", + title: "Core Development", + slug: "/category/core", + image: "/img/docusaurus.png" }, items: [ - "ServerWindow/monitor", - "ServerWindow/users", - "ServerWindow/processes", - "ServerWindow/maintenance", - "ServerWindow/application-server", - "ServerWindow/sql-server", - "ServerWindow/http-server", - "ServerWindow/real-time-monitor", - "ServerWindow/remote-admin" + { + type: "category", + label: "ORDA", + link: { + type: "doc", + id: "ORDA/overview" + }, + items: [ + "ORDA/dsmapping", + "ORDA/ordaClasses", + "ORDA/entities", + "ORDA/global-stamp", + "ORDA/datastores", + "ORDA/privileges", + "ORDA/client-server-optimization", + "ORDA/glossary" ] }, { type: "category", - label: "Web Administration", + label: "Processes", link: { type: "generated-index", - title: "Web Administration", - description: "4D web tools for administrating and monitoring your applications.", - slug: "/category/web-administration", + title: "Processes", + slug: "/category/processes", keywords: [ - "web administration" + "feaprocessestures" ], image: "/img/docusaurus.png" }, items: [ - "Admin/webAdmin", - "Admin/dataExplorer" + "Develop/processes", + "Develop/preemptive-processes" ] }, - { - type: "doc", - label: "Command Line Interface", - id: "Admin/cli" - }, - { - type: "doc", - label: "TLS Protocol", - id: "Admin/tls" - }, - { - type: "doc", - label: "Licenses", - id: "Admin/licenses" - }, { type: "category", - label: "MSC", + label: "Database Methods", link: { - type: "doc", - id: "MSC/overview" + type: "generated-index", + title: "Database Methods", + slug: "/category/database-methods", + image: "/img/docusaurus.png" }, items: [ - "MSC/information", - "MSC/analysis", - "MSC/verify", - "MSC/backup", - "MSC/compact", - "MSC/rollback", - "MSC/restore", - "MSC/repair", - "MSC/encrypt" + "commands-legacy/on-backup-shutdown-database-method", + "commands-legacy/on-backup-startup-database-method", + "commands-legacy/on-drop-database-method", + "commands-legacy/on-exit-database-method", + "commands-legacy/on-host-database-event-database-method", + "commands-legacy/on-mobile-app-action-database-method", + "commands-legacy/on-mobile-app-authentication-database-method", + "commands-legacy/on-rest-authentication-database-method", + "commands-legacy/on-server-close-connection-database-method", + "commands-legacy/on-server-open-connection-database-method", + "commands-legacy/on-server-shutdown-database-method", + "commands-legacy/on-server-startup-database-method", + "commands-legacy/on-sql-authentication-database-method", + "commands-legacy/on-startup-database-method", + "commands-legacy/on-system-event-database-method", + "commands-legacy/on-web-authentication-database-method", + "commands-legacy/on-web-connection-database-method", + "commands-legacy/on-web-legacy-close-session-database-method" ] }, + "Develop-legacy/transactions", + "Tags/transformation-tags", + "Project/date-time-formats" + ] + }, + { + type: "category", + label: "Web Applications", + link: { + type: "generated-index", + title: "Web Applications", + description: "Guides for developing Web applications with 4D", + keywords: [ + "web applications" + ], + image: "/img/docusaurus.png" + }, + items: [ + { + type: "link", + label: "4D Qodly Pro", + href: "https://developer.qodly.com/docs" + }, { type: "category", - label: "Backup and Restore", + label: "Web Server", link: { type: "doc", - id: "Backup/overview" + id: "WebServer/webServer" }, items: [ - "Backup/backup", - "Backup/settings", - "Backup/log", - "Backup/restore" + "WebServer/gettingStarted", + "WebServer/webServerConfig", + "WebServer/webServerAdmin", + "WebServer/webServerObject", + "WebServer/templates", + "WebServer/httpRequests", + "WebServer/http-request-handler", + "WebServer/allowProject", + "WebServer/errorPages", + "WebServer/authentication", + "WebServer/sessions", + "WebServer/preemptiveWeb" ] }, - { - type: "doc", - label: "Data Collection", - id: "Admin/data-collect" - } - ] - }, - { - type: "category", - label: "Extensions", - link: { - type: "doc", - id: "Extensions/overview" - }, - items: [ { type: "category", - label: "4D View Pro", + label: "REST API", link: { type: "generated-index", - title: "4D View Pro", - slug: "/category/4d-view-pro", + title: "REST API", + description: "Exposing your datastore to REST and using the REST API.", keywords: [ - "4D View Pro" + "REST server" ], image: "/img/docusaurus.png" }, items: [ - "ViewPro/getting-started", - "ViewPro/configuring", - "ViewPro/formulas", - "ViewPro/classes", - "ViewPro/advanced-programming", { type: "category", - label: "Commands", + label: "Exposing your datastore in REST", link: { - type: "doc", - id: "ViewPro/commands" + type: "generated-index", + title: "Exposing your datastore in REST", + description: "Configure your datastore for REST access", + keywords: [ + "REST access" + ], + image: "/img/docusaurus.png" }, items: [ - { - type: "category", - label: "A", - link: { - type: "generated-index", - title: "A", - slug: "/commands-legacy/A" - }, - items: [ - "ViewPro/commands/vp-add-formula-name", - "ViewPro/commands/vp-add-range-name", - "ViewPro/commands/vp-add-selection", - "ViewPro/commands/vp-add-sheet", - "ViewPro/commands/vp-add-span", - "ViewPro/commands/vp-add-stylesheet", - "ViewPro/commands/vp-all" - ] - }, - { - type: "category", - label: "C", - link: { - type: "generated-index", - title: "C", - slug: "/commands-legacy/C" - }, - items: [ - "ViewPro/commands/vp-cell", - "ViewPro/commands/vp-cells", - "ViewPro/commands/vp-column", - "ViewPro/commands/vp-column-autofit", - "ViewPro/commands/vp-combine-ranges", - "ViewPro/commands/vp-convert-from-4d-view", - "ViewPro/commands/vp-convert-to-picture", - "ViewPro/commands/vp-copy-to-object", - "ViewPro/commands/vp-create-table" - ] - }, - { - type: "category", - label: "D", - link: { - type: "generated-index", - title: "D", - slug: "/commands-legacy/D" - }, - items: [ - "ViewPro/commands/vp-delete-columns", - "ViewPro/commands/vp-delete-rows" - ] - }, - { - type: "category", - label: "E", - link: { - type: "generated-index", - title: "E", - slug: "/commands-legacy/E" - }, - items: [ - "ViewPro/commands/vp-export-document", - "ViewPro/commands/vp-export-to-blob", - "ViewPro/commands/vp-export-to-object" - ] - }, - { - type: "category", - label: "F", - link: { - type: "generated-index", - title: "F", - slug: "/commands-legacy/F" - }, - items: [ - "ViewPro/commands/vp-find", - "ViewPro/commands/vp-find-table", - "ViewPro/commands/vp-flush-commands", - "ViewPro/commands/vp-font-to-object" - ] - }, - { - type: "category", - label: "G", - link: { - type: "generated-index", - title: "G", - slug: "/commands-legacy/G" - }, - items: [ - "ViewPro/commands/vp-get-active-cell", - "ViewPro/commands/vp-get-binding-path", - "ViewPro/commands/vp-get-cell-style", - "ViewPro/commands/vp-get-column-attributes", - "ViewPro/commands/vp-get-column-count", - "ViewPro/commands/vp-get-current-sheet", - "ViewPro/commands/vp-get-data-context", - "ViewPro/commands/vp-get-default-style", - "ViewPro/commands/vp-get-formula", - "ViewPro/commands/vp-get-formula-by-name", - "ViewPro/commands/vp-get-formulas", - "ViewPro/commands/vp-get-frozen-panes", - "ViewPro/commands/vp-get-names", - "ViewPro/commands/vp-get-print-info", - "ViewPro/commands/vp-get-row-attributes", - "ViewPro/commands/vp-get-row-count", - "ViewPro/commands/vp-get-selection", - "ViewPro/commands/vp-get-sheet-count", - "ViewPro/commands/vp-get-sheet-index", - "ViewPro/commands/vp-get-sheet-name", - "ViewPro/commands/vp-get-sheet-options", - "ViewPro/commands/vp-get-show-print-lines", - "ViewPro/commands/vp-get-spans", - "ViewPro/commands/vp-get-stylesheet", - "ViewPro/commands/vp-get-stylesheets", - "ViewPro/commands/vp-get-table-column-attributes", - "ViewPro/commands/vp-get-table-column-index", - "ViewPro/commands/vp-get-table-dirty-rows", - "ViewPro/commands/vp-get-table-range", - "ViewPro/commands/vp-get-table-theme", - "ViewPro/commands/vp-get-tables", - "ViewPro/commands/vp-get-value", - "ViewPro/commands/vp-get-values", - "ViewPro/commands/vp-get-workbook-options" - ] - }, - { - type: "category", - label: "I", - link: { - type: "generated-index", - title: "I", - slug: "/commands-legacy/I" - }, - items: [ - "ViewPro/commands/vp-import-document", - "ViewPro/commands/vp-import-from-blob", - "ViewPro/commands/vp-import-from-object", - "ViewPro/commands/vp-insert-columns", - "ViewPro/commands/vp-insert-rows", - "ViewPro/commands/vp-insert-table-columns", - "ViewPro/commands/vp-insert-table-rows" - ] - }, - { - type: "category", - label: "M", - link: { - type: "generated-index", - title: "M", - slug: "/commands-legacy/M" - }, - items: [ - "ViewPro/commands/vp-move-cells" - ] - }, - { - type: "category", - label: "N", - link: { - type: "generated-index", - title: "N", - slug: "/commands-legacy/N" - }, - items: [ - "ViewPro/commands/vp-name", - "ViewPro/commands/vp-new-document" - ] - }, - { - type: "category", - label: "O", - link: { - type: "generated-index", - title: "O", - slug: "/commands-legacy/O" - }, - items: [ - "ViewPro/commands/vp-object-to-font" - ] - }, - { - type: "category", - label: "P", - link: { - type: "generated-index", - title: "P", - slug: "/commands-legacy/P" - }, - items: [ - "ViewPro/commands/vp-paste-from-object", - "ViewPro/commands/vp-print" - ] - }, - { - type: "category", - label: "R", - link: { - type: "generated-index", - title: "R", - slug: "/commands-legacy/R" - }, - items: [ - "ViewPro/commands/vp-recompute-formulas", - "ViewPro/commands/vp-remove-name", - "ViewPro/commands/vp-remove-sheet", - "ViewPro/commands/vp-remove-span", - "ViewPro/commands/vp-remove-stylesheet", - "ViewPro/commands/vp-remove-table", - "ViewPro/commands/vp-remove-table-columns", - "ViewPro/commands/vp-remove-table-rows", - "ViewPro/commands/vp-reset-selection", - "ViewPro/commands/vp-resize-table", - "ViewPro/commands/vp-resume-computing", - "ViewPro/commands/vp-row", - "ViewPro/commands/vp-row-autofit", - "ViewPro/commands/vp-run-offscreen-area" - ] - }, - { - type: "category", - label: "S", - link: { - type: "generated-index", - title: "S", - slug: "/commands-legacy/S" - }, - items: [ - "ViewPro/commands/vp-set-active-cell", - "ViewPro/commands/vp-set-allowed-methods", - "ViewPro/commands/vp-set-binding-path", - "ViewPro/commands/vp-set-boolean-value", - "ViewPro/commands/vp-set-border", - "ViewPro/commands/vp-set-cell-style", - "ViewPro/commands/vp-set-column-attributes", - "ViewPro/commands/vp-set-column-count", - "ViewPro/commands/vp-set-current-sheet", - "ViewPro/commands/vp-set-custom-functions", - "ViewPro/commands/vp-set-data-context", - "ViewPro/commands/vp-set-date-time-value", - "ViewPro/commands/vp-set-date-value", - "ViewPro/commands/vp-set-default-style", - "ViewPro/commands/vp-set-field", - "ViewPro/commands/vp-set-formula", - "ViewPro/commands/vp-set-formulas", - "ViewPro/commands/vp-set-frozen-panes", - "ViewPro/commands/vp-set-num-value", - "ViewPro/commands/vp-set-print-info", - "ViewPro/commands/vp-set-row-attributes", - "ViewPro/commands/vp-set-row-count", - "ViewPro/commands/vp-set-selection", - "ViewPro/commands/vp-set-sheet-count", - "ViewPro/commands/vp-set-sheet-name", - "ViewPro/commands/vp-set-sheet-options", - "ViewPro/commands/vp-set-show-print-lines", - "ViewPro/commands/vp-set-table-column-attributes", - "ViewPro/commands/vp-set-table-theme", - "ViewPro/commands/vp-set-text-value", - "ViewPro/commands/vp-set-time-value", - "ViewPro/commands/vp-set-value", - "ViewPro/commands/vp-set-values", - "ViewPro/commands/vp-set-workbook-options", - "ViewPro/commands/vp-show-cell", - "ViewPro/commands/vp-suspend-computing" - ] - } + "REST/gettingStarted", + "REST/configuration", + "REST/authUsers", + "REST/genInfo", + "REST/manData", + "REST/classFunctions", + "REST/REST_requests" + ] + }, + { + type: "category", + label: "API (general)", + link: { + type: "generated-index", + title: "API (general)", + description: "REST API for global information", + keywords: [ + "REST API" + ], + image: "/img/docusaurus.png" + }, + items: [ + "REST/catalog", + "REST/info", + "REST/singleton", + "REST/upload" + ] + }, + { + type: "category", + label: "API (dataClass)", + link: { + type: "generated-index", + title: "API (dataClass)", + description: "REST API for dataClass.", + keywords: [ + "REST API" + ], + image: "/img/docusaurus.png" + }, + items: [ + "REST/dataClass", + "REST/asArray", + "REST/atomic_$atonce", + "REST/attributes", + "REST/binary", + "REST/clean", + "REST/compute", + "REST/distinct", + "REST/entityset", + "REST/expand", + "REST/filter", + "REST/format", + "REST/imageformat", + "REST/lock", + "REST/method", + "REST/orderby", + "REST/querypath", + "REST/queryplan", + "REST/savedfilter", + "REST/savedorderby", + "REST/skip", + "REST/timeout", + "REST/top_$limit", + "REST/version" + ] + } + ] + } + ] + }, + { + type: "category", + label: "Desktop Applications", + link: { + type: "generated-index", + title: "Desktop Applications", + description: "Guides for developing Desktop applications with 4D", + keywords: [ + "desktop applications" + ], + image: "/img/docusaurus.png" + }, + items: [ + { + type: "doc", + label: "Client/Server", + id: "Desktop/clientServer" + }, + { + type: "category", + label: "Forms", + link: { + type: "doc", + id: "FormEditor/forms" + }, + items: [ + "FormEditor/stylesheets", + "FormEditor/pictures", + { + type: "category", + label: "Form Editor", + link: { + type: "doc", + id: "FormEditor/formEditor" + }, + items: [ + "FormEditor/macros", + "FormEditor/objectLibrary" + ] + }, + { + type: "category", + label: "Form Properties", + link: { + type: "doc", + id: "FormEditor/jsonReference" + }, + items: [ + "FormEditor/action", + "FormEditor/propertiesForm", + "FormEditor/formSize", + "FormEditor/markers", + "FormEditor/menu", + "FormEditor/print", + "FormEditor/windowSize" + ] + }, + { + type: "category", + label: "Form Objects", + link: { + type: "doc", + id: "FormObjects/formObjectsOverview" + }, + items: [ + "FormObjects/buttonOverview", + "FormObjects/buttonGridOverview", + "FormObjects/checkboxOverview", + "FormObjects/comboBoxOverview", + "FormObjects/dropdownListOverview", + "FormObjects/groupBox", + "FormObjects/inputOverview", + "FormObjects/listOverview", + "FormObjects/listboxOverview", + "FormObjects/pictureButtonOverview", + "FormObjects/picturePopupMenuOverview", + "FormObjects/pluginAreaOverview", + "FormObjects/progressIndicator", + "FormObjects/radiobuttonOverview", + "FormObjects/ruler", + "FormObjects/shapesOverview", + "FormObjects/spinner", + "FormObjects/splitters", + "FormObjects/staticPicture", + "FormObjects/stepper", + "FormObjects/subformOverview", + "FormObjects/tabControl", + "FormObjects/text", + "FormObjects/webAreaOverview", + "FormObjects/viewProAreaOverview", + "FormObjects/writeProAreaOverview" + ] + }, + { + type: "category", + label: "Form Object Properties", + link: { + type: "doc", + id: "FormObjects/propertiesReference" + }, + items: [ + "FormObjects/propertiesAction", + "FormObjects/propertiesAnimation", + "FormObjects/propertiesAppearance", + "FormObjects/propertiesBackgroundAndBorder", + "FormObjects/propertiesCoordinatesAndSizing", + "FormObjects/propertiesCrop", + "FormObjects/propertiesDataSource", + "FormObjects/propertiesDisplay", + "FormObjects/propertiesEntry", + "FormObjects/propertiesFooters", + "FormObjects/propertiesGridlines", + "FormObjects/propertiesHeaders", + "FormObjects/propertiesHelp", + "FormObjects/propertiesHierarchy", + "FormObjects/propertiesListBox", + "FormObjects/propertiesObject", + "FormObjects/propertiesPicture", + "FormObjects/propertiesPlugIns", + "FormObjects/propertiesPrint", + "FormObjects/propertiesRangeOfValues", + "FormObjects/propertiesResizingOptions", + "FormObjects/propertiesScale", + "FormObjects/propertiesSubform", + "FormObjects/propertiesText", + "FormObjects/propertiesTextAndPicture", + "FormObjects/propertiesWebArea" + ] + }, + { + type: "category", + label: "Form Events", + link: { + type: "doc", + id: "Events/overview" + }, + items: [ + "Events/onActivate", + "Events/onAfterEdit", + "Events/onAfterKeystroke", + "Events/onAfterSort", + "Events/onAlternativeClick", + "Events/onBeforeDataEntry", + "Events/onBeforeKeystroke", + "Events/onBeginDragOver", + "Events/onBeginUrlLoading", + "Events/onBoundVariableChange", + "Events/onClicked", + "Events/onCloseBox", + "Events/onCloseDetail", + "Events/onCollapse", + "Events/onColumnMoved", + "Events/onColumnResize", + "Events/onDataChange", + "Events/onDeactivate", + "Events/onDeleteAction", + "Events/onDisplayDetail", + "Events/onDoubleClicked", + "Events/onDragOver", + "Events/onDrop", + "Events/onEndUrlLoading", + "Events/onExpand", + "Events/onFooterClick", + "Events/onGettingFocus", + "Events/onHeader", + "Events/onHeaderClick", + "Events/onLoad", + "Events/onLoadRecord", + "Events/onLongClick", + "Events/onLosingFocus", + "Events/onMenuSelected", + "Events/onMouseEnter", + "Events/onMouseLeave", + "Events/onMouseMove", + "Events/onMouseUp", + "Events/onOpenDetail", + "Events/onOpenExternalLink", + "Events/onOutsideCall", + "Events/onPageChange", + "Events/onPlugInArea", + "Events/onPrintingBreak", + "Events/onPrintingDetail", + "Events/onPrintingFooter", + "Events/onResize", + "Events/onRowMoved", + "Events/onRowResize", + "Events/onScroll", + "Events/onSelectionChange", + "Events/onTimer", + "Events/onUnload", + "Events/onUrlFiltering", + "Events/onUrlLoadingError", + "Events/onUrlResourceLoading", + "Events/onValidate", + "Events/onVpRangeChanged", + "Events/onVpReady", + "Events/onWindowOpeningDenied" ] } ] }, + { + type: "doc", + label: "Labels", + id: "Desktop/labels" + }, + { + type: "category", + label: "Menus", + link: { + type: "doc", + id: "Menus/overview" + }, + items: [ + "Menus/creating", + "Menus/properties", + "Menus/bars", + "Menus/sdi" + ] + }, + { + type: "category", + label: "Access Rights", + link: { + type: "generated-index", + title: "Access Rights", + description: "Access control and user privileges for desktop applications.", + slug: "/category/access-rights", + keywords: [ + "access rights", + "user settings", + "permissions" + ], + image: "/img/docusaurus.png" + }, + items: [ + "Users/overview", + "Users/editing" + ] + } + ] + }, + { + type: "category", + label: "Administration", + link: { + type: "generated-index", + title: "Administration", + description: "How to monitor your 4D applications", + keywords: [ + "administration" + ], + image: "/img/docusaurus.png" + }, + items: [ { type: "category", - label: "4D Write Pro", + label: "4D Server Administration Window", link: { - type: "generated-index", - title: "4D Write Pro", - slug: "/category/4d-write-pro", - keywords: [ - "4D Write Pro" - ], - image: "/img/docusaurus.png" + type: "doc", + id: "ServerWindow/overview" }, items: [ - "WritePro/writeprointerface", - "WritePro/managing-formulas", - "WritePro/commands-legacy/4d-write-pro-attributes", - { - type: "category", - label: "Commands", - link: { - type: "doc", - id: "WritePro/commands/command-index" - }, - items: [ - "WritePro/commands/wp-add-picture", - "WritePro/commands-legacy/wp-bookmark-range", - "WritePro/commands-legacy/wp-compute-formulas", - "WritePro/commands-legacy/wp-delete-bookmark", - "WritePro/commands-legacy/wp-delete-footer", - "WritePro/commands-legacy/wp-delete-header", - "WritePro/commands-legacy/wp-delete-picture", - "WritePro/commands/wp-delete-section", - "WritePro/commands-legacy/wp-delete-style-sheet", - "WritePro/commands/wp-delete-subsection", - "WritePro/commands-legacy/wp-delete-text-box", - "WritePro/commands/wp-export-document", - "WritePro/commands/wp-export-variable", - "WritePro/commands-legacy/wp-find-all", - "WritePro/commands-legacy/wp-find-next", - "WritePro/commands-legacy/wp-find-previous", - "WritePro/commands-legacy/wp-freeze-formulas", - "WritePro/commands/wp-get-attributes", - "WritePro/commands-legacy/wp-get-body", - "WritePro/commands-legacy/wp-get-bookmarks", - "WritePro/commands-legacy/wp-get-breaks", - "WritePro/commands-legacy/wp-get-data-context", - "WritePro/commands-legacy/wp-get-element-by-id", - "WritePro/commands-legacy/wp-get-elements", - "WritePro/commands-legacy/wp-get-footer", - "WritePro/commands-legacy/wp-get-formulas", - "WritePro/commands-legacy/wp-get-frame", - "WritePro/commands-legacy/wp-get-header", - "WritePro/commands-legacy/wp-get-links", - "WritePro/commands-legacy/wp-get-page-count", - "WritePro/commands-legacy/wp-get-position", - "WritePro/commands-legacy/wp-get-section", - "WritePro/commands-legacy/wp-get-sections", - "WritePro/commands-legacy/wp-get-style-sheet", - "WritePro/commands-legacy/wp-get-style-sheets", - "WritePro/commands-legacy/wp-get-subsection", - "WritePro/commands-legacy/wp-get-text", - "WritePro/commands-legacy/wp-get-view-properties", - "WritePro/commands/wp-import-document", - "WritePro/commands-legacy/wp-import-style-sheets", - "WritePro/commands/wp-insert-break", - "WritePro/commands/wp-insert-document-body", - "WritePro/commands/wp-insert-formula", - "WritePro/commands/wp-insert-picture", - "WritePro/commands-legacy/wp-insert-table", - "WritePro/commands-legacy/wp-is-font-style-supported", - "WritePro/commands-legacy/wp-new", - "WritePro/commands-legacy/wp-new-bookmark", - "WritePro/commands-legacy/wp-new-footer", - "WritePro/commands-legacy/wp-new-header", - "WritePro/commands-legacy/wp-new-style-sheet", - "WritePro/commands-legacy/wp-new-subsection", - "WritePro/commands-legacy/wp-new-text-box", - "WritePro/commands-legacy/wp-paragraph-range", - "WritePro/commands-legacy/wp-picture-range", - "WritePro/commands-legacy/wp-print", - "WritePro/commands/wp-reset-attributes", - "WritePro/commands-legacy/wp-select", - "WritePro/commands-legacy/wp-selection-range", - "WritePro/commands/wp-set-attributes", - "WritePro/commands-legacy/wp-set-data-context", - "WritePro/commands-legacy/wp-set-frame", - "WritePro/commands-legacy/wp-set-link", - "WritePro/commands-legacy/wp-set-text", - "WritePro/commands-legacy/wp-set-view-properties", - "WritePro/commands/wp-table-append-row", - "WritePro/commands-legacy/wp-table-delete-columns", - "WritePro/commands-legacy/wp-table-delete-rows", - "WritePro/commands-legacy/wp-table-get-cells", - "WritePro/commands-legacy/wp-table-get-columns", - "WritePro/commands-legacy/wp-table-get-rows", - "WritePro/commands-legacy/wp-table-insert-columns", - "WritePro/commands-legacy/wp-table-insert-rows", - "WritePro/commands-legacy/wp-table-merge-cells", - "WritePro/commands-legacy/wp-table-range", - "WritePro/commands-legacy/wp-table-split-cells", - "WritePro/commands-legacy/wp-text-range", - "WritePro/commands-legacy/wp-use-page-setup" - ] - } + "ServerWindow/monitor", + "ServerWindow/users", + "ServerWindow/processes", + "ServerWindow/maintenance", + "ServerWindow/application-server", + "ServerWindow/sql-server", + "ServerWindow/http-server", + "ServerWindow/real-time-monitor", + "ServerWindow/remote-admin" ] }, { type: "category", - label: "4D AIKit", + label: "Web Administration", link: { type: "generated-index", - title: "4D AIKit", - slug: "/category/4d-aikit", + title: "Web Administration", + description: "4D web tools for administrating and monitoring your applications.", + slug: "/category/web-administration", keywords: [ - "4D AIKit" + "web administration" ], image: "/img/docusaurus.png" }, items: [ - "aikit/overview", - "aikit/asynchronous-call", - "aikit/compatible-openai", - { - type: "category", - label: "Classes", - items: [ - "aikit/Classes/openai", - "aikit/Classes/openaiapiresource", - "aikit/Classes/openaichatapi", - "aikit/Classes/openaichatcompletionsapi", - "aikit/Classes/openaichatcompletionslistparameters", - "aikit/Classes/openaichatcompletionsmessagesapi", - "aikit/Classes/openaichatcompletionsmessagesparameters", - "aikit/Classes/openaichatcompletionsparameters", - "aikit/Classes/openaichatcompletionsresult", - "aikit/Classes/openaichatcompletionsstreamresult", - "aikit/Classes/openaichathelper", - "aikit/Classes/openaichoice", - "aikit/Classes/openaiembedding", - "aikit/Classes/openaiembeddingsapi", - "aikit/Classes/openaiembeddingsparameters", - "aikit/Classes/openaiembeddingsresult", - "aikit/Classes/openaierror", - "aikit/Classes/openaiimage", - "aikit/Classes/openaiimageparameters", - "aikit/Classes/openaiimagesapi", - "aikit/Classes/openaiimagesresult", - "aikit/Classes/openaimessage", - "aikit/Classes/openaimodel", - "aikit/Classes/openaimodellistresult", - "aikit/Classes/openaimodelresult", - "aikit/Classes/openaimodelsapi", - "aikit/Classes/openaimoderation", - "aikit/Classes/openaimoderationitem", - "aikit/Classes/openaimoderationresult", - "aikit/Classes/openaimoderationsapi", - "aikit/Classes/openaiparameters", - "aikit/Classes/openairesult", - "aikit/Classes/openaivision", - "aikit/Classes/openaivisionhelper" - ] - } + "Admin/webAdmin", + "Admin/dataExplorer" ] }, { - type: "link", - label: "4D Mobile App Server", - href: "https://github.com/4d-go-mobile/4D-Mobile-App-Server" - }, - { - type: "link", - label: "4D NetKit", - href: "https://developer.4d.com/4D-NetKit" + type: "doc", + label: "Command Line Interface", + id: "Admin/cli" }, { - type: "link", - label: "4D Progress", - href: "https://doc.4d.com/4Dv20R10/4D/20-R10/4D-Progress.100-7614210.en.html" + type: "doc", + label: "TLS Protocol", + id: "Admin/tls" }, { - type: "link", - label: "4D SVG", - href: "https://doc.4d.com/4Dv20R10/4D/20-R10/4D-SVG-Component.100-7614300.en.html" + type: "doc", + label: "Licenses", + id: "Admin/licenses" }, { - type: "link", - label: "4D Widgets", - href: "https://doc.4d.com/4Dv20R10/4D/20-R10/4D-Widgets.100-7614949.en.html" + type: "doc", + label: "Log Files", + id: "Debugging/debugLogFiles" }, - "Extensions/develop-components", - "Extensions/develop-plug-ins" - ] - }, - { - type: "category", - label: "Web Applications", - link: { - type: "generated-index", - title: "Web Applications", - description: "Guides for developing Web applications with 4D", - keywords: [ - "web applications" - ], - image: "/img/docusaurus.png" - }, - items: [ { type: "category", - label: "Web Server", + label: "MSC", link: { type: "doc", - id: "WebServer/webServer" + id: "MSC/overview" }, items: [ - "WebServer/webServerConfig", - "WebServer/webServerAdmin", - "WebServer/webServerObject" + "MSC/information", + "MSC/analysis", + "MSC/verify", + "MSC/backup", + "MSC/compact", + "MSC/rollback", + "MSC/restore", + "MSC/repair", + "MSC/encrypt" ] }, { type: "category", - label: "Web Development", + label: "Backup and Restore", link: { type: "doc", - id: "WebServer/gettingStarted" + id: "Backup/overview" }, items: [ - "WebServer/templates", - "WebServer/httpRequests", - "WebServer/http-request-handler", - "WebServer/allowProject", - "WebServer/errorPages", - "WebServer/authentication", - "WebServer/sessions", - "WebServer/preemptiveWeb" + "Backup/backup", + "Backup/settings", + "Backup/log", + "Backup/restore" ] }, { - type: "category", - label: "Qodly Studio", - link: { - type: "generated-index", - title: "Qodly Studio", - description: "Using Qodly Studio to build powerful web interfaces.", - slug: "/category/qodly-studio-in-4d", - keywords: [ - "Qodly Studio" - ], - image: "/img/docusaurus.png" - }, - items: [ - "WebServer/qodly-studio", - "WebServer/from-qodlyscript-to-4d" - ] + type: "doc", + label: "Data Collection", + id: "Admin/data-collect" + } + ] + }, + { + type: "category", + label: "Extensions", + link: { + type: "generated-index", + title: "Extensions", + slug: "/category/extensions", + keywords: [ + "component, extension, plug-in"], + image: "/img/docusaurus.png" + }, + items: [ + { + type: "category", + label: "Extending 4D applications", + link: { + type: "doc", + id: "Extensions/overview" + }, + items: [ + "Extensions/develop-components", + "Extensions/develop-plug-ins" + ] }, { type: "category", - label: "REST API", + label: "4D View Pro", link: { type: "generated-index", - title: "REST API", - description: "Exposing your datastore to REST and using the REST API.", + title: "4D View Pro", + slug: "/category/4d-view-pro", keywords: [ - "REST server" + "4D View Pro" ], image: "/img/docusaurus.png" }, items: [ + "ViewPro/getting-started", + "ViewPro/configuring", + "ViewPro/formulas", + "ViewPro/classes", + "ViewPro/advanced-programming", { type: "category", - label: "Exposing your datastore in REST", - link: { - type: "generated-index", - title: "Exposing your datastore in REST", - description: "Configure your datastore for REST access", - keywords: [ - "REST access" - ], - image: "/img/docusaurus.png" - }, - items: [ - "REST/gettingStarted", - "REST/configuration", - "REST/authUsers", - "REST/genInfo", - "REST/manData", - "REST/classFunctions", - "REST/REST_requests" - ] - }, - { - type: "category", - label: "API (general)", - link: { - type: "generated-index", - title: "API (general)", - description: "REST API for global information", - keywords: [ - "REST API" - ], - image: "/img/docusaurus.png" - }, - items: [ - "REST/catalog", - "REST/info", - "REST/singleton", - "REST/upload" - ] - }, - { - type: "category", - label: "API (dataClass)", + label: "Commands", link: { - type: "generated-index", - title: "API (dataClass)", - description: "REST API for dataClass.", - keywords: [ - "REST API" - ], - image: "/img/docusaurus.png" + type: "doc", + id: "ViewPro/commands" }, items: [ - "REST/dataClass", - "REST/asArray", - "REST/atomic_$atonce", - "REST/attributes", - "REST/binary", - "REST/clean", - "REST/compute", - "REST/distinct", - "REST/entityset", - "REST/expand", - "REST/filter", - "REST/format", - "REST/imageformat", - "REST/lock", - "REST/method", - "REST/orderby", - "REST/querypath", - "REST/queryplan", - "REST/savedfilter", - "REST/savedorderby", - "REST/skip", - "REST/timeout", - "REST/top_$limit", - "REST/version" + { + type: "category", + label: "A", + link: { + type: "generated-index", + title: "A", + slug: "/commands-legacy/A" + }, + items: [ + "ViewPro/commands/vp-add-formula-name", + "ViewPro/commands/vp-add-range-name", + "ViewPro/commands/vp-add-selection", + "ViewPro/commands/vp-add-sheet", + "ViewPro/commands/vp-add-span", + "ViewPro/commands/vp-add-stylesheet", + "ViewPro/commands/vp-all" + ] + }, + { + type: "category", + label: "C", + link: { + type: "generated-index", + title: "C", + slug: "/commands-legacy/C" + }, + items: [ + "ViewPro/commands/vp-cell", + "ViewPro/commands/vp-cells", + "ViewPro/commands/vp-column", + "ViewPro/commands/vp-column-autofit", + "ViewPro/commands/vp-combine-ranges", + "ViewPro/commands/vp-convert-from-4d-view", + "ViewPro/commands/vp-convert-to-picture", + "ViewPro/commands/vp-copy-to-object", + "ViewPro/commands/vp-create-table" + ] + }, + { + type: "category", + label: "D", + link: { + type: "generated-index", + title: "D", + slug: "/commands-legacy/D" + }, + items: [ + "ViewPro/commands/vp-delete-columns", + "ViewPro/commands/vp-delete-rows" + ] + }, + { + type: "category", + label: "E", + link: { + type: "generated-index", + title: "E", + slug: "/commands-legacy/E" + }, + items: [ + "ViewPro/commands/vp-export-document", + "ViewPro/commands/vp-export-to-blob", + "ViewPro/commands/vp-export-to-object" + ] + }, + { + type: "category", + label: "F", + link: { + type: "generated-index", + title: "F", + slug: "/commands-legacy/F" + }, + items: [ + "ViewPro/commands/vp-find", + "ViewPro/commands/vp-find-table", + "ViewPro/commands/vp-flush-commands", + "ViewPro/commands/vp-font-to-object" + ] + }, + { + type: "category", + label: "G", + link: { + type: "generated-index", + title: "G", + slug: "/commands-legacy/G" + }, + items: [ + "ViewPro/commands/vp-get-active-cell", + "ViewPro/commands/vp-get-binding-path", + "ViewPro/commands/vp-get-cell-style", + "ViewPro/commands/vp-get-column-attributes", + "ViewPro/commands/vp-get-column-count", + "ViewPro/commands/vp-get-current-sheet", + "ViewPro/commands/vp-get-data-context", + "ViewPro/commands/vp-get-default-style", + "ViewPro/commands/vp-get-formula", + "ViewPro/commands/vp-get-formula-by-name", + "ViewPro/commands/vp-get-formulas", + "ViewPro/commands/vp-get-frozen-panes", + "ViewPro/commands/vp-get-names", + "ViewPro/commands/vp-get-print-info", + "ViewPro/commands/vp-get-row-attributes", + "ViewPro/commands/vp-get-row-count", + "ViewPro/commands/vp-get-selection", + "ViewPro/commands/vp-get-sheet-count", + "ViewPro/commands/vp-get-sheet-index", + "ViewPro/commands/vp-get-sheet-name", + "ViewPro/commands/vp-get-sheet-options", + "ViewPro/commands/vp-get-show-print-lines", + "ViewPro/commands/vp-get-spans", + "ViewPro/commands/vp-get-stylesheet", + "ViewPro/commands/vp-get-stylesheets", + "ViewPro/commands/vp-get-table-column-attributes", + "ViewPro/commands/vp-get-table-column-index", + "ViewPro/commands/vp-get-table-dirty-rows", + "ViewPro/commands/vp-get-table-range", + "ViewPro/commands/vp-get-table-theme", + "ViewPro/commands/vp-get-tables", + "ViewPro/commands/vp-get-value", + "ViewPro/commands/vp-get-values", + "ViewPro/commands/vp-get-workbook-options" + ] + }, + { + type: "category", + label: "I", + link: { + type: "generated-index", + title: "I", + slug: "/commands-legacy/I" + }, + items: [ + "ViewPro/commands/vp-import-document", + "ViewPro/commands/vp-import-from-blob", + "ViewPro/commands/vp-import-from-object", + "ViewPro/commands/vp-insert-columns", + "ViewPro/commands/vp-insert-rows", + "ViewPro/commands/vp-insert-table-columns", + "ViewPro/commands/vp-insert-table-rows" + ] + }, + { + type: "category", + label: "M", + link: { + type: "generated-index", + title: "M", + slug: "/commands-legacy/M" + }, + items: [ + "ViewPro/commands/vp-move-cells" + ] + }, + { + type: "category", + label: "N", + link: { + type: "generated-index", + title: "N", + slug: "/commands-legacy/N" + }, + items: [ + "ViewPro/commands/vp-name", + "ViewPro/commands/vp-new-document" + ] + }, + { + type: "category", + label: "O", + link: { + type: "generated-index", + title: "O", + slug: "/commands-legacy/O" + }, + items: [ + "ViewPro/commands/vp-object-to-font" + ] + }, + { + type: "category", + label: "P", + link: { + type: "generated-index", + title: "P", + slug: "/commands-legacy/P" + }, + items: [ + "ViewPro/commands/vp-paste-from-object", + "ViewPro/commands/vp-print" + ] + }, + { + type: "category", + label: "R", + link: { + type: "generated-index", + title: "R", + slug: "/commands-legacy/R" + }, + items: [ + "ViewPro/commands/vp-recompute-formulas", + "ViewPro/commands/vp-remove-name", + "ViewPro/commands/vp-remove-sheet", + "ViewPro/commands/vp-remove-span", + "ViewPro/commands/vp-remove-stylesheet", + "ViewPro/commands/vp-remove-table", + "ViewPro/commands/vp-remove-table-columns", + "ViewPro/commands/vp-remove-table-rows", + "ViewPro/commands/vp-reset-selection", + "ViewPro/commands/vp-resize-table", + "ViewPro/commands/vp-resume-computing", + "ViewPro/commands/vp-row", + "ViewPro/commands/vp-row-autofit", + "ViewPro/commands/vp-run-offscreen-area" + ] + }, + { + type: "category", + label: "S", + link: { + type: "generated-index", + title: "S", + slug: "/commands-legacy/S" + }, + items: [ + "ViewPro/commands/vp-set-active-cell", + "ViewPro/commands/vp-set-allowed-methods", + "ViewPro/commands/vp-set-binding-path", + "ViewPro/commands/vp-set-boolean-value", + "ViewPro/commands/vp-set-border", + "ViewPro/commands/vp-set-cell-style", + "ViewPro/commands/vp-set-column-attributes", + "ViewPro/commands/vp-set-column-count", + "ViewPro/commands/vp-set-current-sheet", + "ViewPro/commands/vp-set-custom-functions", + "ViewPro/commands/vp-set-data-context", + "ViewPro/commands/vp-set-date-time-value", + "ViewPro/commands/vp-set-date-value", + "ViewPro/commands/vp-set-default-style", + "ViewPro/commands/vp-set-field", + "ViewPro/commands/vp-set-formula", + "ViewPro/commands/vp-set-formulas", + "ViewPro/commands/vp-set-frozen-panes", + "ViewPro/commands/vp-set-num-value", + "ViewPro/commands/vp-set-print-info", + "ViewPro/commands/vp-set-row-attributes", + "ViewPro/commands/vp-set-row-count", + "ViewPro/commands/vp-set-selection", + "ViewPro/commands/vp-set-sheet-count", + "ViewPro/commands/vp-set-sheet-name", + "ViewPro/commands/vp-set-sheet-options", + "ViewPro/commands/vp-set-show-print-lines", + "ViewPro/commands/vp-set-table-column-attributes", + "ViewPro/commands/vp-set-table-theme", + "ViewPro/commands/vp-set-text-value", + "ViewPro/commands/vp-set-time-value", + "ViewPro/commands/vp-set-value", + "ViewPro/commands/vp-set-values", + "ViewPro/commands/vp-set-workbook-options", + "ViewPro/commands/vp-show-cell", + "ViewPro/commands/vp-suspend-computing" + ] + } ] } ] - } - ] - }, - { - type: "category", - label: "Desktop Applications", - link: { - type: "generated-index", - title: "Desktop Applications", - description: "Guides for developing Desktop applications with 4D", - keywords: [ - "desktop applications" - ], - image: "/img/docusaurus.png" - }, - items: [ - { - type: "doc", - label: "Client/Server", - id: "Desktop/clientServer" }, { type: "category", - label: "Access Rights", + label: "4D Write Pro", link: { type: "generated-index", - title: "Access Rights", - description: "Access control and user privileges for desktop applications.", - slug: "/category/access-rights", + title: "4D Write Pro", + slug: "/category/4d-write-pro", keywords: [ - "access rights" + "4D Write Pro" ], image: "/img/docusaurus.png" }, - items: [ - "Users/overview", - "Users/editing" - ] - }, - { - type: "category", - label: "Forms", - link: { - type: "doc", - id: "FormEditor/forms" - }, - items: [ - "FormEditor/stylesheets", - "FormEditor/pictures", - { - type: "category", - label: "Form Editor", - link: { - type: "doc", - id: "FormEditor/formEditor" - }, - items: [ - "FormEditor/macros", - "FormEditor/objectLibrary" - ] - }, - { - type: "category", - label: "Form Properties", - link: { - type: "doc", - id: "FormEditor/jsonReference" - }, - items: [ - "FormEditor/action", - "FormEditor/propertiesForm", - "FormEditor/formSize", - "FormEditor/markers", - "FormEditor/menu", - "FormEditor/print", - "FormEditor/windowSize" - ] - }, - { - type: "category", - label: "Form Objects", - link: { - type: "doc", - id: "FormObjects/formObjectsOverview" - }, - items: [ - "FormObjects/buttonOverview", - "FormObjects/buttonGridOverview", - "FormObjects/checkboxOverview", - "FormObjects/comboBoxOverview", - "FormObjects/dropdownListOverview", - "FormObjects/groupBox", - "FormObjects/inputOverview", - "FormObjects/listOverview", - "FormObjects/listboxOverview", - "FormObjects/pictureButtonOverview", - "FormObjects/picturePopupMenuOverview", - "FormObjects/pluginAreaOverview", - "FormObjects/progressIndicator", - "FormObjects/radiobuttonOverview", - "FormObjects/ruler", - "FormObjects/shapesOverview", - "FormObjects/spinner", - "FormObjects/splitters", - "FormObjects/staticPicture", - "FormObjects/stepper", - "FormObjects/subformOverview", - "FormObjects/tabControl", - "FormObjects/text", - "FormObjects/webAreaOverview", - "FormObjects/viewProAreaOverview", - "FormObjects/writeProAreaOverview" - ] - }, - { - type: "category", - label: "Form Object Properties", - link: { - type: "doc", - id: "FormObjects/propertiesReference" - }, - items: [ - "FormObjects/propertiesAction", - "FormObjects/propertiesAnimation", - "FormObjects/propertiesAppearance", - "FormObjects/propertiesBackgroundAndBorder", - "FormObjects/propertiesCoordinatesAndSizing", - "FormObjects/propertiesCrop", - "FormObjects/propertiesDataSource", - "FormObjects/propertiesDisplay", - "FormObjects/propertiesEntry", - "FormObjects/propertiesFooters", - "FormObjects/propertiesGridlines", - "FormObjects/propertiesHeaders", - "FormObjects/propertiesHelp", - "FormObjects/propertiesHierarchy", - "FormObjects/propertiesListBox", - "FormObjects/propertiesObject", - "FormObjects/propertiesPicture", - "FormObjects/propertiesPlugIns", - "FormObjects/propertiesPrint", - "FormObjects/propertiesRangeOfValues", - "FormObjects/propertiesResizingOptions", - "FormObjects/propertiesScale", - "FormObjects/propertiesSubform", - "FormObjects/propertiesText", - "FormObjects/propertiesTextAndPicture", - "FormObjects/propertiesWebArea" - ] + items: [ + "WritePro/user-legacy/presentation", + "WritePro/user-legacy/defining-a-4d-write-pro-area", + "WritePro/writeprointerface", + "WritePro/user-legacy/4d-write-pro-documents", + { + type: "category", + label: "Document Elements", + link: { + type: "generated-index", + title: "Document Elements", + }, + items: [ + "WritePro/user-legacy/using-a-4d-write-pro-area", + "WritePro/user-legacy/handling-pictures", + "WritePro/user-legacy/handling-tables", + "WritePro/user-legacy/text-boxes", + "WritePro/user-legacy/ranges", + "WritePro/user-legacy/stylesheets", + "WritePro/managing-formulas" + ] + }, + { + type: "category", + label: "Import and Export", + link: { + type: "generated-index", + title: "Import and Export", + }, + items: [ + "WritePro/user-legacy/importing-4d-write-documents", + "WritePro/user-legacy/importing-and-exporting-in-docx-format", + "WritePro/user-legacy/exporting-to-html-and-mime-html-formats", + "WritePro/user-legacy/exporting-to-svg-format" + ] }, + "WritePro/commands-legacy/4d-write-pro-attributes", { type: "category", - label: "Form Events", + label: "Commands", link: { type: "doc", - id: "Events/overview" + id: "WritePro/commands/command-index" }, items: [ - "Events/onActivate", - "Events/onAfterEdit", - "Events/onAfterKeystroke", - "Events/onAfterSort", - "Events/onAlternativeClick", - "Events/onBeforeDataEntry", - "Events/onBeforeKeystroke", - "Events/onBeginDragOver", - "Events/onBeginUrlLoading", - "Events/onBoundVariableChange", - "Events/onClicked", - "Events/onCloseBox", - "Events/onCloseDetail", - "Events/onCollapse", - "Events/onColumnMoved", - "Events/onColumnResize", - "Events/onDataChange", - "Events/onDeactivate", - "Events/onDeleteAction", - "Events/onDisplayDetail", - "Events/onDoubleClicked", - "Events/onDragOver", - "Events/onDrop", - "Events/onEndUrlLoading", - "Events/onExpand", - "Events/onFooterClick", - "Events/onGettingFocus", - "Events/onHeader", - "Events/onHeaderClick", - "Events/onLoad", - "Events/onLoadRecord", - "Events/onLongClick", - "Events/onLosingFocus", - "Events/onMenuSelected", - "Events/onMouseEnter", - "Events/onMouseLeave", - "Events/onMouseMove", - "Events/onMouseUp", - "Events/onOpenDetail", - "Events/onOpenExternalLink", - "Events/onOutsideCall", - "Events/onPageChange", - "Events/onPlugInArea", - "Events/onPrintingBreak", - "Events/onPrintingDetail", - "Events/onPrintingFooter", - "Events/onResize", - "Events/onRowMoved", - "Events/onRowResize", - "Events/onScroll", - "Events/onSelectionChange", - "Events/onTimer", - "Events/onUnload", - "Events/onUrlFiltering", - "Events/onUrlLoadingError", - "Events/onUrlResourceLoading", - "Events/onValidate", - "Events/onVpRangeChanged", - "Events/onVpReady", - "Events/onWindowOpeningDenied" + "WritePro/commands/wp-add-picture", + "WritePro/commands-legacy/wp-bookmark-range", + "WritePro/commands-legacy/wp-compute-formulas", + "WritePro/commands-legacy/wp-delete-bookmark", + "WritePro/commands-legacy/wp-delete-footer", + "WritePro/commands-legacy/wp-delete-header", + "WritePro/commands-legacy/wp-delete-picture", + "WritePro/commands/wp-delete-section", + "WritePro/commands-legacy/wp-delete-style-sheet", + "WritePro/commands/wp-delete-subsection", + "WritePro/commands-legacy/wp-delete-text-box", + "WritePro/commands/wp-export-document", + "WritePro/commands/wp-export-variable", + "WritePro/commands-legacy/wp-find-all", + "WritePro/commands-legacy/wp-find-next", + "WritePro/commands-legacy/wp-find-previous", + "WritePro/commands-legacy/wp-freeze-formulas", + "WritePro/commands/wp-get-attributes", + "WritePro/commands-legacy/wp-get-body", + "WritePro/commands-legacy/wp-get-bookmarks", + "WritePro/commands-legacy/wp-get-breaks", + "WritePro/commands-legacy/wp-get-data-context", + "WritePro/commands-legacy/wp-get-element-by-id", + "WritePro/commands-legacy/wp-get-elements", + "WritePro/commands-legacy/wp-get-footer", + "WritePro/commands-legacy/wp-get-formulas", + "WritePro/commands-legacy/wp-get-frame", + "WritePro/commands-legacy/wp-get-header", + "WritePro/commands-legacy/wp-get-links", + "WritePro/commands-legacy/wp-get-page-count", + "WritePro/commands-legacy/wp-get-position", + "WritePro/commands-legacy/wp-get-section", + "WritePro/commands-legacy/wp-get-sections", + "WritePro/commands-legacy/wp-get-style-sheet", + "WritePro/commands-legacy/wp-get-style-sheets", + "WritePro/commands-legacy/wp-get-subsection", + "WritePro/commands-legacy/wp-get-text", + "WritePro/commands-legacy/wp-get-view-properties", + "WritePro/commands/wp-import-document", + "WritePro/commands-legacy/wp-import-style-sheets", + "WritePro/commands/wp-insert-break", + "WritePro/commands/wp-insert-document-body", + "WritePro/commands/wp-insert-formula", + "WritePro/commands/wp-insert-picture", + "WritePro/commands-legacy/wp-insert-table", + "WritePro/commands-legacy/wp-is-font-style-supported", + "WritePro/commands-legacy/wp-new", + "WritePro/commands-legacy/wp-new-bookmark", + "WritePro/commands-legacy/wp-new-footer", + "WritePro/commands-legacy/wp-new-header", + "WritePro/commands-legacy/wp-new-style-sheet", + "WritePro/commands-legacy/wp-new-subsection", + "WritePro/commands-legacy/wp-new-text-box", + "WritePro/commands-legacy/wp-paragraph-range", + "WritePro/commands-legacy/wp-picture-range", + "WritePro/commands-legacy/wp-print", + "WritePro/commands/wp-reset-attributes", + "WritePro/commands-legacy/wp-select", + "WritePro/commands-legacy/wp-selection-range", + "WritePro/commands/wp-set-attributes", + "WritePro/commands-legacy/wp-set-data-context", + "WritePro/commands-legacy/wp-set-frame", + "WritePro/commands-legacy/wp-set-link", + "WritePro/commands-legacy/wp-set-text", + "WritePro/commands-legacy/wp-set-view-properties", + "WritePro/commands/wp-table-append-row", + "WritePro/commands-legacy/wp-table-delete-columns", + "WritePro/commands-legacy/wp-table-delete-rows", + "WritePro/commands-legacy/wp-table-get-cells", + "WritePro/commands-legacy/wp-table-get-columns", + "WritePro/commands-legacy/wp-table-get-rows", + "WritePro/commands-legacy/wp-table-insert-columns", + "WritePro/commands-legacy/wp-table-insert-rows", + "WritePro/commands-legacy/wp-table-merge-cells", + "WritePro/commands-legacy/wp-table-range", + "WritePro/commands-legacy/wp-table-split-cells", + "WritePro/commands-legacy/wp-text-range", + "WritePro/commands-legacy/wp-use-page-setup" ] } ] }, { type: "category", - label: "Menus", + label: "4D AIKit", link: { - type: "doc", - id: "Menus/overview" + type: "generated-index", + title: "4D AIKit", + slug: "/category/4d-aikit", + keywords: [ + "4D AIKit" + ], + image: "/img/docusaurus.png" }, items: [ - "Menus/creating", - "Menus/properties", - "Menus/bars", - "Menus/sdi" + "aikit/overview", + "aikit/asynchronous-call", + "aikit/compatible-openai", + { + type: "category", + label: "Classes", + items: [ + "aikit/Classes/openai", + "aikit/Classes/openaiapiresource", + "aikit/Classes/openaichatapi", + "aikit/Classes/openaichatcompletionsapi", + "aikit/Classes/openaichatcompletionslistparameters", + "aikit/Classes/openaichatcompletionsmessagesapi", + "aikit/Classes/openaichatcompletionsmessagesparameters", + "aikit/Classes/openaichatcompletionsparameters", + "aikit/Classes/openaichatcompletionsresult", + "aikit/Classes/openaichatcompletionsstreamresult", + "aikit/Classes/openaichathelper", + "aikit/Classes/openaichoice", + "aikit/Classes/openaiembedding", + "aikit/Classes/openaiembeddingsapi", + "aikit/Classes/openaiembeddingsparameters", + "aikit/Classes/openaiembeddingsresult", + "aikit/Classes/openaierror", + "aikit/Classes/openaiimage", + "aikit/Classes/openaiimageparameters", + "aikit/Classes/openaiimagesapi", + "aikit/Classes/openaiimagesresult", + "aikit/Classes/openaimessage", + "aikit/Classes/openaimodel", + "aikit/Classes/openaimodellistresult", + "aikit/Classes/openaimodelresult", + "aikit/Classes/openaimodelsapi", + "aikit/Classes/openaimoderation", + "aikit/Classes/openaimoderationitem", + "aikit/Classes/openaimoderationresult", + "aikit/Classes/openaimoderationsapi", + "aikit/Classes/openaiparameters", + "aikit/Classes/openairesult", + "aikit/Classes/openaivision", + "aikit/Classes/openaivisionhelper" + ] + } ] }, { - type: "doc", - label: "User Settings", - id: "Desktop/user-settings" + type: "link", + label: "4D Mobile App Server", + href: "https://github.com/4d-go-mobile/4D-Mobile-App-Server" }, { - type: "doc", - label: "Build Application", - id: "Desktop/building" + type: "link", + label: "4D NetKit", + href: "https://developer.4d.com/4D-NetKit" }, { - type: "doc", - label: "Labels", - id: "Desktop/labels" - } - ] - }, - { - type: "category", - label: "Mobile Applications", - items: [ + type: "link", + label: "4D Progress", + href: "https://doc.4d.com/4Dv20R10/4D/20-R10/4D-Progress.100-7614210.en.html" + }, { type: "link", - label: "Go Mobile", - href: "https://developer.4d.com/go-mobile/" + label: "4D SVG", + href: "https://doc.4d.com/4Dv20R10/4D/20-R10/4D-SVG-Component.100-7614300.en.html" }, { type: "link", - label: "4D for iOS (archive)", - href: "https://developer.4d.com/4d-for-ios" - } - ] + label: "4D Widgets", + href: "https://doc.4d.com/4Dv20R10/4D/20-R10/4D-Widgets.100-7614949.en.html" + }, + { + type: "link", + label: "4D QPDF", + href: "https://github.com/4d/4D-QPDF?tab=readme-ov-file#readme" + }, + { + type: "link", + label: "Go Mobile with 4D", + href: "https://developer.4d.com/go-mobile/" + }, + { + type: "link", + label: "Build4D", + href: "https://github.com/4d-depot/Build4D?tab=readme-ov-file#readme" + } + ] } ] -} \ No newline at end of file +} + diff --git a/src/data/homepageTiles.js b/src/data/homepageTiles.js index b4bf315537930a..9892d87a2722fc 100644 --- a/src/data/homepageTiles.js +++ b/src/data/homepageTiles.js @@ -31,169 +31,145 @@ const localizedLinks = { const Sections = [ { - title: translate({ - message: 'Getting Started', - id: 'homepage.sections.getting-started.title', - }), - image: { - src: '/img/illu_GettingStarted.png', - width: 1009.54, - height: 717.96, - }, + +title: ( + <> + +
-
- Project Management
+
+ Creating or opening a project
-
- Handling Code
+
+ Architecture
-
- Debugging
+
+ Project Settings
-
- Object Relational Data Access (ORDA)
+
+ Database structure
-
- 4D Language
+
+ Code & Methods
-
- Processes
+
+ Dependencies
-
- Transformation Tags
+
+ Compilation
-
- Preferences
+
+ Application Builder
+
+
+ Debugging
+
+
+ Application Preferences
),
- },
- {
- title: translate({
- message: 'Administration',
- id: 'homepage.administration.title',
- }),
- image: {
- src: '/img/illu_Administration.png',
- width: 1137.97,
- height: 736.21,
- },
+ },{
+ title: (
+ <>
+
+
-
- 4D Server Administration Window
+
+ Concepts
-
- Web Administration
+
+ Commands by name
-
- Command Line Interface
-
-
- TLS Protocol
-
-
- Licenses
-
-
- Maintenance and Security Center
+
+ Commands by theme
-
- Backup and Restore
+
+ Classes
),
- },
- {
- title: translate({
- message: 'Extensions',
- id: 'homepage.sections.textensions.title',
- }),
- image: {
- src: '/img/illu_Extensions.png',
- width: 1038.23,
- height: 693.31,
- },
+ },{
+ title: (
+ <>
+
+
-
- Overview
-
-
- 4D View Pro
-
-
- 4D Write Pro
-
-
- 4D NetKit
+
+ ORDA
-
- 4D AIKit
-
-
- 4D Progress
+
+ Processes
-
- 4D SVG
+
+ Database Methods
-
- 4D Widgets
+
+ Transactions
-
- Developing Components
+
+ Transformation tags
-
- Developing Plugins
+
+ Date and Time Formats
),
},
{
- title: translate({
- message: 'Web Applications',
- id: 'homepage.sections.web-applications.title',
- }),
- image: {
- src: '/img/illu_WebApplication.png',
- width: 1137,
- height: 776.59,
- },
+ title: (
+ <>
+
+
+
+ 4D Qodly Pro
+
Web Server
-
- Web Development
-
-
- Qodly Studio
-
REST Server
@@ -201,62 +177,126 @@ const Sections = [
),
},
{
- title: translate({
- message: 'Desktop Applications',
- id: 'homepage.sections.desktop-applications.title',
- }),
- image: {
- src: '/img/illu_DesktopApplication.png',
- width: 1108,
- height: 731.18,
- },
+ title: (
+ <>
+
+
+ Desktop Applications
+
+
+ ),
links: (
Client/Server
-
- Access Rights
-
Forms
Menus
+
+ Labels
+
User Settings
-
- Build Application
+
+ Access Rights
),
},
{
- title: translate({
- message: 'Mobile Applications',
- id: 'homepage.sections.mobile-applications.title',
- }),
- image: {
- src: '/img/illu_MobileApplication.png',
- width: 1038.23,
- height: 693.31,
- },
+ title:(
+ <>
+
+
+ Server & Admin
+
+
+ ),
links: (
+ Extensions
+
+
+ ),
+ links: (
+
` elements in previous versions of 4D, are not compatible with the XML syntax. The lines of comments must respect the standard `""` form.
- The `<>` symbols used more particularly for interprocess object names must be encoded. For example, the `<>params` variable must be written `<>params`.
- The initial `` declaration tag could be omitted in previous versions of 4D. It is now mandatory; otherwise, the file will not be loaded.
+
+## Importing and exporting code
+
+You can import and export a method or a class code in the form of a file. These commands are found in the **Method** menu of the [Code editor](../code-editor/write-class-method.md).
+
+- When you select the **Export Method...** command, a standard file saving dialog box appears, allowing you to choose the name, location and format of the export file (see below). As with printing, exporting does not take the collapsed state of code structures into account and the entire code is exported.
+- When you select the **Import Method...** command, a standard file opening dialog box appears, allowing you to designate the file to be imported. Importing replaces the selected text in the method. To replace an existing method by an imported method, select the entire contents of the method before carrying out the import.
+
+The import/export function is multi-platform: a method exported under Mac OS can be imported under Windows and vice versa; 4D handles the conversion of characters when necessary.
+
+4D can export and import methods in two formats:
+
+- 4D method (extension *.c4d*): In this format, methods are exported in encoded form. The names of objects are tokenized. This format is used in particular for exchanging methods between 4D applications and plug-ins in different languages. Conversely, it is not possible to display them in a text editor.
+- Text (extension *.txt*): In this format, methods are exported in text-only form. In this case, the methods are readable using a standard text editor or a source control tool.
diff --git a/versioned_docs/version-20-R10/commands/command-index.md b/versioned_docs/version-20-R10/commands/command-index.md
index 225c10ff49f771..4c296f29ee1766 100644
--- a/versioned_docs/version-20-R10/commands/command-index.md
+++ b/versioned_docs/version-20-R10/commands/command-index.md
@@ -1,6 +1,6 @@
---
id: command-index
-title: Index
+title: Commands by name
---
[4D](#4D) - [A](#A) - [B](#B) - [C](#C) - [D](#D) - [E](#E) - [F](#F) - [G](#G) - [H](#H) - [I](#I) - [J](#J) - [K](#K) - [L](#L) - [M](#M) - [N](#N) - [O](#O) - [P](#P) - [Q](#Q) - [R](#R) - [S](#S) - [T](#T) - [U](#U) - [V](#V) - [W](#W) - [X](#X) - [Y](#Y) - [Z](#Z)
diff --git a/versioned_docs/version-20-R10/commands/create-deployment-license.md b/versioned_docs/version-20-R10/commands/create-deployment-license.md
index dce3cec3f0bec1..0084093004f50c 100644
--- a/versioned_docs/version-20-R10/commands/create-deployment-license.md
+++ b/versioned_docs/version-20-R10/commands/create-deployment-license.md
@@ -91,10 +91,10 @@ The command returns a *status* object containing the following properties:
Use the automatic syntax to create a single-user 4D application:
```4d
- var $status : Object
- var $application : 4D.File
- $application:=Folder(fk desktop folder).folder("myApp.app")
- $status:=Create deployment license($application;4D Volume Desktop)
+ var $status : Object
+ var $application : 4D.File
+ $application:=Folder(fk desktop folder).folder("myApp.app")
+ $status:=Create deployment license($application;4D Volume Desktop)
```
@@ -104,17 +104,17 @@ Use the automatic syntax to create a single-user 4D application:
Designate a license to use:
```4d
- var $status : Object
- var $application : 4D.File
- var $license : 4D.File
- $license:=Folder(fk licenses folder).file("4UUD200-xxx.license4D")
- $application:=Folder(fk desktop folder).folder("myApp.app")
- $status:=Create deployment license($application;$license)
+ var $status : Object
+ var $application : 4D.File
+ var $license : 4D.File
+ $license:=Folder(fk licenses folder).file("4UUD200-xxx.license4D")
+ $application:=Folder(fk desktop folder).folder("myApp.app")
+ $status:=Create deployment license($application;$license)
```
## See also
-[Blog post - Finalize an application with 4D commands](https://blog.4d.com/finalize-an-application-with-4d-commands)
+[Blog post - Build an application with 4D commands](https://blog.4d.com/build-an-application-with-4d-commands)
## Properties
diff --git a/versioned_docs/version-20-R10/commands/theme/Database_Methods.md b/versioned_docs/version-20-R10/commands/theme/Database_Methods.md
deleted file mode 100644
index 9b499e6ee0a644..00000000000000
--- a/versioned_docs/version-20-R10/commands/theme/Database_Methods.md
+++ /dev/null
@@ -1,27 +0,0 @@
----
-id: Database_Methods_theme
-title: Database Methods
-slug: /commands/theme/Database-Methods
----
-
-
-||
-|---|
-|[](../../commands-legacy/on-backup-shutdown-database-method.md)
| -|[](../../commands-legacy/on-backup-startup-database-method.md)
| -|[](../../commands-legacy/on-drop-database-method.md)
| -|[](../../commands-legacy/on-exit-database-method.md)
| -|[](../../commands-legacy/on-host-database-event-database-method.md)
| -|[](../../commands-legacy/on-mobile-app-action-database-method.md)
| -|[](../../commands-legacy/on-mobile-app-authentication-database-method.md)
| -|[](../../commands-legacy/on-rest-authentication-database-method.md)
| -|[](../../commands-legacy/on-server-close-connection-database-method.md)
| -|[](../../commands-legacy/on-server-open-connection-database-method.md)
| -|[](../../commands-legacy/on-server-shutdown-database-method.md)
| -|[](../../commands-legacy/on-server-startup-database-method.md)
| -|[](../../commands-legacy/on-sql-authentication-database-method.md)
| -|[](../../commands-legacy/on-startup-database-method.md)
| -|[](../../commands-legacy/on-system-event-database-method.md)
| -|[](../../commands-legacy/on-web-authentication-database-method.md)
| -|[](../../commands-legacy/on-web-connection-database-method.md)
| -|[](../../commands-legacy/on-web-legacy-close-session-database-method.md)
| diff --git a/versioned_docs/version-20-R10/settings/overview.md b/versioned_docs/version-20-R10/settings/overview.md index 0d52cdbde7c0dc..ede138092298e2 100644 --- a/versioned_docs/version-20-R10/settings/overview.md +++ b/versioned_docs/version-20-R10/settings/overview.md @@ -7,8 +7,12 @@ The Settings configure how the current project functions. These parameters may b  -> 4D provides another set of parameters, called **Preferences**, that apply to the 4D IDE application. For more information, refer to [Preferences](../Preferences/general.md). +:::info + +4D provides another set of parameters, called **Preferences**, that apply to the 4D IDE application. For more information, refer to [Preferences](../Preferences/general.md). + +::: ## Accessing the settings @@ -18,7 +22,7 @@ You can access the Settings dialog box: - by clicking **Settings** on the 4D toolbar - on 4D Server, using the **Edit > Settings...** menu option -When [**User settings** mode is enabled](../Desktop/user-settings.md), **Settings...** is renamed **Structure Settings...** and two additional menu commands are available at each location: +When [**User settings** mode is enabled](#user-settings), **Settings...** is renamed **Structure Settings...** and two additional menu commands are available at each location: - **User Settings...** gives you access to settings that can be stored externally in a user file. If these are modified, they are used instead of structure settings. - **User Settings for Data File...** gives you access to settings that can be stored externally in a user file attached to the current data file. If they are modified, they are used instead of user or structure settings. @@ -47,8 +51,137 @@ A parameter still appears in bold even when its value is replaced manually with Most of the settings are applied immediately. However, a few of them (such as the Startup environment setting) only take effect when the database is restarted. In this case, a dialog box appears to inform you that the change will take effect at the next startup. -## Resetting the settings +### Resetting the settings To reset the parameters to their default values and remove the bold style indicating that they have been customized, click **Reset to factory settings**. This button resets all the parameters of the current page. It becomes active when at least one parameter has been modified on the current page. + + +## User Settings + +4D provides two modes of operation for project Settings: + +* **Standard** mode: all settings are stored in the [*settings.4DSettings* file at the project level](../Project/architecture.md#sources) and are applied in all cases. This is the default mode, suitable for development phase (all applications). + +* **User settings** mode: part of the custom settings are stored in a *settings.4DSettings* file [in the Settings folder](../Project/architecture.md#settings-user) (for all data files) or [in the Data folder](../Project/architecture.md#settings-user-data) (for this data file) and are used instead of the structure settings. This mode is suitable for deployment phase for Desktop applications. You enable this mode using an option located on the [Security page](./security.md) of the Settings. + +By defining user settings, you can keep custom settings between updates of your 4D applications, or manage different settings for the same 4D application deployed on several different sites. It also makes it possible to use programming to manage setting files using XML. + +4D can generate and use two types of user settings: + +- **User Settings**: They are used instead of structure settings for any data file opened with the application. +- **User Settings for Data file**: They can be defined specifically for each data file used with your application, configuring for example the port ID or the server cache. + +With this option, you can easily deploy and update several copies of the same desktop application with several data files, each containing different settings. + +Consider for example the following configuration, where an application is duplicated and each copy uses a different Port ID setting. If this user setting is linked to the data file, you will be able to update the application without having to manually change the Port ID: + + + +### Enabling User settings + +To enable user settings, you need to check the **Settings** > **Security** > **Enable User Settings** option: + + + +When you check this option, the settings are separated into three dialog boxes: + +* **Structure Settings** +* **User Settings** +* **User Settings for Data file** + +You can access these dialog boxes using the **Design > Settings...** menu or the **Settings** button in the toolbar: + + + +You can also access these dialog boxes using the [OPEN SETTINGS WINDOW](../commands-legacy/open-settings-window.md) command with the appropriate *settingsType* selector. + +The Structure Settings dialog box is identical to the standard Settings, and provides access to all its properties (which can be overriden by user settings). + +### User Settings and User Settings for Data file + +The **User Settings** and **User Settings for Data File** dialog boxes contain a selection of relevant properties that can be defined for all data files or a single data file: + + + +The following table lists the pages of settings found in the **User Settings** and **User Settings for Data File** dialog boxes and describes their main differences with respect to standard settings: + +| **Page of Structure Settings** | **Page of User Settings** | **Page of User Settings for Data File**| +| --- | --- | --- | +| [General page](./general.md) | N/a | N/a | +| [Interface page](./interface.md) | Identical to standard settings | Identical to standard settings | +| [Compiler page](./compiler.md) | N/a | N/a | +| [Database/Data storage page](./database.md#data-storage-page) | N/a | N/a | +| [Database/Memory page](./database.md#memory-page) | Identical to standard settings | Identical to standard settings | +| [Backup/Scheduler page](./../Backup/settings.md#scheduler) | N/a | Identical to standard settings | +| [Backup/Configuration page](./../Backup/settings.md#configuration) | N/a | Identical to standard settings | +| [Backup/Backup & Restore page](./../Backup/settings.md#backup--restore) | N/a | Identical to standard settings | +| [Client-server/Network options page](./client-server.md#network-options-page) | Identical to standard settings | Identical to standard settings | +| [Client-server/IP configuration page](./client-server.md#ip-configuration-page) | Identical to standard settings | Identical to standard settings | +| [Web/Configuration page](./web.md#configuration) | Identical to standard settings | Identical to standard settings | +| [Web/Options (I) page](./web.md#options-i) | Identical to standard settings | Identical to standard settings | +| [Web/Options (II) page](./web.md#options-ii) | Identical to standard settings | Identical to standard settings | +| [Web/Log (type) page](./web.md#log-type) | Identical to standard settings | Identical to standard settings | +| [Web/Log (backup) page](./web.md#log-backup) | Identical to standard settings | Identical to standard settings | +| [Web/Web Services page](./web.md#web-services) | Method prefixing option not available | Method prefixing option not available | +| [SQL page](./sql.md) | Identical to standard settings | Identical to standard settings | +| [PHP page](./php.md) | Identical to standard settings | Identical to standard settings | +| [Security page](./security.md) | N/a | N/a | +| [Compatibility page](./compatibility.md) | N/a | N/a | + +When you edit settings in this dialog box, they are automatically stored in the corresponding *settings.4DSettings* file (see below) or the *Backup.4DSettings* file (check the [Backup settings](../Backup/settings.md) page for more information). + +### `SET DATABASE PARAMETER` and user settings + +Some of the user settings are also available through the [SET DATABASE PARAMETER](../commands-legacy/set-database-parameter.md) command. User settings are parameters with the **Kept between two sessions** property set to **Yes**. + +When the **User Settings** feature is enabled, user settings edited by the [SET DATABASE PARAMETER](../commands-legacy/set-database-parameter.md) command are automatically saved in the user settings for the data file. + +> `Table sequence number` is an exception; this setting value is always saved in the data file itself. + +### settings.4DSettings files + +When you [check the **Enable User Settings** option](#enabling-user-settings), user settings files are automatically created. Their location depends on the type of user settings defined. + +#### User Settings + +The standard user settings file is automatically created and placed in a settings folder at the following location: + +[`ProjectFolder/Settings/settings.4DSettings`](../Project/architecture.md#settings-user) + +... where *ProjectFolder* is the name of the folder containing the project structure file. + +In merged applications, the user settings file is placed at the following location: + +* In single-user versions: ProjectFolder/Database/Settings/settings.4DSettings +* In client/server versions: ProjectFolder/Server Database/Settings/settings.4DSettings + +#### User Settings for Data File + +The user settings file linked to the data file is automatically created and placed in a settings folder at the following location: + +[`Data/Settings/settings.4DSettings`](../Project/architecture.md#settings-user-data) + +... where *Data* is the name of the folder containing the current data file of the application. + +> When the data file is located at the same level as the project structure file, structure-based and data-based user settings files share the same location and file. The **User Settings for Data File...** menu command is not proposed. + +:::note + +Settings files are XML files; they can be read and modified using integrated 4D XML commands or using an XML editor. This means that you can manage settings by programming, particularly in the context of applications compiled and merged with 4D Volume Desktop. When you modify this file by programming, the changes are only taken into account the next time the database is opened. + +::: + + +### Priority of settings + +Settings can be stored at three levels. Each setting defined at one level overrides the same setting defined at a previous level, if any: + +| **Priority level** | **Name** | **Location** | **Comments** | +|---|---|---|---| +| 3 (lowest) | Structure settings (or Settings when "User settings" feature not enabled) | ***settings.4DSettings*** file in the Sources folder (project databases) or in the Settings folder as the same level as the structure file (binary databases) | Unique location when user settings are not enabled. Applied to all copies of the application. | +| 2 | User settings (all data files) | ***settings.4DSettings*** file in the Settings folder at the same level as the Project folder | Overrides Structure settings. Stored within the application package. | +| 1 (highest) | User settings (current data file) | ***settings.4DSettings*** file in the Settings folder at the same level as the data file | Overrides Structure settings and User settings. Applied only when the linked data file is used with the application. | + +Keep in mind that user settings files only contain a subset of relevant settings, while the structure file contains all custom settings, including core settings. diff --git a/versioned_docs/version-20-R10/settings/security.md b/versioned_docs/version-20-R10/settings/security.md index 2b7ffd9cfbf12b..572de63c511aa2 100644 --- a/versioned_docs/version-20-R10/settings/security.md +++ b/versioned_docs/version-20-R10/settings/security.md @@ -40,7 +40,7 @@ This page contains options related to data access and protection for your deskto - **Disabled for all**: This option disables control within formulas. When this option is checked, users have access to all the 4D commands and plug-ins as well as all project methods (except for invisible ones). **Note:** This option takes priority over the [`SET ALLOWED METHODS`](../commands/set-allowed-methods.md) command. When it is checked, this command does nothing. -- **Enable User Settings**: You need to check this option to be able to display separated dialog boxes for user settings. When this option is checked, up to three dialog boxes are available: **Structure Settings**, **User Settings**, and **User Settings for Data File**. For more information, refer to [User settings](../Desktop/user-settings.md). +- **Enable User Settings**: You need to check this option to be able to display separated dialog boxes for user settings. When this option is checked, up to three dialog boxes are available: **Structure Settings**, **User Settings**, and **User Settings for Data File**. For more information, refer to [User settings](../settings/overview.md#user-settings). - **Execute "On Host Database Event" method of the components**: The [On Host Database Event database method](../commands-legacy/on-host-database-event-database-method.md) facilitates the initialization and backup phases for 4D components. For security reasons, you must explicitly authorize the execution of this method in each host database. To do this, you must check this option. By default, it is not checked. diff --git a/versioned_docs/version-20-R9/API/SessionClass.md b/versioned_docs/version-20-R9/API/SessionClass.md index 0b4aee999a4efb..00c88a1190f68d 100644 --- a/versioned_docs/version-20-R9/API/SessionClass.md +++ b/versioned_docs/version-20-R9/API/SessionClass.md @@ -140,7 +140,7 @@ The `.createOTP()` function create For more information about the OTP tokens, please refer to [this section](../WebServer/sessions.md#session-token-otp). -By default, if the *lifespan* parameter is omitted, the token is created with the same lifespan as the [`.idleTimeOut`](#idletimeout) of the session. You can set a custom timeout by passing a value in seconds in *lifespan* (the minimum value is 10 seconds, *lifespan* is reset to 10 if a smaller value is passed). If an expired token is used to restore a web user session, it is ignored. +By default, if the *lifespan* parameter is omitted, the token is created with the same lifespan as the [`.idleTimeOut`](#idletimeout) of the session. You can set a custom timeout by passing a value in seconds in *lifespan*. If an expired token is used to restore a web user session, it is ignored. The returned token can then be used in exchanges with third-party applications or websites to securely identify the session. For example, the session OTP token can be used with a payment application. diff --git a/versioned_docs/version-20-R9/Concepts/operators.md b/versioned_docs/version-20-R9/Concepts/operators.md index db5792e85ccf6b..d15c09b5e9319c 100644 --- a/versioned_docs/version-20-R9/Concepts/operators.md +++ b/versioned_docs/version-20-R9/Concepts/operators.md @@ -95,7 +95,9 @@ The following compound assignment operators are supported: ||Time *= Number |Number |`$t1*=5 //$t1:=$t1*5`| ||Picture *= Number|Picture|`$p1*=5 //$p1:=$p1*5 (resize $p1 by 5)`| -These operators apply on any [assignable expressions](quick-tour.md#assignable-vs-non-assignable-expressions) (except pictures as object properties or collection elements). +These operators apply on any [assignable expressions](quick-tour.md#assignable-vs-non-assignable-expressions) except: +- pictures as object properties or collection elements, +- array index variables. The operation "source `operator` value" is not strictly equivalent to "source := source `operator` value" because the expression designating the source (variable, field, object property, collection element) is only evaluated once. For example, in such expression as `getPointer()->+=1` the `getPointer` method is called only once. diff --git a/versioned_docs/version-20-R9/Extensions/overview.md b/versioned_docs/version-20-R9/Extensions/overview.md index 2fabda08c1a413..399a8481196858 100644 --- a/versioned_docs/version-20-R9/Extensions/overview.md +++ b/versioned_docs/version-20-R9/Extensions/overview.md @@ -13,7 +13,7 @@ The 4D [project architecture](../Project/architecture.md) is modular. You can pr |Component|Description|Main Features| |---|---|---| -|[4D AiIKit](https://github.com/4d/4D-AIKit)|Set of classes to connect to third-party OpenAI APIs|`OpenAIChat`, `OpenAIImage`...| +|[4D AIKit](https://github.com/4d/4D-AIKit)|Set of classes to connect to third-party OpenAI APIs|`OpenAIChat`, `OpenAIImage`...| |[4D Labels](https://github.com/4d/4D-Labels)|Internal component required to build label templates|| |[4D NetKit](https://developer.4d.com/4D-NetKit)|Set of web service tools to connect to third-party APIs|`OAuth2Provider` class, `New OAuth2 provider`, `OAuth2ProviderObject.getToken()` | |[4D Progress](https://github.com/4d/4D-Progress)|Open one or more progress bars in the same window|`Progress New`, `Progress SET ON STOP METHOD`, `Progress SET PROGRESS`, ... | diff --git a/versioned_docs/version-20-R9/commands-legacy/create-deployment-license.md b/versioned_docs/version-20-R9/commands-legacy/create-deployment-license.md index bbfa678fc58459..696c13b48bcb0d 100644 --- a/versioned_docs/version-20-R9/commands-legacy/create-deployment-license.md +++ b/versioned_docs/version-20-R9/commands-legacy/create-deployment-license.md @@ -45,17 +45,17 @@ The command returns a *status* object containing the following properties: ## Example ```4d - var $status : Object - var $application : 4D.File - var $license : 4D.File - $license:=Folder(fk licenses folder).file("4UUD200-xxx.license4D") - $application:=Folder(fk desktop folder).folder("myApp.app") - $status:=Create deployment license($application;$license) + var $status : Object + var $application : 4D.File + var $license : 4D.File + $license:=Folder(fk licenses folder).file("4UUD200-xxx.license4D") + $application:=Folder(fk desktop folder).folder("myApp.app") + $status:=Create deployment license($application;$license) ``` ## See also -[Blog post - Finalize an application with 4D commands](https://blog.4d.com/finalize-an-application-with-4d-commands) +[Blog post - Build an application with 4D commands](https://blog.4d.com/build-an-application-with-4d-commands) ## Properties diff --git a/versioned_docs/version-20/Concepts/operators.md b/versioned_docs/version-20/Concepts/operators.md index ec2c69ca40b83c..52e162bb7acb9b 100644 --- a/versioned_docs/version-20/Concepts/operators.md +++ b/versioned_docs/version-20/Concepts/operators.md @@ -93,7 +93,9 @@ The following compound assignment operators are supported: ||Time *= Number |Number |`$t1*=5 //$t1:=$t1*5`| ||Picture *= Number|Picture|`$p1*=5 //$p1:=$p1*5 (resize $p1 by 5)`| -These operators apply on any [assignable expressions](quick-tour.md#assignable-vs-non-assignable-expressions) (except pictures as object properties or collection elements). +These operators apply on any [assignable expressions](quick-tour.md#assignable-vs-non-assignable-expressions) except: +- pictures as object properties or collection elements, +- array index variables. The operation "source `operator` value" is not strictly equivalent to "source := source `operator` value" because the expression designating the source (variable, field, object property, collection element) is only evaluated once. For example, in such expression as `getPointer()->+=1` the `getPointer` method is called only once. diff --git a/versioned_docs/version-20/settings/web.md b/versioned_docs/version-20/settings/web.md index 2c8245afa2126e..847ac4ae728695 100644 --- a/versioned_docs/version-20/settings/web.md +++ b/versioned_docs/version-20/settings/web.md @@ -5,41 +5,37 @@ title: Web page Using the tabs on the **Web** page, you can configure various aspects of the integrated Web server of 4D (security, startup, connections, Web services, etc.). For more information about how the 4D Web server works, see [Web server](../WebServer/webServer.md). For more information about 4D Web services, refer to the [Publication and use of Web Services](https://doc.4d.com/4Dv19/4D/19/Publication-and-use-of-Web-Services.200-5416624.en.html) chapter. -## Configuration +## Configuration ### Publishing Information -#### Launch Web Server at Startup +#### Launch Web Server at Startup Indicates whether the Web server will be launched on startup of the 4D application. This option is described in the [Web server administration](../WebServer/webServerAdmin.md#starting-the-4d-web-server) section. -#### Enable HTTP +#### Enable HTTP Indicates whether or not the Web server will accept non-secure connections. See [Enable HTTP](../WebServer/webServerConfig.md#enable-http). - -#### HTTP Port +#### HTTP Port Listening IP (TCP) port number for HTTP. See [HTTP Port](../WebServer/webServerConfig.md#http-port). -#### IP Address +#### IP Address IP address on which the 4D web server will receive HTTP requests (4D local and 4D Server). See [IP Address to listen](../WebServer/webServerConfig.md#ip-address-to-listen). - -#### Enable HTTPS +#### Enable HTTPS Indicates whether or not the Web server will accept secure connections. See [Enable HTTPS](../WebServer/webServerConfig.md#enable-https). - -#### HTTPS Port +#### HTTPS Port Allows you to modify the TCP/IP port number used by the Web server for secured HTTP connections over TLS (HTTPS protocol). See [HTTPS Port](../WebServer/webServerConfig.md#https-port). #### Allow database access through 4DSYNC URLs -*Compatibility Note*: This option is [deprecated](../WebServer/webServerConfig.md#deprecated-settings). For database access through HTTP, it is now recommended to use ORDA remote datastore features and REST requests. - +_Compatibility Note_: This option is [deprecated](../WebServer/webServerConfig.md#deprecated-settings). For database access through HTTP, it is now recommended to use ORDA remote datastore features and REST requests. ### Paths @@ -51,13 +47,9 @@ Define the default location of the Web site files and to indicate the hierarchic Designate a default home page for the Web server. See [Default Home page](../WebServer/webServerConfig.md#default-home-page). - - - ## Options (I) -### Cache - +### Cache #### Use the 4D Web cache @@ -67,38 +59,36 @@ Enables the web page cache. See [Cache](../WebServer/webServerConfig.md#cache). Sets the cache size. See [Cache](../WebServer/webServerConfig.md#cache). - -#### Clear Cache +#### Clear Cache At any moment, you can clear the cache of the pages and images that it contains (if, for example, you have modified a static page and you want to reload it in the cache). To do so, you just have to click on the **Clear Cache** button. The cache is then immediately cleared. > You can also use the special URL [/4DCACHECLEAR](../WebServer/webServerAdmin.md#4dcacheclear). -### Web Process +### Web Process -This area allows you to configure how the web server will handle user sessions and their associated processes. +This area allows you to configure how the web server will handle user sessions and their associated processes. > The **Legacy sessions** option is only available for compatibility in databases/projects created with 4D versions prior to 4D v18 R6. -#### Scalable sessions (multi-process sessions) - -When you select this option (recommended), a user session is managed through a **Session** object. See the [User sessions page](../WebServer/sessions.md#enabling-sessions). +#### Scalable sessions (multi-process sessions) +When you select this option (recommended), a user session is managed through a **Session** object. See the [User sessions page](../WebServer/sessions.md#enabling-sessions). -#### No sessions +#### No sessions -When this option is selected, the web server does not provide any specific support for [user sessions](../WebServer/sessions.md). Successive requests from web clients are always independent and no context is maintained on the server. +When this option is selected, the web server does not provide any specific support for [user sessions](../WebServer/sessions.md). Successive requests from web clients are always independent and no context is maintained on the server. In this mode, you can configure additional web server setttings: -- [Maximum Concurrent Web Processes](#maximum-concurrent-web-processes) -- [Reuse Temporary Contexts (4D in remote mode)](#reuse-temporary-contexts) -- [Use preemptive processes](#use-preemptive-processes) +- [Maximum Concurrent Web Processes](#maximum-concurrent-web-processes) +- [Reuse Temporary Contexts (4D in remote mode)](#reuse-temporary-contexts) +- [Use preemptive processes](#use-preemptive-processes) #### Legacy sessions (single process sessions) -*Compatibility Note:* This option is only available in databases/projects created with a 4D version prior to 4D v18 R6. +_Compatibility Note:_ This option is only available in databases/projects created with a 4D version prior to 4D v18 R6. This option enables the handling of legacy user sessions by the 4D HTTP server. This mechanism is described in the [Web Sessions Management (Legacy)](https://doc.4d.com/4Dv19/4D/19/Web-Sessions-Management-Legacy.300-5391806.en.html) section. See [Keep Session](../WebServer/webServerConfig.md#keep-session). @@ -110,31 +100,27 @@ Not available with [scalable sessions](../WebServer/sessions.md). Strictly high limit of concurrent web processes. See [Maximum Concurrent Web Processes](../WebServer/webServerConfig.md#maximum-concurrent-web-processes). - #### Reuse Temporary Contexts Not available with [scalable sessions](../WebServer/sessions.md). Allows you to optimize the operation of the 4D Web server in remote mode. See [Reuse temporary contexts in remote mode)](../WebServer/webServerConfig.md#reuse-temporary-contexts-in-remote-mode). -#### Use preemptive processes +#### Use preemptive processes -Not available with [scalable sessions](../WebServer/sessions.md). +Not available with [scalable sessions](../WebServer/sessions.md). Enables preemptive web processes in your compiled applications. When **Use preemptive processes** is selected, the eligibility of your web-related code (including 4D tags and web database methods) to the preemptive execution will be evaluated during the compilation. For more information, see [Using preemptive Web processes](../WebServer/preemptiveWeb.md). -> This option does not apply to scalable sessions, REST processes (compiled mode), and web service processes (server or client). See [Enabling the preemptive mode for the web server](../WebServer/webServerConfig.md#use-preemptive-processes). - +> This option does not apply to scalable sessions, REST processes (compiled mode), and web service processes (server or client). See [Enabling the preemptive mode for the web server](../WebServer/webServerConfig.md#use-preemptive-processes). -#### Inactive Process Timeout +#### Inactive Process Timeout -Not available with [scalable sessions](../WebServer/sessions.md). +Not available with [scalable sessions](../WebServer/sessions.md). Allows you to set the maximum timeout before closing for inactive Web processes on the server. See [Inactive Process Timeout](../WebServer/webServerConfig.md#inactive-process-timeout). - - -### Web Passwords +### Web Passwords Set the authentication system that you want to apply to your Web server. Three options are proposed: @@ -142,12 +128,11 @@ Custom (default) Passwords with BASIC protocol Passwords with DIGEST protocol -Using **Custom** authentication is recommended. See [**Authentication**](../WebServer/authentication.md) chapter in the *Web Development* documentation. - +Using **Custom** authentication is recommended. See [**Authentication**](../WebServer/authentication.md) chapter in the _Web Development_ documentation. ## Options (II) -### Text Conversion +### Text Conversion #### Send Extended Characters Directly @@ -157,7 +142,7 @@ See [Deprecated Settings](../WebServer/webServerConfig.md#deprecated-settings). Define the set of characters to be used by the 4D Web server. See [Character Set](../WebServer/webServerConfig.md#character-set). -### Keep-Alive Connections +### Keep-Alive Connections See [Deprecated Settings](../WebServer/webServerConfig.md#keep-alive-connections). @@ -171,36 +156,31 @@ Enables Cross-origin resource sharing (CORS) service. See [Enable CORS Service]( List of allowed hosts and methods for the CORS service. See [CORS Settings](../WebServer/webServerConfig.md#cors-settings). - - ## Log (type) +### Log Format -### Log Format - -Starts or stops the recording of requests received by the 4D web server in the *logweb.txt* file and sets its format. See [Log Recording](../WebServer/webServerConfig.md#log-recording). +Starts or stops the recording of requests received by the 4D web server in the _logweb.txt_ file and sets its format. See [Log Recording](../WebServer/webServerConfig.md#log-recording). > The activation and deactivation of the log file of requests can also be carried out by programming using the [WEB SET OPTION](https://doc.4d.com/4dv19R/help/command/en/page1210.html) command. - The log format menu provides the following options: -- **No Log File**: When this option is selected, 4D will not generate a log file of requests. - -- **CLF (Common Log Format)**: When this option is selected, the log of requests is generated in CLF format. With the CLF format, each line of the file represents a request, such as:\ - host rfc931 user [DD/MMM/YYYY:HH:MM:SS] "request" state length\ - Each field is separated by a space and each line ends by the CR/LF sequence (character 13, character 10). +- **No Log File**: When this option is selected, 4D will not generate a log file of requests. - - host: IP address of the client (ex. 192.100.100.10) - - rfc931: information not generated by 4D, it's always - (a minus sign) - - user: user name as it is authenticated, or else it is - (a minus sign). If the user name contains spaces, they will be replaced by _ (an underscore). - - DD: day, MMM: a 3-letter abbreviation for the month name (Jan, Feb,...), YYYY: year, HH: hour, MM: minutes, SS: seconds +- **CLF (Common Log Format)**: When this option is selected, the log of requests is generated in CLF format. With the CLF format, each line of the file represents a request, such as:\ + host rfc931 user [DD/MMM/YYYY:HH:MM:SS] "request" state length\ + Each field is separated by a space and each line ends by the CR/LF sequence (character 13, character 10). + - host: IP address of the client (ex. 192.100.100.10) + - rfc931: information not generated by 4D, it's always - (a minus sign) + - user: user name as it is authenticated, or else it is - (a minus sign). If the user name contains spaces, they will be replaced by \_ (an underscore). + - DD: day, MMM: a 3-letter abbreviation for the month name (Jan, Feb,...), YYYY: year, HH: hour, MM: minutes, SS: seconds > The date and time are local to the server. -- request: request sent by the client (ex. GET /index.htm HTTP/1.0) -- state: reply given by the server. -- length: size of the data returned (except the HTTP header) or 0. +- request: request sent by the client (ex. GET /index.htm HTTP/1.0) +- state: reply given by the server. +- length: size of the data returned (except the HTTP header) or 0. > **Note:** For performance reasons, the operations are saved in a memory buffer in packets of 1Kb before being written to disk. The operations are also written to disk if no request has been sent every 5 seconds. > The possible values of state are as follows: @@ -214,16 +194,15 @@ The log format menu provides the following options: > 500: Internal error > The CLF format cannot be customized. -- **DLF (Combined Log Format)**: When this option is selected, the request log is generated in DLF format. DLF format is similar to CLF format and uses exactly the same structure. It simply adds two additional HTTP fields at the end of each request: Referer and User-agent. - - - Referer: Contains the URL of the page pointing to the requested document. - - User-agent: Contains the name and version of the browser or software of the client at the origin of the request. +- **DLF (Combined Log Format)**: When this option is selected, the request log is generated in DLF format. DLF format is similar to CLF format and uses exactly the same structure. It simply adds two additional HTTP fields at the end of each request: Referer and User-agent. + - Referer: Contains the URL of the page pointing to the requested document. + - User-agent: Contains the name and version of the browser or software of the client at the origin of the request. > The DLF format cannot be customized. -- **ELF (Extended Log Format)**: When this option is selected, the request log is generated in ELF format. The ELF format is very widespread in the world of HTTP browsers. It can be used to build sophisticated logs that meet specific needs. For this reason, the ELF format can be customized: it is possible to choose the fields to be recorded as well as their order of insertion into the file. +- **ELF (Extended Log Format)**: When this option is selected, the request log is generated in ELF format. The ELF format is very widespread in the world of HTTP browsers. It can be used to build sophisticated logs that meet specific needs. For this reason, the ELF format can be customized: it is possible to choose the fields to be recorded as well as their order of insertion into the file. -- **WLF (WebStar Log Format)**: When this option is selected, the request log is generated in WLF format. WLF format was developed specifically for the 4D WebSTAR server. It is similar to the ELF format, with only a few additional fields. Like the ELF format, it can be customized. +- **WLF (WebStar Log Format)**: When this option is selected, the request log is generated in WLF format. WLF format was developed specifically for the 4D WebSTAR server. It is similar to the ELF format, with only a few additional fields. Like the ELF format, it can be customized. **Configuring the fields** When you choose the ELF (Extended Log Format) or WLF (WebStar Log Format) format, the "Weg Log Token Selection" area displays the fields available for the chosen format. You will need to select each field to be included in the log. To do so, use the arrow buttons or simply drag and drop the desired fields into the "Selected Tokens" area. @@ -232,30 +211,30 @@ When you choose the ELF (Extended Log Format) or WLF (WebStar Log Format) format The following table lists the fields available for each format (in alphabetical order) and describes its contents: -| Field | ELF | WLF | Value | -| --- | --- | --- | --- | -| BYTES_RECEIVED | | X | Number of bytes received by the server | -| BYTES_SENT | X | X | Number of bytes sent by the server to the client | -| C_DNS | X | X | IP address of the DNS (ELF: field identical to the C_IP field) | -| C_IP | X | X | IP address of the client (for example 192.100.100.10) | -| CONNECTION_ID | | X | Connection ID number | -| CS(COOKIE) | X | X | Information about cookies contained in the HTTP request | -| CS(HOST) | X | X | Host field of the HTTP request | -| CS(REFERER) | X | X | URL of the page pointing to the requested document | -| CS(USER_AGENT) | X | X | Information about the software and operating system of the client | -| CS_SIP | X | X | IP address of the server | -| CS_URI | X | X | URI on which the request is made | -| CS_URI_QUERY | X | X | Request query parameters | -| CS_URI_STEM | X | X | Part of request without query parameters | -| DATE | X | X | DD: day, MMM: 3-letter abbreviation for month (Jan, Feb, etc.), YYYY: year | -| METHOD | X | X | HTTP method used for the request sent to the server | -| PATH_ARGS | | X | CGI parameters: string located after the "$" character | -| STATUS | X | X | Reply provided by the server | -| TIME | X | X | HH: hour, MM: minutes, SS: seconds | -| TRANSFER_TIME | X | X | Time requested by server to generate the reply | -| USER | X | X | User name if authenticated; otherwise - (minus sign). | -| | | | If the user name contains spaces, they are replaced by _ (underlines) | -| URL | | X | URL requested by the client | +| Field | ELF | WLF | Value | +| -------------- | --- | --- | -------------------------------------------------------------------------- | +| BYTES_RECEIVED | | X | Number of bytes received by the server | +| BYTES_SENT | X | X | Number of bytes sent by the server to the client | +| C_DNS | X | X | IP address of the DNS (ELF: field identical to the C_IP field) | +| C_IP | X | X | IP address of the client (for example 192.100.100.10) | +| CONNECTION_ID | | X | Connection ID number | +| CS(COOKIE) | X | X | Information about cookies contained in the HTTP request | +| CS(HOST) | X | X | Host field of the HTTP request | +| CS(REFERER) | X | X | URL of the page pointing to the requested document | +| CS(USER_AGENT) | X | X | Information about the software and operating system of the client | +| CS_SIP | X | X | IP address of the server | +| CS_URI | X | X | URI on which the request is made | +| CS_URI_QUERY | X | X | Request query parameters | +| CS_URI_STEM | X | X | Part of request without query parameters | +| DATE | X | X | DD: day, MMM: 3-letter abbreviation for month (Jan, Feb, etc.), YYYY: year | +| METHOD | X | X | HTTP method used for the request sent to the server | +| PATH_ARGS | | X | CGI parameters: string located after the "$" character | +| STATUS | X | X | Reply provided by the server | +| TIME | X | X | HH: hour, MM: minutes, SS: seconds | +| TRANSFER_TIME | X | X | Time requested by server to generate the reply | +| USER | X | X | User name if authenticated; otherwise - (minus sign). | +| | | | If the user name contains spaces, they are replaced by \_ (underlines) | +| URL | | X | URL requested by the client | > Dates and times are given in GMT. @@ -263,51 +242,50 @@ The following table lists the fields available for each format (in alphabetical Configure the automatic backup parameters for the request log. First you must choose the frequency (days, weeks, etc.) or the file size limit criterion by clicking on the corresponding radio button. You must then specify the precise moment of the backup if necessary. -- **No Backup**: The scheduled backup function is deactivated. -- **Every X hour(s)**: This option is used to program backups on an hourly basis. You can enter a value between 1 and 24 . +- **No Backup**: The scheduled backup function is deactivated. +- **Every X hour(s)**: This option is used to program backups on an hourly basis. You can enter a value between 1 and 24 . + - **starting at**: Used to set the time at which the first back up will begin. - - **starting at**: Used to set the time at which the first back up will begin. -- **Every X day(s) at X**: This option is used to program backups on a daily basis. Enter 1 if you want to perform a daily backup. When this option is checked, you must indicate the time when the backup must be started. -- **Every X week(s), day at X**: This option is used to program backups on a weekly basis. Enter 1 if you want to perform a weekly backup. When this option is checked, you must indicate the day(s) of the week and the time when each backup must be started. You can select several days of the week if desired. For example, you can use this option to set two weekly backups: one on Wednesdays and one on Fridays. -- **Every X month(s), Xth day at X**: This option is used to program backups on a monthly basis. Enter 1 if you want to perform a monthly backup. When this option is checked, you must indicate the day of the month and the time when the backup must be started. -- **Every X MB**: This option is used to program backups based on the size of the current request log file. A backup is automatically triggered when the file reaches the set size. You can set a size limit of 1, 10, 100 or 1000 MB. +- **Every X day(s) at X**: This option is used to program backups on a daily basis. Enter 1 if you want to perform a daily backup. When this option is checked, you must indicate the time when the backup must be started. +- **Every X week(s), day at X**: This option is used to program backups on a weekly basis. Enter 1 if you want to perform a weekly backup. When this option is checked, you must indicate the day(s) of the week and the time when each backup must be started. You can select several days of the week if desired. For example, you can use this option to set two weekly backups: one on Wednesdays and one on Fridays. +- **Every X month(s), Xth day at X**: This option is used to program backups on a monthly basis. Enter 1 if you want to perform a monthly backup. When this option is checked, you must indicate the day of the month and the time when the backup must be started. +- **Every X MB**: This option is used to program backups based on the size of the current request log file. A backup is automatically triggered when the file reaches the set size. You can set a size limit of 1, 10, 100 or 1000 MB. > In the case of scheduled backups, if the Web server was not launched when the backup was scheduled to occur, on the next startup 4D considers the backup as failed and applies the appropriate settings, set via the Database Settings. -## Web Services +## Web Services You use the options on this tab to activate and configure Web services for the 4D project, both for their publishing (server side) and their subscription (client side). For more information about the support of Web Services in 4D, refer to the [Publication and use of Web Services](https://doc.4d.com/What-s-new/4D-Design-Reference-19-R4/Publication-and-use-of-Web-Services.200-5736722.en.html) chapter. -### Server Side +### Server Side + +This area contains various options related to the use of 4D as a Web Services "server" i.e., publishing project methods in the form of Web Services. -This area contains various options related to the use of 4D as a Web Services "server" i.e., publishing project methods in the form of Web Services. +- **Allow Web Services Requests**: This option lets you initialize the publication of Web Services. If this option has not been checked, 4D refuses SOAP requests and does not generate a WSDL - even if methods have the _Published in WSDL_ attribute. When this option is checked, 4D creates the WSDL file. +- **Web Service Name**: This area lets you change the "generic name" of the Web Service. This name is used to differentiate the services both at the SOAP server level (when the server publishes several different Web Services), as well as in the Web Services directories. By default, 4D uses the name A_WebService. +- **Web Services Namespace**: This area is used to change the namespace of the Web Services published by 4D. Each Web Service published on the Internet must be unique. The uniqueness of the names of Web Services is ensured by using XML namespaces. A namespace is an arbitrary character string used to identify a set of XML tags in a unique way. Typically, the namespace begins with the URL of the company (http://mycompany.com/mynamespace). In this case, it is not indispensable to have anything in particular at the URL indicated; what matters is that the character string used is unique. By default, 4D uses the following namespace: http://www.4d.com/namespace/default. -- **Allow Web Services Requests**: This option lets you initialize the publication of Web Services. If this option has not been checked, 4D refuses SOAP requests and does not generate a WSDL - even if methods have the *Published in WSDL* attribute. When this option is checked, 4D creates the WSDL file. -- **Web Service Name**: This area lets you change the "generic name" of the Web Service. This name is used to differentiate the services both at the SOAP server level (when the server publishes several different Web Services), as well as in the Web Services directories. By default, 4D uses the name A_WebService. -- **Web Services Namespace**: This area is used to change the namespace of the Web Services published by 4D. Each Web Service published on the Internet must be unique. The uniqueness of the names of Web Services is ensured by using XML namespaces. A namespace is an arbitrary character string used to identify a set of XML tags in a unique way. Typically, the namespace begins with the URL of the company (http://mycompany.com/mynamespace). In this case, it is not indispensable to have anything in particular at the URL indicated; what matters is that the character string used is unique. By default, 4D uses the following namespace: http://www.4d.com/namespace/default. - > In conformity with the XML standard for tag names, the character strings used must not contain spaces nor start with a number. Moreover, to avoid any risk of incompatibility, we recommend that you do not use any extended characters (such as accented characters). -### Client Side +### Client Side This area contains various options related to the use of 4D as a Web Services "client" i.e., subscribing to services published on the network. -- **Wizard Method Prefix**: This area lets you change the prefix that is added automatically by 4D to the name of proxy methods generated by the Web Services Wizard. Proxy project methods form a link between the 4D application and the Web Services server. By default, 4D uses the prefix "proxy_". - +- **Wizard Method Prefix**: This area lets you change the prefix that is added automatically by 4D to the name of proxy methods generated by the Web Services Wizard. Proxy project methods form a link between the 4D application and the Web Services server. By default, 4D uses the prefix "proxy\_". ## Web Features This page contains the options used to enable and control advanced Web features such as the REST server. -### Publishing +### Publishing #### Expose as REST server Starts and stops the REST Server. See [REST Server Configuration](../REST/configuration.md). -### Access +### Access This option specifies a group of 4D users that is authorized to establish the link to the 4D database using REST requests. See [Configuring REST access](../REST/configuration.md#configuring-rest-access). @@ -315,4 +293,4 @@ This option specifies a group of 4D users that is authorized to establish the li #### Enable access to the web studio -Enables general access to the web studio. You still need to configure it at every project level. \ No newline at end of file +Enables general access to the web studio. You still need to configure it at every project level. diff --git a/versioned_sidebars/version-20-R10-sidebars.json b/versioned_sidebars/version-20-R10-sidebars.json index 7080eec733b24a..077df31748cd41 100644 --- a/versioned_sidebars/version-20-R10-sidebars.json +++ b/versioned_sidebars/version-20-R10-sidebars.json @@ -1,5 +1,5 @@ -{ - "docs": [ + { + "docs": [ { "type": "category", "label": "Getting Started", @@ -14,40 +14,52 @@ }, "items": [ "GettingStarted/installation", - "GettingStarted/creating", + "Project/overview", "Notes/updates" ] }, { "type": "category", - "label": "Core Development", + "label": "Project & IDE", "link": { "type": "generated-index", - "title": "Core Development", - "slug": "/category/core-development", + "title": "Project & IDE", + "slug": "/category/project-ide", "keywords": [ - "core" + "ide" ], "image": "/img/docusaurus.png" }, "items": [ - { + "GettingStarted/creating", + "Project/architecture", + { + "type": "category", + "label": "Dababase structure", + "items": [ + "Develop/field-properties" + ] + }, + { + "type": "category", + "label": "Code & Methods", + "items": [ + "Project/code-overview", + "code-editor/write-class-method", + "Project/project-method-properties", + "Project/documentation" + ] + }, + "Project/components", + "Project/compiler", + { "type": "category", - "label": "Project Management", + "label": "Settings", "link": { - "type": "doc", - "id": "Project/overview" - }, - "items": [ - "Project/architecture", - { - "type": "category", - "label": "Settings", - "link": { "type": "doc", "id": "settings/overview" - }, - "items": [ + }, + "items": [ "settings/general", "settings/interface", "settings/compiler", @@ -60,87 +72,37 @@ "settings/security", "settings/compatibility" ] - }, - "Project/components", - "Project/date-time-formats", - "Project/documentation", - { - "type": "category", - "label": "Dababase structure", - "items": [ - "Develop/field-properties" - ] - } - ] }, - { - "type": "category", - "label": "Development Environment", - "items": [ - "Project/code-overview", - "code-editor/write-class-method", - "Project/compiler", - { - "type": "category", - "label": "Debugging", - "link": { + "Desktop/building", + { + "type": "category", + "label": "Debugging", + "link": { "type": "doc", "id": "Debugging/basics" }, - "items": [ + "items": [ "Debugging/debugger", "Debugging/breakpoints", "Debugging/debugging-remote" ] - }, - "Debugging/debugLogFiles", - { - "type": "category", - "label": "Preferences", - "link": { - "type": "doc", - "id": "Preferences/overview" - }, - "items": [ - "Preferences/general", - "Preferences/structure", - "Preferences/forms", - "Preferences/methods", - "Preferences/shortcuts" - ] - } - ] - }, - { - "type": "category", - "label": "ORDA", - "link": { - "type": "doc", - "id": "ORDA/overview" }, - "items": [ - "ORDA/dsmapping", - "ORDA/ordaClasses", - "ORDA/orda-events", - "ORDA/entities", - "ORDA/global-stamp", - "ORDA/datastores", - "ORDA/privileges", - "ORDA/client-server-optimization", - "ORDA/glossary" - ] - }, - { - "type": "category", - "label": "Processes", - "items": [ - "Develop/processes", - "Develop/preemptive-processes" - ] - }, - "Develop-legacy/transactions", - "Tags/transformation-tags" - ] + { + "type": "category", + "label": "Application Preferences", + "link": { + "type": "doc", + "id": "Preferences/overview" + }, + "items": [ + "Preferences/general", + "Preferences/structure", + "Preferences/forms", + "Preferences/methods", + "Preferences/shortcuts" + ] + } + ] }, { "type": "category", @@ -150,7 +112,7 @@ "title": "4D Language", "slug": "/category/4d-language", "keywords": [ - "language" + "language","orda" ], "image": "/img/docusaurus.png" }, @@ -199,12 +161,13 @@ "Concepts/paths" ] }, + "commands/command-index", { "type": "category", - "label": "Commands", + "label": "Commands by theme", "link": { "type": "generated-index", - "title": "Commands", + "title": "Commands by theme", "slug": "/category/commands", "keywords": [ "commands" @@ -212,7 +175,6 @@ "image": "/img/docusaurus.png" }, "items": [ - "commands/command-index", { "type": "category", "label": "4D Environment", @@ -481,34 +443,6 @@ "commands-legacy/register-data-key" ] }, - { - "type": "category", - "label": "Database Methods", - "link": { - "type": "doc", - "id": "commands/theme/Database_Methods_theme" - }, - "items": [ - "commands-legacy/on-backup-shutdown-database-method", - "commands-legacy/on-backup-startup-database-method", - "commands-legacy/on-drop-database-method", - "commands-legacy/on-exit-database-method", - "commands-legacy/on-host-database-event-database-method", - "commands-legacy/on-mobile-app-action-database-method", - "commands-legacy/on-mobile-app-authentication-database-method", - "commands-legacy/on-rest-authentication-database-method", - "commands-legacy/on-server-close-connection-database-method", - "commands-legacy/on-server-open-connection-database-method", - "commands-legacy/on-server-shutdown-database-method", - "commands-legacy/on-server-startup-database-method", - "commands-legacy/on-sql-authentication-database-method", - "commands-legacy/on-startup-database-method", - "commands-legacy/on-system-event-database-method", - "commands-legacy/on-web-authentication-database-method", - "commands-legacy/on-web-connection-database-method", - "commands-legacy/on-web-legacy-close-session-database-method" - ] - }, { "type": "category", "label": "Date and Time", @@ -2273,7 +2207,6 @@ "type": "category", "label": "Classes", "items": [ - "API/overview", "API/BlobClass", "API/ClassClass", "API/CollectionClass", @@ -2316,7 +2249,7 @@ ], "link": { "type": "generated-index", - "title": "Class Functions", + "title": "Classes", "description": "List of built-in 4D classes", "slug": "/category/class-API-reference", "keywords": [ @@ -2329,683 +2262,140 @@ }, { "type": "category", - "label": "Administration", + "label": "Core Development", "link": { "type": "generated-index", - "title": "Administration", - "description": "How to monitor your 4D applications", - "keywords": [ - "administration" - ], + "title": "Core Development", + "slug": "/category/core", "image": "/img/docusaurus.png" }, "items": [ { "type": "category", - "label": "4D Server Administration Window", + "label": "ORDA", "link": { "type": "doc", - "id": "ServerWindow/overview" + "id": "ORDA/overview" }, "items": [ - "ServerWindow/monitor", - "ServerWindow/users", - "ServerWindow/processes", - "ServerWindow/maintenance", - "ServerWindow/application-server", - "ServerWindow/sql-server", - "ServerWindow/http-server", - "ServerWindow/real-time-monitor", - "ServerWindow/remote-admin" + "ORDA/dsmapping", + "ORDA/ordaClasses", + "ORDA/entities", + "ORDA/global-stamp", + "ORDA/datastores", + "ORDA/privileges", + "ORDA/client-server-optimization", + "ORDA/glossary" ] }, { "type": "category", - "label": "Web Administration", + "label": "Processes", "link": { "type": "generated-index", - "title": "Web Administration", - "description": "4D web tools for administrating and monitoring your applications.", - "slug": "/category/web-administration", + "title": "Processes", + "slug": "/category/processes", "keywords": [ - "web administration" + "processes" ], "image": "/img/docusaurus.png" }, "items": [ - "Admin/webAdmin", - "Admin/dataExplorer" + "Develop/processes", + "Develop/preemptive-processes" ] }, - { - "type": "doc", - "label": "Command Line Interface", - "id": "Admin/cli" - }, - { - "type": "doc", - "label": "TLS Protocol", - "id": "Admin/tls" - }, - { - "type": "doc", - "label": "Licenses", - "id": "Admin/licenses" - }, { "type": "category", - "label": "MSC", + "label": "Database Methods", "link": { - "type": "doc", - "id": "MSC/overview" - }, - "items": [ - "MSC/information", - "MSC/analysis", - "MSC/verify", - "MSC/backup", - "MSC/compact", - "MSC/rollback", - "MSC/restore", - "MSC/repair", - "MSC/encrypt" - ] + "type": "generated-index", + "title": "Database Methods", + "slug": "/category/database-methods", + "image": "/img/docusaurus.png" + }, + "items": [ + "commands-legacy/on-backup-shutdown-database-method", + "commands-legacy/on-backup-startup-database-method", + "commands-legacy/on-drop-database-method", + "commands-legacy/on-exit-database-method", + "commands-legacy/on-host-database-event-database-method", + "commands-legacy/on-mobile-app-action-database-method", + "commands-legacy/on-mobile-app-authentication-database-method", + "commands-legacy/on-rest-authentication-database-method", + "commands-legacy/on-server-close-connection-database-method", + "commands-legacy/on-server-open-connection-database-method", + "commands-legacy/on-server-shutdown-database-method", + "commands-legacy/on-server-startup-database-method", + "commands-legacy/on-sql-authentication-database-method", + "commands-legacy/on-startup-database-method", + "commands-legacy/on-system-event-database-method", + "commands-legacy/on-web-authentication-database-method", + "commands-legacy/on-web-connection-database-method", + "commands-legacy/on-web-legacy-close-session-database-method" + ] + }, + "Develop-legacy/transactions", + "Tags/transformation-tags", + "Project/date-time-formats" + ] + }, + { + "type": "category", + "label": "Web Applications", + "link": { + "type": "generated-index", + "title": "Web Applications", + "description": "Guides for developing Web applications with 4D", + "keywords": [ + "web applications" + ], + "image": "/img/docusaurus.png" + }, + "items": [ + { + "type": "link", + "label": "4D Qodly Pro", + "href": "https://developer.4d.com/qodly/" }, { "type": "category", - "label": "Backup and Restore", + "label": "Web Server", "link": { "type": "doc", - "id": "Backup/overview" + "id": "WebServer/webServer" }, "items": [ - "Backup/backup", - "Backup/settings", - "Backup/log", - "Backup/restore" + "WebServer/gettingStarted", + "WebServer/webServerConfig", + "WebServer/webServerAdmin", + "WebServer/webServerObject", + "WebServer/templates", + "WebServer/httpRequests", + "WebServer/http-request-handler", + "WebServer/allowProject", + "WebServer/errorPages", + "WebServer/authentication", + "WebServer/sessions", + "WebServer/preemptiveWeb" ] }, - { - "type": "doc", - "label": "Data Collection", - "id": "Admin/data-collect" - } - ] - }, - { - "type": "category", - "label": "Extensions", - "link": { - "type": "doc", - "id": "Extensions/overview" - }, - "items": [ { "type": "category", - "label": "4D View Pro", + "label": "REST API", "link": { "type": "generated-index", - "title": "4D View Pro", - "slug": "/category/4d-view-pro", + "title": "REST API", + "description": "Exposing your datastore to REST and using the REST API.", "keywords": [ - "4D View Pro" + "REST server" ], "image": "/img/docusaurus.png" }, "items": [ - "ViewPro/getting-started", - "ViewPro/configuring", - "ViewPro/formulas", - "ViewPro/classes", - "ViewPro/advanced-programming", { "type": "category", - "label": "Commands", - "link": { - "type": "doc", - "id": "ViewPro/commands" - }, - "items": [ - { - "type": "category", - "label": "A", - "link": { - "type": "generated-index", - "title": "A", - "slug": "/commands-legacy/A" - }, - "items": [ - "ViewPro/commands/vp-add-formula-name", - "ViewPro/commands/vp-add-range-name", - "ViewPro/commands/vp-add-selection", - "ViewPro/commands/vp-add-sheet", - "ViewPro/commands/vp-add-span", - "ViewPro/commands/vp-add-stylesheet", - "ViewPro/commands/vp-all" - ] - }, - { - "type": "category", - "label": "C", - "link": { - "type": "generated-index", - "title": "C", - "slug": "/commands-legacy/C" - }, - "items": [ - "ViewPro/commands/vp-cell", - "ViewPro/commands/vp-cells", - "ViewPro/commands/vp-column", - "ViewPro/commands/vp-column-autofit", - "ViewPro/commands/vp-combine-ranges", - "ViewPro/commands/vp-convert-from-4d-view", - "ViewPro/commands/vp-convert-to-picture", - "ViewPro/commands/vp-copy-to-object", - "ViewPro/commands/vp-create-table" - ] - }, - { - "type": "category", - "label": "D", - "link": { - "type": "generated-index", - "title": "D", - "slug": "/commands-legacy/D" - }, - "items": [ - "ViewPro/commands/vp-delete-columns", - "ViewPro/commands/vp-delete-rows" - ] - }, - { - "type": "category", - "label": "E", - "link": { - "type": "generated-index", - "title": "E", - "slug": "/commands-legacy/E" - }, - "items": [ - "ViewPro/commands/vp-export-document", - "ViewPro/commands/vp-export-to-blob", - "ViewPro/commands/vp-export-to-object" - ] - }, - { - "type": "category", - "label": "F", - "link": { - "type": "generated-index", - "title": "F", - "slug": "/commands-legacy/F" - }, - "items": [ - "ViewPro/commands/vp-find", - "ViewPro/commands/vp-find-table", - "ViewPro/commands/vp-flush-commands", - "ViewPro/commands/vp-font-to-object" - ] - }, - { - "type": "category", - "label": "G", - "link": { - "type": "generated-index", - "title": "G", - "slug": "/commands-legacy/G" - }, - "items": [ - "ViewPro/commands/vp-get-active-cell", - "ViewPro/commands/vp-get-binding-path", - "ViewPro/commands/vp-get-cell-style", - "ViewPro/commands/vp-get-column-attributes", - "ViewPro/commands/vp-get-column-count", - "ViewPro/commands/vp-get-current-sheet", - "ViewPro/commands/vp-get-data-context", - "ViewPro/commands/vp-get-default-style", - "ViewPro/commands/vp-get-formula", - "ViewPro/commands/vp-get-formula-by-name", - "ViewPro/commands/vp-get-formulas", - "ViewPro/commands/vp-get-frozen-panes", - "ViewPro/commands/vp-get-names", - "ViewPro/commands/vp-get-print-info", - "ViewPro/commands/vp-get-row-attributes", - "ViewPro/commands/vp-get-row-count", - "ViewPro/commands/vp-get-selection", - "ViewPro/commands/vp-get-sheet-count", - "ViewPro/commands/vp-get-sheet-index", - "ViewPro/commands/vp-get-sheet-name", - "ViewPro/commands/vp-get-sheet-options", - "ViewPro/commands/vp-get-show-print-lines", - "ViewPro/commands/vp-get-spans", - "ViewPro/commands/vp-get-stylesheet", - "ViewPro/commands/vp-get-stylesheets", - "ViewPro/commands/vp-get-table-column-attributes", - "ViewPro/commands/vp-get-table-column-index", - "ViewPro/commands/vp-get-table-dirty-rows", - "ViewPro/commands/vp-get-table-range", - "ViewPro/commands/vp-get-table-theme", - "ViewPro/commands/vp-get-tables", - "ViewPro/commands/vp-get-value", - "ViewPro/commands/vp-get-values", - "ViewPro/commands/vp-get-workbook-options" - ] - }, - { - "type": "category", - "label": "I", - "link": { - "type": "generated-index", - "title": "I", - "slug": "/commands-legacy/I" - }, - "items": [ - "ViewPro/commands/vp-import-document", - "ViewPro/commands/vp-import-from-blob", - "ViewPro/commands/vp-import-from-object", - "ViewPro/commands/vp-insert-columns", - "ViewPro/commands/vp-insert-rows", - "ViewPro/commands/vp-insert-table-columns", - "ViewPro/commands/vp-insert-table-rows" - ] - }, - { - "type": "category", - "label": "M", - "link": { - "type": "generated-index", - "title": "M", - "slug": "/commands-legacy/M" - }, - "items": [ - "ViewPro/commands/vp-move-cells" - ] - }, - { - "type": "category", - "label": "N", - "link": { - "type": "generated-index", - "title": "N", - "slug": "/commands-legacy/N" - }, - "items": [ - "ViewPro/commands/vp-name", - "ViewPro/commands/vp-new-document" - ] - }, - { - "type": "category", - "label": "O", - "link": { - "type": "generated-index", - "title": "O", - "slug": "/commands-legacy/O" - }, - "items": [ - "ViewPro/commands/vp-object-to-font" - ] - }, - { - "type": "category", - "label": "P", - "link": { - "type": "generated-index", - "title": "P", - "slug": "/commands-legacy/P" - }, - "items": [ - "ViewPro/commands/vp-paste-from-object", - "ViewPro/commands/vp-print" - ] - }, - { - "type": "category", - "label": "R", - "link": { - "type": "generated-index", - "title": "R", - "slug": "/commands-legacy/R" - }, - "items": [ - "ViewPro/commands/vp-recompute-formulas", - "ViewPro/commands/vp-remove-name", - "ViewPro/commands/vp-remove-sheet", - "ViewPro/commands/vp-remove-span", - "ViewPro/commands/vp-remove-stylesheet", - "ViewPro/commands/vp-remove-table", - "ViewPro/commands/vp-remove-table-columns", - "ViewPro/commands/vp-remove-table-rows", - "ViewPro/commands/vp-reset-selection", - "ViewPro/commands/vp-resize-table", - "ViewPro/commands/vp-resume-computing", - "ViewPro/commands/vp-row", - "ViewPro/commands/vp-row-autofit", - "ViewPro/commands/vp-run-offscreen-area" - ] - }, - { - "type": "category", - "label": "S", - "link": { - "type": "generated-index", - "title": "S", - "slug": "/commands-legacy/S" - }, - "items": [ - "ViewPro/commands/vp-set-active-cell", - "ViewPro/commands/vp-set-allowed-methods", - "ViewPro/commands/vp-set-binding-path", - "ViewPro/commands/vp-set-boolean-value", - "ViewPro/commands/vp-set-border", - "ViewPro/commands/vp-set-cell-style", - "ViewPro/commands/vp-set-column-attributes", - "ViewPro/commands/vp-set-column-count", - "ViewPro/commands/vp-set-current-sheet", - "ViewPro/commands/vp-set-custom-functions", - "ViewPro/commands/vp-set-data-context", - "ViewPro/commands/vp-set-date-time-value", - "ViewPro/commands/vp-set-date-value", - "ViewPro/commands/vp-set-default-style", - "ViewPro/commands/vp-set-field", - "ViewPro/commands/vp-set-formula", - "ViewPro/commands/vp-set-formulas", - "ViewPro/commands/vp-set-frozen-panes", - "ViewPro/commands/vp-set-num-value", - "ViewPro/commands/vp-set-print-info", - "ViewPro/commands/vp-set-row-attributes", - "ViewPro/commands/vp-set-row-count", - "ViewPro/commands/vp-set-selection", - "ViewPro/commands/vp-set-sheet-count", - "ViewPro/commands/vp-set-sheet-name", - "ViewPro/commands/vp-set-sheet-options", - "ViewPro/commands/vp-set-show-print-lines", - "ViewPro/commands/vp-set-table-column-attributes", - "ViewPro/commands/vp-set-table-theme", - "ViewPro/commands/vp-set-text-value", - "ViewPro/commands/vp-set-time-value", - "ViewPro/commands/vp-set-value", - "ViewPro/commands/vp-set-values", - "ViewPro/commands/vp-set-workbook-options", - "ViewPro/commands/vp-show-cell", - "ViewPro/commands/vp-suspend-computing" - ] - } - ] - } - ] - }, - { - "type": "category", - "label": "4D Write Pro", - "link": { - "type": "generated-index", - "title": "4D Write Pro", - "slug": "/category/4d-write-pro", - "keywords": [ - "4D Write Pro" - ], - "image": "/img/docusaurus.png" - }, - "items": [ - "WritePro/writeprointerface", - "WritePro/managing-formulas", - "WritePro/commands-legacy/4d-write-pro-attributes", - { - "type": "category", - "label": "Commands", - "link": { - "type": "doc", - "id": "WritePro/commands/command-index" - }, - "items": [ - "WritePro/commands/wp-add-picture", - "WritePro/commands-legacy/wp-bookmark-range", - "WritePro/commands-legacy/wp-compute-formulas", - "WritePro/commands-legacy/wp-delete-bookmark", - "WritePro/commands-legacy/wp-delete-footer", - "WritePro/commands-legacy/wp-delete-header", - "WritePro/commands-legacy/wp-delete-picture", - "WritePro/commands/wp-delete-section", - "WritePro/commands-legacy/wp-delete-style-sheet", - "WritePro/commands/wp-delete-subsection", - "WritePro/commands-legacy/wp-delete-text-box", - "WritePro/commands/wp-export-document", - "WritePro/commands/wp-export-variable", - "WritePro/commands-legacy/wp-find-all", - "WritePro/commands-legacy/wp-find-next", - "WritePro/commands-legacy/wp-find-previous", - "WritePro/commands-legacy/wp-freeze-formulas", - "WritePro/commands/wp-get-attributes", - "WritePro/commands-legacy/wp-get-body", - "WritePro/commands-legacy/wp-get-bookmarks", - "WritePro/commands-legacy/wp-get-breaks", - "WritePro/commands-legacy/wp-get-data-context", - "WritePro/commands-legacy/wp-get-element-by-id", - "WritePro/commands-legacy/wp-get-elements", - "WritePro/commands-legacy/wp-get-footer", - "WritePro/commands-legacy/wp-get-formulas", - "WritePro/commands-legacy/wp-get-frame", - "WritePro/commands-legacy/wp-get-header", - "WritePro/commands-legacy/wp-get-links", - "WritePro/commands-legacy/wp-get-page-count", - "WritePro/commands-legacy/wp-get-position", - "WritePro/commands-legacy/wp-get-section", - "WritePro/commands-legacy/wp-get-sections", - "WritePro/commands-legacy/wp-get-style-sheet", - "WritePro/commands-legacy/wp-get-style-sheets", - "WritePro/commands-legacy/wp-get-subsection", - "WritePro/commands-legacy/wp-get-text", - "WritePro/commands-legacy/wp-get-view-properties", - "WritePro/commands/wp-import-document", - "WritePro/commands-legacy/wp-import-style-sheets", - "WritePro/commands/wp-insert-break", - "WritePro/commands/wp-insert-document-body", - "WritePro/commands/wp-insert-formula", - "WritePro/commands/wp-insert-picture", - "WritePro/commands-legacy/wp-insert-table", - "WritePro/commands-legacy/wp-is-font-style-supported", - "WritePro/commands-legacy/wp-new", - "WritePro/commands-legacy/wp-new-bookmark", - "WritePro/commands-legacy/wp-new-footer", - "WritePro/commands-legacy/wp-new-header", - "WritePro/commands-legacy/wp-new-style-sheet", - "WritePro/commands-legacy/wp-new-subsection", - "WritePro/commands-legacy/wp-new-text-box", - "WritePro/commands-legacy/wp-paragraph-range", - "WritePro/commands-legacy/wp-picture-range", - "WritePro/commands-legacy/wp-print", - "WritePro/commands/wp-reset-attributes", - "WritePro/commands-legacy/wp-select", - "WritePro/commands-legacy/wp-selection-range", - "WritePro/commands/wp-set-attributes", - "WritePro/commands-legacy/wp-set-data-context", - "WritePro/commands-legacy/wp-set-frame", - "WritePro/commands-legacy/wp-set-link", - "WritePro/commands-legacy/wp-set-text", - "WritePro/commands-legacy/wp-set-view-properties", - "WritePro/commands/wp-table-append-row", - "WritePro/commands-legacy/wp-table-delete-columns", - "WritePro/commands-legacy/wp-table-delete-rows", - "WritePro/commands-legacy/wp-table-get-cells", - "WritePro/commands-legacy/wp-table-get-columns", - "WritePro/commands-legacy/wp-table-get-rows", - "WritePro/commands-legacy/wp-table-insert-columns", - "WritePro/commands-legacy/wp-table-insert-rows", - "WritePro/commands-legacy/wp-table-merge-cells", - "WritePro/commands-legacy/wp-table-range", - "WritePro/commands-legacy/wp-table-split-cells", - "WritePro/commands-legacy/wp-text-range", - "WritePro/commands-legacy/wp-use-page-setup" - ] - } - ] - }, - { - "type": "category", - "label": "4D AIKit", - "link": { - "type": "generated-index", - "title": "4D AIKit", - "slug": "/category/4d-aikit", - "keywords": [ - "4D AIKit" - ], - "image": "/img/docusaurus.png" - }, - "items": [ - "aikit/overview", - "aikit/asynchronous-call", - "aikit/compatible-openai", - { - "type": "category", - "label": "Classes", - "items": [ - "aikit/Classes/openai", - "aikit/Classes/openaiapiresource", - "aikit/Classes/openaichatapi", - "aikit/Classes/openaichatcompletionsapi", - "aikit/Classes/openaichatcompletionslistparameters", - "aikit/Classes/openaichatcompletionsmessagesapi", - "aikit/Classes/openaichatcompletionsmessagesparameters", - "aikit/Classes/openaichatcompletionsparameters", - "aikit/Classes/openaichatcompletionsresult", - "aikit/Classes/openaichatcompletionsstreamresult", - "aikit/Classes/openaichathelper", - "aikit/Classes/openaichoice", - "aikit/Classes/openaiembedding", - "aikit/Classes/openaiembeddingsapi", - "aikit/Classes/openaiembeddingsparameters", - "aikit/Classes/openaiembeddingsresult", - "aikit/Classes/openaierror", - "aikit/Classes/openaiimage", - "aikit/Classes/openaiimageparameters", - "aikit/Classes/openaiimagesapi", - "aikit/Classes/openaiimagesresult", - "aikit/Classes/openaimessage", - "aikit/Classes/openaimodel", - "aikit/Classes/openaimodellistresult", - "aikit/Classes/openaimodelresult", - "aikit/Classes/openaimodelsapi", - "aikit/Classes/openaimoderation", - "aikit/Classes/openaimoderationitem", - "aikit/Classes/openaimoderationresult", - "aikit/Classes/openaimoderationsapi", - "aikit/Classes/openaiparameters", - "aikit/Classes/openairesult", - "aikit/Classes/openaivision", - "aikit/Classes/openaivisionhelper" - ] - } - ] - }, - { - "type": "link", - "label": "4D Mobile App Server", - "href": "https://github.com/4d-go-mobile/4D-Mobile-App-Server" - }, - { - "type": "link", - "label": "4D NetKit", - "href": "https://developer.4d.com/4D-NetKit" - }, - { - "type": "link", - "label": "4D Progress", - "href": "https://doc.4d.com/4Dv20R10/4D/20-R10/4D-Progress.100-7614210.en.html" - }, - { - "type": "link", - "label": "4D SVG", - "href": "https://doc.4d.com/4Dv20R10/4D/20-R10/4D-SVG-Component.100-7614300.en.html" - }, - { - "type": "link", - "label": "4D Widgets", - "href": "https://doc.4d.com/4Dv20R10/4D/20-R10/4D-Widgets.100-7614949.en.html" - }, - "Extensions/develop-components", - "Extensions/develop-plug-ins" - ] - }, - { - "type": "category", - "label": "Web Applications", - "link": { - "type": "generated-index", - "title": "Web Applications", - "description": "Guides for developing Web applications with 4D", - "keywords": [ - "web applications" - ], - "image": "/img/docusaurus.png" - }, - "items": [ - { - "type": "category", - "label": "Web Server", - "link": { - "type": "doc", - "id": "WebServer/webServer" - }, - "items": [ - "WebServer/webServerConfig", - "WebServer/webServerAdmin", - "WebServer/webServerObject" - ] - }, - { - "type": "category", - "label": "Web Development", - "link": { - "type": "doc", - "id": "WebServer/gettingStarted" - }, - "items": [ - "WebServer/templates", - "WebServer/httpRequests", - "WebServer/http-request-handler", - "WebServer/allowProject", - "WebServer/errorPages", - "WebServer/authentication", - "WebServer/sessions", - "WebServer/preemptiveWeb" - ] - }, - { - "type": "category", - "label": "Qodly Studio", - "link": { - "type": "generated-index", - "title": "Qodly Studio", - "description": "Using Qodly Studio to build powerful web interfaces.", - "slug": "/category/qodly-studio-in-4d", - "keywords": [ - "Qodly Studio" - ], - "image": "/img/docusaurus.png" - }, - "items": [ - "WebServer/qodly-studio", - "WebServer/from-qodlyscript-to-4d" - ] - }, - { - "type": "category", - "label": "REST API", - "link": { - "type": "generated-index", - "title": "REST API", - "description": "Exposing your datastore to REST and using the REST API.", - "keywords": [ - "REST server" - ], - "image": "/img/docusaurus.png" - }, - "items": [ - { - "type": "category", - "label": "Exposing your datastore in REST", + "label": "Exposing your datastore in REST", "link": { "type": "generated-index", "title": "Exposing your datastore in REST", @@ -3084,273 +2474,883 @@ ] } ] - } + } + ] + }, + { + "type": "category", + "label": "Desktop Applications", + "link": { + "type": "generated-index", + "title": "Desktop Applications", + "description": "Guides for developing Desktop applications with 4D", + "keywords": [ + "desktop applications" + ], + "image": "/img/docusaurus.png" + }, + "items": [ + { + "type": "doc", + "label": "Client/Server", + "id": "Desktop/clientServer" + }, + { + "type": "category", + "label": "Forms", + "link": { + "type": "doc", + "id": "FormEditor/forms" + }, + "items": [ + "FormEditor/stylesheets", + "FormEditor/pictures", + { + "type": "category", + "label": "Form Editor", + "link": { + "type": "doc", + "id": "FormEditor/formEditor" + }, + "items": [ + "FormEditor/macros", + "FormEditor/objectLibrary" + ] + }, + { + "type": "category", + "label": "Form Properties", + "link": { + "type": "doc", + "id": "FormEditor/jsonReference" + }, + "items": [ + "FormEditor/action", + "FormEditor/propertiesForm", + "FormEditor/formSize", + "FormEditor/markers", + "FormEditor/menu", + "FormEditor/print", + "FormEditor/windowSize" + ] + }, + { + "type": "category", + "label": "Form Objects", + "link": { + "type": "doc", + "id": "FormObjects/formObjectsOverview" + }, + "items": [ + "FormObjects/buttonOverview", + "FormObjects/buttonGridOverview", + "FormObjects/checkboxOverview", + "FormObjects/comboBoxOverview", + "FormObjects/dropdownListOverview", + "FormObjects/groupBox", + "FormObjects/inputOverview", + "FormObjects/listOverview", + "FormObjects/listboxOverview", + "FormObjects/pictureButtonOverview", + "FormObjects/picturePopupMenuOverview", + "FormObjects/pluginAreaOverview", + "FormObjects/progressIndicator", + "FormObjects/radiobuttonOverview", + "FormObjects/ruler", + "FormObjects/shapesOverview", + "FormObjects/spinner", + "FormObjects/splitters", + "FormObjects/staticPicture", + "FormObjects/stepper", + "FormObjects/subformOverview", + "FormObjects/tabControl", + "FormObjects/text", + "FormObjects/webAreaOverview", + "FormObjects/viewProAreaOverview", + "FormObjects/writeProAreaOverview" + ] + }, + { + "type": "category", + "label": "Form Object Properties", + "link": { + "type": "doc", + "id": "FormObjects/propertiesReference" + }, + "items": [ + "FormObjects/propertiesAction", + "FormObjects/propertiesAnimation", + "FormObjects/propertiesAppearance", + "FormObjects/propertiesBackgroundAndBorder", + "FormObjects/propertiesCoordinatesAndSizing", + "FormObjects/propertiesCrop", + "FormObjects/propertiesDataSource", + "FormObjects/propertiesDisplay", + "FormObjects/propertiesEntry", + "FormObjects/propertiesFooters", + "FormObjects/propertiesGridlines", + "FormObjects/propertiesHeaders", + "FormObjects/propertiesHelp", + "FormObjects/propertiesHierarchy", + "FormObjects/propertiesListBox", + "FormObjects/propertiesObject", + "FormObjects/propertiesPicture", + "FormObjects/propertiesPlugIns", + "FormObjects/propertiesPrint", + "FormObjects/propertiesRangeOfValues", + "FormObjects/propertiesResizingOptions", + "FormObjects/propertiesScale", + "FormObjects/propertiesSubform", + "FormObjects/propertiesText", + "FormObjects/propertiesTextAndPicture", + "FormObjects/propertiesWebArea" + ] + }, + { + "type": "category", + "label": "Form Events", + "link": { + "type": "doc", + "id": "Events/overview" + }, + "items": [ + "Events/onActivate", + "Events/onAfterEdit", + "Events/onAfterKeystroke", + "Events/onAfterSort", + "Events/onAlternativeClick", + "Events/onBeforeDataEntry", + "Events/onBeforeKeystroke", + "Events/onBeginDragOver", + "Events/onBeginUrlLoading", + "Events/onBoundVariableChange", + "Events/onClicked", + "Events/onCloseBox", + "Events/onCloseDetail", + "Events/onCollapse", + "Events/onColumnMoved", + "Events/onColumnResize", + "Events/onDataChange", + "Events/onDeactivate", + "Events/onDeleteAction", + "Events/onDisplayDetail", + "Events/onDoubleClicked", + "Events/onDragOver", + "Events/onDrop", + "Events/onEndUrlLoading", + "Events/onExpand", + "Events/onFooterClick", + "Events/onGettingFocus", + "Events/onHeader", + "Events/onHeaderClick", + "Events/onLoad", + "Events/onLoadRecord", + "Events/onLongClick", + "Events/onLosingFocus", + "Events/onMenuSelected", + "Events/onMouseEnter", + "Events/onMouseLeave", + "Events/onMouseMove", + "Events/onMouseUp", + "Events/onOpenDetail", + "Events/onOpenExternalLink", + "Events/onOutsideCall", + "Events/onPageChange", + "Events/onPlugInArea", + "Events/onPrintingBreak", + "Events/onPrintingDetail", + "Events/onPrintingFooter", + "Events/onResize", + "Events/onRowMoved", + "Events/onRowResize", + "Events/onScroll", + "Events/onSelectionChange", + "Events/onTimer", + "Events/onUnload", + "Events/onUrlFiltering", + "Events/onUrlLoadingError", + "Events/onUrlResourceLoading", + "Events/onValidate", + "Events/onVpRangeChanged", + "Events/onVpReady", + "Events/onWindowOpeningDenied" + ] + } + ] + }, + { + "type": "doc", + "label": "Labels", + "id": "Desktop/labels" + }, + { + "type": "category", + "label": "Menus", + "link": { + "type": "doc", + "id": "Menus/overview" + }, + "items": [ + "Menus/creating", + "Menus/properties", + "Menus/bars", + "Menus/sdi" + ] + }, + { + "type": "category", + "label": "Access Rights", + "link": { + "type": "generated-index", + "title": "Access Rights", + "description": "Access control and user privileges for desktop applications.", + "slug": "/category/access-rights", + "keywords": [ + "access rights" + ], + "image": "/img/docusaurus.png" + }, + "items": [ + "Users/overview", + "Users/editing" + ] + } ] }, { "type": "category", - "label": "Desktop Applications", + "label": "Administration", "link": { "type": "generated-index", - "title": "Desktop Applications", - "description": "Guides for developing Desktop applications with 4D", + "title": "Administration", + "description": "How to monitor your 4D applications", "keywords": [ - "desktop applications" + "administration" ], "image": "/img/docusaurus.png" }, "items": [ { - "type": "doc", - "label": "Client/Server", - "id": "Desktop/clientServer" + "type": "category", + "label": "4D Server Administration Window", + "link": { + "type": "doc", + "id": "ServerWindow/overview" + }, + "items": [ + "ServerWindow/monitor", + "ServerWindow/users", + "ServerWindow/processes", + "ServerWindow/maintenance", + "ServerWindow/application-server", + "ServerWindow/sql-server", + "ServerWindow/http-server", + "ServerWindow/real-time-monitor", + "ServerWindow/remote-admin" + ] }, { "type": "category", - "label": "Access Rights", + "label": "Web Administration", "link": { "type": "generated-index", - "title": "Access Rights", - "description": "Access control and user privileges for desktop applications.", - "slug": "/category/access-rights", + "title": "Web Administration", + "description": "4D web tools for administrating and monitoring your applications.", + "slug": "/category/web-administration", "keywords": [ - "access rights" + "web administration" ], "image": "/img/docusaurus.png" }, "items": [ - "Users/overview", - "Users/editing" + "Admin/webAdmin", + "Admin/dataExplorer" ] }, + { + "type": "doc", + "label": "Command Line Interface", + "id": "Admin/cli" + }, + { + "type": "doc", + "label": "TLS Protocol", + "id": "Admin/tls" + }, + { + "type": "doc", + "label": "Licenses", + "id": "Admin/licenses" + }, + { + "type": "doc", + "label": "Log Files", + "id": "Debugging/debugLogFiles" + }, { "type": "category", - "label": "Forms", + "label": "MSC", "link": { "type": "doc", - "id": "FormEditor/forms" + "id": "MSC/overview" }, "items": [ - "FormEditor/stylesheets", - "FormEditor/pictures", - { - "type": "category", - "label": "Form Editor", - "link": { - "type": "doc", - "id": "FormEditor/formEditor" - }, - "items": [ - "FormEditor/macros", - "FormEditor/objectLibrary" - ] - }, - { - "type": "category", - "label": "Form Properties", - "link": { - "type": "doc", - "id": "FormEditor/jsonReference" - }, - "items": [ - "FormEditor/action", - "FormEditor/propertiesForm", - "FormEditor/formSize", - "FormEditor/markers", - "FormEditor/menu", - "FormEditor/print", - "FormEditor/windowSize" - ] - }, + "MSC/information", + "MSC/analysis", + "MSC/verify", + "MSC/backup", + "MSC/compact", + "MSC/rollback", + "MSC/restore", + "MSC/repair", + "MSC/encrypt" + ] + }, + { + "type": "category", + "label": "Backup and Restore", + "link": { + "type": "doc", + "id": "Backup/overview" + }, + "items": [ + "Backup/backup", + "Backup/settings", + "Backup/log", + "Backup/restore" + ] + }, + { + "type": "doc", + "label": "Data Collection", + "id": "Admin/data-collect" + } + ] + }, + { + "type": "category", + "label": "Extensions", + "link": { + "type": "generated-index", + "title": "Extensions", + "slug": "/category/extensions", + "keywords": [ + "component, extension, plug-in" + ], + "image": "/img/docusaurus.png" + }, + "items": [ { - "type": "category", - "label": "Form Objects", - "link": { - "type": "doc", - "id": "FormObjects/formObjectsOverview" - }, - "items": [ - "FormObjects/buttonOverview", - "FormObjects/buttonGridOverview", - "FormObjects/checkboxOverview", - "FormObjects/comboBoxOverview", - "FormObjects/dropdownListOverview", - "FormObjects/groupBox", - "FormObjects/inputOverview", - "FormObjects/listOverview", - "FormObjects/listboxOverview", - "FormObjects/pictureButtonOverview", - "FormObjects/picturePopupMenuOverview", - "FormObjects/pluginAreaOverview", - "FormObjects/progressIndicator", - "FormObjects/radiobuttonOverview", - "FormObjects/ruler", - "FormObjects/shapesOverview", - "FormObjects/spinner", - "FormObjects/splitters", - "FormObjects/staticPicture", - "FormObjects/stepper", - "FormObjects/subformOverview", - "FormObjects/tabControl", - "FormObjects/text", - "FormObjects/webAreaOverview", - "FormObjects/viewProAreaOverview", - "FormObjects/writeProAreaOverview" - ] + "type": "category", + "label": "Extending 4D applications", + "link": { + "type": "doc", + "id": "Extensions/overview" }, + "items": [ + "Extensions/develop-components", + "Extensions/develop-plug-ins" + ] + }, + { + "type": "category", + "label": "4D View Pro", + "link": { + "type": "generated-index", + "title": "4D View Pro", + "slug": "/category/4d-view-pro", + "keywords": [ + "4D View Pro" + ], + "image": "/img/docusaurus.png" + }, + "items": [ + "ViewPro/getting-started", + "ViewPro/configuring", + "ViewPro/formulas", + "ViewPro/classes", + "ViewPro/advanced-programming", { "type": "category", - "label": "Form Object Properties", + "label": "Commands", "link": { "type": "doc", - "id": "FormObjects/propertiesReference" + "id": "ViewPro/commands" }, "items": [ - "FormObjects/propertiesAction", - "FormObjects/propertiesAnimation", - "FormObjects/propertiesAppearance", - "FormObjects/propertiesBackgroundAndBorder", - "FormObjects/propertiesCoordinatesAndSizing", - "FormObjects/propertiesCrop", - "FormObjects/propertiesDataSource", - "FormObjects/propertiesDisplay", - "FormObjects/propertiesEntry", - "FormObjects/propertiesFooters", - "FormObjects/propertiesGridlines", - "FormObjects/propertiesHeaders", - "FormObjects/propertiesHelp", - "FormObjects/propertiesHierarchy", - "FormObjects/propertiesListBox", - "FormObjects/propertiesObject", - "FormObjects/propertiesPicture", - "FormObjects/propertiesPlugIns", - "FormObjects/propertiesPrint", - "FormObjects/propertiesRangeOfValues", - "FormObjects/propertiesResizingOptions", - "FormObjects/propertiesScale", - "FormObjects/propertiesSubform", - "FormObjects/propertiesText", - "FormObjects/propertiesTextAndPicture", - "FormObjects/propertiesWebArea" + { + "type": "category", + "label": "A", + "link": { + "type": "generated-index", + "title": "A", + "slug": "/commands-legacy/A" + }, + "items": [ + "ViewPro/commands/vp-add-formula-name", + "ViewPro/commands/vp-add-range-name", + "ViewPro/commands/vp-add-selection", + "ViewPro/commands/vp-add-sheet", + "ViewPro/commands/vp-add-span", + "ViewPro/commands/vp-add-stylesheet", + "ViewPro/commands/vp-all" + ] + }, + { + "type": "category", + "label": "C", + "link": { + "type": "generated-index", + "title": "C", + "slug": "/commands-legacy/C" + }, + "items": [ + "ViewPro/commands/vp-cell", + "ViewPro/commands/vp-cells", + "ViewPro/commands/vp-column", + "ViewPro/commands/vp-column-autofit", + "ViewPro/commands/vp-combine-ranges", + "ViewPro/commands/vp-convert-from-4d-view", + "ViewPro/commands/vp-convert-to-picture", + "ViewPro/commands/vp-copy-to-object", + "ViewPro/commands/vp-create-table" + ] + }, + { + "type": "category", + "label": "D", + "link": { + "type": "generated-index", + "title": "D", + "slug": "/commands-legacy/D" + }, + "items": [ + "ViewPro/commands/vp-delete-columns", + "ViewPro/commands/vp-delete-rows" + ] + }, + { + "type": "category", + "label": "E", + "link": { + "type": "generated-index", + "title": "E", + "slug": "/commands-legacy/E" + }, + "items": [ + "ViewPro/commands/vp-export-document", + "ViewPro/commands/vp-export-to-blob", + "ViewPro/commands/vp-export-to-object" + ] + }, + { + "type": "category", + "label": "F", + "link": { + "type": "generated-index", + "title": "F", + "slug": "/commands-legacy/F" + }, + "items": [ + "ViewPro/commands/vp-find", + "ViewPro/commands/vp-find-table", + "ViewPro/commands/vp-flush-commands", + "ViewPro/commands/vp-font-to-object" + ] + }, + { + "type": "category", + "label": "G", + "link": { + "type": "generated-index", + "title": "G", + "slug": "/commands-legacy/G" + }, + "items": [ + "ViewPro/commands/vp-get-active-cell", + "ViewPro/commands/vp-get-binding-path", + "ViewPro/commands/vp-get-cell-style", + "ViewPro/commands/vp-get-column-attributes", + "ViewPro/commands/vp-get-column-count", + "ViewPro/commands/vp-get-current-sheet", + "ViewPro/commands/vp-get-data-context", + "ViewPro/commands/vp-get-default-style", + "ViewPro/commands/vp-get-formula", + "ViewPro/commands/vp-get-formula-by-name", + "ViewPro/commands/vp-get-formulas", + "ViewPro/commands/vp-get-frozen-panes", + "ViewPro/commands/vp-get-names", + "ViewPro/commands/vp-get-print-info", + "ViewPro/commands/vp-get-row-attributes", + "ViewPro/commands/vp-get-row-count", + "ViewPro/commands/vp-get-selection", + "ViewPro/commands/vp-get-sheet-count", + "ViewPro/commands/vp-get-sheet-index", + "ViewPro/commands/vp-get-sheet-name", + "ViewPro/commands/vp-get-sheet-options", + "ViewPro/commands/vp-get-show-print-lines", + "ViewPro/commands/vp-get-spans", + "ViewPro/commands/vp-get-stylesheet", + "ViewPro/commands/vp-get-stylesheets", + "ViewPro/commands/vp-get-table-column-attributes", + "ViewPro/commands/vp-get-table-column-index", + "ViewPro/commands/vp-get-table-dirty-rows", + "ViewPro/commands/vp-get-table-range", + "ViewPro/commands/vp-get-table-theme", + "ViewPro/commands/vp-get-tables", + "ViewPro/commands/vp-get-value", + "ViewPro/commands/vp-get-values", + "ViewPro/commands/vp-get-workbook-options" + ] + }, + { + "type": "category", + "label": "I", + "link": { + "type": "generated-index", + "title": "I", + "slug": "/commands-legacy/I" + }, + "items": [ + "ViewPro/commands/vp-import-document", + "ViewPro/commands/vp-import-from-blob", + "ViewPro/commands/vp-import-from-object", + "ViewPro/commands/vp-insert-columns", + "ViewPro/commands/vp-insert-rows", + "ViewPro/commands/vp-insert-table-columns", + "ViewPro/commands/vp-insert-table-rows" + ] + }, + { + "type": "category", + "label": "M", + "link": { + "type": "generated-index", + "title": "M", + "slug": "/commands-legacy/M" + }, + "items": [ + "ViewPro/commands/vp-move-cells" + ] + }, + { + "type": "category", + "label": "N", + "link": { + "type": "generated-index", + "title": "N", + "slug": "/commands-legacy/N" + }, + "items": [ + "ViewPro/commands/vp-name", + "ViewPro/commands/vp-new-document" + ] + }, + { + "type": "category", + "label": "O", + "link": { + "type": "generated-index", + "title": "O", + "slug": "/commands-legacy/O" + }, + "items": [ + "ViewPro/commands/vp-object-to-font" + ] + }, + { + "type": "category", + "label": "P", + "link": { + "type": "generated-index", + "title": "P", + "slug": "/commands-legacy/P" + }, + "items": [ + "ViewPro/commands/vp-paste-from-object", + "ViewPro/commands/vp-print" + ] + }, + { + "type": "category", + "label": "R", + "link": { + "type": "generated-index", + "title": "R", + "slug": "/commands-legacy/R" + }, + "items": [ + "ViewPro/commands/vp-recompute-formulas", + "ViewPro/commands/vp-remove-name", + "ViewPro/commands/vp-remove-sheet", + "ViewPro/commands/vp-remove-span", + "ViewPro/commands/vp-remove-stylesheet", + "ViewPro/commands/vp-remove-table", + "ViewPro/commands/vp-remove-table-columns", + "ViewPro/commands/vp-remove-table-rows", + "ViewPro/commands/vp-reset-selection", + "ViewPro/commands/vp-resize-table", + "ViewPro/commands/vp-resume-computing", + "ViewPro/commands/vp-row", + "ViewPro/commands/vp-row-autofit", + "ViewPro/commands/vp-run-offscreen-area" + ] + }, + { + "type": "category", + "label": "S", + "link": { + "type": "generated-index", + "title": "S", + "slug": "/commands-legacy/S" + }, + "items": [ + "ViewPro/commands/vp-set-active-cell", + "ViewPro/commands/vp-set-allowed-methods", + "ViewPro/commands/vp-set-binding-path", + "ViewPro/commands/vp-set-boolean-value", + "ViewPro/commands/vp-set-border", + "ViewPro/commands/vp-set-cell-style", + "ViewPro/commands/vp-set-column-attributes", + "ViewPro/commands/vp-set-column-count", + "ViewPro/commands/vp-set-current-sheet", + "ViewPro/commands/vp-set-custom-functions", + "ViewPro/commands/vp-set-data-context", + "ViewPro/commands/vp-set-date-time-value", + "ViewPro/commands/vp-set-date-value", + "ViewPro/commands/vp-set-default-style", + "ViewPro/commands/vp-set-field", + "ViewPro/commands/vp-set-formula", + "ViewPro/commands/vp-set-formulas", + "ViewPro/commands/vp-set-frozen-panes", + "ViewPro/commands/vp-set-num-value", + "ViewPro/commands/vp-set-print-info", + "ViewPro/commands/vp-set-row-attributes", + "ViewPro/commands/vp-set-row-count", + "ViewPro/commands/vp-set-selection", + "ViewPro/commands/vp-set-sheet-count", + "ViewPro/commands/vp-set-sheet-name", + "ViewPro/commands/vp-set-sheet-options", + "ViewPro/commands/vp-set-show-print-lines", + "ViewPro/commands/vp-set-table-column-attributes", + "ViewPro/commands/vp-set-table-theme", + "ViewPro/commands/vp-set-text-value", + "ViewPro/commands/vp-set-time-value", + "ViewPro/commands/vp-set-value", + "ViewPro/commands/vp-set-values", + "ViewPro/commands/vp-set-workbook-options", + "ViewPro/commands/vp-show-cell", + "ViewPro/commands/vp-suspend-computing" + ] + } ] - }, + } + ] + }, + { + "type": "category", + "label": "4D Write Pro", + "link": { + "type": "generated-index", + "title": "4D Write Pro", + "slug": "/category/4d-write-pro", + "keywords": [ + "4D Write Pro" + ], + "image": "/img/docusaurus.png" + }, + "items": [ + "WritePro/writeprointerface", + "WritePro/managing-formulas", + "WritePro/commands-legacy/4d-write-pro-attributes", { "type": "category", - "label": "Form Events", + "label": "Commands", "link": { "type": "doc", - "id": "Events/overview" + "id": "WritePro/commands/command-index" }, "items": [ - "Events/onActivate", - "Events/onAfterEdit", - "Events/onAfterKeystroke", - "Events/onAfterSort", - "Events/onAlternativeClick", - "Events/onBeforeDataEntry", - "Events/onBeforeKeystroke", - "Events/onBeginDragOver", - "Events/onBeginUrlLoading", - "Events/onBoundVariableChange", - "Events/onClicked", - "Events/onCloseBox", - "Events/onCloseDetail", - "Events/onCollapse", - "Events/onColumnMoved", - "Events/onColumnResize", - "Events/onDataChange", - "Events/onDeactivate", - "Events/onDeleteAction", - "Events/onDisplayDetail", - "Events/onDoubleClicked", - "Events/onDragOver", - "Events/onDrop", - "Events/onEndUrlLoading", - "Events/onExpand", - "Events/onFooterClick", - "Events/onGettingFocus", - "Events/onHeader", - "Events/onHeaderClick", - "Events/onLoad", - "Events/onLoadRecord", - "Events/onLongClick", - "Events/onLosingFocus", - "Events/onMenuSelected", - "Events/onMouseEnter", - "Events/onMouseLeave", - "Events/onMouseMove", - "Events/onMouseUp", - "Events/onOpenDetail", - "Events/onOpenExternalLink", - "Events/onOutsideCall", - "Events/onPageChange", - "Events/onPlugInArea", - "Events/onPrintingBreak", - "Events/onPrintingDetail", - "Events/onPrintingFooter", - "Events/onResize", - "Events/onRowMoved", - "Events/onRowResize", - "Events/onScroll", - "Events/onSelectionChange", - "Events/onTimer", - "Events/onUnload", - "Events/onUrlFiltering", - "Events/onUrlLoadingError", - "Events/onUrlResourceLoading", - "Events/onValidate", - "Events/onVpRangeChanged", - "Events/onVpReady", - "Events/onWindowOpeningDenied" + "WritePro/commands/wp-add-picture", + "WritePro/commands-legacy/wp-bookmark-range", + "WritePro/commands-legacy/wp-compute-formulas", + "WritePro/commands-legacy/wp-delete-bookmark", + "WritePro/commands-legacy/wp-delete-footer", + "WritePro/commands-legacy/wp-delete-header", + "WritePro/commands-legacy/wp-delete-picture", + "WritePro/commands/wp-delete-section", + "WritePro/commands-legacy/wp-delete-style-sheet", + "WritePro/commands/wp-delete-subsection", + "WritePro/commands-legacy/wp-delete-text-box", + "WritePro/commands/wp-export-document", + "WritePro/commands/wp-export-variable", + "WritePro/commands-legacy/wp-find-all", + "WritePro/commands-legacy/wp-find-next", + "WritePro/commands-legacy/wp-find-previous", + "WritePro/commands-legacy/wp-freeze-formulas", + "WritePro/commands/wp-get-attributes", + "WritePro/commands-legacy/wp-get-body", + "WritePro/commands-legacy/wp-get-bookmarks", + "WritePro/commands-legacy/wp-get-breaks", + "WritePro/commands-legacy/wp-get-data-context", + "WritePro/commands-legacy/wp-get-element-by-id", + "WritePro/commands-legacy/wp-get-elements", + "WritePro/commands-legacy/wp-get-footer", + "WritePro/commands-legacy/wp-get-formulas", + "WritePro/commands-legacy/wp-get-frame", + "WritePro/commands-legacy/wp-get-header", + "WritePro/commands-legacy/wp-get-links", + "WritePro/commands-legacy/wp-get-page-count", + "WritePro/commands-legacy/wp-get-position", + "WritePro/commands-legacy/wp-get-section", + "WritePro/commands-legacy/wp-get-sections", + "WritePro/commands-legacy/wp-get-style-sheet", + "WritePro/commands-legacy/wp-get-style-sheets", + "WritePro/commands-legacy/wp-get-subsection", + "WritePro/commands-legacy/wp-get-text", + "WritePro/commands-legacy/wp-get-view-properties", + "WritePro/commands/wp-import-document", + "WritePro/commands-legacy/wp-import-style-sheets", + "WritePro/commands/wp-insert-break", + "WritePro/commands/wp-insert-document-body", + "WritePro/commands/wp-insert-formula", + "WritePro/commands/wp-insert-picture", + "WritePro/commands-legacy/wp-insert-table", + "WritePro/commands-legacy/wp-is-font-style-supported", + "WritePro/commands-legacy/wp-new", + "WritePro/commands-legacy/wp-new-bookmark", + "WritePro/commands-legacy/wp-new-footer", + "WritePro/commands-legacy/wp-new-header", + "WritePro/commands-legacy/wp-new-style-sheet", + "WritePro/commands-legacy/wp-new-subsection", + "WritePro/commands-legacy/wp-new-text-box", + "WritePro/commands-legacy/wp-paragraph-range", + "WritePro/commands-legacy/wp-picture-range", + "WritePro/commands-legacy/wp-print", + "WritePro/commands/wp-reset-attributes", + "WritePro/commands-legacy/wp-select", + "WritePro/commands-legacy/wp-selection-range", + "WritePro/commands/wp-set-attributes", + "WritePro/commands-legacy/wp-set-data-context", + "WritePro/commands-legacy/wp-set-frame", + "WritePro/commands-legacy/wp-set-link", + "WritePro/commands-legacy/wp-set-text", + "WritePro/commands-legacy/wp-set-view-properties", + "WritePro/commands/wp-table-append-row", + "WritePro/commands-legacy/wp-table-delete-columns", + "WritePro/commands-legacy/wp-table-delete-rows", + "WritePro/commands-legacy/wp-table-get-cells", + "WritePro/commands-legacy/wp-table-get-columns", + "WritePro/commands-legacy/wp-table-get-rows", + "WritePro/commands-legacy/wp-table-insert-columns", + "WritePro/commands-legacy/wp-table-insert-rows", + "WritePro/commands-legacy/wp-table-merge-cells", + "WritePro/commands-legacy/wp-table-range", + "WritePro/commands-legacy/wp-table-split-cells", + "WritePro/commands-legacy/wp-text-range", + "WritePro/commands-legacy/wp-use-page-setup" ] } ] }, { "type": "category", - "label": "Menus", + "label": "4D AIKit", "link": { - "type": "doc", - "id": "Menus/overview" + "type": "generated-index", + "title": "4D AIKit", + "slug": "/category/4d-aikit", + "keywords": [ + "4D AIKit" + ], + "image": "/img/docusaurus.png" }, "items": [ - "Menus/creating", - "Menus/properties", - "Menus/bars", - "Menus/sdi" + "aikit/overview", + "aikit/asynchronous-call", + "aikit/compatible-openai", + { + "type": "category", + "label": "Classes", + "items": [ + "aikit/Classes/openai", + "aikit/Classes/openaiapiresource", + "aikit/Classes/openaichatapi", + "aikit/Classes/openaichatcompletionsapi", + "aikit/Classes/openaichatcompletionslistparameters", + "aikit/Classes/openaichatcompletionsmessagesapi", + "aikit/Classes/openaichatcompletionsmessagesparameters", + "aikit/Classes/openaichatcompletionsparameters", + "aikit/Classes/openaichatcompletionsresult", + "aikit/Classes/openaichatcompletionsstreamresult", + "aikit/Classes/openaichathelper", + "aikit/Classes/openaichoice", + "aikit/Classes/openaiembedding", + "aikit/Classes/openaiembeddingsapi", + "aikit/Classes/openaiembeddingsparameters", + "aikit/Classes/openaiembeddingsresult", + "aikit/Classes/openaierror", + "aikit/Classes/openaiimage", + "aikit/Classes/openaiimageparameters", + "aikit/Classes/openaiimagesapi", + "aikit/Classes/openaiimagesresult", + "aikit/Classes/openaimessage", + "aikit/Classes/openaimodel", + "aikit/Classes/openaimodellistresult", + "aikit/Classes/openaimodelresult", + "aikit/Classes/openaimodelsapi", + "aikit/Classes/openaimoderation", + "aikit/Classes/openaimoderationitem", + "aikit/Classes/openaimoderationresult", + "aikit/Classes/openaimoderationsapi", + "aikit/Classes/openaiparameters", + "aikit/Classes/openairesult", + "aikit/Classes/openaivision", + "aikit/Classes/openaivisionhelper" + ] + } ] }, { - "type": "doc", - "label": "User Settings", - "id": "Desktop/user-settings" + "type": "link", + "label": "4D Mobile App Server", + "href": "https://github.com/4d-go-mobile/4D-Mobile-App-Server" }, { - "type": "doc", - "label": "Build Application", - "id": "Desktop/building" + "type": "link", + "label": "4D NetKit", + "href": "https://developer.4d.com/4D-NetKit" }, { - "type": "doc", - "label": "Labels", - "id": "Desktop/labels" - } - ] - }, - { - "type": "category", - "label": "Mobile Applications", - "items": [ + "type": "link", + "label": "4D Progress", + "href": "https://doc.4d.com/4Dv20R10/4D/20-R10/4D-Progress.100-7614210.en.html" + }, { "type": "link", - "label": "Go Mobile", - "href": "https://developer.4d.com/go-mobile/" + "label": "4D SVG", + "href": "https://doc.4d.com/4Dv20R10/4D/20-R10/4D-SVG-Component.100-7614300.en.html" }, { "type": "link", - "label": "4D for iOS (archive)", - "href": "https://developer.4d.com/4d-for-ios" - } + "label": "4D Widgets", + "href": "https://doc.4d.com/4Dv20R10/4D/20-R10/4D-Widgets.100-7614949.en.html" + }, + { + "type": "link", + "label": "4D QPDF", + "href": "https://github.com/4d/4D-QPDF?tab=readme-ov-file#readme" + }, + { + "type": "link", + "label": "Go Mobile with 4D", + "href": "https://developer.4d.com/go-mobile/" + }, + { + "type": "link", + "label": "Build4D", + "href": "https://github.com/4d-depot/Build4D?tab=readme-ov-file#readme" + } ] } ]
-
- Go Mobile with 4D
+
+ 4D Server Window
+
+
+ WebAdmin & Data Explorer
+
+
+ Command Line Interface
+
+
+ TLS
-
- 4D Mobile App Server
+
+ Licenses
-
- 4D for iOS (Archive)
+
+ Log Files
+
+
+ Maintenance and Security Center
+
+
+ Backup and Restore
),
},
+ {
+ title: (
+ <>
+
+
+
+ Extending 4D applications
+
+
+ 4D Qodly Pro
+
+
+ 4D View Pro
+
+
+ 4D Write Pro
+
+
+ 4D NetKit
+
+
+ 4D AIKit
+
+
+ 4D Progress
+
+
+ 4D SVG
+
+
+ 4D Widgets
+
+
+ 4D QPDF
+
+
+ Go Mobile with 4D
+
+
+ Build4D
+
+
+ ),
+ },
+
];
export default Sections;
diff --git a/src/pages/index.js b/src/pages/index.js
index 7193c8a5fcbfb9..698818b8f69752 100644
--- a/src/pages/index.js
+++ b/src/pages/index.js
@@ -50,6 +50,7 @@ function Tile({
return (
+ {tile.image && tile.image.src && (
})
+ )}
diff --git a/src/pages/styles.module.css b/src/pages/styles.module.css
index d5ff4b94726ca1..f6efd6105ec8b8 100644
--- a/src/pages/styles.module.css
+++ b/src/pages/styles.module.css
@@ -6,6 +6,7 @@
.tilesHeading {
font-size: var(--ifm-h3-font-size);
+ font-weight: 400;
padding-top: 1rem;
}
@@ -19,7 +20,6 @@
}
.hero {
- background-color: #2b3137;
padding: 48px;
margin-bottom: 100px;
}
@@ -31,7 +31,6 @@
}
.heroProjectTagline {
- color: #fff;
font-size: 60px;
margin: 0;
}
diff --git a/versioned_docs/version-20-R10/API/SessionClass.md b/versioned_docs/version-20-R10/API/SessionClass.md
index 2240df5fe8f36f..526317eb2856e4 100644
--- a/versioned_docs/version-20-R10/API/SessionClass.md
+++ b/versioned_docs/version-20-R10/API/SessionClass.md
@@ -142,7 +142,7 @@ The `.createOTP()` function create
For more information about the OTP tokens, please refer to [this section](../WebServer/sessions.md#session-token-otp).
-By default, if the *lifespan* parameter is omitted, the token is created with the same lifespan as the [`.idleTimeOut`](#idletimeout) of the session. You can set a custom timeout by passing a value in seconds in *lifespan* (the minimum value is 10 seconds, *lifespan* is reset to 10 if a smaller value is passed). If an expired token is used to restore a web user session, it is ignored.
+By default, if the *lifespan* parameter is omitted, the token is created with the same lifespan as the [`.idleTimeOut`](#idletimeout) of the session. You can set a custom timeout by passing a value in seconds in *lifespan*. If an expired token is used to restore a web user session, it is ignored.
The returned token can then be used in exchanges with third-party applications or websites to securely identify the session. For example, the session OTP token can be used with a payment application.
diff --git a/versioned_docs/version-20-R10/Backup/log.md b/versioned_docs/version-20-R10/Backup/log.md
index 0eee46f46f4fa1..98ed9a47339927 100644
--- a/versioned_docs/version-20-R10/Backup/log.md
+++ b/versioned_docs/version-20-R10/Backup/log.md
@@ -71,7 +71,7 @@ You must create another log file if you create a new data file. You must set or
The [log file settings](settings.md#log-management) are based on two pieces of information: a boolean value and a path.
-1. **Boolean Value**: indicating whether the "Use Log File" feature is enabled or disabled within the application. By default, the boolean value is stored in *catalog.4DCatalog*. However, when the [user settings](../Desktop/user-settings.md) are activated, the *catalog.4DCatalog* file configuration is overriden, and the boolean value can then be set either in the *Backup.4DSettings* file [next to the data file](../Project/architecture.md#settings-user-data) or the *Backup.4DSettings* file [in the project folder](../Project/architecture.md#settings-user) (see also the `JournalFileEnabled` xml backup key documentation on [doc.4d.com](https://doc.4d.com)).
+1. **Boolean Value**: indicating whether the "Use Log File" feature is enabled or disabled within the application. By default, the boolean value is stored in *catalog.4DCatalog*. However, when the [user settings](../settings/overview.md#user-settings) are activated, the *catalog.4DCatalog* file configuration is overriden, and the boolean value can then be set either in the *Backup.4DSettings* file [next to the data file](../Project/architecture.md#settings-user-data) or the *Backup.4DSettings* file [in the project folder](../Project/architecture.md#settings-user) (see also the `JournalFileEnabled` xml backup key documentation on [doc.4d.com](https://doc.4d.com)).
2. **Path**: a string pointing to where the log file is located. The log file path is always stored in the linked data file.
diff --git a/versioned_docs/version-20-R10/Concepts/operators.md b/versioned_docs/version-20-R10/Concepts/operators.md
index db5792e85ccf6b..d15c09b5e9319c 100644
--- a/versioned_docs/version-20-R10/Concepts/operators.md
+++ b/versioned_docs/version-20-R10/Concepts/operators.md
@@ -95,7 +95,9 @@ The following compound assignment operators are supported:
||Time *= Number |Number |`$t1*=5 //$t1:=$t1*5`|
||Picture *= Number|Picture|`$p1*=5 //$p1:=$p1*5 (resize $p1 by 5)`|
-These operators apply on any [assignable expressions](quick-tour.md#assignable-vs-non-assignable-expressions) (except pictures as object properties or collection elements).
+These operators apply on any [assignable expressions](quick-tour.md#assignable-vs-non-assignable-expressions) except:
+- pictures as object properties or collection elements,
+- array index variables.
The operation "source `operator` value" is not strictly equivalent to "source := source `operator` value" because the expression designating the source (variable, field, object property, collection element) is only evaluated once. For example, in such expression as `getPointer()->+=1` the `getPointer` method is called only once.
diff --git a/versioned_docs/version-20-R10/Desktop/user-settings.md b/versioned_docs/version-20-R10/Desktop/user-settings.md
deleted file mode 100644
index 333e9ad838f77d..00000000000000
--- a/versioned_docs/version-20-R10/Desktop/user-settings.md
+++ /dev/null
@@ -1,130 +0,0 @@
----
-id: user-settings
-title: User Settings
----
-
-4D provides two modes of operation for project Settings:
-
-* **Standard** mode: all [settings](../settings/overview.md) are stored in the [*settings.4DSettings* file at the project level](../Project/architecture.md#sources) and are applied in all cases. This is the default mode, suitable for development phase (all applications).
-
-* **User settings** mode: part of the custom settings are stored in a *settings.4DSettings* file [in the Settings folder](../Project/architecture.md#settings-user) (for all data files) or [in the Data folder](../Project/architecture.md#settings-user-data) (for this data file) and are used instead of the structure settings. This mode is suitable for deployment phase for Desktop applications. You enable this mode using an option located on the [Security page](../settings/security.md) of the Settings.
-
-By defining user settings, you can keep custom settings between updates of your 4D applications, or manage different settings for the same 4D application deployed on several different sites. It also makes it possible to use programming to manage setting files using XML.
-
-4D can generate and use two types of user settings:
-
-- **User Settings**: They are used instead of structure settings for any data file opened with the application.
-- **User Settings for Data file**: They can be defined specifically for each data file used with your application, configuring for example the port ID or the server cache.
-
-With this option, you can easily deploy and update several copies of the same desktop application with several data files, each containing different settings.
-
-Consider for example the following configuration, where an application is duplicated and each copy uses a different Port ID setting. If this user setting is linked to the data file, you will be able to update the application without having to manually change the Port ID:
-
-
-
-## Enabling User settings
-
-To enable user settings, you need to check the **Settings** > **Security** > **Enable User Settings** option:
-
-
-
-When you check this option, the settings are separated into three dialog boxes:
-
-* **Structure Settings**
-* **User Settings**
-* **User Settings for Data file**
-
-You can access these dialog boxes using the **Design > Settings...** menu or the **Settings** button in the toolbar:
-
-
-
-You can also access these dialog boxes using the [OPEN SETTINGS WINDOW](../commands-legacy/open-settings-window.md) command with the appropriate *settingsType* selector.
-
-The Structure Settings dialog box is identical to the standard Settings, and provides access to all its properties (which can be overriden by user settings).
-
-## User Settings and User Settings for Data file
-
-The **User Settings** and **User Settings for Data File** dialog boxes contain a selection of relevant properties that can be defined for all data files or a single data file:
-
-
-
-The following table lists the pages of settings found in the **User Settings** and **User Settings for Data File** dialog boxes and describes their main differences with respect to standard settings:
-
-| **Page of Structure Settings** | **Page of User Settings** | **Page of User Settings for Data File**|
-| --- | --- | --- |
-| [General page](../settings/general.md) | N/a | N/a |
-| [Interface page](../settings/interface.md) | Identical to standard settings | Identical to standard settings |
-| [Compiler page](../settings/compiler.md) | N/a | N/a |
-| [Database/Data storage page](../settings/database.md#data-storage-page) | N/a | N/a |
-| [Database/Memory page](../settings/database.md#memory-page) | Identical to standard settings | Identical to standard settings |
-| [Backup/Scheduler page](../settings/../Backup/settings.md#scheduler) | N/a | Identical to standard settings |
-| [Backup/Configuration page](../settings/../Backup/settings.md#configuration) | N/a | Identical to standard settings |
-| [Backup/Backup & Restore page](../settings/../Backup/settings.md#backup--restore) | N/a | Identical to standard settings |
-| [Client-server/Network options page](../settings/client-server.md#network-options-page) | Identical to standard settings | Identical to standard settings |
-| [Client-server/IP configuration page](../settings/client-server.md#ip-configuration-page) | Identical to standard settings | Identical to standard settings |
-| [Web/Configuration page](../settings/web.md#configuration) | Identical to standard settings | Identical to standard settings |
-| [Web/Options (I) page](../settings/web.md#options-i) | Identical to standard settings | Identical to standard settings |
-| [Web/Options (II) page](../settings/web.md#options-ii) | Identical to standard settings | Identical to standard settings |
-| [Web/Log (type) page](../settings/web.md#log-type) | Identical to standard settings | Identical to standard settings |
-| [Web/Log (backup) page](../settings/web.md#log-backup) | Identical to standard settings | Identical to standard settings |
-| [Web/Web Services page](../settings/web.md#web-services) | Method prefixing option not available | Method prefixing option not available |
-| [SQL page](../settings/sql.md) | Identical to standard settings | Identical to standard settings |
-| [PHP page](../settings/php.md) | Identical to standard settings | Identical to standard settings |
-| [Security page](../settings/security.md) | N/a | N/a |
-| [Compatibility page](../settings/compatibility.md) | N/a | N/a |
-
-When you edit settings in this dialog box, they are automatically stored in the corresponding *settings.4DSettings* file (see below) or the *Backup.4DSettings* file (check the [Backup settings](../Backup/settings.md) page for more information).
-
-## `SET DATABASE PARAMETER` and user settings
-
-Some of the user settings are also available through the [SET DATABASE PARAMETER](../commands-legacy/set-database-parameter.md) command. User settings are parameters with the **Kept between two sessions** property set to **Yes**.
-
-When the **User Settings** feature is enabled, user settings edited by the [SET DATABASE PARAMETER](../commands-legacy/set-database-parameter.md) command are automatically saved in the user settings for the data file.
-
-> `Table sequence number` is an exception; this setting value is always saved in the data file itself.
-
-## settings.4DSettings files
-
-When you [check the **Enable User Settings** option](#enabling-user-settings), user settings files are automatically created. Their location depends on the type of user settings defined.
-
-### User Settings
-
-The standard user settings file is automatically created and placed in a settings folder at the following location:
-
-[`ProjectFolder/Settings/settings.4DSettings`](../Project/architecture.md#settings-user)
-
-... where *ProjectFolder* is the name of the folder containing the project structure file.
-
-In merged applications, the user settings file is placed at the following location:
-
-* In single-user versions: ProjectFolder/Database/Settings/settings.4DSettings
-* In client/server versions: ProjectFolder/Server Database/Settings/settings.4DSettings
-
-### User Settings for Data File
-
-The user settings file linked to the data file is automatically created and placed in a settings folder at the following location:
-
-[`Data/Settings/settings.4DSettings`](../Project/architecture.md#settings-user-data)
-
-... where *Data* is the name of the folder containing the current data file of the application.
-
-> When the data file is located at the same level as the project structure file, structure-based and data-based user settings files share the same location and file. The **User Settings for Data File...** menu command is not proposed.
-
-:::note
-
-Settings files are XML files; they can be read and modified using integrated 4D XML commands or using an XML editor. This means that you can manage settings by programming, particularly in the context of applications compiled and merged with 4D Volume Desktop. When you modify this file by programming, the changes are only taken into account the next time the database is opened.
-
-:::
-
-
-## Priority of settings
-
-Settings can be stored at three levels. Each setting defined at one level overrides the same setting defined at a previous level, if any:
-
-| **Priority level** | **Name** | **Location** | **Comments** |
-|---|---|---|---|
-| 3 (lowest) | Structure settings (or Settings when "User settings" feature not enabled) | ***settings.4DSettings*** file in the Sources folder (project databases) or in the Settings folder as the same level as the structure file (binary databases) | Unique location when user settings are not enabled. Applied to all copies of the application. |
-| 2 | User settings (all data files) | ***settings.4DSettings*** file in the Settings folder at the same level as the Project folder | Overrides Structure settings. Stored within the application package. |
-| 1 (highest) | User settings (current data file) | ***settings.4DSettings*** file in the Settings folder at the same level as the data file | Overrides Structure settings and User settings. Applied only when the linked data file is used with the application. |
-
-Keep in mind that user settings files only contain a subset of relevant settings, while the structure file contains all custom settings, including core settings.
diff --git a/versioned_docs/version-20-R10/Extensions/_overview-old.md b/versioned_docs/version-20-R10/Extensions/_overview-old.md
new file mode 100644
index 00000000000000..bb550385074f30
--- /dev/null
+++ b/versioned_docs/version-20-R10/Extensions/_overview-old.md
@@ -0,0 +1,41 @@
+---
+id: overview-old
+title: Extensions
+---
+
+The 4D [project architecture](../Project/architecture.md) is modular. You can provide additional functionalities to your 4D projects by installing [**components**](Concepts/components.md) and [**plug-ins**](../Concepts/plug-ins.md). Components are made of 4D code, while plug-ins can be built using any language.
+
+
+## Preinstalled 4D components
+
+4D includes by default a set of built-in 4D components, that you can see in the **Component Methods** theme of the Explorer's Methods page. All these components can also be found on the [4D github repository](https://github.com/4d).
+
+
+|Component|Description|Main Features|
+|---|---|---|
+|[4D AiIKit](https://github.com/4d/4D-AIKit)|Set of classes to connect to third-party OpenAI APIs|`OpenAIChat`, `OpenAIImage`...|
+|[4D Labels](https://github.com/4d/4D-Labels)|Internal component required to build label templates||
+|[4D NetKit](https://developer.4d.com/4D-NetKit)|Set of web service tools to connect to third-party APIs|`OAuth2Provider` class, `New OAuth2 provider`, `OAuth2ProviderObject.getToken()` |
+|[4D Progress](https://github.com/4d/4D-Progress)|Open one or more progress bars in the same window|`Progress New`, `Progress SET ON STOP METHOD`, `Progress SET PROGRESS`, ... |
+|[4D SVG](https://github.com/4d/4D-SVG)|Create and manipulate common svg graphic objects|`SVGTool_Display_viewer`, multiple `SVG_` methods |
+|[4D ViewPro](ViewPro/getting-started.md)|Spreadsheet features in your forms|See [4D View Pro documentation](ViewPro/getting-started.md)|
+|[4D Widgets](https://github.com/4d/4D-Widgets)|Manage DatePicker, TimePicker, SearchPicker 4D widgets|`DatePicker calendar`, `DateEntry area`, `TimeEntry`, `SearchPicker SET HELP TEXT`, ...|
+|[4D WritePro Interface](https://github.com/4d/4D-WritePro-Interface)|Manage [4D Write Pro palettes](https://doc.4d.com/4Dv20R9/4D/20-R9/Entry-areas.300-7543821.en.html and [table wizard](../WritePro/writeprointerface.md#table-wizard)|`WP PictureSettings`, `WP ShowTabPages`, `WP SwitchToolbar`, `WP UpdateWidget`|
+
+
+## Third-party components
+
+You can develop and install your own 4D components. See [this page](develop-components.md) for more information.
+
+Many developers from the 4D community have shared 4D components that you can install and use in you projects.
+
+Browse Github to have a list of public 4D components gathered with the [`4d-component`](https://github.com/topics/4d-component) topic.
+
+
+## Plugins
+
+Plugins do things that 4D does not natively (e.g., specific platform technology), or would be very hard to write just using 4D. As described in [this page](develop-plug-ins.md), you can develop your own plug-ins.
+
+A lot of functionnalities are covered by the existing 4D plug-ins. Browse Github to have a list of public 4D plugins gathered with the [`4d-plugin`](https://github.com/topics/4d-plugin) topic.
+
+
diff --git a/versioned_docs/version-20-R10/Extensions/overview.md b/versioned_docs/version-20-R10/Extensions/overview.md
index 2fabda08c1a413..447cbacdea85fa 100644
--- a/versioned_docs/version-20-R10/Extensions/overview.md
+++ b/versioned_docs/version-20-R10/Extensions/overview.md
@@ -1,41 +1,13 @@
---
id: overview
-title: Extensions
+title: Extending 4D Applications
---
-The 4D [project architecture](../Project/architecture.md) is modular. You can provide additional functionalities to your 4D projects by installing [**components**](Concepts/components.md) and [**plug-ins**](../Concepts/plug-ins.md). Components are made of 4D code, while plug-ins can be built using any language.
-
-
-## Preinstalled 4D components
-
-4D includes by default a set of built-in 4D components, that you can see in the **Component Methods** theme of the Explorer's Methods page. All these components can also be found on the [4D github repository](https://github.com/4d).
-
-
-|Component|Description|Main Features|
-|---|---|---|
-|[4D AiIKit](https://github.com/4d/4D-AIKit)|Set of classes to connect to third-party OpenAI APIs|`OpenAIChat`, `OpenAIImage`...|
-|[4D Labels](https://github.com/4d/4D-Labels)|Internal component required to build label templates||
-|[4D NetKit](https://developer.4d.com/4D-NetKit)|Set of web service tools to connect to third-party APIs|`OAuth2Provider` class, `New OAuth2 provider`, `OAuth2ProviderObject.getToken()` |
-|[4D Progress](https://github.com/4d/4D-Progress)|Open one or more progress bars in the same window|`Progress New`, `Progress SET ON STOP METHOD`, `Progress SET PROGRESS`, ... |
-|[4D SVG](https://github.com/4d/4D-SVG)|Create and manipulate common svg graphic objects|`SVGTool_Display_viewer`, multiple `SVG_` methods |
-|[4D ViewPro](ViewPro/getting-started.md)|Spreadsheet features in your forms|See [4D View Pro documentation](ViewPro/getting-started.md)|
-|[4D Widgets](https://github.com/4d/4D-Widgets)|Manage DatePicker, TimePicker, SearchPicker 4D widgets|`DatePicker calendar`, `DateEntry area`, `TimeEntry`, `SearchPicker SET HELP TEXT`, ...|
-|[4D WritePro Interface](https://github.com/4d/4D-WritePro-Interface)|Manage [4D Write Pro palettes](https://doc.4d.com/4Dv20R9/4D/20-R9/Entry-areas.300-7543821.en.html and [table wizard](../WritePro/writeprointerface.md#table-wizard)|`WP PictureSettings`, `WP ShowTabPages`, `WP SwitchToolbar`, `WP UpdateWidget`|
-
-
-## Third-party components
-
-You can develop and install your own 4D components. See [this page](develop-components.md) for more information.
-
-Many developers from the 4D community have shared 4D components that you can install and use in you projects.
-
-Browse Github to have a list of public 4D components gathered with the [`4d-component`](https://github.com/topics/4d-component) topic.
-
-
-## Plugins
-
-Plugins do things that 4D does not natively (e.g., specific platform technology), or would be very hard to write just using 4D. As described in [this page](develop-plug-ins.md), you can develop your own plug-ins.
-
-A lot of functionnalities are covered by the existing 4D plug-ins. Browse Github to have a list of public 4D plugins gathered with the [`4d-plugin`](https://github.com/topics/4d-plugin) topic.
-
+The 4D architecture is open and can be extended in different ways. If you need a feature that is not available natively in 4D, you can always integrate it into your application in a variety of ways, i.e.:
+- [**System workers**](../API/SystemWorkerClass.md) allow the 4D code to call any external process (a shell command, PHP, any script, etc.) and monitor its execution.
+- [**SQL commands**](../commands/theme/SQL) allow you to connect and use various SQL data sources.
+- The [**built-in HTTP client**](../API/HTTPRequestClass.md) can request any HTTP server and process data.
+- [**Web Areas**](../FormObjects/webArea_overview.md) can give access to web pages or various HTML contents within your forms.
+- [**Components**](Concepts/components.md). Components are made of 4D code. 4D includes by default [a set of built-in 4D components](../Project/components.md#preinstalled-4d-components). You can also [develop your own 4D components](develop-components.md), or use third-party components. Many developers from the 4D community have shared 4D components (browse Github to have a list of public 4D components gathered with the [`4d-component`](https://github.com/topics/4d-component) topic).
+- [**Plug-ins**](../Concepts/plug-ins.md). Plug-ins can be built using any language. Plugins do things that 4D does not natively (e.g., specific platform technology), or would be very hard to write just using 4D. As described in [this page](develop-plug-ins.md), you can develop your own plug-ins. A lot of functionnalities are covered by the existing 4D plug-ins. Browse Github to have a list of public 4D plugins gathered with the [`4d-plugin`](https://github.com/topics/4d-plugin) topic.
diff --git a/versioned_docs/version-20-R10/ORDA/overview.md b/versioned_docs/version-20-R10/ORDA/overview.md
index 1af5cc99717b77..7874ff5325a812 100644
--- a/versioned_docs/version-20-R10/ORDA/overview.md
+++ b/versioned_docs/version-20-R10/ORDA/overview.md
@@ -1,6 +1,6 @@
---
id: overview
-title: ORDA
+title: Overview
---
ORDA stands for **Object Relational Data Access**. It is an enhanced technology allowing to access both the model and the data of a database through objects.
diff --git a/versioned_docs/version-20-R10/ORDA/privileges.md b/versioned_docs/version-20-R10/ORDA/privileges.md
index 5ba37761607d18..97f4d0003bf9dd 100644
--- a/versioned_docs/version-20-R10/ORDA/privileges.md
+++ b/versioned_docs/version-20-R10/ORDA/privileges.md
@@ -1,6 +1,6 @@
---
id: privileges
-title: Privileges
+title: Roles and Privileges
---
diff --git a/versioned_docs/version-20-R10/Preferences/overview.md b/versioned_docs/version-20-R10/Preferences/overview.md
index f50f05b23cc511..731063a3bf4834 100644
--- a/versioned_docs/version-20-R10/Preferences/overview.md
+++ b/versioned_docs/version-20-R10/Preferences/overview.md
@@ -1,6 +1,6 @@
---
id: overview
-title: Preferences
+title: Application Preferences
---
User preferences specify various settings affecting your working environment, e.g. default options, display themes, Code Editor features, shortcuts, etc. They are applied to all projects opened with your 4D or 4D Server application.
diff --git a/versioned_docs/version-20-R10/Project/architecture.md b/versioned_docs/version-20-R10/Project/architecture.md
index 21ba62863c58e6..dd618d5cd5b887 100644
--- a/versioned_docs/version-20-R10/Project/architecture.md
+++ b/versioned_docs/version-20-R10/Project/architecture.md
@@ -1,6 +1,6 @@
---
id: architecture
-title: Architecture of a project
+title: Architecture
---
A 4D project is made of several folders and files, stored within a project root folder (package folder). For example:
@@ -60,7 +60,7 @@ catalog_editor.json|Custom positions and colors of tables, fields, and links in
folders.json|Explorer folder definitions|JSON
menus.json|Menu definitions|JSON
roles.json|[Privileges, permissions](../ORDA/privileges.md#rolesjson-file) and other security settings for the project|JSON
-settings.4DSettings|*Structure* database settings. They are not taken into account if *[user settings](#settings-user)* or *[user settings for data](#settings-user-data)* are defined (see also [Priority of settings](../Desktop/user-settings.md#priority-of-settings). **Warning**: In compiled applications, structure settings are stored in the .4dz file (read-only). For deployment needs, it is necessary to [enable](../Desktop/user-settings.md#enabling-user-settings) and use *user settings* or *user settings for data* to define custom settings.|XML
+settings.4DSettings|*Structure* database settings. They are not taken into account if *[user settings](#settings-user)* or *[user settings for data](#settings-user-data)* are defined (see also [Priority of settings](../settings/overview.md#user-settings#priority-of-settings). **Warning**: In compiled applications, structure settings are stored in the .4dz file (read-only). For deployment needs, it is necessary to [enable](../settings/overview.md#user-settings#enabling-user-settings) and use *user settings* or *user settings for data* to define custom settings.|XML
tips.json|Defined tips|JSON
lists.json|Defined lists|JSON
filters.json|Defined filters|JSON
@@ -170,9 +170,9 @@ data.match|(internal) UUID matching table number|XML
### `Settings` (user data)
-This folder contains [**user settings for data**](../Desktop/user-settings.md#user-settings-for-data-file) used for application administration.
+This folder contains [**user settings for data**](../settings/overview.md#user-settings#user-settings-for-data-file) used for application administration.
-> These settings take priority over [user settings](#settings-user) and [structure settings](#sources). See also [Priority of settings](../Desktop/user-settings.md#priority-of-settings).
+> These settings take priority over [user settings](#settings-user) and [structure settings](#sources). See also [Priority of settings](../settings/overview.md#user-settings#priority-of-settings).
|Contents|Description|Format|
|----|----|---|
@@ -195,9 +195,9 @@ The Logs folder contains all log files used by the project. Log files include, i
## `Settings` (user)
-This folder contains [**user settings**](../Desktop/user-settings.md#user-settings) used for application administration.
+This folder contains [**user settings**](../settings/overview.md#user-settings#user-settings) used for application administration.
-> These settings take priority over [structure settings](#sources) file. However, if [user settings for data](#settings-user-data) exist, they take priority over the user settings. See also [Priority of settings](../Desktop/user-settings.md#priority-of-settings).
+> These settings take priority over [structure settings](#sources) file. However, if [user settings for data](#settings-user-data) exist, they take priority over the user settings. See also [Priority of settings](../settings/overview.md#user-settings#priority-of-settings).
|Contents|Description|Format|
|----|----|---|
diff --git a/versioned_docs/version-20-R10/Project/code-overview.md b/versioned_docs/version-20-R10/Project/code-overview.md
index 3a9c3e2e99e2eb..2f410cdef574bb 100644
--- a/versioned_docs/version-20-R10/Project/code-overview.md
+++ b/versioned_docs/version-20-R10/Project/code-overview.md
@@ -1,6 +1,6 @@
---
id: code-overview
-title: Methods and classes
+title: Creating Methods and classes
---
@@ -37,150 +37,3 @@ To delete an existing method or class, you can:
> To delete an object method, choose **Clear Object Method** from the [Form editor](../FormEditor/formEditor.md) (**Object** menu or context menu).
-
-## Importing and exporting code
-
-You can import and export a method or a class code in the form of a file. These commands are found in the **Method** menu of the [Code editor](../code-editor/write-class-method.md).
-
-- When you select the **Export Method...** command, a standard file saving dialog box appears, allowing you to choose the name, location and format of the export file (see below). As with printing, exporting does not take the collapsed state of code structures into account and the entire code is exported.
-- When you select the **Import Method...** command, a standard file opening dialog box appears, allowing you to designate the file to be imported. Importing replaces the selected text in the method. To replace an existing method by an imported method, select the entire contents of the method before carrying out the import.
-
-The import/export function is multi-platform: a method exported under Mac OS can be imported under Windows and vice versa; 4D handles the conversion of characters when necessary.
-
-4D can export and import methods in two formats:
-
-- 4D method (extension *.c4d*): In this format, methods are exported in encoded form. The names of objects are tokenized. This format is used in particular for exchanging methods between 4D applications and plug-ins in different languages. Conversely, it is not possible to display them in a text editor.
-- Text (extension *.txt*): In this format, methods are exported in text-only form. In this case, the methods are readable using a standard text editor or a source control tool.
-
-
-## Project method properties
-
-After creating a project method, you can rename it and modify its properties. Project method properties mainly concern their access and security conditions (access by users, integrated servers or services) as well as their execution mode.
-
-The other types of methods do not have specific properties. Their properties are related to those of the objects to which they are attached.
-
-To display the **Method Properties** dialog box for a project method, you can either:
-
-- in the [Code Editor](../code-editor/write-class-method.md), select the **Method Properties...** command in the **Method** menu,
-- or on the **Methods** page of the Explorer, **right-click** on the project method and select **Method Properties...** in the context menu or options menu.
-
-
-> A batch setting function allows you to modify a property for all or part of the database project methods in a single operation (see [Batch setting for method attributes](#batch-setting-for-method-attributes)).
-
-### Name
-
-You can change the name of a project method in the **Name** area of the **Method Properties** window or in the Explorer.
-
-The new name must comply with 4D naming rules (see [Identifiers](../Concepts/identifiers.md)). If a method with the same name already exists, 4D displays a message saying that the method name has already been used. If necessary, 4D sorts the list of methods again.
-
-:::caution
-
-Changing the name of a method already used in the database can invalidate any methods or formulas that use the old method name and runs the risk of disrupting application functioning. You can rename the method manually but it is strongly recommended to use the renaming function for project methods, described in [Renaming](https://doc.4d.com/4Dv20/4D/20.2/Renaming.300-6750165.en.html). With this function, you can automatically update the name wherever the method is called throughout the Design environment.
-
-With 4D Server, the method name is changed on the server when you finish editing it. If more than one user is modifying the method name at the same time, the final method name will be the name specified by the last user to finish editing it. You may want to specify a method owner so that only certain users can change the method's name
-
-:::
-
-:::info
-
-Database methods cannot be renamed. The same goes for triggers, form methods, and object methods, which are bound to objects and take their names from the object concerned.
-
-:::
-
-### Attributes
-
-You can control how project methods are used and/or called in different contexts using attributes. Note that you can set attributes for an entire selection of project methods using the Explorer (see following section).
-
-#### Invisible
-
-If you do not want users to be able to run a project method using the **Method...** command of the **Run** menu, you can make it Invisible by checking this option. An invisible method does not appear in the method execution dialog box.
-
-When you make a project method invisible, it is still available to database programmers. It remains listed on the method list of the Explorer and of the Code Editor.
-
-#### Shared by components and host database
-
-This attribute is used within the framework of components. When it is checked, it indicates that the method will be available to components when the application is used as the host database. On the other hand, when the application is used as a component, the method will be available to the host databases.
-
-For more information about components, refer to the [Developing and installing 4D components](../Extensions/develop-components.md) chapter.
-
-#### Execute on Server
-
-This attribute is only taken into account for a 4D application in client-server mode. When this option is checked, the project method is always executed on the server, regardless of how it is called.
-
-For more information on this option, refer to [Execute on Server attribute](https://doc.4d.com/4Dv20/4D/20/Execute-on-Server-attribute.300-6330555.en.html).
-
-### Execution mode
-
-This option allows you to declare the method eligible for execution in preemptive mode. It is described in the [Preemptive processes section](../Develop/preemptive.md).
-
-### Available through
-
-Availability attributes specify the external services which are allowed to explicitly call the method.
-
-#### Web Services
-
-This attribute lets you publish the current method as a Web Service accessible via SOAP requests. For more information, refer to the [Publication and use of Web Services](https://doc.4d.com/4Dv20/4D/20.2/Publication-and-use-of-Web-Services.200-6750103.en.html) chapter. When this option is checked, the **Published in WSDL** option is enabled.
-
-In the Explorer, project methods that are offered as a Web Service are given a specific icon.
-
-**Note:** You cannot publish a method as a Web service if its name includes characters that do not comply with XML nomenclature (e.g. containing spaces). If the method name is not in keeping with this, 4D does not assign the property.
-
-#### Published in WSDL
-
-This attribute is only available when the "Web Service" attribute is checked. It lets you include the current method in the WSDL of the 4D application. For more information about this, refer to [Generation of the WSDL](https://doc.4d.com/4Dv20/4D/20.2/Publishing-a-Web-Service-with-4D.300-6750334.en.html#502689).
-
-In the Explorer, project methods that are offered as a Web Service and published in WSDL are given a specific icon.
-
-#### 4D tags and URLs (4DACTION...)
-
-This option is used to reinforce 4D Web server security: when it is not checked, the project method cannot be executed via an HTTP request containing the special [4DACTION URL](../WebServer/httpRequests.md#4daction) used for calling 4D methods, nor the special [4DSCRIPT, 4DTEXT and 4DHTML tags](../Tags/transformation-tags.md).
-
-In the Explorer, project methods with this attribute are given a specific icon.
-
-For security reasons, this option is unchecked by default. Each method that can be executed using the special Web URL or tags must be indicated individually.
-
-#### SQL
-
-When it is checked, this option allows the project method to be executed by the SQL engine of 4D. By default, it is not selected, which means that, unless explicitly authorized, 4D project methods are protected and cannot be called by the SQL engine of 4D.
-
-This property applies to all internal and external SQL queries --- executed via the ODBC driver, SQL code inserted between the [Begin SQL](../commands-legacy/begin-sql.md)/[End SQL](../commands-legacy/end-sql.md) tags or the [QUERY BY SQL](../commands-legacy/query-by-sql.md) command.
-
-**Notes:**
-
-- Even if a method has the "SQL" attribute, access rights set at the level of the database settings and method properties are taken into account for the execution of the method.
-- The ODBC **SQLProcedure** function only returns project methods with the "SQL" attribute.
-
-For more information, refer to [4D SQL engine implementation](https://doc.4d.com/4Dv20/4D/20/4D-SQL-engine-implementation.300-6342089.en.html) in the 4D SQL manual.
-
-#### REST Server
-
-*This option is deprecated. Calling code through REST calls is only supported with [ORDA data model class functions](../REST/ClassFunctions.md).*
-
-#### Batch setting for method attributes
-
-Using the "Attributes for methods" dialog box, you can modify an attribute (Invisible, Offered as a Web Service, etc.) for all or part of the database project methods in a single operation. This feature is especially useful for modifying the attributes of a large number of project methods. It can also be used during development to apply common attributes to groups of similar methods quickly.
-
-For batch setting of method attributes:
-
-1. On the [Methods Page](https://doc.4d.com/4Dv20/4D/20.2/Methods-Page.300-6750119.en.html) of the 4D Explorer, expand the options menu, then choose the **Batch setting of attributes...** command. The **Attributes for methods** dialog appears.
-
-2. In the "Matching method name:" area, enter a string that lets you designate the methods you want to modify as a batch.
-The character string is used as a search criterion for the method names.
-
-Use the wildcard character @ to help define groups of methods:
-
-- To designate methods whose names begin with..., type @ at the end of the string. For example: `web@`
-- To designate methods whose names contain..., type @ in the middle of the string. For example: `web@write`
-- To designate methods whose names end with..., type @ at the beginning of the string. For example: `@write`
-- To designate all of the methods, just type @ in the area.
-
-**Notes:**
-- The search does not take upper/lower case into account.
-- You can enter several @ characters in the string, for example `dtro_@web@pro.@`
-
-3. In the "Attribute to Modify" area, choose an attribute from the drop-down list, then click on the **True** or **False** radio button corresponding to the value to be applied.
-
-**Note:** If the "Published in WSDL" attribute is set to True, it will only be applied to project methods already containing the "Offered as a Web Service" attribute.
-
-4. Click on **Apply**. The modification is applied instantly to all the project methods designated by the character string entered.
-
diff --git a/versioned_docs/version-20-R10/Project/components.md b/versioned_docs/version-20-R10/Project/components.md
index 0401a2609f1f16..b149e7e1faf406 100644
--- a/versioned_docs/version-20-R10/Project/components.md
+++ b/versioned_docs/version-20-R10/Project/components.md
@@ -1,6 +1,6 @@
---
id: components
-title: Components
+title: Dependencies
---
A 4D component is a set of 4D code and/or 4D forms representing one or more functionalities that you can add and use in your projects. For example, the [4D SVG](https://github.com/4d/4D-SVG) component adds advanced commands and an integrated rendering engine that can be used to display SVG files.
@@ -32,6 +32,23 @@ The "Contents" folder architecture is recommended for components if you want to
:::
+## Components made by 4D
+
+
+4D includes a set of components developed in-house. They can also be found in the [4D github repository](https://github.com/4d).
+
+
+|Component|Description|Main Features|
+|---|---|---|
+|[4D AiIKit](https://github.com/4d/4D-AIKit)|Set of classes to connect to third-party OpenAI APIs|`OpenAIChat`, `OpenAIImage`...|
+|[4D Labels](https://github.com/4d/4D-Labels)|Internal component required to build label templates||
+|[4D NetKit](https://developer.4d.com/4D-NetKit)|Set of web service tools to connect to third-party APIs|`OAuth2Provider` class, `New OAuth2 provider`, `OAuth2ProviderObject.getToken()` |
+|[4D Progress](https://github.com/4d/4D-Progress)|Open one or more progress bars in the same window|`Progress New`, `Progress SET ON STOP METHOD`, `Progress SET PROGRESS`, ... |
+|[4D SVG](https://github.com/4d/4D-SVG)|Create and manipulate common svg graphic objects|`SVGTool_Display_viewer`, multiple `SVG_` methods |
+|[4D ViewPro](ViewPro/getting-started.md)|Spreadsheet features in your forms|See [4D View Pro documentation](ViewPro/getting-started.md)|
+|[4D Widgets](https://github.com/4d/4D-Widgets)|Manage DatePicker, TimePicker, SearchPicker 4D widgets|`DatePicker calendar`, `DateEntry area`, `TimeEntry`, `SearchPicker SET HELP TEXT`, ...|
+|[4D WritePro Interface](https://github.com/4d/4D-WritePro-Interface)|Manage [4D Write Pro palettes](https://doc.4d.com/4Dv20R9/4D/20-R9/Entry-areas.300-7543821.en.html) and [table wizard](../WritePro/writeprointerface.md#table-wizard)|`WP PictureSettings`, `WP ShowTabPages`, `WP SwitchToolbar`, `WP UpdateWidget`|
+
## Loading components
diff --git a/versioned_docs/version-20-R10/Project/documentation.md b/versioned_docs/version-20-R10/Project/documentation.md
index 878f0074adddb6..4e7c7830f5602c 100644
--- a/versioned_docs/version-20-R10/Project/documentation.md
+++ b/versioned_docs/version-20-R10/Project/documentation.md
@@ -1,6 +1,6 @@
---
id: documentation
-title: Documenting a project
+title: Documentation
---
diff --git a/versioned_docs/version-20-R10/Project/overview.md b/versioned_docs/version-20-R10/Project/overview.md
index 4f0db73fe8ce30..9770f98fb75c01 100644
--- a/versioned_docs/version-20-R10/Project/overview.md
+++ b/versioned_docs/version-20-R10/Project/overview.md
@@ -1,6 +1,6 @@
---
id: overview
-title: Overview
+title: 4D at a glance
---
A 4D project contains all of the source code of a 4D application, whatever its deployment type (web, mobile, or desktop), from the database structure to the user interface, including code, forms, menus, user settings, or any required resources. A 4D project is primarily made of text-based files.
@@ -24,10 +24,6 @@ Multi-user development is managed via standard **source control** repository too
## Final application
-Project files can be [compiled](compiler.md) and easily deployed. 4D allows you to create three types of applications from your projects:
-
-- [web](WebServer/webServer.md) applications,
-- [mobile](https://developer.4d.com/go-mobile/) applications,
-- [desktop](Desktop/building.md) applications (client/server or single-user).
+Project files can be [compiled](compiler.md) and easily deployed. 4D allows you to create several types of application from your projects, including [web](WebServer/webServer.md) applications, [desktop](Desktop/building.md) applications (client/server or single-user), or mobile applications.
Back end applications can be deployed using 4D Server, 4D, or [merged with 4D Volume Desktop](../Desktop/building.md).
\ No newline at end of file
diff --git a/versioned_docs/version-20-R10/Project/project-method-properties.md b/versioned_docs/version-20-R10/Project/project-method-properties.md
new file mode 100644
index 00000000000000..9ef8bcffb9516d
--- /dev/null
+++ b/versioned_docs/version-20-R10/Project/project-method-properties.md
@@ -0,0 +1,135 @@
+---
+id: project-method-properties
+title: Project Method Properties
+---
+
+
+After creating a project method, you can rename it and modify its properties. Project method properties mainly concern their access and security conditions (access by users, integrated servers or services) as well as their execution mode.
+
+The other types of methods do not have specific properties. Their properties are related to those of the objects to which they are attached.
+
+To display the **Method Properties** dialog box for a project method, you can either:
+
+- in the [Code Editor](../code-editor/write-class-method.md), select the **Method Properties...** command in the **Method** menu,
+- or on the **Methods** page of the Explorer, **right-click** on the project method and select **Method Properties...** in the context menu or options menu.
+
+
+> A batch setting function allows you to modify a property for all or part of the database project methods in a single operation (see [Batch setting for method attributes](#batch-setting-for-method-attributes)).
+
+## Name
+
+You can change the name of a project method in the **Name** area of the **Method Properties** window or in the Explorer.
+
+The new name must comply with 4D naming rules (see [Identifiers](../Concepts/identifiers.md)). If a method with the same name already exists, 4D displays a message saying that the method name has already been used. If necessary, 4D sorts the list of methods again.
+
+:::caution
+
+Changing the name of a method already used in the database can invalidate any methods or formulas that use the old method name and runs the risk of disrupting application functioning. You can rename the method manually but it is strongly recommended to use the renaming function for project methods, described in [Renaming](https://doc.4d.com/4Dv20/4D/20.2/Renaming.300-6750165.en.html). With this function, you can automatically update the name wherever the method is called throughout the Design environment.
+
+With 4D Server, the method name is changed on the server when you finish editing it. If more than one user is modifying the method name at the same time, the final method name will be the name specified by the last user to finish editing it. You may want to specify a method owner so that only certain users can change the method's name
+
+:::
+
+:::info
+
+Database methods cannot be renamed. The same goes for triggers, form methods, and object methods, which are bound to objects and take their names from the object concerned.
+
+:::
+
+## Attributes
+
+You can control how project methods are used and/or called in different contexts using attributes. Note that you can set attributes for an entire selection of project methods using the Explorer (see following section).
+
+### Invisible
+
+If you do not want users to be able to run a project method using the **Method...** command of the **Run** menu, you can make it Invisible by checking this option. An invisible method does not appear in the method execution dialog box.
+
+When you make a project method invisible, it is still available to database programmers. It remains listed on the method list of the Explorer and of the Code Editor.
+
+### Shared by components and host database
+
+This attribute is used within the framework of components. When it is checked, it indicates that the method will be available to components when the application is used as the host database. On the other hand, when the application is used as a component, the method will be available to the host databases.
+
+For more information about components, refer to the [Developing and installing 4D components](../Extensions/develop-components.md) chapter.
+
+### Execute on Server
+
+This attribute is only taken into account for a 4D application in client-server mode. When this option is checked, the project method is always executed on the server, regardless of how it is called.
+
+For more information on this option, refer to [Execute on Server attribute](https://doc.4d.com/4Dv20/4D/20/Execute-on-Server-attribute.300-6330555.en.html).
+
+## Execution mode
+
+This option allows you to declare the method eligible for execution in preemptive mode. It is described in the [Preemptive processes section](../Develop/preemptive.md).
+
+## Available through
+
+Availability attributes specify the external services which are allowed to explicitly call the method.
+
+### Web Services
+
+This attribute lets you publish the current method as a Web Service accessible via SOAP requests. For more information, refer to the [Publication and use of Web Services](https://doc.4d.com/4Dv20/4D/20.2/Publication-and-use-of-Web-Services.200-6750103.en.html) chapter. When this option is checked, the **Published in WSDL** option is enabled.
+
+In the Explorer, project methods that are offered as a Web Service are given a specific icon.
+
+**Note:** You cannot publish a method as a Web service if its name includes characters that do not comply with XML nomenclature (e.g. containing spaces). If the method name is not in keeping with this, 4D does not assign the property.
+
+### Published in WSDL
+
+This attribute is only available when the "Web Service" attribute is checked. It lets you include the current method in the WSDL of the 4D application. For more information about this, refer to [Generation of the WSDL](https://doc.4d.com/4Dv20/4D/20.2/Publishing-a-Web-Service-with-4D.300-6750334.en.html#502689).
+
+In the Explorer, project methods that are offered as a Web Service and published in WSDL are given a specific icon.
+
+### 4D tags and URLs (4DACTION...)
+
+This option is used to reinforce 4D Web server security: when it is not checked, the project method cannot be executed via an HTTP request containing the special [4DACTION URL](../WebServer/httpRequests.md#4daction) used for calling 4D methods, nor the special [4DSCRIPT, 4DTEXT and 4DHTML tags](../Tags/transformation-tags.md).
+
+In the Explorer, project methods with this attribute are given a specific icon.
+
+For security reasons, this option is unchecked by default. Each method that can be executed using the special Web URL or tags must be indicated individually.
+
+### SQL
+
+When it is checked, this option allows the project method to be executed by the SQL engine of 4D. By default, it is not selected, which means that, unless explicitly authorized, 4D project methods are protected and cannot be called by the SQL engine of 4D.
+
+This property applies to all internal and external SQL queries --- executed via the ODBC driver, SQL code inserted between the [Begin SQL](../commands-legacy/begin-sql.md)/[End SQL](../commands-legacy/end-sql.md) tags or the [QUERY BY SQL](../commands-legacy/query-by-sql.md) command.
+
+**Notes:**
+
+- Even if a method has the "SQL" attribute, access rights set at the level of the database settings and method properties are taken into account for the execution of the method.
+- The ODBC **SQLProcedure** function only returns project methods with the "SQL" attribute.
+
+For more information, refer to [4D SQL engine implementation](https://doc.4d.com/4Dv20/4D/20/4D-SQL-engine-implementation.300-6342089.en.html) in the 4D SQL manual.
+
+### REST Server
+
+*This option is deprecated. Calling code through REST calls is only supported with [ORDA data model class functions](../REST/ClassFunctions.md).*
+
+### Batch setting for method attributes
+
+Using the "Attributes for methods" dialog box, you can modify an attribute (Invisible, Offered as a Web Service, etc.) for all or part of the database project methods in a single operation. This feature is especially useful for modifying the attributes of a large number of project methods. It can also be used during development to apply common attributes to groups of similar methods quickly.
+
+For batch setting of method attributes:
+
+1. On the [Methods Page](https://doc.4d.com/4Dv20/4D/20.2/Methods-Page.300-6750119.en.html) of the 4D Explorer, expand the options menu, then choose the **Batch setting of attributes...** command. The **Attributes for methods** dialog appears.
+
+2. In the "Matching method name:" area, enter a string that lets you designate the methods you want to modify as a batch.
+The character string is used as a search criterion for the method names.
+
+Use the wildcard character @ to help define groups of methods:
+
+- To designate methods whose names begin with..., type @ at the end of the string. For example: `web@`
+- To designate methods whose names contain..., type @ in the middle of the string. For example: `web@write`
+- To designate methods whose names end with..., type @ at the beginning of the string. For example: `@write`
+- To designate all of the methods, just type @ in the area.
+
+**Notes:**
+- The search does not take upper/lower case into account.
+- You can enter several @ characters in the string, for example `dtro_@web@pro.@`
+
+3. In the "Attribute to Modify" area, choose an attribute from the drop-down list, then click on the **True** or **False** radio button corresponding to the value to be applied.
+
+**Note:** If the "Published in WSDL" attribute is set to True, it will only be applied to project methods already containing the "Offered as a Web Service" attribute.
+
+4. Click on **Apply**. The modification is applied instantly to all the project methods designated by the character string entered.
+
diff --git a/versioned_docs/version-20-R10/Users/overview.md b/versioned_docs/version-20-R10/Users/overview.md
index 5ab43252d88ab9..5b605736ba4df6 100644
--- a/versioned_docs/version-20-R10/Users/overview.md
+++ b/versioned_docs/version-20-R10/Users/overview.md
@@ -7,19 +7,21 @@ If more than one person uses an application, which is usually the case in client
4D access control strategy depends on your deployment configuration:
-- in multi-user applications, you can rely on 4D users and groups,
+- in multi-user Web and REST applications, access control is based upon [ORDA's Roles and privileges](../ORDA/privileges.md) features.
+- in multi-user desktop applications, you can rely on 4D users and groups,
- in single-user applications, user access is controlled through the system session, using commands such as [`Current system user`](../commands-legacy/current-system-user.md).
-> For an overview of 4D's security features, see the [4D Security guide](https://blog.4d.com/4d-security-guide/).
+:::tip Related Blog post
+For an overview of 4D's security features, see the [4D Security guide](https://blog.4d.com/4d-security-guide/).
+:::
-## Access control in multi-user applications
-Multi-user applications are deployed with 4D Server. They include client-server, Web, or REST applications.
+## Access control in multi-user applications
-In multi-user applications, access control is done through [4D users and groups](handling_users_groups.md). You create users, assign passwords, create access groups that have different levels of privileges in the application.
+Multi-user desktop applications are deployed with 4D Server. In multi-user applications, access control is done through [4D users and groups](handling_users_groups.md). You create users, assign passwords, create access groups that have different levels of privileges in the application.
You initiate the 4D password access control system with 4D Server by [assigning a password to the Designer user](handling_users_groups.md#designer-and-administrator). Until you give the Designer a password, all application access are done with the Designer's access rights, even if you have [set up users and groups](handling_users_groups.md) (when the application opens, no ID is required). Any part of the application can be opened.
@@ -28,6 +30,7 @@ When a password is assigned to the Designer, all the access privileges take effe
To disable the password access system, you just need to remove the Designer password.
+
## Access control in single-user applications
diff --git a/versioned_docs/version-20-R10/WebServer/gettingStarted.md b/versioned_docs/version-20-R10/WebServer/gettingStarted.md
index 70944f2fa5678e..cafea2e0afef2a 100644
--- a/versioned_docs/version-20-R10/WebServer/gettingStarted.md
+++ b/versioned_docs/version-20-R10/WebServer/gettingStarted.md
@@ -1,6 +1,6 @@
---
id: gettingStarted
-title: Web Development
+title: Getting started
---
This "Getting started" section is geared at first-time users who want an overall overview on how to go from zero to a 4D website that handles data from the database. Let's start!
diff --git a/versioned_docs/version-20-R10/WebServer/webServerObject.md b/versioned_docs/version-20-R10/WebServer/webServerObject.md
index 5b6fb9ca138964..74063641d6ffd2 100644
--- a/versioned_docs/version-20-R10/WebServer/webServerObject.md
+++ b/versioned_docs/version-20-R10/WebServer/webServerObject.md
@@ -1,10 +1,10 @@
---
id: webServerObject
-title: Web Server object
+title: Web Server instances
---
-A 4D project can start and monitor a web server for the main (host) application as well as each hosted component.
+A 4D project can start and monitor a web server for the main (host) application as well as each [hosted component](../Concepts/components.md).
For example, if you installed two components in your main application, you can start and monitor up to three independant web servers from your application:
diff --git a/versioned_docs/version-20-R10/code-editor/write-class-method.md b/versioned_docs/version-20-R10/code-editor/write-class-method.md
index 7782fb1c578ef1..5fe71f11ca8b6d 100644
--- a/versioned_docs/version-20-R10/code-editor/write-class-method.md
+++ b/versioned_docs/version-20-R10/code-editor/write-class-method.md
@@ -892,3 +892,17 @@ Strict syntax rules must be observed in order for macros files to respect the XM
- Comments of the "// my comment" type, allowed inside `
+ )}
{tile.title}
{tile.links}
| -|[](../../commands-legacy/on-backup-startup-database-method.md)
| -|[](../../commands-legacy/on-drop-database-method.md)
| -|[](../../commands-legacy/on-exit-database-method.md)
| -|[](../../commands-legacy/on-host-database-event-database-method.md)
| -|[](../../commands-legacy/on-mobile-app-action-database-method.md)
| -|[](../../commands-legacy/on-mobile-app-authentication-database-method.md)
| -|[](../../commands-legacy/on-rest-authentication-database-method.md)
| -|[](../../commands-legacy/on-server-close-connection-database-method.md)
| -|[](../../commands-legacy/on-server-open-connection-database-method.md)
| -|[](../../commands-legacy/on-server-shutdown-database-method.md)
| -|[](../../commands-legacy/on-server-startup-database-method.md)
| -|[](../../commands-legacy/on-sql-authentication-database-method.md)
| -|[](../../commands-legacy/on-startup-database-method.md)
| -|[](../../commands-legacy/on-system-event-database-method.md)
| -|[](../../commands-legacy/on-web-authentication-database-method.md)
| -|[](../../commands-legacy/on-web-connection-database-method.md)
| -|[](../../commands-legacy/on-web-legacy-close-session-database-method.md)
| diff --git a/versioned_docs/version-20-R10/settings/overview.md b/versioned_docs/version-20-R10/settings/overview.md index 0d52cdbde7c0dc..ede138092298e2 100644 --- a/versioned_docs/version-20-R10/settings/overview.md +++ b/versioned_docs/version-20-R10/settings/overview.md @@ -7,8 +7,12 @@ The Settings configure how the current project functions. These parameters may b  -> 4D provides another set of parameters, called **Preferences**, that apply to the 4D IDE application. For more information, refer to [Preferences](../Preferences/general.md). +:::info + +4D provides another set of parameters, called **Preferences**, that apply to the 4D IDE application. For more information, refer to [Preferences](../Preferences/general.md). + +::: ## Accessing the settings @@ -18,7 +22,7 @@ You can access the Settings dialog box: - by clicking **Settings** on the 4D toolbar - on 4D Server, using the **Edit > Settings...** menu option -When [**User settings** mode is enabled](../Desktop/user-settings.md), **Settings...** is renamed **Structure Settings...** and two additional menu commands are available at each location: +When [**User settings** mode is enabled](#user-settings), **Settings...** is renamed **Structure Settings...** and two additional menu commands are available at each location: - **User Settings...** gives you access to settings that can be stored externally in a user file. If these are modified, they are used instead of structure settings. - **User Settings for Data File...** gives you access to settings that can be stored externally in a user file attached to the current data file. If they are modified, they are used instead of user or structure settings. @@ -47,8 +51,137 @@ A parameter still appears in bold even when its value is replaced manually with Most of the settings are applied immediately. However, a few of them (such as the Startup environment setting) only take effect when the database is restarted. In this case, a dialog box appears to inform you that the change will take effect at the next startup. -## Resetting the settings +### Resetting the settings To reset the parameters to their default values and remove the bold style indicating that they have been customized, click **Reset to factory settings**. This button resets all the parameters of the current page. It becomes active when at least one parameter has been modified on the current page. + + +## User Settings + +4D provides two modes of operation for project Settings: + +* **Standard** mode: all settings are stored in the [*settings.4DSettings* file at the project level](../Project/architecture.md#sources) and are applied in all cases. This is the default mode, suitable for development phase (all applications). + +* **User settings** mode: part of the custom settings are stored in a *settings.4DSettings* file [in the Settings folder](../Project/architecture.md#settings-user) (for all data files) or [in the Data folder](../Project/architecture.md#settings-user-data) (for this data file) and are used instead of the structure settings. This mode is suitable for deployment phase for Desktop applications. You enable this mode using an option located on the [Security page](./security.md) of the Settings. + +By defining user settings, you can keep custom settings between updates of your 4D applications, or manage different settings for the same 4D application deployed on several different sites. It also makes it possible to use programming to manage setting files using XML. + +4D can generate and use two types of user settings: + +- **User Settings**: They are used instead of structure settings for any data file opened with the application. +- **User Settings for Data file**: They can be defined specifically for each data file used with your application, configuring for example the port ID or the server cache. + +With this option, you can easily deploy and update several copies of the same desktop application with several data files, each containing different settings. + +Consider for example the following configuration, where an application is duplicated and each copy uses a different Port ID setting. If this user setting is linked to the data file, you will be able to update the application without having to manually change the Port ID: + + + +### Enabling User settings + +To enable user settings, you need to check the **Settings** > **Security** > **Enable User Settings** option: + + + +When you check this option, the settings are separated into three dialog boxes: + +* **Structure Settings** +* **User Settings** +* **User Settings for Data file** + +You can access these dialog boxes using the **Design > Settings...** menu or the **Settings** button in the toolbar: + + + +You can also access these dialog boxes using the [OPEN SETTINGS WINDOW](../commands-legacy/open-settings-window.md) command with the appropriate *settingsType* selector. + +The Structure Settings dialog box is identical to the standard Settings, and provides access to all its properties (which can be overriden by user settings). + +### User Settings and User Settings for Data file + +The **User Settings** and **User Settings for Data File** dialog boxes contain a selection of relevant properties that can be defined for all data files or a single data file: + + + +The following table lists the pages of settings found in the **User Settings** and **User Settings for Data File** dialog boxes and describes their main differences with respect to standard settings: + +| **Page of Structure Settings** | **Page of User Settings** | **Page of User Settings for Data File**| +| --- | --- | --- | +| [General page](./general.md) | N/a | N/a | +| [Interface page](./interface.md) | Identical to standard settings | Identical to standard settings | +| [Compiler page](./compiler.md) | N/a | N/a | +| [Database/Data storage page](./database.md#data-storage-page) | N/a | N/a | +| [Database/Memory page](./database.md#memory-page) | Identical to standard settings | Identical to standard settings | +| [Backup/Scheduler page](./../Backup/settings.md#scheduler) | N/a | Identical to standard settings | +| [Backup/Configuration page](./../Backup/settings.md#configuration) | N/a | Identical to standard settings | +| [Backup/Backup & Restore page](./../Backup/settings.md#backup--restore) | N/a | Identical to standard settings | +| [Client-server/Network options page](./client-server.md#network-options-page) | Identical to standard settings | Identical to standard settings | +| [Client-server/IP configuration page](./client-server.md#ip-configuration-page) | Identical to standard settings | Identical to standard settings | +| [Web/Configuration page](./web.md#configuration) | Identical to standard settings | Identical to standard settings | +| [Web/Options (I) page](./web.md#options-i) | Identical to standard settings | Identical to standard settings | +| [Web/Options (II) page](./web.md#options-ii) | Identical to standard settings | Identical to standard settings | +| [Web/Log (type) page](./web.md#log-type) | Identical to standard settings | Identical to standard settings | +| [Web/Log (backup) page](./web.md#log-backup) | Identical to standard settings | Identical to standard settings | +| [Web/Web Services page](./web.md#web-services) | Method prefixing option not available | Method prefixing option not available | +| [SQL page](./sql.md) | Identical to standard settings | Identical to standard settings | +| [PHP page](./php.md) | Identical to standard settings | Identical to standard settings | +| [Security page](./security.md) | N/a | N/a | +| [Compatibility page](./compatibility.md) | N/a | N/a | + +When you edit settings in this dialog box, they are automatically stored in the corresponding *settings.4DSettings* file (see below) or the *Backup.4DSettings* file (check the [Backup settings](../Backup/settings.md) page for more information). + +### `SET DATABASE PARAMETER` and user settings + +Some of the user settings are also available through the [SET DATABASE PARAMETER](../commands-legacy/set-database-parameter.md) command. User settings are parameters with the **Kept between two sessions** property set to **Yes**. + +When the **User Settings** feature is enabled, user settings edited by the [SET DATABASE PARAMETER](../commands-legacy/set-database-parameter.md) command are automatically saved in the user settings for the data file. + +> `Table sequence number` is an exception; this setting value is always saved in the data file itself. + +### settings.4DSettings files + +When you [check the **Enable User Settings** option](#enabling-user-settings), user settings files are automatically created. Their location depends on the type of user settings defined. + +#### User Settings + +The standard user settings file is automatically created and placed in a settings folder at the following location: + +[`ProjectFolder/Settings/settings.4DSettings`](../Project/architecture.md#settings-user) + +... where *ProjectFolder* is the name of the folder containing the project structure file. + +In merged applications, the user settings file is placed at the following location: + +* In single-user versions: ProjectFolder/Database/Settings/settings.4DSettings +* In client/server versions: ProjectFolder/Server Database/Settings/settings.4DSettings + +#### User Settings for Data File + +The user settings file linked to the data file is automatically created and placed in a settings folder at the following location: + +[`Data/Settings/settings.4DSettings`](../Project/architecture.md#settings-user-data) + +... where *Data* is the name of the folder containing the current data file of the application. + +> When the data file is located at the same level as the project structure file, structure-based and data-based user settings files share the same location and file. The **User Settings for Data File...** menu command is not proposed. + +:::note + +Settings files are XML files; they can be read and modified using integrated 4D XML commands or using an XML editor. This means that you can manage settings by programming, particularly in the context of applications compiled and merged with 4D Volume Desktop. When you modify this file by programming, the changes are only taken into account the next time the database is opened. + +::: + + +### Priority of settings + +Settings can be stored at three levels. Each setting defined at one level overrides the same setting defined at a previous level, if any: + +| **Priority level** | **Name** | **Location** | **Comments** | +|---|---|---|---| +| 3 (lowest) | Structure settings (or Settings when "User settings" feature not enabled) | ***settings.4DSettings*** file in the Sources folder (project databases) or in the Settings folder as the same level as the structure file (binary databases) | Unique location when user settings are not enabled. Applied to all copies of the application. | +| 2 | User settings (all data files) | ***settings.4DSettings*** file in the Settings folder at the same level as the Project folder | Overrides Structure settings. Stored within the application package. | +| 1 (highest) | User settings (current data file) | ***settings.4DSettings*** file in the Settings folder at the same level as the data file | Overrides Structure settings and User settings. Applied only when the linked data file is used with the application. | + +Keep in mind that user settings files only contain a subset of relevant settings, while the structure file contains all custom settings, including core settings. diff --git a/versioned_docs/version-20-R10/settings/security.md b/versioned_docs/version-20-R10/settings/security.md index 2b7ffd9cfbf12b..572de63c511aa2 100644 --- a/versioned_docs/version-20-R10/settings/security.md +++ b/versioned_docs/version-20-R10/settings/security.md @@ -40,7 +40,7 @@ This page contains options related to data access and protection for your deskto - **Disabled for all**: This option disables control within formulas. When this option is checked, users have access to all the 4D commands and plug-ins as well as all project methods (except for invisible ones). **Note:** This option takes priority over the [`SET ALLOWED METHODS`](../commands/set-allowed-methods.md) command. When it is checked, this command does nothing. -- **Enable User Settings**: You need to check this option to be able to display separated dialog boxes for user settings. When this option is checked, up to three dialog boxes are available: **Structure Settings**, **User Settings**, and **User Settings for Data File**. For more information, refer to [User settings](../Desktop/user-settings.md). +- **Enable User Settings**: You need to check this option to be able to display separated dialog boxes for user settings. When this option is checked, up to three dialog boxes are available: **Structure Settings**, **User Settings**, and **User Settings for Data File**. For more information, refer to [User settings](../settings/overview.md#user-settings). - **Execute "On Host Database Event" method of the components**: The [On Host Database Event database method](../commands-legacy/on-host-database-event-database-method.md) facilitates the initialization and backup phases for 4D components. For security reasons, you must explicitly authorize the execution of this method in each host database. To do this, you must check this option. By default, it is not checked. diff --git a/versioned_docs/version-20-R9/API/SessionClass.md b/versioned_docs/version-20-R9/API/SessionClass.md index 0b4aee999a4efb..00c88a1190f68d 100644 --- a/versioned_docs/version-20-R9/API/SessionClass.md +++ b/versioned_docs/version-20-R9/API/SessionClass.md @@ -140,7 +140,7 @@ The `.createOTP()` function create For more information about the OTP tokens, please refer to [this section](../WebServer/sessions.md#session-token-otp). -By default, if the *lifespan* parameter is omitted, the token is created with the same lifespan as the [`.idleTimeOut`](#idletimeout) of the session. You can set a custom timeout by passing a value in seconds in *lifespan* (the minimum value is 10 seconds, *lifespan* is reset to 10 if a smaller value is passed). If an expired token is used to restore a web user session, it is ignored. +By default, if the *lifespan* parameter is omitted, the token is created with the same lifespan as the [`.idleTimeOut`](#idletimeout) of the session. You can set a custom timeout by passing a value in seconds in *lifespan*. If an expired token is used to restore a web user session, it is ignored. The returned token can then be used in exchanges with third-party applications or websites to securely identify the session. For example, the session OTP token can be used with a payment application. diff --git a/versioned_docs/version-20-R9/Concepts/operators.md b/versioned_docs/version-20-R9/Concepts/operators.md index db5792e85ccf6b..d15c09b5e9319c 100644 --- a/versioned_docs/version-20-R9/Concepts/operators.md +++ b/versioned_docs/version-20-R9/Concepts/operators.md @@ -95,7 +95,9 @@ The following compound assignment operators are supported: ||Time *= Number |Number |`$t1*=5 //$t1:=$t1*5`| ||Picture *= Number|Picture|`$p1*=5 //$p1:=$p1*5 (resize $p1 by 5)`| -These operators apply on any [assignable expressions](quick-tour.md#assignable-vs-non-assignable-expressions) (except pictures as object properties or collection elements). +These operators apply on any [assignable expressions](quick-tour.md#assignable-vs-non-assignable-expressions) except: +- pictures as object properties or collection elements, +- array index variables. The operation "source `operator` value" is not strictly equivalent to "source := source `operator` value" because the expression designating the source (variable, field, object property, collection element) is only evaluated once. For example, in such expression as `getPointer()->+=1` the `getPointer` method is called only once. diff --git a/versioned_docs/version-20-R9/Extensions/overview.md b/versioned_docs/version-20-R9/Extensions/overview.md index 2fabda08c1a413..399a8481196858 100644 --- a/versioned_docs/version-20-R9/Extensions/overview.md +++ b/versioned_docs/version-20-R9/Extensions/overview.md @@ -13,7 +13,7 @@ The 4D [project architecture](../Project/architecture.md) is modular. You can pr |Component|Description|Main Features| |---|---|---| -|[4D AiIKit](https://github.com/4d/4D-AIKit)|Set of classes to connect to third-party OpenAI APIs|`OpenAIChat`, `OpenAIImage`...| +|[4D AIKit](https://github.com/4d/4D-AIKit)|Set of classes to connect to third-party OpenAI APIs|`OpenAIChat`, `OpenAIImage`...| |[4D Labels](https://github.com/4d/4D-Labels)|Internal component required to build label templates|| |[4D NetKit](https://developer.4d.com/4D-NetKit)|Set of web service tools to connect to third-party APIs|`OAuth2Provider` class, `New OAuth2 provider`, `OAuth2ProviderObject.getToken()` | |[4D Progress](https://github.com/4d/4D-Progress)|Open one or more progress bars in the same window|`Progress New`, `Progress SET ON STOP METHOD`, `Progress SET PROGRESS`, ... | diff --git a/versioned_docs/version-20-R9/commands-legacy/create-deployment-license.md b/versioned_docs/version-20-R9/commands-legacy/create-deployment-license.md index bbfa678fc58459..696c13b48bcb0d 100644 --- a/versioned_docs/version-20-R9/commands-legacy/create-deployment-license.md +++ b/versioned_docs/version-20-R9/commands-legacy/create-deployment-license.md @@ -45,17 +45,17 @@ The command returns a *status* object containing the following properties: ## Example ```4d - var $status : Object - var $application : 4D.File - var $license : 4D.File - $license:=Folder(fk licenses folder).file("4UUD200-xxx.license4D") - $application:=Folder(fk desktop folder).folder("myApp.app") - $status:=Create deployment license($application;$license) + var $status : Object + var $application : 4D.File + var $license : 4D.File + $license:=Folder(fk licenses folder).file("4UUD200-xxx.license4D") + $application:=Folder(fk desktop folder).folder("myApp.app") + $status:=Create deployment license($application;$license) ``` ## See also -[Blog post - Finalize an application with 4D commands](https://blog.4d.com/finalize-an-application-with-4d-commands) +[Blog post - Build an application with 4D commands](https://blog.4d.com/build-an-application-with-4d-commands) ## Properties diff --git a/versioned_docs/version-20/Concepts/operators.md b/versioned_docs/version-20/Concepts/operators.md index ec2c69ca40b83c..52e162bb7acb9b 100644 --- a/versioned_docs/version-20/Concepts/operators.md +++ b/versioned_docs/version-20/Concepts/operators.md @@ -93,7 +93,9 @@ The following compound assignment operators are supported: ||Time *= Number |Number |`$t1*=5 //$t1:=$t1*5`| ||Picture *= Number|Picture|`$p1*=5 //$p1:=$p1*5 (resize $p1 by 5)`| -These operators apply on any [assignable expressions](quick-tour.md#assignable-vs-non-assignable-expressions) (except pictures as object properties or collection elements). +These operators apply on any [assignable expressions](quick-tour.md#assignable-vs-non-assignable-expressions) except: +- pictures as object properties or collection elements, +- array index variables. The operation "source `operator` value" is not strictly equivalent to "source := source `operator` value" because the expression designating the source (variable, field, object property, collection element) is only evaluated once. For example, in such expression as `getPointer()->+=1` the `getPointer` method is called only once. diff --git a/versioned_docs/version-20/settings/web.md b/versioned_docs/version-20/settings/web.md index 2c8245afa2126e..847ac4ae728695 100644 --- a/versioned_docs/version-20/settings/web.md +++ b/versioned_docs/version-20/settings/web.md @@ -5,41 +5,37 @@ title: Web page Using the tabs on the **Web** page, you can configure various aspects of the integrated Web server of 4D (security, startup, connections, Web services, etc.). For more information about how the 4D Web server works, see [Web server](../WebServer/webServer.md). For more information about 4D Web services, refer to the [Publication and use of Web Services](https://doc.4d.com/4Dv19/4D/19/Publication-and-use-of-Web-Services.200-5416624.en.html) chapter. -## Configuration +## Configuration ### Publishing Information -#### Launch Web Server at Startup +#### Launch Web Server at Startup Indicates whether the Web server will be launched on startup of the 4D application. This option is described in the [Web server administration](../WebServer/webServerAdmin.md#starting-the-4d-web-server) section. -#### Enable HTTP +#### Enable HTTP Indicates whether or not the Web server will accept non-secure connections. See [Enable HTTP](../WebServer/webServerConfig.md#enable-http). - -#### HTTP Port +#### HTTP Port Listening IP (TCP) port number for HTTP. See [HTTP Port](../WebServer/webServerConfig.md#http-port). -#### IP Address +#### IP Address IP address on which the 4D web server will receive HTTP requests (4D local and 4D Server). See [IP Address to listen](../WebServer/webServerConfig.md#ip-address-to-listen). - -#### Enable HTTPS +#### Enable HTTPS Indicates whether or not the Web server will accept secure connections. See [Enable HTTPS](../WebServer/webServerConfig.md#enable-https). - -#### HTTPS Port +#### HTTPS Port Allows you to modify the TCP/IP port number used by the Web server for secured HTTP connections over TLS (HTTPS protocol). See [HTTPS Port](../WebServer/webServerConfig.md#https-port). #### Allow database access through 4DSYNC URLs -*Compatibility Note*: This option is [deprecated](../WebServer/webServerConfig.md#deprecated-settings). For database access through HTTP, it is now recommended to use ORDA remote datastore features and REST requests. - +_Compatibility Note_: This option is [deprecated](../WebServer/webServerConfig.md#deprecated-settings). For database access through HTTP, it is now recommended to use ORDA remote datastore features and REST requests. ### Paths @@ -51,13 +47,9 @@ Define the default location of the Web site files and to indicate the hierarchic Designate a default home page for the Web server. See [Default Home page](../WebServer/webServerConfig.md#default-home-page). - - - ## Options (I) -### Cache - +### Cache #### Use the 4D Web cache @@ -67,38 +59,36 @@ Enables the web page cache. See [Cache](../WebServer/webServerConfig.md#cache). Sets the cache size. See [Cache](../WebServer/webServerConfig.md#cache). - -#### Clear Cache +#### Clear Cache At any moment, you can clear the cache of the pages and images that it contains (if, for example, you have modified a static page and you want to reload it in the cache). To do so, you just have to click on the **Clear Cache** button. The cache is then immediately cleared. > You can also use the special URL [/4DCACHECLEAR](../WebServer/webServerAdmin.md#4dcacheclear). -### Web Process +### Web Process -This area allows you to configure how the web server will handle user sessions and their associated processes. +This area allows you to configure how the web server will handle user sessions and their associated processes. > The **Legacy sessions** option is only available for compatibility in databases/projects created with 4D versions prior to 4D v18 R6. -#### Scalable sessions (multi-process sessions) - -When you select this option (recommended), a user session is managed through a **Session** object. See the [User sessions page](../WebServer/sessions.md#enabling-sessions). +#### Scalable sessions (multi-process sessions) +When you select this option (recommended), a user session is managed through a **Session** object. See the [User sessions page](../WebServer/sessions.md#enabling-sessions). -#### No sessions +#### No sessions -When this option is selected, the web server does not provide any specific support for [user sessions](../WebServer/sessions.md). Successive requests from web clients are always independent and no context is maintained on the server. +When this option is selected, the web server does not provide any specific support for [user sessions](../WebServer/sessions.md). Successive requests from web clients are always independent and no context is maintained on the server. In this mode, you can configure additional web server setttings: -- [Maximum Concurrent Web Processes](#maximum-concurrent-web-processes) -- [Reuse Temporary Contexts (4D in remote mode)](#reuse-temporary-contexts) -- [Use preemptive processes](#use-preemptive-processes) +- [Maximum Concurrent Web Processes](#maximum-concurrent-web-processes) +- [Reuse Temporary Contexts (4D in remote mode)](#reuse-temporary-contexts) +- [Use preemptive processes](#use-preemptive-processes) #### Legacy sessions (single process sessions) -*Compatibility Note:* This option is only available in databases/projects created with a 4D version prior to 4D v18 R6. +_Compatibility Note:_ This option is only available in databases/projects created with a 4D version prior to 4D v18 R6. This option enables the handling of legacy user sessions by the 4D HTTP server. This mechanism is described in the [Web Sessions Management (Legacy)](https://doc.4d.com/4Dv19/4D/19/Web-Sessions-Management-Legacy.300-5391806.en.html) section. See [Keep Session](../WebServer/webServerConfig.md#keep-session). @@ -110,31 +100,27 @@ Not available with [scalable sessions](../WebServer/sessions.md). Strictly high limit of concurrent web processes. See [Maximum Concurrent Web Processes](../WebServer/webServerConfig.md#maximum-concurrent-web-processes). - #### Reuse Temporary Contexts Not available with [scalable sessions](../WebServer/sessions.md). Allows you to optimize the operation of the 4D Web server in remote mode. See [Reuse temporary contexts in remote mode)](../WebServer/webServerConfig.md#reuse-temporary-contexts-in-remote-mode). -#### Use preemptive processes +#### Use preemptive processes -Not available with [scalable sessions](../WebServer/sessions.md). +Not available with [scalable sessions](../WebServer/sessions.md). Enables preemptive web processes in your compiled applications. When **Use preemptive processes** is selected, the eligibility of your web-related code (including 4D tags and web database methods) to the preemptive execution will be evaluated during the compilation. For more information, see [Using preemptive Web processes](../WebServer/preemptiveWeb.md). -> This option does not apply to scalable sessions, REST processes (compiled mode), and web service processes (server or client). See [Enabling the preemptive mode for the web server](../WebServer/webServerConfig.md#use-preemptive-processes). - +> This option does not apply to scalable sessions, REST processes (compiled mode), and web service processes (server or client). See [Enabling the preemptive mode for the web server](../WebServer/webServerConfig.md#use-preemptive-processes). -#### Inactive Process Timeout +#### Inactive Process Timeout -Not available with [scalable sessions](../WebServer/sessions.md). +Not available with [scalable sessions](../WebServer/sessions.md). Allows you to set the maximum timeout before closing for inactive Web processes on the server. See [Inactive Process Timeout](../WebServer/webServerConfig.md#inactive-process-timeout). - - -### Web Passwords +### Web Passwords Set the authentication system that you want to apply to your Web server. Three options are proposed: @@ -142,12 +128,11 @@ Custom (default) Passwords with BASIC protocol Passwords with DIGEST protocol -Using **Custom** authentication is recommended. See [**Authentication**](../WebServer/authentication.md) chapter in the *Web Development* documentation. - +Using **Custom** authentication is recommended. See [**Authentication**](../WebServer/authentication.md) chapter in the _Web Development_ documentation. ## Options (II) -### Text Conversion +### Text Conversion #### Send Extended Characters Directly @@ -157,7 +142,7 @@ See [Deprecated Settings](../WebServer/webServerConfig.md#deprecated-settings). Define the set of characters to be used by the 4D Web server. See [Character Set](../WebServer/webServerConfig.md#character-set). -### Keep-Alive Connections +### Keep-Alive Connections See [Deprecated Settings](../WebServer/webServerConfig.md#keep-alive-connections). @@ -171,36 +156,31 @@ Enables Cross-origin resource sharing (CORS) service. See [Enable CORS Service]( List of allowed hosts and methods for the CORS service. See [CORS Settings](../WebServer/webServerConfig.md#cors-settings). - - ## Log (type) +### Log Format -### Log Format - -Starts or stops the recording of requests received by the 4D web server in the *logweb.txt* file and sets its format. See [Log Recording](../WebServer/webServerConfig.md#log-recording). +Starts or stops the recording of requests received by the 4D web server in the _logweb.txt_ file and sets its format. See [Log Recording](../WebServer/webServerConfig.md#log-recording). > The activation and deactivation of the log file of requests can also be carried out by programming using the [WEB SET OPTION](https://doc.4d.com/4dv19R/help/command/en/page1210.html) command. - The log format menu provides the following options: -- **No Log File**: When this option is selected, 4D will not generate a log file of requests. - -- **CLF (Common Log Format)**: When this option is selected, the log of requests is generated in CLF format. With the CLF format, each line of the file represents a request, such as:\ - host rfc931 user [DD/MMM/YYYY:HH:MM:SS] "request" state length\ - Each field is separated by a space and each line ends by the CR/LF sequence (character 13, character 10). +- **No Log File**: When this option is selected, 4D will not generate a log file of requests. - - host: IP address of the client (ex. 192.100.100.10) - - rfc931: information not generated by 4D, it's always - (a minus sign) - - user: user name as it is authenticated, or else it is - (a minus sign). If the user name contains spaces, they will be replaced by _ (an underscore). - - DD: day, MMM: a 3-letter abbreviation for the month name (Jan, Feb,...), YYYY: year, HH: hour, MM: minutes, SS: seconds +- **CLF (Common Log Format)**: When this option is selected, the log of requests is generated in CLF format. With the CLF format, each line of the file represents a request, such as:\ + host rfc931 user [DD/MMM/YYYY:HH:MM:SS] "request" state length\ + Each field is separated by a space and each line ends by the CR/LF sequence (character 13, character 10). + - host: IP address of the client (ex. 192.100.100.10) + - rfc931: information not generated by 4D, it's always - (a minus sign) + - user: user name as it is authenticated, or else it is - (a minus sign). If the user name contains spaces, they will be replaced by \_ (an underscore). + - DD: day, MMM: a 3-letter abbreviation for the month name (Jan, Feb,...), YYYY: year, HH: hour, MM: minutes, SS: seconds > The date and time are local to the server. -- request: request sent by the client (ex. GET /index.htm HTTP/1.0) -- state: reply given by the server. -- length: size of the data returned (except the HTTP header) or 0. +- request: request sent by the client (ex. GET /index.htm HTTP/1.0) +- state: reply given by the server. +- length: size of the data returned (except the HTTP header) or 0. > **Note:** For performance reasons, the operations are saved in a memory buffer in packets of 1Kb before being written to disk. The operations are also written to disk if no request has been sent every 5 seconds. > The possible values of state are as follows: @@ -214,16 +194,15 @@ The log format menu provides the following options: > 500: Internal error > The CLF format cannot be customized. -- **DLF (Combined Log Format)**: When this option is selected, the request log is generated in DLF format. DLF format is similar to CLF format and uses exactly the same structure. It simply adds two additional HTTP fields at the end of each request: Referer and User-agent. - - - Referer: Contains the URL of the page pointing to the requested document. - - User-agent: Contains the name and version of the browser or software of the client at the origin of the request. +- **DLF (Combined Log Format)**: When this option is selected, the request log is generated in DLF format. DLF format is similar to CLF format and uses exactly the same structure. It simply adds two additional HTTP fields at the end of each request: Referer and User-agent. + - Referer: Contains the URL of the page pointing to the requested document. + - User-agent: Contains the name and version of the browser or software of the client at the origin of the request. > The DLF format cannot be customized. -- **ELF (Extended Log Format)**: When this option is selected, the request log is generated in ELF format. The ELF format is very widespread in the world of HTTP browsers. It can be used to build sophisticated logs that meet specific needs. For this reason, the ELF format can be customized: it is possible to choose the fields to be recorded as well as their order of insertion into the file. +- **ELF (Extended Log Format)**: When this option is selected, the request log is generated in ELF format. The ELF format is very widespread in the world of HTTP browsers. It can be used to build sophisticated logs that meet specific needs. For this reason, the ELF format can be customized: it is possible to choose the fields to be recorded as well as their order of insertion into the file. -- **WLF (WebStar Log Format)**: When this option is selected, the request log is generated in WLF format. WLF format was developed specifically for the 4D WebSTAR server. It is similar to the ELF format, with only a few additional fields. Like the ELF format, it can be customized. +- **WLF (WebStar Log Format)**: When this option is selected, the request log is generated in WLF format. WLF format was developed specifically for the 4D WebSTAR server. It is similar to the ELF format, with only a few additional fields. Like the ELF format, it can be customized. **Configuring the fields** When you choose the ELF (Extended Log Format) or WLF (WebStar Log Format) format, the "Weg Log Token Selection" area displays the fields available for the chosen format. You will need to select each field to be included in the log. To do so, use the arrow buttons or simply drag and drop the desired fields into the "Selected Tokens" area. @@ -232,30 +211,30 @@ When you choose the ELF (Extended Log Format) or WLF (WebStar Log Format) format The following table lists the fields available for each format (in alphabetical order) and describes its contents: -| Field | ELF | WLF | Value | -| --- | --- | --- | --- | -| BYTES_RECEIVED | | X | Number of bytes received by the server | -| BYTES_SENT | X | X | Number of bytes sent by the server to the client | -| C_DNS | X | X | IP address of the DNS (ELF: field identical to the C_IP field) | -| C_IP | X | X | IP address of the client (for example 192.100.100.10) | -| CONNECTION_ID | | X | Connection ID number | -| CS(COOKIE) | X | X | Information about cookies contained in the HTTP request | -| CS(HOST) | X | X | Host field of the HTTP request | -| CS(REFERER) | X | X | URL of the page pointing to the requested document | -| CS(USER_AGENT) | X | X | Information about the software and operating system of the client | -| CS_SIP | X | X | IP address of the server | -| CS_URI | X | X | URI on which the request is made | -| CS_URI_QUERY | X | X | Request query parameters | -| CS_URI_STEM | X | X | Part of request without query parameters | -| DATE | X | X | DD: day, MMM: 3-letter abbreviation for month (Jan, Feb, etc.), YYYY: year | -| METHOD | X | X | HTTP method used for the request sent to the server | -| PATH_ARGS | | X | CGI parameters: string located after the "$" character | -| STATUS | X | X | Reply provided by the server | -| TIME | X | X | HH: hour, MM: minutes, SS: seconds | -| TRANSFER_TIME | X | X | Time requested by server to generate the reply | -| USER | X | X | User name if authenticated; otherwise - (minus sign). | -| | | | If the user name contains spaces, they are replaced by _ (underlines) | -| URL | | X | URL requested by the client | +| Field | ELF | WLF | Value | +| -------------- | --- | --- | -------------------------------------------------------------------------- | +| BYTES_RECEIVED | | X | Number of bytes received by the server | +| BYTES_SENT | X | X | Number of bytes sent by the server to the client | +| C_DNS | X | X | IP address of the DNS (ELF: field identical to the C_IP field) | +| C_IP | X | X | IP address of the client (for example 192.100.100.10) | +| CONNECTION_ID | | X | Connection ID number | +| CS(COOKIE) | X | X | Information about cookies contained in the HTTP request | +| CS(HOST) | X | X | Host field of the HTTP request | +| CS(REFERER) | X | X | URL of the page pointing to the requested document | +| CS(USER_AGENT) | X | X | Information about the software and operating system of the client | +| CS_SIP | X | X | IP address of the server | +| CS_URI | X | X | URI on which the request is made | +| CS_URI_QUERY | X | X | Request query parameters | +| CS_URI_STEM | X | X | Part of request without query parameters | +| DATE | X | X | DD: day, MMM: 3-letter abbreviation for month (Jan, Feb, etc.), YYYY: year | +| METHOD | X | X | HTTP method used for the request sent to the server | +| PATH_ARGS | | X | CGI parameters: string located after the "$" character | +| STATUS | X | X | Reply provided by the server | +| TIME | X | X | HH: hour, MM: minutes, SS: seconds | +| TRANSFER_TIME | X | X | Time requested by server to generate the reply | +| USER | X | X | User name if authenticated; otherwise - (minus sign). | +| | | | If the user name contains spaces, they are replaced by \_ (underlines) | +| URL | | X | URL requested by the client | > Dates and times are given in GMT. @@ -263,51 +242,50 @@ The following table lists the fields available for each format (in alphabetical Configure the automatic backup parameters for the request log. First you must choose the frequency (days, weeks, etc.) or the file size limit criterion by clicking on the corresponding radio button. You must then specify the precise moment of the backup if necessary. -- **No Backup**: The scheduled backup function is deactivated. -- **Every X hour(s)**: This option is used to program backups on an hourly basis. You can enter a value between 1 and 24 . +- **No Backup**: The scheduled backup function is deactivated. +- **Every X hour(s)**: This option is used to program backups on an hourly basis. You can enter a value between 1 and 24 . + - **starting at**: Used to set the time at which the first back up will begin. - - **starting at**: Used to set the time at which the first back up will begin. -- **Every X day(s) at X**: This option is used to program backups on a daily basis. Enter 1 if you want to perform a daily backup. When this option is checked, you must indicate the time when the backup must be started. -- **Every X week(s), day at X**: This option is used to program backups on a weekly basis. Enter 1 if you want to perform a weekly backup. When this option is checked, you must indicate the day(s) of the week and the time when each backup must be started. You can select several days of the week if desired. For example, you can use this option to set two weekly backups: one on Wednesdays and one on Fridays. -- **Every X month(s), Xth day at X**: This option is used to program backups on a monthly basis. Enter 1 if you want to perform a monthly backup. When this option is checked, you must indicate the day of the month and the time when the backup must be started. -- **Every X MB**: This option is used to program backups based on the size of the current request log file. A backup is automatically triggered when the file reaches the set size. You can set a size limit of 1, 10, 100 or 1000 MB. +- **Every X day(s) at X**: This option is used to program backups on a daily basis. Enter 1 if you want to perform a daily backup. When this option is checked, you must indicate the time when the backup must be started. +- **Every X week(s), day at X**: This option is used to program backups on a weekly basis. Enter 1 if you want to perform a weekly backup. When this option is checked, you must indicate the day(s) of the week and the time when each backup must be started. You can select several days of the week if desired. For example, you can use this option to set two weekly backups: one on Wednesdays and one on Fridays. +- **Every X month(s), Xth day at X**: This option is used to program backups on a monthly basis. Enter 1 if you want to perform a monthly backup. When this option is checked, you must indicate the day of the month and the time when the backup must be started. +- **Every X MB**: This option is used to program backups based on the size of the current request log file. A backup is automatically triggered when the file reaches the set size. You can set a size limit of 1, 10, 100 or 1000 MB. > In the case of scheduled backups, if the Web server was not launched when the backup was scheduled to occur, on the next startup 4D considers the backup as failed and applies the appropriate settings, set via the Database Settings. -## Web Services +## Web Services You use the options on this tab to activate and configure Web services for the 4D project, both for their publishing (server side) and their subscription (client side). For more information about the support of Web Services in 4D, refer to the [Publication and use of Web Services](https://doc.4d.com/What-s-new/4D-Design-Reference-19-R4/Publication-and-use-of-Web-Services.200-5736722.en.html) chapter. -### Server Side +### Server Side + +This area contains various options related to the use of 4D as a Web Services "server" i.e., publishing project methods in the form of Web Services. -This area contains various options related to the use of 4D as a Web Services "server" i.e., publishing project methods in the form of Web Services. +- **Allow Web Services Requests**: This option lets you initialize the publication of Web Services. If this option has not been checked, 4D refuses SOAP requests and does not generate a WSDL - even if methods have the _Published in WSDL_ attribute. When this option is checked, 4D creates the WSDL file. +- **Web Service Name**: This area lets you change the "generic name" of the Web Service. This name is used to differentiate the services both at the SOAP server level (when the server publishes several different Web Services), as well as in the Web Services directories. By default, 4D uses the name A_WebService. +- **Web Services Namespace**: This area is used to change the namespace of the Web Services published by 4D. Each Web Service published on the Internet must be unique. The uniqueness of the names of Web Services is ensured by using XML namespaces. A namespace is an arbitrary character string used to identify a set of XML tags in a unique way. Typically, the namespace begins with the URL of the company (http://mycompany.com/mynamespace). In this case, it is not indispensable to have anything in particular at the URL indicated; what matters is that the character string used is unique. By default, 4D uses the following namespace: http://www.4d.com/namespace/default. -- **Allow Web Services Requests**: This option lets you initialize the publication of Web Services. If this option has not been checked, 4D refuses SOAP requests and does not generate a WSDL - even if methods have the *Published in WSDL* attribute. When this option is checked, 4D creates the WSDL file. -- **Web Service Name**: This area lets you change the "generic name" of the Web Service. This name is used to differentiate the services both at the SOAP server level (when the server publishes several different Web Services), as well as in the Web Services directories. By default, 4D uses the name A_WebService. -- **Web Services Namespace**: This area is used to change the namespace of the Web Services published by 4D. Each Web Service published on the Internet must be unique. The uniqueness of the names of Web Services is ensured by using XML namespaces. A namespace is an arbitrary character string used to identify a set of XML tags in a unique way. Typically, the namespace begins with the URL of the company (http://mycompany.com/mynamespace). In this case, it is not indispensable to have anything in particular at the URL indicated; what matters is that the character string used is unique. By default, 4D uses the following namespace: http://www.4d.com/namespace/default. - > In conformity with the XML standard for tag names, the character strings used must not contain spaces nor start with a number. Moreover, to avoid any risk of incompatibility, we recommend that you do not use any extended characters (such as accented characters). -### Client Side +### Client Side This area contains various options related to the use of 4D as a Web Services "client" i.e., subscribing to services published on the network. -- **Wizard Method Prefix**: This area lets you change the prefix that is added automatically by 4D to the name of proxy methods generated by the Web Services Wizard. Proxy project methods form a link between the 4D application and the Web Services server. By default, 4D uses the prefix "proxy_". - +- **Wizard Method Prefix**: This area lets you change the prefix that is added automatically by 4D to the name of proxy methods generated by the Web Services Wizard. Proxy project methods form a link between the 4D application and the Web Services server. By default, 4D uses the prefix "proxy\_". ## Web Features This page contains the options used to enable and control advanced Web features such as the REST server. -### Publishing +### Publishing #### Expose as REST server Starts and stops the REST Server. See [REST Server Configuration](../REST/configuration.md). -### Access +### Access This option specifies a group of 4D users that is authorized to establish the link to the 4D database using REST requests. See [Configuring REST access](../REST/configuration.md#configuring-rest-access). @@ -315,4 +293,4 @@ This option specifies a group of 4D users that is authorized to establish the li #### Enable access to the web studio -Enables general access to the web studio. You still need to configure it at every project level. \ No newline at end of file +Enables general access to the web studio. You still need to configure it at every project level. diff --git a/versioned_sidebars/version-20-R10-sidebars.json b/versioned_sidebars/version-20-R10-sidebars.json index 7080eec733b24a..077df31748cd41 100644 --- a/versioned_sidebars/version-20-R10-sidebars.json +++ b/versioned_sidebars/version-20-R10-sidebars.json @@ -1,5 +1,5 @@ -{ - "docs": [ + { + "docs": [ { "type": "category", "label": "Getting Started", @@ -14,40 +14,52 @@ }, "items": [ "GettingStarted/installation", - "GettingStarted/creating", + "Project/overview", "Notes/updates" ] }, { "type": "category", - "label": "Core Development", + "label": "Project & IDE", "link": { "type": "generated-index", - "title": "Core Development", - "slug": "/category/core-development", + "title": "Project & IDE", + "slug": "/category/project-ide", "keywords": [ - "core" + "ide" ], "image": "/img/docusaurus.png" }, "items": [ - { + "GettingStarted/creating", + "Project/architecture", + { + "type": "category", + "label": "Dababase structure", + "items": [ + "Develop/field-properties" + ] + }, + { + "type": "category", + "label": "Code & Methods", + "items": [ + "Project/code-overview", + "code-editor/write-class-method", + "Project/project-method-properties", + "Project/documentation" + ] + }, + "Project/components", + "Project/compiler", + { "type": "category", - "label": "Project Management", + "label": "Settings", "link": { - "type": "doc", - "id": "Project/overview" - }, - "items": [ - "Project/architecture", - { - "type": "category", - "label": "Settings", - "link": { "type": "doc", "id": "settings/overview" - }, - "items": [ + }, + "items": [ "settings/general", "settings/interface", "settings/compiler", @@ -60,87 +72,37 @@ "settings/security", "settings/compatibility" ] - }, - "Project/components", - "Project/date-time-formats", - "Project/documentation", - { - "type": "category", - "label": "Dababase structure", - "items": [ - "Develop/field-properties" - ] - } - ] }, - { - "type": "category", - "label": "Development Environment", - "items": [ - "Project/code-overview", - "code-editor/write-class-method", - "Project/compiler", - { - "type": "category", - "label": "Debugging", - "link": { + "Desktop/building", + { + "type": "category", + "label": "Debugging", + "link": { "type": "doc", "id": "Debugging/basics" }, - "items": [ + "items": [ "Debugging/debugger", "Debugging/breakpoints", "Debugging/debugging-remote" ] - }, - "Debugging/debugLogFiles", - { - "type": "category", - "label": "Preferences", - "link": { - "type": "doc", - "id": "Preferences/overview" - }, - "items": [ - "Preferences/general", - "Preferences/structure", - "Preferences/forms", - "Preferences/methods", - "Preferences/shortcuts" - ] - } - ] - }, - { - "type": "category", - "label": "ORDA", - "link": { - "type": "doc", - "id": "ORDA/overview" }, - "items": [ - "ORDA/dsmapping", - "ORDA/ordaClasses", - "ORDA/orda-events", - "ORDA/entities", - "ORDA/global-stamp", - "ORDA/datastores", - "ORDA/privileges", - "ORDA/client-server-optimization", - "ORDA/glossary" - ] - }, - { - "type": "category", - "label": "Processes", - "items": [ - "Develop/processes", - "Develop/preemptive-processes" - ] - }, - "Develop-legacy/transactions", - "Tags/transformation-tags" - ] + { + "type": "category", + "label": "Application Preferences", + "link": { + "type": "doc", + "id": "Preferences/overview" + }, + "items": [ + "Preferences/general", + "Preferences/structure", + "Preferences/forms", + "Preferences/methods", + "Preferences/shortcuts" + ] + } + ] }, { "type": "category", @@ -150,7 +112,7 @@ "title": "4D Language", "slug": "/category/4d-language", "keywords": [ - "language" + "language","orda" ], "image": "/img/docusaurus.png" }, @@ -199,12 +161,13 @@ "Concepts/paths" ] }, + "commands/command-index", { "type": "category", - "label": "Commands", + "label": "Commands by theme", "link": { "type": "generated-index", - "title": "Commands", + "title": "Commands by theme", "slug": "/category/commands", "keywords": [ "commands" @@ -212,7 +175,6 @@ "image": "/img/docusaurus.png" }, "items": [ - "commands/command-index", { "type": "category", "label": "4D Environment", @@ -481,34 +443,6 @@ "commands-legacy/register-data-key" ] }, - { - "type": "category", - "label": "Database Methods", - "link": { - "type": "doc", - "id": "commands/theme/Database_Methods_theme" - }, - "items": [ - "commands-legacy/on-backup-shutdown-database-method", - "commands-legacy/on-backup-startup-database-method", - "commands-legacy/on-drop-database-method", - "commands-legacy/on-exit-database-method", - "commands-legacy/on-host-database-event-database-method", - "commands-legacy/on-mobile-app-action-database-method", - "commands-legacy/on-mobile-app-authentication-database-method", - "commands-legacy/on-rest-authentication-database-method", - "commands-legacy/on-server-close-connection-database-method", - "commands-legacy/on-server-open-connection-database-method", - "commands-legacy/on-server-shutdown-database-method", - "commands-legacy/on-server-startup-database-method", - "commands-legacy/on-sql-authentication-database-method", - "commands-legacy/on-startup-database-method", - "commands-legacy/on-system-event-database-method", - "commands-legacy/on-web-authentication-database-method", - "commands-legacy/on-web-connection-database-method", - "commands-legacy/on-web-legacy-close-session-database-method" - ] - }, { "type": "category", "label": "Date and Time", @@ -2273,7 +2207,6 @@ "type": "category", "label": "Classes", "items": [ - "API/overview", "API/BlobClass", "API/ClassClass", "API/CollectionClass", @@ -2316,7 +2249,7 @@ ], "link": { "type": "generated-index", - "title": "Class Functions", + "title": "Classes", "description": "List of built-in 4D classes", "slug": "/category/class-API-reference", "keywords": [ @@ -2329,683 +2262,140 @@ }, { "type": "category", - "label": "Administration", + "label": "Core Development", "link": { "type": "generated-index", - "title": "Administration", - "description": "How to monitor your 4D applications", - "keywords": [ - "administration" - ], + "title": "Core Development", + "slug": "/category/core", "image": "/img/docusaurus.png" }, "items": [ { "type": "category", - "label": "4D Server Administration Window", + "label": "ORDA", "link": { "type": "doc", - "id": "ServerWindow/overview" + "id": "ORDA/overview" }, "items": [ - "ServerWindow/monitor", - "ServerWindow/users", - "ServerWindow/processes", - "ServerWindow/maintenance", - "ServerWindow/application-server", - "ServerWindow/sql-server", - "ServerWindow/http-server", - "ServerWindow/real-time-monitor", - "ServerWindow/remote-admin" + "ORDA/dsmapping", + "ORDA/ordaClasses", + "ORDA/entities", + "ORDA/global-stamp", + "ORDA/datastores", + "ORDA/privileges", + "ORDA/client-server-optimization", + "ORDA/glossary" ] }, { "type": "category", - "label": "Web Administration", + "label": "Processes", "link": { "type": "generated-index", - "title": "Web Administration", - "description": "4D web tools for administrating and monitoring your applications.", - "slug": "/category/web-administration", + "title": "Processes", + "slug": "/category/processes", "keywords": [ - "web administration" + "processes" ], "image": "/img/docusaurus.png" }, "items": [ - "Admin/webAdmin", - "Admin/dataExplorer" + "Develop/processes", + "Develop/preemptive-processes" ] }, - { - "type": "doc", - "label": "Command Line Interface", - "id": "Admin/cli" - }, - { - "type": "doc", - "label": "TLS Protocol", - "id": "Admin/tls" - }, - { - "type": "doc", - "label": "Licenses", - "id": "Admin/licenses" - }, { "type": "category", - "label": "MSC", + "label": "Database Methods", "link": { - "type": "doc", - "id": "MSC/overview" - }, - "items": [ - "MSC/information", - "MSC/analysis", - "MSC/verify", - "MSC/backup", - "MSC/compact", - "MSC/rollback", - "MSC/restore", - "MSC/repair", - "MSC/encrypt" - ] + "type": "generated-index", + "title": "Database Methods", + "slug": "/category/database-methods", + "image": "/img/docusaurus.png" + }, + "items": [ + "commands-legacy/on-backup-shutdown-database-method", + "commands-legacy/on-backup-startup-database-method", + "commands-legacy/on-drop-database-method", + "commands-legacy/on-exit-database-method", + "commands-legacy/on-host-database-event-database-method", + "commands-legacy/on-mobile-app-action-database-method", + "commands-legacy/on-mobile-app-authentication-database-method", + "commands-legacy/on-rest-authentication-database-method", + "commands-legacy/on-server-close-connection-database-method", + "commands-legacy/on-server-open-connection-database-method", + "commands-legacy/on-server-shutdown-database-method", + "commands-legacy/on-server-startup-database-method", + "commands-legacy/on-sql-authentication-database-method", + "commands-legacy/on-startup-database-method", + "commands-legacy/on-system-event-database-method", + "commands-legacy/on-web-authentication-database-method", + "commands-legacy/on-web-connection-database-method", + "commands-legacy/on-web-legacy-close-session-database-method" + ] + }, + "Develop-legacy/transactions", + "Tags/transformation-tags", + "Project/date-time-formats" + ] + }, + { + "type": "category", + "label": "Web Applications", + "link": { + "type": "generated-index", + "title": "Web Applications", + "description": "Guides for developing Web applications with 4D", + "keywords": [ + "web applications" + ], + "image": "/img/docusaurus.png" + }, + "items": [ + { + "type": "link", + "label": "4D Qodly Pro", + "href": "https://developer.4d.com/qodly/" }, { "type": "category", - "label": "Backup and Restore", + "label": "Web Server", "link": { "type": "doc", - "id": "Backup/overview" + "id": "WebServer/webServer" }, "items": [ - "Backup/backup", - "Backup/settings", - "Backup/log", - "Backup/restore" + "WebServer/gettingStarted", + "WebServer/webServerConfig", + "WebServer/webServerAdmin", + "WebServer/webServerObject", + "WebServer/templates", + "WebServer/httpRequests", + "WebServer/http-request-handler", + "WebServer/allowProject", + "WebServer/errorPages", + "WebServer/authentication", + "WebServer/sessions", + "WebServer/preemptiveWeb" ] }, - { - "type": "doc", - "label": "Data Collection", - "id": "Admin/data-collect" - } - ] - }, - { - "type": "category", - "label": "Extensions", - "link": { - "type": "doc", - "id": "Extensions/overview" - }, - "items": [ { "type": "category", - "label": "4D View Pro", + "label": "REST API", "link": { "type": "generated-index", - "title": "4D View Pro", - "slug": "/category/4d-view-pro", + "title": "REST API", + "description": "Exposing your datastore to REST and using the REST API.", "keywords": [ - "4D View Pro" + "REST server" ], "image": "/img/docusaurus.png" }, "items": [ - "ViewPro/getting-started", - "ViewPro/configuring", - "ViewPro/formulas", - "ViewPro/classes", - "ViewPro/advanced-programming", { "type": "category", - "label": "Commands", - "link": { - "type": "doc", - "id": "ViewPro/commands" - }, - "items": [ - { - "type": "category", - "label": "A", - "link": { - "type": "generated-index", - "title": "A", - "slug": "/commands-legacy/A" - }, - "items": [ - "ViewPro/commands/vp-add-formula-name", - "ViewPro/commands/vp-add-range-name", - "ViewPro/commands/vp-add-selection", - "ViewPro/commands/vp-add-sheet", - "ViewPro/commands/vp-add-span", - "ViewPro/commands/vp-add-stylesheet", - "ViewPro/commands/vp-all" - ] - }, - { - "type": "category", - "label": "C", - "link": { - "type": "generated-index", - "title": "C", - "slug": "/commands-legacy/C" - }, - "items": [ - "ViewPro/commands/vp-cell", - "ViewPro/commands/vp-cells", - "ViewPro/commands/vp-column", - "ViewPro/commands/vp-column-autofit", - "ViewPro/commands/vp-combine-ranges", - "ViewPro/commands/vp-convert-from-4d-view", - "ViewPro/commands/vp-convert-to-picture", - "ViewPro/commands/vp-copy-to-object", - "ViewPro/commands/vp-create-table" - ] - }, - { - "type": "category", - "label": "D", - "link": { - "type": "generated-index", - "title": "D", - "slug": "/commands-legacy/D" - }, - "items": [ - "ViewPro/commands/vp-delete-columns", - "ViewPro/commands/vp-delete-rows" - ] - }, - { - "type": "category", - "label": "E", - "link": { - "type": "generated-index", - "title": "E", - "slug": "/commands-legacy/E" - }, - "items": [ - "ViewPro/commands/vp-export-document", - "ViewPro/commands/vp-export-to-blob", - "ViewPro/commands/vp-export-to-object" - ] - }, - { - "type": "category", - "label": "F", - "link": { - "type": "generated-index", - "title": "F", - "slug": "/commands-legacy/F" - }, - "items": [ - "ViewPro/commands/vp-find", - "ViewPro/commands/vp-find-table", - "ViewPro/commands/vp-flush-commands", - "ViewPro/commands/vp-font-to-object" - ] - }, - { - "type": "category", - "label": "G", - "link": { - "type": "generated-index", - "title": "G", - "slug": "/commands-legacy/G" - }, - "items": [ - "ViewPro/commands/vp-get-active-cell", - "ViewPro/commands/vp-get-binding-path", - "ViewPro/commands/vp-get-cell-style", - "ViewPro/commands/vp-get-column-attributes", - "ViewPro/commands/vp-get-column-count", - "ViewPro/commands/vp-get-current-sheet", - "ViewPro/commands/vp-get-data-context", - "ViewPro/commands/vp-get-default-style", - "ViewPro/commands/vp-get-formula", - "ViewPro/commands/vp-get-formula-by-name", - "ViewPro/commands/vp-get-formulas", - "ViewPro/commands/vp-get-frozen-panes", - "ViewPro/commands/vp-get-names", - "ViewPro/commands/vp-get-print-info", - "ViewPro/commands/vp-get-row-attributes", - "ViewPro/commands/vp-get-row-count", - "ViewPro/commands/vp-get-selection", - "ViewPro/commands/vp-get-sheet-count", - "ViewPro/commands/vp-get-sheet-index", - "ViewPro/commands/vp-get-sheet-name", - "ViewPro/commands/vp-get-sheet-options", - "ViewPro/commands/vp-get-show-print-lines", - "ViewPro/commands/vp-get-spans", - "ViewPro/commands/vp-get-stylesheet", - "ViewPro/commands/vp-get-stylesheets", - "ViewPro/commands/vp-get-table-column-attributes", - "ViewPro/commands/vp-get-table-column-index", - "ViewPro/commands/vp-get-table-dirty-rows", - "ViewPro/commands/vp-get-table-range", - "ViewPro/commands/vp-get-table-theme", - "ViewPro/commands/vp-get-tables", - "ViewPro/commands/vp-get-value", - "ViewPro/commands/vp-get-values", - "ViewPro/commands/vp-get-workbook-options" - ] - }, - { - "type": "category", - "label": "I", - "link": { - "type": "generated-index", - "title": "I", - "slug": "/commands-legacy/I" - }, - "items": [ - "ViewPro/commands/vp-import-document", - "ViewPro/commands/vp-import-from-blob", - "ViewPro/commands/vp-import-from-object", - "ViewPro/commands/vp-insert-columns", - "ViewPro/commands/vp-insert-rows", - "ViewPro/commands/vp-insert-table-columns", - "ViewPro/commands/vp-insert-table-rows" - ] - }, - { - "type": "category", - "label": "M", - "link": { - "type": "generated-index", - "title": "M", - "slug": "/commands-legacy/M" - }, - "items": [ - "ViewPro/commands/vp-move-cells" - ] - }, - { - "type": "category", - "label": "N", - "link": { - "type": "generated-index", - "title": "N", - "slug": "/commands-legacy/N" - }, - "items": [ - "ViewPro/commands/vp-name", - "ViewPro/commands/vp-new-document" - ] - }, - { - "type": "category", - "label": "O", - "link": { - "type": "generated-index", - "title": "O", - "slug": "/commands-legacy/O" - }, - "items": [ - "ViewPro/commands/vp-object-to-font" - ] - }, - { - "type": "category", - "label": "P", - "link": { - "type": "generated-index", - "title": "P", - "slug": "/commands-legacy/P" - }, - "items": [ - "ViewPro/commands/vp-paste-from-object", - "ViewPro/commands/vp-print" - ] - }, - { - "type": "category", - "label": "R", - "link": { - "type": "generated-index", - "title": "R", - "slug": "/commands-legacy/R" - }, - "items": [ - "ViewPro/commands/vp-recompute-formulas", - "ViewPro/commands/vp-remove-name", - "ViewPro/commands/vp-remove-sheet", - "ViewPro/commands/vp-remove-span", - "ViewPro/commands/vp-remove-stylesheet", - "ViewPro/commands/vp-remove-table", - "ViewPro/commands/vp-remove-table-columns", - "ViewPro/commands/vp-remove-table-rows", - "ViewPro/commands/vp-reset-selection", - "ViewPro/commands/vp-resize-table", - "ViewPro/commands/vp-resume-computing", - "ViewPro/commands/vp-row", - "ViewPro/commands/vp-row-autofit", - "ViewPro/commands/vp-run-offscreen-area" - ] - }, - { - "type": "category", - "label": "S", - "link": { - "type": "generated-index", - "title": "S", - "slug": "/commands-legacy/S" - }, - "items": [ - "ViewPro/commands/vp-set-active-cell", - "ViewPro/commands/vp-set-allowed-methods", - "ViewPro/commands/vp-set-binding-path", - "ViewPro/commands/vp-set-boolean-value", - "ViewPro/commands/vp-set-border", - "ViewPro/commands/vp-set-cell-style", - "ViewPro/commands/vp-set-column-attributes", - "ViewPro/commands/vp-set-column-count", - "ViewPro/commands/vp-set-current-sheet", - "ViewPro/commands/vp-set-custom-functions", - "ViewPro/commands/vp-set-data-context", - "ViewPro/commands/vp-set-date-time-value", - "ViewPro/commands/vp-set-date-value", - "ViewPro/commands/vp-set-default-style", - "ViewPro/commands/vp-set-field", - "ViewPro/commands/vp-set-formula", - "ViewPro/commands/vp-set-formulas", - "ViewPro/commands/vp-set-frozen-panes", - "ViewPro/commands/vp-set-num-value", - "ViewPro/commands/vp-set-print-info", - "ViewPro/commands/vp-set-row-attributes", - "ViewPro/commands/vp-set-row-count", - "ViewPro/commands/vp-set-selection", - "ViewPro/commands/vp-set-sheet-count", - "ViewPro/commands/vp-set-sheet-name", - "ViewPro/commands/vp-set-sheet-options", - "ViewPro/commands/vp-set-show-print-lines", - "ViewPro/commands/vp-set-table-column-attributes", - "ViewPro/commands/vp-set-table-theme", - "ViewPro/commands/vp-set-text-value", - "ViewPro/commands/vp-set-time-value", - "ViewPro/commands/vp-set-value", - "ViewPro/commands/vp-set-values", - "ViewPro/commands/vp-set-workbook-options", - "ViewPro/commands/vp-show-cell", - "ViewPro/commands/vp-suspend-computing" - ] - } - ] - } - ] - }, - { - "type": "category", - "label": "4D Write Pro", - "link": { - "type": "generated-index", - "title": "4D Write Pro", - "slug": "/category/4d-write-pro", - "keywords": [ - "4D Write Pro" - ], - "image": "/img/docusaurus.png" - }, - "items": [ - "WritePro/writeprointerface", - "WritePro/managing-formulas", - "WritePro/commands-legacy/4d-write-pro-attributes", - { - "type": "category", - "label": "Commands", - "link": { - "type": "doc", - "id": "WritePro/commands/command-index" - }, - "items": [ - "WritePro/commands/wp-add-picture", - "WritePro/commands-legacy/wp-bookmark-range", - "WritePro/commands-legacy/wp-compute-formulas", - "WritePro/commands-legacy/wp-delete-bookmark", - "WritePro/commands-legacy/wp-delete-footer", - "WritePro/commands-legacy/wp-delete-header", - "WritePro/commands-legacy/wp-delete-picture", - "WritePro/commands/wp-delete-section", - "WritePro/commands-legacy/wp-delete-style-sheet", - "WritePro/commands/wp-delete-subsection", - "WritePro/commands-legacy/wp-delete-text-box", - "WritePro/commands/wp-export-document", - "WritePro/commands/wp-export-variable", - "WritePro/commands-legacy/wp-find-all", - "WritePro/commands-legacy/wp-find-next", - "WritePro/commands-legacy/wp-find-previous", - "WritePro/commands-legacy/wp-freeze-formulas", - "WritePro/commands/wp-get-attributes", - "WritePro/commands-legacy/wp-get-body", - "WritePro/commands-legacy/wp-get-bookmarks", - "WritePro/commands-legacy/wp-get-breaks", - "WritePro/commands-legacy/wp-get-data-context", - "WritePro/commands-legacy/wp-get-element-by-id", - "WritePro/commands-legacy/wp-get-elements", - "WritePro/commands-legacy/wp-get-footer", - "WritePro/commands-legacy/wp-get-formulas", - "WritePro/commands-legacy/wp-get-frame", - "WritePro/commands-legacy/wp-get-header", - "WritePro/commands-legacy/wp-get-links", - "WritePro/commands-legacy/wp-get-page-count", - "WritePro/commands-legacy/wp-get-position", - "WritePro/commands-legacy/wp-get-section", - "WritePro/commands-legacy/wp-get-sections", - "WritePro/commands-legacy/wp-get-style-sheet", - "WritePro/commands-legacy/wp-get-style-sheets", - "WritePro/commands-legacy/wp-get-subsection", - "WritePro/commands-legacy/wp-get-text", - "WritePro/commands-legacy/wp-get-view-properties", - "WritePro/commands/wp-import-document", - "WritePro/commands-legacy/wp-import-style-sheets", - "WritePro/commands/wp-insert-break", - "WritePro/commands/wp-insert-document-body", - "WritePro/commands/wp-insert-formula", - "WritePro/commands/wp-insert-picture", - "WritePro/commands-legacy/wp-insert-table", - "WritePro/commands-legacy/wp-is-font-style-supported", - "WritePro/commands-legacy/wp-new", - "WritePro/commands-legacy/wp-new-bookmark", - "WritePro/commands-legacy/wp-new-footer", - "WritePro/commands-legacy/wp-new-header", - "WritePro/commands-legacy/wp-new-style-sheet", - "WritePro/commands-legacy/wp-new-subsection", - "WritePro/commands-legacy/wp-new-text-box", - "WritePro/commands-legacy/wp-paragraph-range", - "WritePro/commands-legacy/wp-picture-range", - "WritePro/commands-legacy/wp-print", - "WritePro/commands/wp-reset-attributes", - "WritePro/commands-legacy/wp-select", - "WritePro/commands-legacy/wp-selection-range", - "WritePro/commands/wp-set-attributes", - "WritePro/commands-legacy/wp-set-data-context", - "WritePro/commands-legacy/wp-set-frame", - "WritePro/commands-legacy/wp-set-link", - "WritePro/commands-legacy/wp-set-text", - "WritePro/commands-legacy/wp-set-view-properties", - "WritePro/commands/wp-table-append-row", - "WritePro/commands-legacy/wp-table-delete-columns", - "WritePro/commands-legacy/wp-table-delete-rows", - "WritePro/commands-legacy/wp-table-get-cells", - "WritePro/commands-legacy/wp-table-get-columns", - "WritePro/commands-legacy/wp-table-get-rows", - "WritePro/commands-legacy/wp-table-insert-columns", - "WritePro/commands-legacy/wp-table-insert-rows", - "WritePro/commands-legacy/wp-table-merge-cells", - "WritePro/commands-legacy/wp-table-range", - "WritePro/commands-legacy/wp-table-split-cells", - "WritePro/commands-legacy/wp-text-range", - "WritePro/commands-legacy/wp-use-page-setup" - ] - } - ] - }, - { - "type": "category", - "label": "4D AIKit", - "link": { - "type": "generated-index", - "title": "4D AIKit", - "slug": "/category/4d-aikit", - "keywords": [ - "4D AIKit" - ], - "image": "/img/docusaurus.png" - }, - "items": [ - "aikit/overview", - "aikit/asynchronous-call", - "aikit/compatible-openai", - { - "type": "category", - "label": "Classes", - "items": [ - "aikit/Classes/openai", - "aikit/Classes/openaiapiresource", - "aikit/Classes/openaichatapi", - "aikit/Classes/openaichatcompletionsapi", - "aikit/Classes/openaichatcompletionslistparameters", - "aikit/Classes/openaichatcompletionsmessagesapi", - "aikit/Classes/openaichatcompletionsmessagesparameters", - "aikit/Classes/openaichatcompletionsparameters", - "aikit/Classes/openaichatcompletionsresult", - "aikit/Classes/openaichatcompletionsstreamresult", - "aikit/Classes/openaichathelper", - "aikit/Classes/openaichoice", - "aikit/Classes/openaiembedding", - "aikit/Classes/openaiembeddingsapi", - "aikit/Classes/openaiembeddingsparameters", - "aikit/Classes/openaiembeddingsresult", - "aikit/Classes/openaierror", - "aikit/Classes/openaiimage", - "aikit/Classes/openaiimageparameters", - "aikit/Classes/openaiimagesapi", - "aikit/Classes/openaiimagesresult", - "aikit/Classes/openaimessage", - "aikit/Classes/openaimodel", - "aikit/Classes/openaimodellistresult", - "aikit/Classes/openaimodelresult", - "aikit/Classes/openaimodelsapi", - "aikit/Classes/openaimoderation", - "aikit/Classes/openaimoderationitem", - "aikit/Classes/openaimoderationresult", - "aikit/Classes/openaimoderationsapi", - "aikit/Classes/openaiparameters", - "aikit/Classes/openairesult", - "aikit/Classes/openaivision", - "aikit/Classes/openaivisionhelper" - ] - } - ] - }, - { - "type": "link", - "label": "4D Mobile App Server", - "href": "https://github.com/4d-go-mobile/4D-Mobile-App-Server" - }, - { - "type": "link", - "label": "4D NetKit", - "href": "https://developer.4d.com/4D-NetKit" - }, - { - "type": "link", - "label": "4D Progress", - "href": "https://doc.4d.com/4Dv20R10/4D/20-R10/4D-Progress.100-7614210.en.html" - }, - { - "type": "link", - "label": "4D SVG", - "href": "https://doc.4d.com/4Dv20R10/4D/20-R10/4D-SVG-Component.100-7614300.en.html" - }, - { - "type": "link", - "label": "4D Widgets", - "href": "https://doc.4d.com/4Dv20R10/4D/20-R10/4D-Widgets.100-7614949.en.html" - }, - "Extensions/develop-components", - "Extensions/develop-plug-ins" - ] - }, - { - "type": "category", - "label": "Web Applications", - "link": { - "type": "generated-index", - "title": "Web Applications", - "description": "Guides for developing Web applications with 4D", - "keywords": [ - "web applications" - ], - "image": "/img/docusaurus.png" - }, - "items": [ - { - "type": "category", - "label": "Web Server", - "link": { - "type": "doc", - "id": "WebServer/webServer" - }, - "items": [ - "WebServer/webServerConfig", - "WebServer/webServerAdmin", - "WebServer/webServerObject" - ] - }, - { - "type": "category", - "label": "Web Development", - "link": { - "type": "doc", - "id": "WebServer/gettingStarted" - }, - "items": [ - "WebServer/templates", - "WebServer/httpRequests", - "WebServer/http-request-handler", - "WebServer/allowProject", - "WebServer/errorPages", - "WebServer/authentication", - "WebServer/sessions", - "WebServer/preemptiveWeb" - ] - }, - { - "type": "category", - "label": "Qodly Studio", - "link": { - "type": "generated-index", - "title": "Qodly Studio", - "description": "Using Qodly Studio to build powerful web interfaces.", - "slug": "/category/qodly-studio-in-4d", - "keywords": [ - "Qodly Studio" - ], - "image": "/img/docusaurus.png" - }, - "items": [ - "WebServer/qodly-studio", - "WebServer/from-qodlyscript-to-4d" - ] - }, - { - "type": "category", - "label": "REST API", - "link": { - "type": "generated-index", - "title": "REST API", - "description": "Exposing your datastore to REST and using the REST API.", - "keywords": [ - "REST server" - ], - "image": "/img/docusaurus.png" - }, - "items": [ - { - "type": "category", - "label": "Exposing your datastore in REST", + "label": "Exposing your datastore in REST", "link": { "type": "generated-index", "title": "Exposing your datastore in REST", @@ -3084,273 +2474,883 @@ ] } ] - } + } + ] + }, + { + "type": "category", + "label": "Desktop Applications", + "link": { + "type": "generated-index", + "title": "Desktop Applications", + "description": "Guides for developing Desktop applications with 4D", + "keywords": [ + "desktop applications" + ], + "image": "/img/docusaurus.png" + }, + "items": [ + { + "type": "doc", + "label": "Client/Server", + "id": "Desktop/clientServer" + }, + { + "type": "category", + "label": "Forms", + "link": { + "type": "doc", + "id": "FormEditor/forms" + }, + "items": [ + "FormEditor/stylesheets", + "FormEditor/pictures", + { + "type": "category", + "label": "Form Editor", + "link": { + "type": "doc", + "id": "FormEditor/formEditor" + }, + "items": [ + "FormEditor/macros", + "FormEditor/objectLibrary" + ] + }, + { + "type": "category", + "label": "Form Properties", + "link": { + "type": "doc", + "id": "FormEditor/jsonReference" + }, + "items": [ + "FormEditor/action", + "FormEditor/propertiesForm", + "FormEditor/formSize", + "FormEditor/markers", + "FormEditor/menu", + "FormEditor/print", + "FormEditor/windowSize" + ] + }, + { + "type": "category", + "label": "Form Objects", + "link": { + "type": "doc", + "id": "FormObjects/formObjectsOverview" + }, + "items": [ + "FormObjects/buttonOverview", + "FormObjects/buttonGridOverview", + "FormObjects/checkboxOverview", + "FormObjects/comboBoxOverview", + "FormObjects/dropdownListOverview", + "FormObjects/groupBox", + "FormObjects/inputOverview", + "FormObjects/listOverview", + "FormObjects/listboxOverview", + "FormObjects/pictureButtonOverview", + "FormObjects/picturePopupMenuOverview", + "FormObjects/pluginAreaOverview", + "FormObjects/progressIndicator", + "FormObjects/radiobuttonOverview", + "FormObjects/ruler", + "FormObjects/shapesOverview", + "FormObjects/spinner", + "FormObjects/splitters", + "FormObjects/staticPicture", + "FormObjects/stepper", + "FormObjects/subformOverview", + "FormObjects/tabControl", + "FormObjects/text", + "FormObjects/webAreaOverview", + "FormObjects/viewProAreaOverview", + "FormObjects/writeProAreaOverview" + ] + }, + { + "type": "category", + "label": "Form Object Properties", + "link": { + "type": "doc", + "id": "FormObjects/propertiesReference" + }, + "items": [ + "FormObjects/propertiesAction", + "FormObjects/propertiesAnimation", + "FormObjects/propertiesAppearance", + "FormObjects/propertiesBackgroundAndBorder", + "FormObjects/propertiesCoordinatesAndSizing", + "FormObjects/propertiesCrop", + "FormObjects/propertiesDataSource", + "FormObjects/propertiesDisplay", + "FormObjects/propertiesEntry", + "FormObjects/propertiesFooters", + "FormObjects/propertiesGridlines", + "FormObjects/propertiesHeaders", + "FormObjects/propertiesHelp", + "FormObjects/propertiesHierarchy", + "FormObjects/propertiesListBox", + "FormObjects/propertiesObject", + "FormObjects/propertiesPicture", + "FormObjects/propertiesPlugIns", + "FormObjects/propertiesPrint", + "FormObjects/propertiesRangeOfValues", + "FormObjects/propertiesResizingOptions", + "FormObjects/propertiesScale", + "FormObjects/propertiesSubform", + "FormObjects/propertiesText", + "FormObjects/propertiesTextAndPicture", + "FormObjects/propertiesWebArea" + ] + }, + { + "type": "category", + "label": "Form Events", + "link": { + "type": "doc", + "id": "Events/overview" + }, + "items": [ + "Events/onActivate", + "Events/onAfterEdit", + "Events/onAfterKeystroke", + "Events/onAfterSort", + "Events/onAlternativeClick", + "Events/onBeforeDataEntry", + "Events/onBeforeKeystroke", + "Events/onBeginDragOver", + "Events/onBeginUrlLoading", + "Events/onBoundVariableChange", + "Events/onClicked", + "Events/onCloseBox", + "Events/onCloseDetail", + "Events/onCollapse", + "Events/onColumnMoved", + "Events/onColumnResize", + "Events/onDataChange", + "Events/onDeactivate", + "Events/onDeleteAction", + "Events/onDisplayDetail", + "Events/onDoubleClicked", + "Events/onDragOver", + "Events/onDrop", + "Events/onEndUrlLoading", + "Events/onExpand", + "Events/onFooterClick", + "Events/onGettingFocus", + "Events/onHeader", + "Events/onHeaderClick", + "Events/onLoad", + "Events/onLoadRecord", + "Events/onLongClick", + "Events/onLosingFocus", + "Events/onMenuSelected", + "Events/onMouseEnter", + "Events/onMouseLeave", + "Events/onMouseMove", + "Events/onMouseUp", + "Events/onOpenDetail", + "Events/onOpenExternalLink", + "Events/onOutsideCall", + "Events/onPageChange", + "Events/onPlugInArea", + "Events/onPrintingBreak", + "Events/onPrintingDetail", + "Events/onPrintingFooter", + "Events/onResize", + "Events/onRowMoved", + "Events/onRowResize", + "Events/onScroll", + "Events/onSelectionChange", + "Events/onTimer", + "Events/onUnload", + "Events/onUrlFiltering", + "Events/onUrlLoadingError", + "Events/onUrlResourceLoading", + "Events/onValidate", + "Events/onVpRangeChanged", + "Events/onVpReady", + "Events/onWindowOpeningDenied" + ] + } + ] + }, + { + "type": "doc", + "label": "Labels", + "id": "Desktop/labels" + }, + { + "type": "category", + "label": "Menus", + "link": { + "type": "doc", + "id": "Menus/overview" + }, + "items": [ + "Menus/creating", + "Menus/properties", + "Menus/bars", + "Menus/sdi" + ] + }, + { + "type": "category", + "label": "Access Rights", + "link": { + "type": "generated-index", + "title": "Access Rights", + "description": "Access control and user privileges for desktop applications.", + "slug": "/category/access-rights", + "keywords": [ + "access rights" + ], + "image": "/img/docusaurus.png" + }, + "items": [ + "Users/overview", + "Users/editing" + ] + } ] }, { "type": "category", - "label": "Desktop Applications", + "label": "Administration", "link": { "type": "generated-index", - "title": "Desktop Applications", - "description": "Guides for developing Desktop applications with 4D", + "title": "Administration", + "description": "How to monitor your 4D applications", "keywords": [ - "desktop applications" + "administration" ], "image": "/img/docusaurus.png" }, "items": [ { - "type": "doc", - "label": "Client/Server", - "id": "Desktop/clientServer" + "type": "category", + "label": "4D Server Administration Window", + "link": { + "type": "doc", + "id": "ServerWindow/overview" + }, + "items": [ + "ServerWindow/monitor", + "ServerWindow/users", + "ServerWindow/processes", + "ServerWindow/maintenance", + "ServerWindow/application-server", + "ServerWindow/sql-server", + "ServerWindow/http-server", + "ServerWindow/real-time-monitor", + "ServerWindow/remote-admin" + ] }, { "type": "category", - "label": "Access Rights", + "label": "Web Administration", "link": { "type": "generated-index", - "title": "Access Rights", - "description": "Access control and user privileges for desktop applications.", - "slug": "/category/access-rights", + "title": "Web Administration", + "description": "4D web tools for administrating and monitoring your applications.", + "slug": "/category/web-administration", "keywords": [ - "access rights" + "web administration" ], "image": "/img/docusaurus.png" }, "items": [ - "Users/overview", - "Users/editing" + "Admin/webAdmin", + "Admin/dataExplorer" ] }, + { + "type": "doc", + "label": "Command Line Interface", + "id": "Admin/cli" + }, + { + "type": "doc", + "label": "TLS Protocol", + "id": "Admin/tls" + }, + { + "type": "doc", + "label": "Licenses", + "id": "Admin/licenses" + }, + { + "type": "doc", + "label": "Log Files", + "id": "Debugging/debugLogFiles" + }, { "type": "category", - "label": "Forms", + "label": "MSC", "link": { "type": "doc", - "id": "FormEditor/forms" + "id": "MSC/overview" }, "items": [ - "FormEditor/stylesheets", - "FormEditor/pictures", - { - "type": "category", - "label": "Form Editor", - "link": { - "type": "doc", - "id": "FormEditor/formEditor" - }, - "items": [ - "FormEditor/macros", - "FormEditor/objectLibrary" - ] - }, - { - "type": "category", - "label": "Form Properties", - "link": { - "type": "doc", - "id": "FormEditor/jsonReference" - }, - "items": [ - "FormEditor/action", - "FormEditor/propertiesForm", - "FormEditor/formSize", - "FormEditor/markers", - "FormEditor/menu", - "FormEditor/print", - "FormEditor/windowSize" - ] - }, + "MSC/information", + "MSC/analysis", + "MSC/verify", + "MSC/backup", + "MSC/compact", + "MSC/rollback", + "MSC/restore", + "MSC/repair", + "MSC/encrypt" + ] + }, + { + "type": "category", + "label": "Backup and Restore", + "link": { + "type": "doc", + "id": "Backup/overview" + }, + "items": [ + "Backup/backup", + "Backup/settings", + "Backup/log", + "Backup/restore" + ] + }, + { + "type": "doc", + "label": "Data Collection", + "id": "Admin/data-collect" + } + ] + }, + { + "type": "category", + "label": "Extensions", + "link": { + "type": "generated-index", + "title": "Extensions", + "slug": "/category/extensions", + "keywords": [ + "component, extension, plug-in" + ], + "image": "/img/docusaurus.png" + }, + "items": [ { - "type": "category", - "label": "Form Objects", - "link": { - "type": "doc", - "id": "FormObjects/formObjectsOverview" - }, - "items": [ - "FormObjects/buttonOverview", - "FormObjects/buttonGridOverview", - "FormObjects/checkboxOverview", - "FormObjects/comboBoxOverview", - "FormObjects/dropdownListOverview", - "FormObjects/groupBox", - "FormObjects/inputOverview", - "FormObjects/listOverview", - "FormObjects/listboxOverview", - "FormObjects/pictureButtonOverview", - "FormObjects/picturePopupMenuOverview", - "FormObjects/pluginAreaOverview", - "FormObjects/progressIndicator", - "FormObjects/radiobuttonOverview", - "FormObjects/ruler", - "FormObjects/shapesOverview", - "FormObjects/spinner", - "FormObjects/splitters", - "FormObjects/staticPicture", - "FormObjects/stepper", - "FormObjects/subformOverview", - "FormObjects/tabControl", - "FormObjects/text", - "FormObjects/webAreaOverview", - "FormObjects/viewProAreaOverview", - "FormObjects/writeProAreaOverview" - ] + "type": "category", + "label": "Extending 4D applications", + "link": { + "type": "doc", + "id": "Extensions/overview" }, + "items": [ + "Extensions/develop-components", + "Extensions/develop-plug-ins" + ] + }, + { + "type": "category", + "label": "4D View Pro", + "link": { + "type": "generated-index", + "title": "4D View Pro", + "slug": "/category/4d-view-pro", + "keywords": [ + "4D View Pro" + ], + "image": "/img/docusaurus.png" + }, + "items": [ + "ViewPro/getting-started", + "ViewPro/configuring", + "ViewPro/formulas", + "ViewPro/classes", + "ViewPro/advanced-programming", { "type": "category", - "label": "Form Object Properties", + "label": "Commands", "link": { "type": "doc", - "id": "FormObjects/propertiesReference" + "id": "ViewPro/commands" }, "items": [ - "FormObjects/propertiesAction", - "FormObjects/propertiesAnimation", - "FormObjects/propertiesAppearance", - "FormObjects/propertiesBackgroundAndBorder", - "FormObjects/propertiesCoordinatesAndSizing", - "FormObjects/propertiesCrop", - "FormObjects/propertiesDataSource", - "FormObjects/propertiesDisplay", - "FormObjects/propertiesEntry", - "FormObjects/propertiesFooters", - "FormObjects/propertiesGridlines", - "FormObjects/propertiesHeaders", - "FormObjects/propertiesHelp", - "FormObjects/propertiesHierarchy", - "FormObjects/propertiesListBox", - "FormObjects/propertiesObject", - "FormObjects/propertiesPicture", - "FormObjects/propertiesPlugIns", - "FormObjects/propertiesPrint", - "FormObjects/propertiesRangeOfValues", - "FormObjects/propertiesResizingOptions", - "FormObjects/propertiesScale", - "FormObjects/propertiesSubform", - "FormObjects/propertiesText", - "FormObjects/propertiesTextAndPicture", - "FormObjects/propertiesWebArea" + { + "type": "category", + "label": "A", + "link": { + "type": "generated-index", + "title": "A", + "slug": "/commands-legacy/A" + }, + "items": [ + "ViewPro/commands/vp-add-formula-name", + "ViewPro/commands/vp-add-range-name", + "ViewPro/commands/vp-add-selection", + "ViewPro/commands/vp-add-sheet", + "ViewPro/commands/vp-add-span", + "ViewPro/commands/vp-add-stylesheet", + "ViewPro/commands/vp-all" + ] + }, + { + "type": "category", + "label": "C", + "link": { + "type": "generated-index", + "title": "C", + "slug": "/commands-legacy/C" + }, + "items": [ + "ViewPro/commands/vp-cell", + "ViewPro/commands/vp-cells", + "ViewPro/commands/vp-column", + "ViewPro/commands/vp-column-autofit", + "ViewPro/commands/vp-combine-ranges", + "ViewPro/commands/vp-convert-from-4d-view", + "ViewPro/commands/vp-convert-to-picture", + "ViewPro/commands/vp-copy-to-object", + "ViewPro/commands/vp-create-table" + ] + }, + { + "type": "category", + "label": "D", + "link": { + "type": "generated-index", + "title": "D", + "slug": "/commands-legacy/D" + }, + "items": [ + "ViewPro/commands/vp-delete-columns", + "ViewPro/commands/vp-delete-rows" + ] + }, + { + "type": "category", + "label": "E", + "link": { + "type": "generated-index", + "title": "E", + "slug": "/commands-legacy/E" + }, + "items": [ + "ViewPro/commands/vp-export-document", + "ViewPro/commands/vp-export-to-blob", + "ViewPro/commands/vp-export-to-object" + ] + }, + { + "type": "category", + "label": "F", + "link": { + "type": "generated-index", + "title": "F", + "slug": "/commands-legacy/F" + }, + "items": [ + "ViewPro/commands/vp-find", + "ViewPro/commands/vp-find-table", + "ViewPro/commands/vp-flush-commands", + "ViewPro/commands/vp-font-to-object" + ] + }, + { + "type": "category", + "label": "G", + "link": { + "type": "generated-index", + "title": "G", + "slug": "/commands-legacy/G" + }, + "items": [ + "ViewPro/commands/vp-get-active-cell", + "ViewPro/commands/vp-get-binding-path", + "ViewPro/commands/vp-get-cell-style", + "ViewPro/commands/vp-get-column-attributes", + "ViewPro/commands/vp-get-column-count", + "ViewPro/commands/vp-get-current-sheet", + "ViewPro/commands/vp-get-data-context", + "ViewPro/commands/vp-get-default-style", + "ViewPro/commands/vp-get-formula", + "ViewPro/commands/vp-get-formula-by-name", + "ViewPro/commands/vp-get-formulas", + "ViewPro/commands/vp-get-frozen-panes", + "ViewPro/commands/vp-get-names", + "ViewPro/commands/vp-get-print-info", + "ViewPro/commands/vp-get-row-attributes", + "ViewPro/commands/vp-get-row-count", + "ViewPro/commands/vp-get-selection", + "ViewPro/commands/vp-get-sheet-count", + "ViewPro/commands/vp-get-sheet-index", + "ViewPro/commands/vp-get-sheet-name", + "ViewPro/commands/vp-get-sheet-options", + "ViewPro/commands/vp-get-show-print-lines", + "ViewPro/commands/vp-get-spans", + "ViewPro/commands/vp-get-stylesheet", + "ViewPro/commands/vp-get-stylesheets", + "ViewPro/commands/vp-get-table-column-attributes", + "ViewPro/commands/vp-get-table-column-index", + "ViewPro/commands/vp-get-table-dirty-rows", + "ViewPro/commands/vp-get-table-range", + "ViewPro/commands/vp-get-table-theme", + "ViewPro/commands/vp-get-tables", + "ViewPro/commands/vp-get-value", + "ViewPro/commands/vp-get-values", + "ViewPro/commands/vp-get-workbook-options" + ] + }, + { + "type": "category", + "label": "I", + "link": { + "type": "generated-index", + "title": "I", + "slug": "/commands-legacy/I" + }, + "items": [ + "ViewPro/commands/vp-import-document", + "ViewPro/commands/vp-import-from-blob", + "ViewPro/commands/vp-import-from-object", + "ViewPro/commands/vp-insert-columns", + "ViewPro/commands/vp-insert-rows", + "ViewPro/commands/vp-insert-table-columns", + "ViewPro/commands/vp-insert-table-rows" + ] + }, + { + "type": "category", + "label": "M", + "link": { + "type": "generated-index", + "title": "M", + "slug": "/commands-legacy/M" + }, + "items": [ + "ViewPro/commands/vp-move-cells" + ] + }, + { + "type": "category", + "label": "N", + "link": { + "type": "generated-index", + "title": "N", + "slug": "/commands-legacy/N" + }, + "items": [ + "ViewPro/commands/vp-name", + "ViewPro/commands/vp-new-document" + ] + }, + { + "type": "category", + "label": "O", + "link": { + "type": "generated-index", + "title": "O", + "slug": "/commands-legacy/O" + }, + "items": [ + "ViewPro/commands/vp-object-to-font" + ] + }, + { + "type": "category", + "label": "P", + "link": { + "type": "generated-index", + "title": "P", + "slug": "/commands-legacy/P" + }, + "items": [ + "ViewPro/commands/vp-paste-from-object", + "ViewPro/commands/vp-print" + ] + }, + { + "type": "category", + "label": "R", + "link": { + "type": "generated-index", + "title": "R", + "slug": "/commands-legacy/R" + }, + "items": [ + "ViewPro/commands/vp-recompute-formulas", + "ViewPro/commands/vp-remove-name", + "ViewPro/commands/vp-remove-sheet", + "ViewPro/commands/vp-remove-span", + "ViewPro/commands/vp-remove-stylesheet", + "ViewPro/commands/vp-remove-table", + "ViewPro/commands/vp-remove-table-columns", + "ViewPro/commands/vp-remove-table-rows", + "ViewPro/commands/vp-reset-selection", + "ViewPro/commands/vp-resize-table", + "ViewPro/commands/vp-resume-computing", + "ViewPro/commands/vp-row", + "ViewPro/commands/vp-row-autofit", + "ViewPro/commands/vp-run-offscreen-area" + ] + }, + { + "type": "category", + "label": "S", + "link": { + "type": "generated-index", + "title": "S", + "slug": "/commands-legacy/S" + }, + "items": [ + "ViewPro/commands/vp-set-active-cell", + "ViewPro/commands/vp-set-allowed-methods", + "ViewPro/commands/vp-set-binding-path", + "ViewPro/commands/vp-set-boolean-value", + "ViewPro/commands/vp-set-border", + "ViewPro/commands/vp-set-cell-style", + "ViewPro/commands/vp-set-column-attributes", + "ViewPro/commands/vp-set-column-count", + "ViewPro/commands/vp-set-current-sheet", + "ViewPro/commands/vp-set-custom-functions", + "ViewPro/commands/vp-set-data-context", + "ViewPro/commands/vp-set-date-time-value", + "ViewPro/commands/vp-set-date-value", + "ViewPro/commands/vp-set-default-style", + "ViewPro/commands/vp-set-field", + "ViewPro/commands/vp-set-formula", + "ViewPro/commands/vp-set-formulas", + "ViewPro/commands/vp-set-frozen-panes", + "ViewPro/commands/vp-set-num-value", + "ViewPro/commands/vp-set-print-info", + "ViewPro/commands/vp-set-row-attributes", + "ViewPro/commands/vp-set-row-count", + "ViewPro/commands/vp-set-selection", + "ViewPro/commands/vp-set-sheet-count", + "ViewPro/commands/vp-set-sheet-name", + "ViewPro/commands/vp-set-sheet-options", + "ViewPro/commands/vp-set-show-print-lines", + "ViewPro/commands/vp-set-table-column-attributes", + "ViewPro/commands/vp-set-table-theme", + "ViewPro/commands/vp-set-text-value", + "ViewPro/commands/vp-set-time-value", + "ViewPro/commands/vp-set-value", + "ViewPro/commands/vp-set-values", + "ViewPro/commands/vp-set-workbook-options", + "ViewPro/commands/vp-show-cell", + "ViewPro/commands/vp-suspend-computing" + ] + } ] - }, + } + ] + }, + { + "type": "category", + "label": "4D Write Pro", + "link": { + "type": "generated-index", + "title": "4D Write Pro", + "slug": "/category/4d-write-pro", + "keywords": [ + "4D Write Pro" + ], + "image": "/img/docusaurus.png" + }, + "items": [ + "WritePro/writeprointerface", + "WritePro/managing-formulas", + "WritePro/commands-legacy/4d-write-pro-attributes", { "type": "category", - "label": "Form Events", + "label": "Commands", "link": { "type": "doc", - "id": "Events/overview" + "id": "WritePro/commands/command-index" }, "items": [ - "Events/onActivate", - "Events/onAfterEdit", - "Events/onAfterKeystroke", - "Events/onAfterSort", - "Events/onAlternativeClick", - "Events/onBeforeDataEntry", - "Events/onBeforeKeystroke", - "Events/onBeginDragOver", - "Events/onBeginUrlLoading", - "Events/onBoundVariableChange", - "Events/onClicked", - "Events/onCloseBox", - "Events/onCloseDetail", - "Events/onCollapse", - "Events/onColumnMoved", - "Events/onColumnResize", - "Events/onDataChange", - "Events/onDeactivate", - "Events/onDeleteAction", - "Events/onDisplayDetail", - "Events/onDoubleClicked", - "Events/onDragOver", - "Events/onDrop", - "Events/onEndUrlLoading", - "Events/onExpand", - "Events/onFooterClick", - "Events/onGettingFocus", - "Events/onHeader", - "Events/onHeaderClick", - "Events/onLoad", - "Events/onLoadRecord", - "Events/onLongClick", - "Events/onLosingFocus", - "Events/onMenuSelected", - "Events/onMouseEnter", - "Events/onMouseLeave", - "Events/onMouseMove", - "Events/onMouseUp", - "Events/onOpenDetail", - "Events/onOpenExternalLink", - "Events/onOutsideCall", - "Events/onPageChange", - "Events/onPlugInArea", - "Events/onPrintingBreak", - "Events/onPrintingDetail", - "Events/onPrintingFooter", - "Events/onResize", - "Events/onRowMoved", - "Events/onRowResize", - "Events/onScroll", - "Events/onSelectionChange", - "Events/onTimer", - "Events/onUnload", - "Events/onUrlFiltering", - "Events/onUrlLoadingError", - "Events/onUrlResourceLoading", - "Events/onValidate", - "Events/onVpRangeChanged", - "Events/onVpReady", - "Events/onWindowOpeningDenied" + "WritePro/commands/wp-add-picture", + "WritePro/commands-legacy/wp-bookmark-range", + "WritePro/commands-legacy/wp-compute-formulas", + "WritePro/commands-legacy/wp-delete-bookmark", + "WritePro/commands-legacy/wp-delete-footer", + "WritePro/commands-legacy/wp-delete-header", + "WritePro/commands-legacy/wp-delete-picture", + "WritePro/commands/wp-delete-section", + "WritePro/commands-legacy/wp-delete-style-sheet", + "WritePro/commands/wp-delete-subsection", + "WritePro/commands-legacy/wp-delete-text-box", + "WritePro/commands/wp-export-document", + "WritePro/commands/wp-export-variable", + "WritePro/commands-legacy/wp-find-all", + "WritePro/commands-legacy/wp-find-next", + "WritePro/commands-legacy/wp-find-previous", + "WritePro/commands-legacy/wp-freeze-formulas", + "WritePro/commands/wp-get-attributes", + "WritePro/commands-legacy/wp-get-body", + "WritePro/commands-legacy/wp-get-bookmarks", + "WritePro/commands-legacy/wp-get-breaks", + "WritePro/commands-legacy/wp-get-data-context", + "WritePro/commands-legacy/wp-get-element-by-id", + "WritePro/commands-legacy/wp-get-elements", + "WritePro/commands-legacy/wp-get-footer", + "WritePro/commands-legacy/wp-get-formulas", + "WritePro/commands-legacy/wp-get-frame", + "WritePro/commands-legacy/wp-get-header", + "WritePro/commands-legacy/wp-get-links", + "WritePro/commands-legacy/wp-get-page-count", + "WritePro/commands-legacy/wp-get-position", + "WritePro/commands-legacy/wp-get-section", + "WritePro/commands-legacy/wp-get-sections", + "WritePro/commands-legacy/wp-get-style-sheet", + "WritePro/commands-legacy/wp-get-style-sheets", + "WritePro/commands-legacy/wp-get-subsection", + "WritePro/commands-legacy/wp-get-text", + "WritePro/commands-legacy/wp-get-view-properties", + "WritePro/commands/wp-import-document", + "WritePro/commands-legacy/wp-import-style-sheets", + "WritePro/commands/wp-insert-break", + "WritePro/commands/wp-insert-document-body", + "WritePro/commands/wp-insert-formula", + "WritePro/commands/wp-insert-picture", + "WritePro/commands-legacy/wp-insert-table", + "WritePro/commands-legacy/wp-is-font-style-supported", + "WritePro/commands-legacy/wp-new", + "WritePro/commands-legacy/wp-new-bookmark", + "WritePro/commands-legacy/wp-new-footer", + "WritePro/commands-legacy/wp-new-header", + "WritePro/commands-legacy/wp-new-style-sheet", + "WritePro/commands-legacy/wp-new-subsection", + "WritePro/commands-legacy/wp-new-text-box", + "WritePro/commands-legacy/wp-paragraph-range", + "WritePro/commands-legacy/wp-picture-range", + "WritePro/commands-legacy/wp-print", + "WritePro/commands/wp-reset-attributes", + "WritePro/commands-legacy/wp-select", + "WritePro/commands-legacy/wp-selection-range", + "WritePro/commands/wp-set-attributes", + "WritePro/commands-legacy/wp-set-data-context", + "WritePro/commands-legacy/wp-set-frame", + "WritePro/commands-legacy/wp-set-link", + "WritePro/commands-legacy/wp-set-text", + "WritePro/commands-legacy/wp-set-view-properties", + "WritePro/commands/wp-table-append-row", + "WritePro/commands-legacy/wp-table-delete-columns", + "WritePro/commands-legacy/wp-table-delete-rows", + "WritePro/commands-legacy/wp-table-get-cells", + "WritePro/commands-legacy/wp-table-get-columns", + "WritePro/commands-legacy/wp-table-get-rows", + "WritePro/commands-legacy/wp-table-insert-columns", + "WritePro/commands-legacy/wp-table-insert-rows", + "WritePro/commands-legacy/wp-table-merge-cells", + "WritePro/commands-legacy/wp-table-range", + "WritePro/commands-legacy/wp-table-split-cells", + "WritePro/commands-legacy/wp-text-range", + "WritePro/commands-legacy/wp-use-page-setup" ] } ] }, { "type": "category", - "label": "Menus", + "label": "4D AIKit", "link": { - "type": "doc", - "id": "Menus/overview" + "type": "generated-index", + "title": "4D AIKit", + "slug": "/category/4d-aikit", + "keywords": [ + "4D AIKit" + ], + "image": "/img/docusaurus.png" }, "items": [ - "Menus/creating", - "Menus/properties", - "Menus/bars", - "Menus/sdi" + "aikit/overview", + "aikit/asynchronous-call", + "aikit/compatible-openai", + { + "type": "category", + "label": "Classes", + "items": [ + "aikit/Classes/openai", + "aikit/Classes/openaiapiresource", + "aikit/Classes/openaichatapi", + "aikit/Classes/openaichatcompletionsapi", + "aikit/Classes/openaichatcompletionslistparameters", + "aikit/Classes/openaichatcompletionsmessagesapi", + "aikit/Classes/openaichatcompletionsmessagesparameters", + "aikit/Classes/openaichatcompletionsparameters", + "aikit/Classes/openaichatcompletionsresult", + "aikit/Classes/openaichatcompletionsstreamresult", + "aikit/Classes/openaichathelper", + "aikit/Classes/openaichoice", + "aikit/Classes/openaiembedding", + "aikit/Classes/openaiembeddingsapi", + "aikit/Classes/openaiembeddingsparameters", + "aikit/Classes/openaiembeddingsresult", + "aikit/Classes/openaierror", + "aikit/Classes/openaiimage", + "aikit/Classes/openaiimageparameters", + "aikit/Classes/openaiimagesapi", + "aikit/Classes/openaiimagesresult", + "aikit/Classes/openaimessage", + "aikit/Classes/openaimodel", + "aikit/Classes/openaimodellistresult", + "aikit/Classes/openaimodelresult", + "aikit/Classes/openaimodelsapi", + "aikit/Classes/openaimoderation", + "aikit/Classes/openaimoderationitem", + "aikit/Classes/openaimoderationresult", + "aikit/Classes/openaimoderationsapi", + "aikit/Classes/openaiparameters", + "aikit/Classes/openairesult", + "aikit/Classes/openaivision", + "aikit/Classes/openaivisionhelper" + ] + } ] }, { - "type": "doc", - "label": "User Settings", - "id": "Desktop/user-settings" + "type": "link", + "label": "4D Mobile App Server", + "href": "https://github.com/4d-go-mobile/4D-Mobile-App-Server" }, { - "type": "doc", - "label": "Build Application", - "id": "Desktop/building" + "type": "link", + "label": "4D NetKit", + "href": "https://developer.4d.com/4D-NetKit" }, { - "type": "doc", - "label": "Labels", - "id": "Desktop/labels" - } - ] - }, - { - "type": "category", - "label": "Mobile Applications", - "items": [ + "type": "link", + "label": "4D Progress", + "href": "https://doc.4d.com/4Dv20R10/4D/20-R10/4D-Progress.100-7614210.en.html" + }, { "type": "link", - "label": "Go Mobile", - "href": "https://developer.4d.com/go-mobile/" + "label": "4D SVG", + "href": "https://doc.4d.com/4Dv20R10/4D/20-R10/4D-SVG-Component.100-7614300.en.html" }, { "type": "link", - "label": "4D for iOS (archive)", - "href": "https://developer.4d.com/4d-for-ios" - } + "label": "4D Widgets", + "href": "https://doc.4d.com/4Dv20R10/4D/20-R10/4D-Widgets.100-7614949.en.html" + }, + { + "type": "link", + "label": "4D QPDF", + "href": "https://github.com/4d/4D-QPDF?tab=readme-ov-file#readme" + }, + { + "type": "link", + "label": "Go Mobile with 4D", + "href": "https://developer.4d.com/go-mobile/" + }, + { + "type": "link", + "label": "Build4D", + "href": "https://github.com/4d-depot/Build4D?tab=readme-ov-file#readme" + } ] } ]