[prev in list] [next in list] [prev in thread] [next in thread]
List: kfm-devel
Subject: Re: Proposal: add group sorting filter
From: Mark <markg85 () gmail ! com>
Date: 2013-10-09 15:20:48
Message-ID: CAPd6JnEOJ-mZD-FgsydmgtTXk_S9Hr1wV=nzrWfWHZCibFL_Aw () mail ! gmail ! com
[Download RAW message or body]
On Wed, Oct 9, 2013 at 4:45 PM, Frank Reininghaus
<frank78ac@googlemail.com>wrote:
> Hi,
>
> 2013/10/8 Mark:
> > Hi,
> >
> > I'm using Dolphin' "Show in Groups" for a couple of days now and i must
> say
> > it works awesome! But while using it i began noticing missing certain
> > features. The feature that i'm going to describe in this mail is the
> first
> > one.
> >
> > When grouping is enabled i would like to have an option to sort the data
> > inside the groups in a global manner (so not per group, that would
> become to
> > complicated). My specific use case is grouping and then sorting the
> groups
> > by size, name, date, ... any of the options that is currently available
> > under Control -> Sort By.
> >
> > To make this example more "visible". My current setup groups by "type"
> and
> > then i want to sort the new groups by "date". Right now that is not
> > possible.
>
> Allowing the user to group the files not by the "sort role", but by a
> different "group role" would be possible. But like most features, this
> would come at a price:
>
as usual :)
>
> (a) Besides the existing menu entry "Show in groups", we would need
> another menu "Group by". This would basically be a copy of the "Sort
> by" menu, but should probably have another radio button "Same as sort
> role" or something like that, which is chosen by default and which
> would mean that the current behavior ("group role" == "sort role") is
> used.
>
> (b) Sorting items would have to be done in two stages: First sort by
> the "group role", then identify where the groups start and end, and
> sort these groups separately by the "sort role". Alternatively, one
> could modify the "lessThan" function such that it compares items
> according to the "group role" and uses the "sort role" as the
> fallback. Either way, the code in KFileItemModel will become more
> complex, and some additional code is needed in other places as well to
> provide an interface between the "Group by" menu and the new member
> variables in the model which would control the grouping behavior.
>
Ah damn, that's what i expected and feared. The KFileItemModel class is
already way to complex for my taste to even attempt adding anything more
complicated. I think this feature is very much likable at the very least
but perhaps it's a little too complicated to cram into an already
complicated class. Shall we just leave this as a nice "would like to have"
feature then?
>
> Now my question is: is there any evidence that this feature would be
> so useful to a large user group that cluttering the UI with the
> additional menu and making the code more complex (and thus harder to
> maintain in the future) is justified?
>
> Cheers,
> Frank
>
[Attachment #3 (text/html)]
<div dir="ltr">On Wed, Oct 9, 2013 at 4:45 PM, Frank Reininghaus <span \
dir="ltr"><<a href="mailto:frank78ac@googlemail.com" \
target="_blank">frank78ac@googlemail.com</a>></span> wrote:<br><div \
class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Hi,<br>
<br>
2013/10/8 Mark:<br>
<div><div class="h5">> Hi,<br>
><br>
> I'm using Dolphin' "Show in Groups" for a couple of days now \
and i must say<br> > it works awesome! But while using it i began noticing missing \
certain<br> > features. The feature that i'm going to describe in this mail is \
the first<br> > one.<br>
><br>
> When grouping is enabled i would like to have an option to sort the data<br>
> inside the groups in a global manner (so not per group, that would become to<br>
> complicated). My specific use case is grouping and then sorting the groups<br>
> by size, name, date, ... any of the options that is currently available<br>
> under Control -> Sort By.<br>
><br>
> To make this example more "visible". My current setup groups by \
"type" and<br> > then i want to sort the new groups by "date". \
Right now that is not<br> > possible.<br>
<br>
</div></div>Allowing the user to group the files not by the "sort role", \
but by a<br> different "group role" would be possible. But like most \
features, this<br> would come at a price:<br></blockquote><div><br></div><div>as \
usual :) </div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
(a) Besides the existing menu entry "Show in groups", we would need<br>
another menu "Group by". This would basically be a copy of the \
"Sort<br> by" menu, but should probably have another radio button \
"Same as sort<br> role" or something like that, which is chosen by default \
and which<br> would mean that the current behavior ("group role" == \
"sort role") is<br> used.<br>
<br>
(b) Sorting items would have to be done in two stages: First sort by<br>
the "group role", then identify where the groups start and end, and<br>
sort these groups separately by the "sort role". Alternatively, one<br>
could modify the "lessThan" function such that it compares items<br>
according to the "group role" and uses the "sort role" as the<br>
fallback. Either way, the code in KFileItemModel will become more<br>
complex, and some additional code is needed in other places as well to<br>
provide an interface between the "Group by" menu and the new member<br>
variables in the model which would control the grouping \
behavior.<br></blockquote><div><br></div><div>Ah damn, that's what i expected and \
feared. The KFileItemModel class is already way to complex for my taste to even \
attempt adding anything more complicated. I think this feature is very much likable \
at the very least but perhaps it's a little too complicated to cram into an \
already complicated class. Shall we just leave this as a nice "would like to \
have" feature then?</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
Now my question is: is there any evidence that this feature would be<br>
so useful to a large user group that cluttering the UI with the<br>
additional menu and making the code more complex (and thus harder to<br>
maintain in the future) is justified?<br></blockquote><blockquote class="gmail_quote" \
style="margin:0px 0px 0px \
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><br>
Cheers,<br>
Frank<br>
</blockquote></div><br></div></div>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic