Mailing-List: contact bloodhound-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: bloodhound-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of olemis@gmail.com designates
 74.125.82.175 as permitted sender)
Received-SPF: pass (google.com: domain of olemis@gmail.com designates
 10.180.90.212 as permitted sender) client-ip=10.180.90.212;
MIME-Version: 1.0
In-Reply-To: 
 <CAKoya90WQFFWfKQEv-r1HMhfVxzJJASEv29JSbkZ3ELsX8mcVg@mail.gmail.com>
References: 
 <CAGMZAuOAKJO2OgkuSMCKnmxR_b5ZJL-qR-JnP23=ehKJmENzQQ@mail.gmail.com>
	<CAKoya908cbvTzX=_w85cR1aZLa8gShscmbHW92vznh_e2BoAKw@mail.gmail.com>
	<CAGMZAuO0TZ7q89SzrXsDHiODkw3GsPz8gHti00z9XpzYP=VL3g@mail.gmail.com>
	<CAGMZAuP2Ti-7MxjD2WeewLoXjHiw5=z8ze6y-2586_+W6b9-mQ@mail.gmail.com>
	<CAGMZAuPEMRBmNVyp8+O_YsVSJLEwvWsNCWfGJKA12DdRaD3vAA@mail.gmail.com>
	<CAGMZAuPUSxUtbAQERzfB-Ngmm0u7YEUPSMKHmBgTDB9_QyqBYg@mail.gmail.com>
	<CAGMZAuNeM6v0eDvp_SYNJHDJJCxUEfg_SdVg6qx4hHMCisw+=A@mail.gmail.com>
	<CAKoya90WQFFWfKQEv-r1HMhfVxzJJASEv29JSbkZ3ELsX8mcVg@mail.gmail.com>
Date: Mon, 20 Feb 2012 17:08:29 -0500
Message-ID: 
 <CAGMZAuNdtqM_aGLr7HwJSpkEf0NUgZ0PdSdSqsp9XgLvwncuHQ@mail.gmail.com>
Subject: Re: Initial version of Bloodhound WAS: Dashboard design,
 Wiki (incl HTML/CSS)
From: Olemis Lang <olemis@gmail.com>
To: bloodhound-dev@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Mon, Feb 20, 2012 at 4:29 PM, Joachim Dreimann
<joachim.dreimann@wandisco.com> wrote:
> I'll address points made throughout the last few Emails by Olemis in
> one below, in chronological order:
>
>> PS: So far bootstrap CSS needs a patch in order to render breadcrumbs co=
rrectly
>
> That's fine. A small, well documented patch is worth a thousand big
> patches, right?
>

wise words

>> I'll move forward and implement a components cloud (widget) so as to com=
plete dashboard UI
>
> Apologies if you've started with this already, but it seems like we'll
> approach this issue differently. Instead of providing the <well>
> </well> for Components, we'll have a button bar above the list of
> tickets that allows you to select this or other options. You can see
> this already on the Version view for example:
> http://dl.dropbox.com/u/59840506/Bloodhound/bh-html/version.html
>

ok , but there are a few things I might not understand quite well ...

> I'll be able to update this for the Dashboard tomorrow.
>

... so maybe I should wait for this to happen
;)

>> - Colors for reports
>> - Styles for timeline events
>> - Context navigation in dashboard page
>> - Links to download widget contents inserted in dropdown
>> =A0menu at widgets header
>
> I would leave the download links out for now. We should definitely
> provide them in the Custom Query and Reports interface though -
> because that's where the user has a whole lot more control over the
> query itself and can therefore easily generate the right information
> to export.
>

ok . I'll hide them ;)

> I'm not quite sure what impacts the other points have? (Styles for
> timeline events,

e.g. icons for each timeline event

> colors for reports?)
>

background-color of rows set considering ticket priority

> In regards to the colors highlighting priority in the Dashboard: I
> much prefer showing high importance via left-alignment in the Priority
> columns of High priority items (while Medium and Low priority are
> aligned right in the column). With the colors you may get in a
> situation otherwise where they constantly repeat for every day, which
> could result in a double rainbow :)
>

ok, I agree . I'll revert that ... and try to add a column containing
dots and colors according to priority value (just like in initial
design ;) in order to see what it'd look like . If you are ok with it
then it stays otherwise dots go away (... just scratching my itch ;)

>> Besides I also added another widget displaying a tag cloud similar to =
=ABProjects=BB in Joachim's proposal .
>
> Oops, sorry! This will most likely be replaced with a button bar, as
> described above (and shown in the Version view). Since you've built it
> though, there may be other places where it could come in handy.
>

ok ... or be embedded inside of the more elaborate version containing
buttons et al.
who knows ? life's beautiful !
;)

--=20
Regards,

Olemis.