Page History
...
- 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 (needs https://git.magnolia-cms.com/users/apchelintcev/repos/main/commits/b071e67ae64e4bf0199478e610e834df20777568 in order to fix an issue with
LazyNodeWrapperor multiform(s) will be saved only if the parent node has pending changes too)
Here's an example of how data are stored in JCR
...
Overview
Content Tools