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
Sender: peter@xlii.si
In-Reply-To: 
 <CAGMZAuNskn6uXKuumjTQOFuKSOU-sZOD6Vfa6XeJAiUDicx=Lg@mail.gmail.com>
References: <506DA300.4010002@wandisco.com>
	<CAKE9Bs_4kYaTtJBMcoma_ANwEtHpb9TyNUJQqYaqvhtDXi2CkA@mail.gmail.com>
	<CAGMZAuNskn6uXKuumjTQOFuKSOU-sZOD6Vfa6XeJAiUDicx=Lg@mail.gmail.com>
Date: Mon, 8 Oct 2012 10:39:02 +0200
Message-ID: 
 <CAKE9Bs9VGmRUV_QqgNS9uzWH55F3ifLPon-O6cA7JTF_4jy0iQ@mail.gmail.com>
Subject: Re: dashboard ticket query ordering
From: =?UTF-8?Q?Peter_Ko=C5=BEelj?= <peter@digiverse.si>
To: bloodhound-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=e89a8f3b9f7d59aaf904cb8827f8

--e89a8f3b9f7d59aaf904cb8827f8
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Totally agree on REST api thing! Ideally all data that UI displays should
come through REST web services.
That would give us complete freedom on UI front (UX, multidevice,
technology) and would make Bloodhound easier to integrate into enterprise
environments.

Peter

On Fri, Oct 5, 2012 at 5:27 PM, Olemis Lang <olemis@gmail.com> wrote:

> On 10/5/12, Peter Ko=C5=BEelj <peter@digiverse.si> wrote:
> > If we are only talking about ordering, why not just enhance the widgets
> so
> > that if the user clicks on a column title, that is the field that the
> > results are sorted by?
>
> +1 ... we'll need them to become more AJAX-ready because IMO this
> should happen without leaving dashboard page . Besides changing order
> is not just about sorting the same rows displayed in first place but
> the whole query result set .
>
> If this has not been implemented before is just because there was no
> much time available and there were other priorities . Indeed previous
> mockups include similar features requiring dynamic updates , even if
> not exactly sorting by field .
>
> OTOH ... we shall see how to make this work with reports ... if not
> already implemented , of course . We'll have to check that .
>
> This , together with #146 and a few more tickets makes me wonder
> whether we should be thinking in adding some generic RESTful
> infrastructure , based on known APIs (e.g. XmlRpcPlugin) . This would
> be quite important to implement dynamic AJAX widgets and speed up the
> process .
>
> > What is in dashboard definition would only be the
> > default then.
> >
>
> +1
>
> > In to long run we need user configurable dashboard
>
> +1
>
> > as well as user
> > configurable widgets.
> >
>
> that's what #83 is for , afaicr .
>
> --
> Regards,
>
> Olemis.
>
> Blog ES: http://simelo-es.blogspot.com/
> Blog EN: http://simelo-en.blogspot.com/
>
> Featured article:
>

--e89a8f3b9f7d59aaf904cb8827f8--