Mailing-List: contact bloodhound-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: bloodhound-dev@incubator.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
MIME-Version: 1.0
Date: Wed, 15 Feb 2012 16:51:12 +0000
Message-ID: 
 <CAKoya93j_3H=9QnJMNpDv653F3SGRja8ow2Y3Ag0tEG3HxfznA@mail.gmail.com>
Subject: Product / Version view
From: Joachim Dreimann <joachim.dreimann@wandisco.com>
To: bloodhound-dev@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1

I have now created HTML mockups for the Product and Version views
within Apache Bloodhound:

Product view: http://dl.dropbox.com/u/59840506/Bloodhound/bh-html/product.html
Version view: http://dl.dropbox.com/u/59840506/Bloodhound/bh-html/version.html

The idea behind both of these is to provide the description and status
of what you are looking at (Product/Version) and a peek into the level
below. When you look at the Product page for example, you'd be allowed
to use the tabs to cycle through different Versions associated with
this. Once you have decided you want to dive deeper into that version,
you click the heading to take you to the version view.

Initial feedback I received said that the user would have expected to
go straight to the Version when clicking on the relevant tab, rather
than just the tab-content changing. My response was that when clicking
on a tab, the tab content should be shown - this interface allows the
user to quickly check different versions when they are unsure which
one to look into further.

I have not had the time yet to fully document the functionality and
setup of these screens, but an initial outline of this will follow
tomorrow in the Wiki:
Product view: https://issues.apache.org/bloodhound/wiki/Ui/Product
Version view: https://issues.apache.org/bloodhound/wiki/Ui/Version

As a side note, some of the links between the mockups now also work.
The idea behind that is that once a few more screens are designed we/I
will be able to test how well navigating for use cases works.