From bloodhound-dev-return-34-apmail-incubator-bloodhound-dev-archive=incubator.apache.org@incubator.apache.org Wed Jan 18 14:28:08 2012 Return-Path: X-Original-To: apmail-incubator-bloodhound-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-bloodhound-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A357BB3ED for ; Wed, 18 Jan 2012 14:28:08 +0000 (UTC) Received: (qmail 27898 invoked by uid 500); 18 Jan 2012 14:28:08 -0000 Delivered-To: apmail-incubator-bloodhound-dev-archive@incubator.apache.org Received: (qmail 27866 invoked by uid 500); 18 Jan 2012 14:28:08 -0000 Mailing-List: contact bloodhound-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: bloodhound-dev@incubator.apache.org Delivered-To: mailing list bloodhound-dev@incubator.apache.org Received: (qmail 27858 invoked by uid 99); 18 Jan 2012 14:28:08 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Jan 2012 14:28:08 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of olemis@gmail.com designates 74.125.82.175 as permitted sender) Received: from [74.125.82.175] (HELO mail-we0-f175.google.com) (74.125.82.175) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Jan 2012 14:28:02 +0000 Received: by werb12 with SMTP id b12so1061849wer.6 for ; Wed, 18 Jan 2012 06:27:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=wG8AZAFoYBAz2HfSN4A9TMTrm6vhQgI86EW5azMThE8=; b=UtPvi+oGEsYzu6LSrZsTQ+Sgb1qALHl+rWJB+RUoe7zwb6sQ9SqfzYI5oWI1KZvsH2 0gxavNpX98f+T1G/JXUQXr1q37p6k19W+qoPSeJCMC0a4Zb91tXMS1N8Ni/CS148HD3b ozmcOJ4iIv1vI2klGdXXU+7BesFAJ+uXpUx7s= MIME-Version: 1.0 Received: by 10.216.139.205 with SMTP id c55mr9242717wej.31.1326896862141; Wed, 18 Jan 2012 06:27:42 -0800 (PST) Received: by 10.223.85.196 with HTTP; Wed, 18 Jan 2012 06:27:42 -0800 (PST) In-Reply-To: <4F16BCE1.40402@wandisco.com> References: <4F15D1DE.7080009@wandisco.com> <4F15D27D.1020300@wandisco.com> <4F16BCE1.40402@wandisco.com> Date: Wed, 18 Jan 2012 09:27:42 -0500 Message-ID: Subject: Re: Bloodhound Theme/Dashboard design From: Olemis Lang To: bloodhound-dev@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org On Wed, Jan 18, 2012 at 7:36 AM, Gary wrote: > On 01/17/2012 09:48 PM, Olemis Lang wrote: >> On Tue, Jan 17, 2012 at 4:37 PM, Olemis Lang =A0wrote: >>> On Tue, Jan 17, 2012 at 2:56 PM, Gary =A0wrot= e: >>>> On 01/17/2012 07:54 PM, Gary wrote: >> >> [...] >>>>> >>>>> In addition to the theme, these images also show an interpretation of >>>>> what >>>>> a multi-project dashboard view could look like and a possible >>>>> quick-create >>>>> ticket functionality. >>>>> >>> About the dashboard ... in an advanced stage of its implementation , >>> it should be similar to others (e.g. Blogger) and allow for selecting >>> multiple widgets (maybe with DnD support ;) and saving that >>> configuration in preferences (users-specific dashboard) and/or admin >>> panel (site-default dashboard view) > > That would be good, yes. There could be some cool features to add to this > dashboard view, depending on how configurable we want it. Probably someth= ing > we might aim for a bit further down the line though. > :) [...] >> Another two aspects : >> >> - I see navigation items are different to those people find in Trac >> =A0 itself (e.g. create ticket in Trac main nav is now in BH context nav= ) . >> =A0 Will site navigation change ? What other similar changes do you >> =A0 have in mind ? > > A good question.. I think that there is value in challenging our ideas in > these areas on the basis of what might be good for a fresh audience. > > We should be looking to existing mechanisms to provide any changes as muc= h > as possible, including existing trac-hacks if required. > In order to change that it will be necessary to (patch / change) Trac core , as e.g. new tickets in metanav is defined in a component provided by Trac distribution ;) >> - Dashboard ctxtnav item is under Ticket section (in mainnav) . >> =A0 Isn't it a much more general concept ? I mean maybe in dashboard >> =A0 there's much more than tickets and e.g. someone prefers to >> =A0 add some other information in there (e.g. QA team inserts build >> =A0 results report) > > I see what you mean. It might be worth considering whether we could have = a > Home dashboard with dashboards available for different menus with differe= nt > perspectives - again, perhaps as a long term goal. > that's a good point . Something like having a global dashboard + separate instances for e.g. each mainnav item I think it's interesting ... or maybe just filtering dashboard items shown considering active mainnav item . Though IMO that should be another subject deserving a whole new separate thread in this ML =A0. ;) -- Regards, Olemis Facebook =3D>=A0http://www.facebook.com/olemis Twitter =3D>=A0http://www.twitter.com/olemislc=A0(@olemislc) Blog ES =3D> http://simelo-es.blogspot.com Blog EN =3D> http://simelo-en.blogspot.com Quora =3D>=A0http://www.quora.com/olemis Youtube =3D> http://youtube.com/user/greatsoftw Featured article : Identificando n=FAmeros primos con expresi=F3n regular e= n Perl http://feedproxy.google.com/~r/simelo-news/~3/BHr859OSndo/identificando-num= eros-primos-con.html Tweet: Identificando n=FAmeros primos con expresi=F3n regular en #Perl http://t.co/0UTEpvt9 #Simelo #blog #fb #comandos Follow @olemislc Reply Retweet =A0=A020:12 Jan-10 =A0=A0Get this email app! Get a signature like this. CLICK HERE.