[MGNLDATA-174] Provide a wrapper app to manage custom node types Created: 09/Apr/13  Updated: 24/Apr/13  Resolved: 15/Apr/13

Status: Closed
Project: Magnolia Data Module (closed)
Component/s: None
Affects Version/s: 2.0
Fix Version/s: 2.0

Type: Task Priority: Critical
Reporter: Federico Grilli Assignee: Federico Grilli
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MGNLDATA-175 DataModule should not add menu entrie... Closed
is related to MGNLUI-1027 Remove pages apps configuration Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Sprint: Iteration 2013-16

 Description   

In 4.x the Data module builds dynamically the menu entries to manage the various custom types. This happens on module startup in the DataModule#registerCustomTypes() method. For each registred custom type the method updateDataMenu(TypeDefinition type) is called which basically creates a button to open a tree with the following code

subMenu.createNodeData("onclick", "MgnlAdminCentral.showTree('" + type.getName() + "')")

Now, wrapping each of those trees with WrapLegacyTreeUIAsMagnoliaAppTask(..) as a M5 app will end up creating a deluge of apps in the app launcher. Methinks, a different approach has to be found in this case.



 Comments   
Comment by Federico Grilli [ 23/Apr/13 ]

The tree handlers missing during review are actually brought in by other modules, i.e. categorisation, rssaggregator.

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