Harden various editor implementations/incarnations (MGNLUI-5407)

[MGNLUI-5419] Replace search box with filters in chooser dialog Created: 11/Oct/19  Updated: 24/Mar/20  Resolved: 13/Nov/19

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: None
Fix Version/s: 6.2

Type: Sub-task Priority: Neutral
Reporter: Federico Grilli Assignee: Federico Grilli
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Screenshot 2019-10-14 at 17.06.41.png    
Issue Links:
relation
is related to MGNLUI-5426 Harmonize light and strong dialogs Closed
is related to MGNLUI-5765 Chooser filters don't work in tree view Closed
Template:
Documentation update required:
Yes
Date of First Response:
Sprint: UI Framework 8, UI framework 9, UI Framework 10, UI Framework 11

 Description   

Chooser's visuals are not production ready. See https://app.zeplin.io/project/5acc848ede054e0a4865f805/screen/5b10fa30e585a8f99a820dc4

What to do with the search box? In m5 realm it was implemented as a so-called content tool and in case of JCR it would fire up a full-text search. 

  • Can we use column filters (better)? Or maybe a composition of workbench and search box UI?


 Comments   
Comment by Anja von Gunten [ 15/Oct/19 ]

yes i think that could work, i have 2 inputs though

  • too many columns for a chooser > i'd say even the name only is enough for a chooser
  • add search icon and placeholder text ("search") in the search input field so that the user knows
Comment by Federico Grilli [ 13/Nov/19 ]

For the docu team: the chooser dialog will automatically display a text filter for its columns assuming none is configured and the column type is String.class. Remind that a chooser can resolve its configuration either by appName or by referring to an existing workbench and datasource.
If a filter is already configured for the column being displayed in the chooser, that will take precedence over the default one.

Generated at Mon Feb 12 09:26:25 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.