docs: B28 - Form, report design#1667
Merged
Merged
Conversation
Complete the paradigm-tier articles for the form-design / form-views / report-design block (en+ru, line-synchronous). Report_design (was a stub): add a lead definition, section structure (Templates / Automatic design / Template format) and a Language section pointing to the FORM statement (REPORT/REPORTFILES) — the construct that attaches a custom template, not DESIGN. Keeps master's canonical-name template-naming detail. Form_design: extend the default-design hierarchy to match the current auto-layout (FILTERBOX wrapping FILTERS+FILTERCONTROLS before the grid, POPUP under TOOLBARLEFT, CALCULATIONS under TOOLBARRIGHT); add the Calculations base component; correct the default value-cell widths (BOOLEAN 30, object classes 13) against the web-client type code; add the "container is vertical by default" note to EN for EN/RU parity; fix the RU typo вертилальным; keep the numeric-length footnote in both languages. Form_views left unchanged — already a complete, rule-compliant umbrella article (no Language/Examples section, by design). Verified against the server form-design classes (GroupObjectContainerSet, FormContainerSet, GridView) and web-client value-class types; docs-only. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Complete the language-tier articles DESIGN_statement and Pivot_block (en+ru, line-synchronous). DESIGN_statement: fill in every previously-`todo` design-property description across the component / container / property-action / grid / toolbar tables, verified against the design view-proxy / view setter classes. Correct value-types and defaults to match code (auto-derived booleans stated as "depends on ..."; valueOverflowHorz/valueAlignment* type-derived; captionEllipsis TRUE; grid autosize->autoSize binding fix; tabVertical/quickSearch FALSE; grid boxed TRUE; showChangeKey/Mouse FALSE; panelCaption* are plain Logical literals; charWidth/Height default -1 with explanation). Add the FILTER(filterName) selector, the OBJECTS / POPUP / FILTERBOX / FILTERCONTROLS container-type selectors (noting OBJECTS has no per-object-group form), and the reversed / lineShrink / valueClass / captionClass properties. Remove the no-op property/action boxed row. Normalize value-type terminology to "Logical literal" (canonical) and backtick every NULL. Pivot_block: add the CONFIG option (a client-side JS function name overriding the pivot renderer options), shown as `CONFIG configFunction`. Verified against LsfLogics.g (designStatement, componentSelector, container-type rules, pivotOptions) and the proxy/view setter classes; docs-only. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The FORM statement does not "specify the template" — the template is the external jrxml file. Its REPORT / REPORTS / REPORTFILES options specify a property whose value gives the report file NAME, i.e. they choose WHICH report file (template) is used, overriding the default <form>_<group> naming. Reword the Language section accordingly (en+ru). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.