[MGNLSLOCK-27] As an editor, I can use the soft locking module in Magnolia 5 Created: 25/Nov/13  Updated: 04/Jun/15  Resolved: 04/Jun/15

Status: Closed
Project: Magnolia Soft Locking Module
Component/s: None
Affects Version/s: 2.5
Fix Version/s: 2.5

Type: Story Priority: Major
Reporter: Federico Grilli Assignee: Federico Grilli
Resolution: Fixed Votes: 0
Labels: support
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Appearance of soft-locking tooltip.png     File Soft-locking.mockups.pdf    
Issue Links:
dependency
depends upon MGNLUI-3309 Provide a rich tooltip component Closed
depends upon MGNLSLOCK-32 Port soft locking module to 5.0 Closed
relation
is related to MGNLUI-2805 Implement the new status bar 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)
Date of First Response:

 Description   

See basic concept at http://wiki.magnolia-cms.com/display/DEV/Concept+-+Soft+Locking+for+Magnolia+5



 Comments   
Comment by Andreas Weder [ 15/Jul/14 ]

Note that the new place for soft-locking information to go is the status bar in the footer below the editor. We already shows the publication state there, but we've done so using a hackish solution. When we plan to show additional information, I'd like to see the new, redesigned status bar implemented first.

See: http://jira.magnolia-cms.com/browse/MGNLUI-2805

Comment by Andreas Weder [ 22/Aug/14 ]

I've attached a PDF containing a set of mockups illustrating several aspects of soft-locking and how I intend to solve them. This follows our discussion in the UX cell.

The set consists of three parts.

The first shows the page editor during a regular co-edit: we just indicate somebody else is editing and name that user/those users in the tooltip. I would at max. show the names of three to five users. If more edit, show a gray "more" or "..." line at the end. It really doesn't make sense to show them all.

The second part shows the behavior if one of the concurrently editing users saves his changes. We replace the "group" icon with the black-on-yellow warning alert and also modify the message and possibly looks of the tooltip.

The third part finally shows how the indicator and tooltip could look and work in the page preview, following the discussing we had in the UX cell. As you can see, the wording has to slightly change.

What is an open questio*n to me here, however, is if we actually *when and if we have to show any warning in the page preview. If a client uses versioning, then we actually see a particular version of the page. If I'm a publisher, for instance, that got the task through Pulse to publish a particular version of a page, there's no need to show me a warning; this would actually be confusing. So probably the only safe thing we can do in the preview is to just show the indicator, but never a warning.

Comment by Andreas Weder [ 22/Aug/14 ]

Attached the visual design showing the regular tooltip showing info. The text is wrong (see PDF mockups here instead), but the shape, colors, fonts are what we want.

Comment by Federico Grilli [ 27/Aug/14 ]

Let's keep the story open else it adds to the stack of in progress issues on jira board

Comment by Federico Grilli [ 01/Sep/14 ]

Some styling for the tooltip widget has to be done but the module is basically ready, tests and MVH included.

Comment by Federico Grilli [ 10/Dec/14 ]

It was decided to postpone the release and wait for Magnolia 5.4 which will bring improvements and changes to the page editor and new Vaadin version 7.3. The latter in particular will avoid using the deprecated and no longer actively developed Refresher add-on and instead rely on Vaadin's built-in polling mechanism. In particular, since Vaadin 7.2 http://dev.vaadin.com/ticket/12466 a PollListener has been added to the UI class.

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