You are viewing an historical archive of past issues. Please report new issues to the appropriate project issue tracker on GitHub.

Feature request #1271: Sort and divide product pop-up menu into sections

Kind feature request
Product wincent.dev
When Created , updated
Status closed
Reporter Greg Hurrell
Tags no tags

Description

The product pop-up menu is starting to get a bit long and unwieldy.

At the very least I should add a "sort order" column to the database so that I can control the order in which items appear in the least (either that or I could explicitly sort alphabetically when I retrieve the list from the database).

Somewhat better would be to actually divide the menu into groups: something like "Consumer products" (Synergy et al), "Developer tools" (Install, perhaps Walrus etc), and maybe "Ruby" (Rails apps, Ruby extensions etc).

Comments

  1. Greg Hurrell

    Status changed:

    • From: New
    • To: Open
  2. Greg Hurrell

    Will have to play with the optgroup HTML element. Note also that the option element supports a disabled attribute, so that could be used to make "headings" within the pop-up.

  3. Greg Hurrell

    Will probably want to two fields to the products table: "postion" (an integer specifying display order) and "group" (a string such as "Developer", "Consumer" etc). I could model this as a proper, normalized association (ie with a separate "groups" or "product_groups" table and possible a "through" table as well) but I don't know if it's worth it when all I really want to do is sort the items in a pop-up (and later divide the product listing pages up into sections).

  4. Greg Hurrell

    I think the final category name list is going to be:

    • Consumer
    • Developer
    • Server
  5. Greg Hurrell

    Ok, model changes have been made and products#index updated too.

    Last piece of the puzzle will be the pop-up menus.

  6. Greg Hurrell

    Ok, this is now done and it's definitely a nice UI improvement.

    For now the static product pop-ups (issues#new, issues#edit, and issue search too) are done. The AJAX in-place editing (as in issues#show) still uses the old style (1-level) menu.

  7. Greg Hurrell

    Ok, the AJAX case is now handled too.

    Will mark as closed.

  8. Greg Hurrell

    Status changed:

    • From: open
    • To: closed
Add a comment

Comments are now closed for this issue.

Menu