click here for details... Sakai Executive Director Position Search now open
Issue Details (XML | Word | Printable)

Key: SAK-12870
Type: Task Task
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Noah Botimer
Reporter: John Leasia
Votes: 0
Watchers: 3
Operations

If you were logged in you would be able to see more operations.
Sakai

Add ability to move to top or bottom with one click in customize tabs

Created: 30-Jan-2008 07:41   Updated: 24-Nov-2009 09:01
Component/s: Preferences, Tab Management
Affects Version/s: 2.2.0, 2.2.1, 2.2.2, 2.2.3, 2.3.0, 2.3.1, 2.3.2, 2.4.0, 2.4.1, 2.5.0, 2.5.2
Fix Version/s: 2.6.0

Time Tracking:
Not Specified

File Attachments: 1. GZip Archive SAK-12870_2-3-x.tar.gz (7 kB)

Image Attachments:

1. tab-enhancement.jpg
(54 kB)
Issue Links:
Relate
 

2.6.x Status: None
2.5.x Status: None
2.4.x Status: None


 Description  « Hide
Users with hundreds of tabs have to click hundreds of times to move a site in the list from top to bottom. Add a double arrow up and down so that they can move all the way to the top or bottom. Also allow multiple selections to work , so that you could move 5 courses to the top of the list or bottom.

 All   Comments   Work Log   Change History   Subversion Commits   git Commits      Sort Order: Ascending order - Click to sort in descending order
Peter A. Knoop added a comment - 30-Jan-2008 08:32
I'm sure this is pobably included, but don't overlook the multiple selections working with more than just the move to the absolute top or bottom of the list. It should work with the single-step arrows too. For instance, if you want to move a single item a distance in the list, you should be able to multiple-select a group, and then move that group "one step" in order to move a single adjacent item above/below that group

Noah Botimer added a comment - 30-Jan-2008 10:16
This is implemented and getting a final UI review. The feature works as follows:

When using absolute movement, all selected items are moved to top or bottom, in a contiguous group, in their original order.

When using incremental movement:
 * Single items are swapped with the next item in the selected direction (or staying at the top/bottom)
 * Groups are moved, intact, and in order by one slot. Any gaps in selection are preserved unless moving against the top or bottom. In this case, the group is compressed with successive clicks, approaching the behavior of absolute movement.

Noah Botimer added a comment - 24-May-2008 13:35
Attaching a bundle to apply to 2.3.x. See the README inside for the very simple details.

Noah Botimer added a comment - 27-May-2008 12:42
This change has been made across 2.3.x, 2.4.x, 2.5.x, and trunk. The 2.4.x and 2.5.x versions have their own branches under user and the 2.3.x version is attached here. The trunk version (SAK-12870 branch) should be merged to trunk and verified on a nightly that does not have the DHTML more sites menu enabled.

Noah Botimer added a comment - 27-May-2008 14:38
Attaching screenshot of change, highlighting move to top and move to bottom functions and multiple selection.

Peter A. Knoop added a comment - 10-Aug-2008 05:11
Noah, I see the check-ins to trunk from the SAK-12870 branch, however, I don't see similiar check-ins for the 2.4.x and 2.5.x branches from their flavours of the SAK-12870 branch. (I also still see None as the 2.4.x and 2.5.x statuses.) Do those other SAK-12870 branches still need to be merged to the respective maintenance branches?

Noah Botimer added a comment - 12-Aug-2008 11:26
Peter: Since there are UI and behavior changes, we declined to request merge to the maintenance branches. However, there are patches that can be picked up for 2.3, 2.4, and 2.5. Please advise on appropriate fix/affects versions.

Peter A. Knoop added a comment - 13-Aug-2008 18:55
Gotcha, so its only fixed directly in trunk, so 2.6 is the only fix version needed. For the other versions folks will have to manually obtain and install the appropriate code you've made available.

Tim Hull added a comment - 08-Jan-2009 13:56
This says that it is fixed in 2.6.0-alpha02, but I'm not seeing it fixed in that release. Is it indeed fixed (and something is wrong with the test server I'm using), or is this only resolved in trunk?

Tim Hull added a comment - 09-Jan-2009 13:37
I'm reopening this because it doesn't seem fully fixed. In 2.6.0-alpha02 one does see the updated Customized Tabs screen when Preferences is opened. However, this screen doesn't work at all - if you press any of the buttons the updated screen disappears and the old one appears. As such, it seems that the code is not fully integrated - at least on alpha-02.

Peter A. Knoop added a comment - 02-Mar-2009 09:34
[Bulk Comment] This is issue is currently scheduled to be resolved for inclusion in the Sakai 2.6.0 release, however, it is still unresolved. If you still planning on resolving it, please reply with a comment indicating when you expect to have it resolved. If you don't think you will be able to address this issue in time for the release, please reply with a comment indicating such; particularly if this issue is Blocker or Critical priority. If the resolution of this issue is to be delayed until a future release (i.e., 2.7), then please update the Fix Version accordingly.

Noah Botimer added a comment - 20-May-2009 11:26
Marking this as fixed. The feature is implemented as intended, though it does not appear properly when using the DHTML More Sites drop-down. The feature should be verified as a part of the final 2.6.0 QA sweep. A new issue has been created to track the consistency between the modes, which may involve some design and semantic considerations -- SAK-16376.