Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • (DO)Performance improvements
  • (DO)You can't drop here message should say something about why you can't drop here that allows the user to know why.  Needs to be concise.
    • (AB) Gary and I had come up with: "This box cannot be moved here. The box currently located here is locked."
  • (DO)The green box could look different when it appears where you picked up the portlet than it does when it shows you where it will be dragged?
  • (DO)Allow dragging into anyplace in the column and drop it underneath the last portlet in that column.
  • (AB) Update the Layout Preview design pattern to explain the difficulties of using it with large portlets, and give guidelines for when it should not be used. Also talk about performance requirements and the difficulties of dragging large portlets across the page 'fold' (e.g. perhaps drag and drop may not be appropriate to use with large portlets which must be dragged across a fold.)
  • (AB) Allow dragging and dropping into the region above or below of a column of portlets (e.g. don't require that the user get right next to the portlet above it to drop. This may mean dragging into an empty region at the bottom of a column, or dragging on top of the Welcome message at the top.).
    • (AB) "This box cannot be moved here" warning message should appear if it appears to the user that they are dragging on top of a locked portlet, even if user initially drags the top of the portlet above an area which is not droppable (e.g. the orange "Welcome" text in the testing prototype).
  • (AB) uPortal advice: there are so many links to "Customize" the portal and users aren't sure what they do--try to consolidate them. Perhaps explain how portlets can also be dragged and dropped on the Customize page, as well as how this relates the activities that are performed on this page.
  • Portlet title bar should indicate somehow it can be moved. (Already has other icons that indicate functionality).
  • Warning message not obvious. Could be hard to see against 2 different portlets.