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.212.47 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <073.22cbd29bca7f36a5c6331d575709d440@incubator.apache.org>
References: <058.57224df07188c14f36645fb9758197c6@incubator.apache.org>
	<073.22cbd29bca7f36a5c6331d575709d440@incubator.apache.org>
Date: Wed, 3 Oct 2012 14:50:35 -0500
Message-ID: 
 <CAGMZAuMtFY4cRmB8UBOp9JwTi8_00zADFZo5zfeiBQj1wusejw@mail.gmail.com>
Subject: Re: [Apache Bloodhound] #146: Inline editing of objects
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 10/3/12, Apache Bloodhound <bloodhound-dev@incubator.apache.org> wrote:
> #146: Inline editing of objects
[...]
> Comment (by olemis):
[...]
>
>  New features
>  are :
>
>    1. Wiki toolbar buttons are usable now
[...]
>    1. In  place edits take place and are reflected correctly in the UI .
[...]

At the moment major pending improvements related to this ticket are :

  - Decide how to notify in-place modifications (verbose vs quiet ,
configurable ? , ...)
  - Do not show =ABClick to edit=BB placeholder in assigned wiki textarea f=
ields
  - In-place editors for description (+ tags) inside well
  - Implement in-place editing for ticket view inside a single component
  - Error handling
  - Recovery strategy

About the later , there should be informative elements to know whether
in-place submission failed (e.g. on collisions ... ) . What about at
least using validation states [1]_ to highlight in the UI ticket
fields for which submission failed .

.. [1] Validation states
        (http://twitter.github.com/bootstrap/base-css.html#forms)

--=20
Regards,

Olemis.

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

Featured article: