Enter your feature wish or bug report

Sort columns in preset browser

Sort via columns (author, preset name, tags, ratings) upwards and downwards.

14 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Jakob RangAdminJakob Rang (Founder, Cableguys) shared this idea  ·   ·  Admin →

    5 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • Jakob RangAdminJakob Rang (Founder, Cableguys) commented  · 

        @jasonswe: If you have more wishes for improving the browser, we are of course happy and interested if you create entries (or mail us).

      • Jakob RangAdminJakob Rang (Founder, Cableguys) commented  · 

        So this seems to be the next thing we do (it has less votes than others, but is only little work to do, so that's the biggest bang for the buck).

      • jasonswejasonswe commented  · 

        Disregard the previous comment, I forgot that we receive new votes upon implementation of a feature request in Curve. I feel this is soon to become an extremely important addition for the purpose of organization. Would also like a tag implemented for patch design works in-progress or capability of assigning custom tags. I vote for general browser enhancements across the board ;) So I throw 3 full votes into the pot.

      • jasonswejasonswe commented  · 

        I won't waste votes on this because I feel it should automatically be implemented...and soon, because the library is growing rapidly and it is a real pain to relocate patches at times. Thank you.

      • Jakob RangAdminJakob Rang (Founder, Cableguys) commented  · 

        This feature has a time estimate of: 1

        The order in which we implement features is determined by the "bang". This is your votes divided by a time estimate (specification + implementation time).

        A simple feature will have a time estimate of "1". A more complex feature that takes 20 times as long to implement has an estimate of "20", and needs 20 times as many points as the simple one before we address it.

        Of course the bang is not the only thing that influences us, we also see our role in making the final decision. But we need strong arguments if we postpone a feature with a high bang.

      Feedback and Knowledge Base