whipcracks: (Default)
Calamity Jane ([personal profile] whipcracks) wrote in [site community profile] dw_suggestions2012-10-22 10:58 pm

Sort Icon Page by Active/Inactive Status

Title:
Sort Icon Page by Active/Inactive Status

Area:
icons

Summary:
On the View Icons page (and possibly the Upload Icon page) allow a sort option which will group Active/Inactive icons (preferably Active on the top/first page) together for ease of finding them.

Description:
Since there are already sorting options for Keyword and Upload Order, having this additional sorting option would be beneficial for accounts which have had paid or premium status previously and are expired, etc. particularly now that there are permanent icon slots available which increase the overall capacity of an account's icon slots.

I believe the method dictating which icons are left active go by most-used in journals followed by most recently uploaded? (I could be wrong on this, it's just what I've observed). However these options both leave active icons scattered through the overall icon page(s). Although the icon browser does only load active icons IF the user still has a paid, it doesn't help free accounts who may be trying to search out 15 active icons from 100, 250, or even more.

I'm not foreseeing any immediate problems if this were implemented due to the fact that there are other existing sort options, but if anyone spots something I've missed...?

Poll #12197 Sort Icon Page by Active/Inactive Status
Open to: Registered Users, detailed results viewable to: All, participants: 67


This suggestion:

View Answers

Should be implemented as-is.
56 (83.6%)

Should be implemented with changes. (please comment)
2 (3.0%)

Shouldn't be implemented.
1 (1.5%)

(I have no opinion)
7 (10.4%)

(Other: please comment)
1 (1.5%)

[personal profile] alexbayleaf 2012-11-30 01:27 pm (UTC)(link)
There's something in the [site community profile] dw_suggestions FAQ that talks about prioritising suggestions, and why this comm isn't really about that, but just about whether or not the idea is feasible/good at all. Mostly has to do with a volunteer developer commumnity -- if someone really wants to work on this, even if it's not a priority, and it's the only thing they're really interested in working on, we'll hardly try and force them to work on something else. So if the answer is "sure, as long as anyone cares enough to actually work on it" then you should vote yes. Whereas if it's "no, not even if someone volunteers to work on it" then vote "no".