Ensure that indication of locked portlets is *very* clear in the uPortal mock-up
Description
This replaces Fluid-522 which was a subtask of a design review. Created a new implementation task and will recreate the subtasks and close the others (can't move a subtask).
In the uPortal 3 reorderable portlets mock-up, the indication of a locked portlet (currently a padlock icon) is not sufficient. We need to either implement the darkened portlet styling presented in the design mockups, or a popup message saying that the portlet cannot be moved.
dev-iteration33
Environment
None
Activity
Show:
Jonathan Hung May 27, 2008 at 8:10 PM
Visual style of locked portlet more distinct.
Michelle D'Souza May 27, 2008 at 3:33 PM
The locked portlet in the uPortal example looks different from the other portlets.
Anastasia Cheetham May 16, 2008 at 2:55 PM
It seems that this requirement is not necessarily decided on yet. In his email of Wed, 14 May, titled " Re: Finishing the Layout Customizer", Gary wrote
"...I am leaning toward having locked portlets visually be no different than unlocked portlets, with perhaps the one change of replacing the remove icon (the red X) with a lock icon..."
I'm going to reduce this issue from Blocker to Major until the discussion is settled.
This replaces Fluid-522 which was a subtask of a design review. Created a new implementation task and will recreate the subtasks and close the others (can't move a subtask).
In the uPortal 3 reorderable portlets mock-up, the indication of a locked portlet (currently a padlock icon) is not sufficient. We need to either implement the darkened portlet styling presented in the design mockups, or a popup message saying that the portlet cannot be moved.
dev-iteration33