Michael Voříšek

I see what you want - a translation method in ui persistence, which would be invoked from every place where an ui string is built [1]. This is reasonable. In...

With the analysis above, Atk4\Data\Field caption should not be translated. Let's not discuss this case as the best solution might pop out during implementation. What I stress is this: Imagine...

> If you separate into two repos, I think conceptually you in your projects then should set atk4/data model/field captions from your Ui repo when you instantiate them (thus also...

> No, since the translation method requires an identifier we need to update it during refactoring of atk4/core I have also noticed there is some translation logic - https://github.com/atk4/core/tree/develop/src/Translator and...

> It is not justified for that to force people to use i18n always good point still, I do not like `'form.saveButton') ?? 'Save'` as it introduces some semi translation,...

Are you defending translations by ID primary because atk4/i18n does not support is currently? I understand your example with "volume", but as long as you extend the source text +...

slightly related with https://github.com/atk4/ui/issues/1848, I highly support unified look & feel (and impl.)

Initially, I thought this is supported, but not honored by CardDeck. The UserAction is a class defined in atk4/data. This class cannot hold any UI specific information. `icon` is UI...

Also, what would happen if you have errors in more tabs/accordions? I would expect some error icon on the tabs/accordion menus - the "first accordion error" might be an error...

I fully confirm this issue and agree it must be fixed. I however do not agree the implementation with nested `getOwner` is valid and even belive it can crash the...