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 gary.martin@wandisco.com
 designates 209.85.214.47 as permitted sender)
Message-ID: <506DB268.5060908@wandisco.com>
Date: Thu, 04 Oct 2012 16:59:36 +0100
From: Gary Martin <gary.martin@wandisco.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:15.0) Gecko/20120912 Thunderbird/15.0.1
MIME-Version: 1.0
To: bloodhound-dev@incubator.apache.org
Subject: Re: [Apache Bloodhound] #146: Inline editing of objects
References: <058.57224df07188c14f36645fb9758197c6@incubator.apache.org>
 <073.22cbd29bca7f36a5c6331d575709d440@incubator.apache.org>
 <CAGMZAuMtFY4cRmB8UBOp9JwTi8_00zADFZo5zfeiBQj1wusejw@mail.gmail.com>
 <506D6C76.1090505@wandisco.com>
 <102201E8-01B8-4785-A126-F4463B3DBEF5@wandisco.com>
In-Reply-To: <102201E8-01B8-4785-A126-F4463B3DBEF5@wandisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 04/10/12 16:54, Joachim Dreimann wrote:
> On 4 Oct 2012, at 12:01, Gary Martin <gary.martin@wandisco.com> wrote:
>>> On 03/10/12 20:50, Olemis Lang wrote:
>>>    - Decide how to notify in-place modifications (verbose vs quiet ,
>>> configurable ? , ...)
>> Does this mean that each change individually updates the ticket on the server? I thought that we would be going with users submitting all changes once they are happy with the new state of the ticket.
>>
> I would expect every radio button / drop down change to save immediately, users should only need to confirm textfields or similar where incomplete information would be very likely if we save after every letter or when the box loses focus.
>
> Joe
>

I don't like the inconsistency there. Personally I would store up the 
changes, marking which fields are altered in some way and provide a 
means to submit those changes as a set.

Cheers,
     Gary