Mailing-List: contact bloodhound-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: bloodhound-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of olemis@gmail.com designates
 209.85.220.175 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <50B75F3C.2050307@wandisco.com>
References: <50A51EA4.5050501@wandisco.com>
	<CAGMZAuN=92d9rggHE9QDe9sn9v1EqeCUd--+NFH44MqaNWZFWQ@mail.gmail.com>
	<CAJSKAsisiLoXckBe-hrNweVKV_obTN6H46hU8FMSLn462aLzQw@mail.gmail.com>
	<CAGMZAuNxUS_iCPSVfLLCixKR3K+HM8KVuUa=gWMME=p8945YhA@mail.gmail.com>
	<50B75F3C.2050307@wandisco.com>
Date: Thu, 29 Nov 2012 10:16:28 -0500
Message-ID: 
 <CAGMZAuN6A4Z-w2r7rYZSOUaQNr=7qiVYGYyVMEz792+gL6REKQ@mail.gmail.com>
Subject: Re: widget macros (ticket #138)
From: Olemis Lang <olemis@gmail.com>
To: bloodhound-dev@incubator.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 11/29/12, Gary Martin <gary.martin@wandisco.com> wrote:
> On 19/11/12 15:36, Olemis Lang wrote:
>> On 11/19/12, Peter Ko=C5=BEelj <peter@digiverse.si> wrote:
>>> First I would like to check if I understand this correctly.
>>> So, this means that a user can embed widgets from dashboard in wiki
>>> pages
>>> or ticket descriptions?
>>>
>> anywhere WikiFormatting is supported , yes . Widgets are enhanced
>> macros in first place.
>>
>>> I do not se any problems with this at the moment
>> cool
>>
>>> but, this can not be a
>>> substitute for user customizable dashboard.
>>> We still need to provide fully customizable dashboard
>> +1
>> for the moment think of it like the replacement to TicketQuery et al.
>> as we use it today on i.a.o . It looks weird to me that we were able
>> to customize those views and we can not embed a similar widget in a
>> wiki page when we need it .
>
> I don't see that it is weird not to be able to do this.

I could find the right word ...

> The advantage is
> if we bring enhancements to the existing functionality. At the moment,
> in terms of TicketQuery vs Widget(TicketQuery, ...) we bring certain
> improvements but not all the functionality yet.
>

what's missing

> At some point, once we get feature parity, we could consider overriding
> TicketQuery so that it uses Widget(TicketQuery,...) instead.
>

fwiw it's possible to have TicketQueryWidget( ... ) rather than
Widget(TicketQuery, ...) . In general , <WidgetName>Widget( ... ) vs
Widget(<WidgetName>, ...)

> Anyway, I'll try to commit the work soon and see where we are as it
> seems to be providing less controversy now given that discussion on this
> was limited.
>

thanks .
I look forward to implement further improvements .

--=20
Regards,

Olemis.

Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/

Featured article: