Page History
...
Reasons to bother | What changes | Outcome |
---|---|---|
|
Possibly we introduce an alternative term 'editor' which is more generic than the form | Benefits
Questions
|
I18N support in dialogs
Solution proposal
- One Binder per Locale, one layout per Locale
- Common non i18n properties share the same Binder (typically the one for the default language configured in Magnolia)
- Layouts are created eagerly and are simply switched when changing language in the UI. Memory consumption should be no issue, cause usually configured languages are just a few - we cache the layouts anyway and don't need to recreate them upon every language switch
- Current implementation at https://git.magnolia-cms.com/users/apchelintcev/repos/ui-framework-vaadin8/commits/5493abd438dd257cbb47ea57df6a6d9287ee605f
Here's an example of how data are stored in JCR
and the UI part
Column definitions
Complex fields
Overview
Content Tools