[MGNLUI-4127] Applauncher layout without JCR config Created: 19/Jan/17  Updated: 23/May/17  Resolved: 03/Feb/17

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

Type: New Feature Priority: Neutral
Reporter: Espen Jervidalo Assignee: Roman Kovařík
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 0.5h
Original Estimate: Not Specified

Attachments: PNG File screenshot-1.png    
Issue Links:
Relates
supersession
Template:
Acceptance criteria:
Empty
Documentation update required:
Yes
Date of First Response:
Sprint: Kromeriz 81
Story Points: 5

 Description   

The only thing missing for an app to be hot-registered during startup or runtime without storing data in JCR is the AppLauncher layout configuration. This should not be necessary. The configuration needed to have the app displayed in the launcher should either be part of the app-descriptor or derived from default settings. The ability to re-arrange and possibly hide apps should not be lost, so this is not about deprecating the applauncher config altogether.



 Comments   
Comment by Mikaël Geljić [ 19/Jan/17 ]

my 2¢: file on webapp/overlay level would make sense, as the integration point for all modules—eventually externalizable via magnolia.properties; that layout should be considered a blueprint, modules in particular shouldn't even have to do anything there.
For what it's worth, the CKEditor toolbar config (pardon the reference) is such an example.

Last but not least, do we do anything with orphaned apps (and if so, with explicitly excluded vs. omitted apps).

Comment by Roman Kovařík [ 26/Jan/17 ]

ejervidalo

The configuration needed to have the app displayed in the launcher should either be part of the app-descriptor or derived from default settings

So the app will be added automatically if it's not part of the JCR layout config, e.g. to a default group, right?

mgeljic

my 2¢: file on webapp/overlay level would make sense

That looks like something different then the description of the ticket. So we'd have the JCR layout config plus a config by file? How is goes with "this is not about deprecating the applauncher config altogether."? How it would be merged?

modules in particular shouldn't even have to do anything there

So there'd be only the groups layout? What's the advantage compared to the current JCR config?

do we do anything with orphaned apps

Could we define a list of excluded apps?

rkovarik
I don't know if you had a discussion about this elsewhere but for me it looks like everybody wants something different

Comment by Mikaël Geljić [ 26/Jan/17 ]

everybody wants something different

—which is why the ticket is about coming up with a concept. Title and first sentence of the description (describe the issue, not the solution) leave it open enough imo.

Re: deprecation, you could imagine for instance that if node exists at /modules/ui-admincentral/config/appLauncherLayout then it keeps precedence... but to me, yes we deprecate it.
The overall layout cannot be driven by individual apps, unless you want to give them a group name and a silly weight.

So there'd be only the groups layout?

—No no, both apps and groups. I meant there should no longer be anything like MVHs or module startup adding apps into the launcher.

Re: default group, excludes, these are ideas worth digging imo.
Do feel free to make up your own mind about it, keep going!

Comment by Espen Jervidalo [ 26/Jan/17 ]

https://wiki.magnolia-cms.com/display/ARCHI/2017-01-26+Meeting+notes

Comment by Evzen Fochr [ 01/Feb/17 ]

After fist logout/login after changing of hiddenApps i got duplicates apps in applauncher

EDIT: After instance restart, I can't reproduce this one

Comment by Evzen Fochr [ 01/Feb/17 ]

After login as eric, i see apps that are defined in groups disabled for user by group permissions.

Comment by Roman Kovařík [ 16/Feb/17 ]

mdrapela
If property defaultGroup=defaultGroupName is added to the app launcher config, apps which are not added to the layout explicitly are added automatically.
defaultGroupName has to be a name of a group configured under groups.
You can still hide unwanted apps by adding hiddenApps node with app names as properties:anAppWhichIDontWantToShowInTheApplauncher=appName

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