[MGNLUI-4638] Chooser dialog in Vaadin 8 Created: 28/May/18 Updated: 22/Dec/21 Resolved: 20/Sep/18 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.0 |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Aleksandr Pchelintcev | Assignee: | Cedric Reichenbach |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Template: |
|
||||||||||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||||||||||||||||||
| Documentation update required: |
Yes
|
||||||||||||||||||||||||
| Date of First Response: | |||||||||||||||||||||||||
| Epic Link: | UI framework: forms, dialogs, content editing | ||||||||||||||||||||||||
| Sprint: | Basel 153, Basel 154, Basel 155, Basel 156 | ||||||||||||||||||||||||
| Story Points: | 8 | ||||||||||||||||||||||||
| Description |
|
Re-implementation of chooser dialog with Vaadin 8 powered UI framework. New strategy for resolving the definition. Current strategy is rather rigid:
possible solution: However, the link field could point to a content type, maybe JCR workspace, or smth completely custom. That way every link field would be able to have their own unique chooser, but then the burden of creating it will be put on e.g. LinkFieldFactory and not on the respective app. The latter probably not bad, cause it would potentially let us get rid of that hack that starts the app instances without showing their UI (see AppController#startAppWithoutFocusing or similar). Instead of that hack, a dedicated chooser dialog factory (or similar utility) should setup IoC context, find out where the choose dialog definition should come from and then instantiate it. Improvements, can be split into a separate enhancement story:
|
| Comments |
| Comment by Antti Hietala [ 02/Aug/18 ] |
|
Timebox to 5 SP. Create a naive choose dialog implementation. Basically a grid in a Vaadin window, that's it. Possibly leveraging the UI framework view building. |