Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of
 joaopedromartinsfernandes@gmail.com designates 209.85.215.175 as permitted
 sender)
MIME-Version: 1.0
In-Reply-To: <CCDB8D05.49238%aharui@adobe.com>
References: 
 <CAGgUee2P3NsypdjOtTmGaqQUi_im71yZtE6O0yWR1rMo6pu_Xw@mail.gmail.com>
 <CCDB8D05.49238%aharui@adobe.com>
From: =?ISO-8859-1?Q?Jo=E3o_Fernandes?= <joaopedromartinsfernandes@gmail.com>
Date: Wed, 28 Nov 2012 17:55:58 +0000
Message-ID: 
 <CAGgUee3EVT1XgC545MAaZ1kA+pOPVv0sURok5HZdTTDK2X38NA@mail.gmail.com>
Subject: Re: Spark Datagrid editor session ending
To: flex-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=047d7b66f32931603e04cf91e2b8

--047d7b66f32931603e04cf91e2b8
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 28 November 2012 17:42, Alex Harui <aharui@adobe.com> wrote:

>  modify DG to dispatch such an event.
> Another is to provide an alternate item editor that dispatches the event
> from the DG in its save() method.
>
> In the new framework I am rewriting, I would argue for the second option.
> The DG should not waste time dispatching events just-in-case.  You can tu=
rn
> on that capability by choosing a new default renderer.
>

Thanks Alex, in my opinion I would implement the event the same way SAVE
and CANCEL are handled currently but in the future I agree it should be
handled by the ItemEditor instance itself.

I'll log a bug later today with a patch to it.
--=20

Jo=E3o Fernandes

--047d7b66f32931603e04cf91e2b8--