[MGNLUI-138] ItemSubApp: create new AbstractSubApp class to handle editing of items Created: 05/Nov/12  Updated: 11/Feb/13  Resolved: 04/Dec/12

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

Type: Task Priority: Neutral
Reporter: Espen Jervidalo Assignee: Espen Jervidalo
Resolution: Fixed Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Issue Links:
relation
is related to MGNLUI-339 ActionbarBuilder: check for existing ... Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
MGNLUI-153 ItemSubApp: create action to open sub... Sub-task Closed Espen Jervidalo  
MGNLUI-187 itemsubapp: actions for saving node f... Sub-task Closed Espen Jervidalo  
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:

 Description   

Based heavily on AbstractContentSubApp and ContentWorkbenchPresenter etc.

ContactsItemSubApp has been used as reference implementation. Currently also used in Assets App.

http://wiki.magnolia-cms.com/display/DEV/Concept+-+App+Framework+and+Tabbed+editing+view+of+items



 Comments   
Comment by Jan Haderka [ 27/Nov/12 ]

can be closed once the subtickets are fixed

Comment by Tobias Mattsson [ 03/Dec/12 ]
  • ActionbarBuilder
    • was changing 'Action' to 'ViewType' in the log message intended?
    • the 'actionNames' list is queried but never added to so the check has no effect right?
Comment by Espen Jervidalo [ 04/Dec/12 ]

created new ticket for review remarks

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