Improve handling and look of Page, Area and Component edit bars (MAGNOLIA-4308)

[MAGNOLIA-4336] Implement appearance of optional areas Created: 25/Oct/11  Updated: 22/Mar/12  Resolved: 08/Nov/11

Status: Closed
Project: Magnolia
Component/s: page editor
Affects Version/s: None
Fix Version/s: 4.5

Type: Sub-task Priority: Neutral
Reporter: Andreas Weder Assignee: Espen Jervidalo
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Optional areas.png    
Template:
Date of First Response:

 Description   

Optional areas have to be added first before they can accept components. They may also be removed again.

The mockups show how the edit bars of optional areas present themselves.

  • the "add" button is used to add the optional area, "remove" to remove it again.
  • the button hosting the destructive "remove" operation is to the left of the "new"/"edit" button pair and must be separated from them using whitespace.

Note that "add"/"remove" for adding and removing an optional area contrasts with "new"/"delete" for adding a new and deleting an existing component.



 Comments   
Comment by Espen Jervidalo [ 08/Nov/11 ]

The naming of the actions must be reconsidered imho. The positioning is fixed in SCRUM-497

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