From dev-return-2658-apmail-bloodhound-dev-archive=bloodhound.apache.org@bloodhound.apache.org Thu May 2 22:32:22 2013 Return-Path: X-Original-To: apmail-bloodhound-dev-archive@www.apache.org Delivered-To: apmail-bloodhound-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9DBA010D07 for ; Thu, 2 May 2013 22:32:22 +0000 (UTC) Received: (qmail 29032 invoked by uid 500); 2 May 2013 22:32:22 -0000 Delivered-To: apmail-bloodhound-dev-archive@bloodhound.apache.org Received: (qmail 28998 invoked by uid 500); 2 May 2013 22:32:22 -0000 Mailing-List: contact dev-help@bloodhound.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@bloodhound.apache.org Delivered-To: mailing list dev@bloodhound.apache.org Received: (qmail 28988 invoked by uid 99); 2 May 2013 22:32:22 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 May 2013 22:32:22 +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 209.85.210.171 as permitted sender) Received: from [209.85.210.171] (HELO mail-ia0-f171.google.com) (209.85.210.171) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 May 2013 22:32:16 +0000 Received: by mail-ia0-f171.google.com with SMTP id r13so891250iar.30 for ; Thu, 02 May 2013 15:31:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type:content-transfer-encoding; bh=Mmy3os9iikK0Rqpck4RihYaXVRzm45yFTBrHKTflF/4=; b=TMCphtvblZ4LRtjaR4rLTDL0IQtpt64v9bZY8rrlSYraWa5v3Yl1f29M2z93H6SglI VoW1SakfzhRawdpG05iWgIhgAeSCyzxqT10doE2HMX+8ejVHb/Mey4up+RrY4k/4ylf1 9mEcYYPuV8URU2dEcvggU5ojTLUuS+QiTgpee4tvosbsMeJ7qnRDvbv7GgjLnDLmFnH7 kFQNbaONNTbyW+5caJoI7mPFmyoregR0seNNiPU0zh06jtwRZckhkJku4ImOT/5od4sg iU+Mwlm29a2pmSa+ollfyiMyGO6tpWLal2dx7B7PfRx5jcDENxVumlhMlwUYpTIl1kQa 0H3w== MIME-Version: 1.0 X-Received: by 10.50.77.33 with SMTP id p1mr4482717igw.36.1367533915331; Thu, 02 May 2013 15:31:55 -0700 (PDT) Received: by 10.50.130.14 with HTTP; Thu, 2 May 2013 15:31:55 -0700 (PDT) In-Reply-To: References: <20130430105859.BD45523888E4@eris.apache.org> Date: Thu, 2 May 2013 17:31:55 -0500 Message-ID: Subject: Re: svn commit: r1477551 - in /bloodhound/trunk: bloodhound_dashboard/ bloodhound_dashboard/bhdashboard/widgets/ bloodhound_dashboard/bhdashboard/widgets/templates/ bloodhound_theme/bhtheme/htdocs/ bloodhound_theme/bhtheme/templates/ From: Olemis Lang To: dev@bloodhound.apache.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org On 5/2/13, Matev=C5=BE Brada=C4=8D wrote: > On 1. May, 2013, at 3:00, Olemis Lang wrote: >> On 4/30/13, matevz@apache.org wrote: >>> Author: matevz >>> Date: Tue Apr 30 10:58:59 2013 >>> New Revision: 1477551 >>> >>> URL: http://svn.apache.org/r1477551 >>> Log: >>> Ticket relations widget - initial implementation >>> >> >> I'm really excited to see this >> :) > > Glad to hear it. =3D) > It's currently in very basic form, but should improve soon. > :) Good work . I look forward to see more >> >> Is there a chance to move these ticket relations widgets on to BH >> Relations plugin ? [...] > > I'm all for decoupling, but I ran into some issues when the widget > was placed into bhrelations plugin. I'll recheck what it was and > try to resolve it. ok ... > Same goes for the ProductWidget which should > be moved to multiproduct plugin. > + > BTW, is the dashboard prerequisite for all other BH plugins? Once upon a (long) time we had two options wrt common assets : 1. a whole new (plugin | lib) for common assets 2. include common assets and reusable code in BH Dashboard plugin ... and we chose (2) . Since that moment , yes , BH Dashboard is a required dependency . > Can it be turned off, but still have e.g. multiproduct support > enabled? I'm tempted to say =C2=ABno=C2=BB . In a few words : Twitter Bootstrap file= s (i.e. an instance of common assets ;) are contributed by BH Dashboard plugin . However afaicr , at least the first versions of default multi-product templates did not depend upon bootstrap styling . BH Theme plugin was in charge of installing Bootstrap-specific MP look and feel . > AFAICS, the widgets won't render without dashboard, > but I'm not 100% sure. > Widgets are a derivative of dashboard concept . Indeed the later may be defined as the combination of layout(s) + widget(s) . So there are no dashboards without widgets (and layouts) , from an architectural perspective . --=20 Regards, Olemis.