Bug 688474 - RFE: Use a (dynamic) tree to list and pick distros
Summary: RFE: Use a (dynamic) tree to list and pick distros
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Beaker
Classification: Retired
Component: web UI
Version: 0.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified vote
Target Milestone: future_maint
Assignee: Raymond Mancy
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-17 07:36 UTC by Marian Csontos
Modified: 2014-12-08 01:08 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-10-02 05:18:56 UTC


Attachments (Terms of Use)

Description Marian Csontos 2011-03-17 07:36:59 UTC
Picking a distro on "Provision" tab is very inconvenient.
The distros page is much better - at least has a search capability. But it lacks e.g. the ability to pick family and tag from list.

Could we use a (dynamic AJAX?) tree for easier navigation?

May be AJAX would be just an overhead and we could easily cache the whole tree - creating and keeping a separate JS file on server, which would be cached with expiration set to 6 hours or so? This could save CPU and bandwidth as people often access the tree again and again. The file would be regenerated when distro is added/removed/tagged.

/ breed / OS Major / OS Minor / arch / variant / tags

Also showing some marks for tags with name would be advantage.

This would be useful in Reserve page as well.

Sci-Fi?

An advanced graphics:

redhat
+ RHEL3
+ RHEL4
+ RHEL5
+ RHEL6
  + 6.0
    + i386
    + x86_64
      + Server
        + ALL
          + 2010
          + 2011
            + 2011/01
            + 2011/02
            + 2011/03
              + *S* StableDistro1
              + *I* InstallableDistro2
              +     OtherDistro
        + RELEASED
        + STABLE
        + INSTALLS
      + Client
  + 6.1
fedora

Some examples of shiny AJAXy trees here:

  http://www.dreamcss.com/2009/07/9-useful-javascript-and-ajax-tree-menus.html

Comment 1 Marian Csontos 2011-03-17 07:48:57 UTC
> which would be cached [1] with expiration set to 6 hours or so

[1] on the client of course.

Comment 2 Dan Callaghan 2012-10-02 05:18:56 UTC
We now have something very similar to this on the Reserve Workflow page. We have bug 619335 about the Provision tab, I imagine the solution will be to make it use the same UI as we have for the Reserve Workflow.


Note You need to log in before you can comment on or make changes to this bug.