Community
Participate
Working Groups
As I played around with the new sorting mechanism, I realized that there is no support for easy sorting in both directions, i.e., if I want to sort a column with numbers in decreasing and increasing order, I have to write two ViewerSorter implementations. I came up with a solution which works pretty good for me, so I suggest adding it to JFace. Maybe it's just to small and easy, so it doesn't make sense to be add it to the platform, but that's up to you...
Created attachment 29113 [details] Part of sorting framework
Created attachment 29114 [details] Part of sorting framework
Created attachment 29115 [details] Part of sorting framework
Created attachment 29116 [details] "snippet kind" demo of sorting framework
I've implemented some small enhancements to this "framework": You can configure the default sorting direction of each column, and you can choose if a column should remember its last sorting direction or not. As I don't want to flood anybodys mailbox by uploading my changes, I let you know this way. If anybody is interested in the code, just drop me an email - I'm happy to send you the current version (or upload it if you want).
we should move all discussion on this to one bug because currently we have 4 I know of: - bug #182791 - bug #166153 - bug #170187 - this one If you want you can hand over the resulting bug to me because I'm eager on implementation this kind of function in 3.4. By the way we also have a snippet which might be a starting point.
(In reply to comment #6) > If you want you can hand over the resulting bug to me Sure - go ahead and mark as duplicate / assign to you as you see fit.
Mass update - removing 3.4 target. This was one of the bugs I marked for investigation (and potential fixing) in 3.4 but I ran out of time. Please ping on the bug if fixing it would be really important for 3.4, and does not require API changes or feature work.
Hitesh is now responsible for watching bugs in the [Viewers] component area.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
