[MGNLUI-4474] Tune the presentation of the browser UI Created: 16/Apr/18  Updated: 25/Jul/18  Resolved: 02/Jul/18

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

Type: Story Priority: Neutral
Reporter: Christopher Zimmermann Assignee: Oanh Thai Hoang
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 7.75d
Original Estimate: Not Specified

Attachments: Zip Archive decorate-tour-example.zip     PNG File expect-hello-app.png     Zip Archive hello-contentType.zip     PNG File image-2018-06-29-09-18-01-884.png     PNG File orderIsCorrect.png     PNG File output.png     PNG File overridingWORKS.png     PNG File tree-view.png    
Issue Links:
dependency
depends upon MAGNOLIA-7343 Respect order of keys coming from dec... Closed
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)
Release notes required:
Yes
Documentation update required:
Yes
Date of First Response:
Epic Link: Content types Developer Preview
Sprint: Saigon 148
Story Points: 8

 Description   

User story:

As a Developer, I can tune the default presentation of the browser UI, independently of the actual data model, so that the browser UI will work the best for my authors.

Acceptance criteria:

  • If a developer specifies nothing - the browser UI has a sensible default configuration.
  • A developer can specify the default presentation of the browser UI for the content type:
    • which columns are displayed, their order, and the width of the columns.
    • which column formatters are used.
    • which views are displayed, and the default view.
  • The browser UI is rendered based on the configured values.


 Comments   
Comment by Oanh Thai Hoang [ 28/Jun/18 ]

Here is module example for auto-generation hello-contentType.zip It already includes the config to decorate orders of columns, views and actions

Note: You still need to configure helloContentType to app-launcher at current time 

 

Expect app: 

  • list view  
  • tree view 
Comment by Dai Ha [ 03/Jul/18 ]

Verified, app with browser sub-app generated/updated upon yaml added/changed

Comment by Hieu Nguyen Duc [ 03/Jul/18 ]

Reordering "actions" using "!override" works but the result also includes other nodes. This seems like a bug of the directive.

Comment by Hieu Nguyen Duc [ 04/Jul/18 ]

We just found out the "!override" works correctly but it needs to be put exactly at the map "actions", which contains the action nodes.

!inherit:pizza-app
label: Pizza Improved
icon: icon-people
subApps: !override
  browser:
    subAppClass: info.magnolia.ui.contentapp.browser.BrowserSubApp
    class: info.magnolia.ui.contentapp.browser.BrowserSubAppDescriptor
    actions: !override # HERE, NOT THERE!
      editFolder:
        dialogName: ui-framework:folder
        icon: icon-edit
        class: info.magnolia.ui.framework.action.OpenEditDialogActionDefinition
        availability:
          writePermissionRequired: true
          rules:
            - name: IsNotDeletedRule
              implementationClass: info.magnolia.ui.framework.availability.IsNotDeletedRule
      addFolder:
        icon: icon-add-folder
        class: info.magnolia.ui.framework.action.AddFolderActionDefinition
        availability:
          writePermissionRequired: true
          root: true
          rules:
            - name: IsNotDeletedRule
              implementationClass: info.magnolia.ui.framework.availability.IsNotDeletedRule
      activate:
        command: activate
        icon: icon-publish
        catalog: versioned
        class: info.magnolia.ui.framework.action.ActivationActionDefinition
        availability:
          writePermissionRequired: true
          rules:
            - name: IsNotDeletedRule
              implementationClass: info.magnolia.ui.framework.availability.IsNotDeletedRule

Result:

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