Response from Deepa and Glenn: a.) We didn't know if a component-level Boolean flag to control editability was necessary (it was the source for a notorious set of hairy issues in Halo List and we were wary of tackling that in Spark)
b.) It was relatively straightforward to extend the component to include the concept of an editable state and author an edit-aware skin. So we're not necessarily providing that subclass of the component out of the box, but it should be easy for you :-) Matt On 2/11/09 9:05 AM, "Matt Chotin" <mcho...@adobe.com> wrote: I'm checking with some folks, but we're not changing the way Halo works so I think you'd consider to be a Spark adjustment. On 2/11/09 12:19 AM, "Gregor Kiddie" <gkid...@inpses.co.uk> wrote: Brief and succinct, like it! Is this being handled under the more general look at Lists and the DG, or under Spark? Gk. Gregor Kiddie Senior Developer INPS Tel: 01382 564343 Registered address: The Bread Factory, 1a Broughton Street, London SW8 3QJ Registered Number: 1788577 Registered in the UK Visit our Internet Web site at www.inps.co.uk <blocked::http://www.inps.co.uk/> The information in this internet email is confidential and is intended solely for the addressee. Access, copying or re-use of information in it by anyone else is not authorised. Any views or opinions presented are solely those of the author and do not necessarily represent those of INPS or any of its affiliates. If you are not the intended recipient please contact is.helpd...@inps.co.uk ________________________________ From: flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] On Behalf Of Matt Chotin Sent: 11 February 2009 00:33 To: flexcoders@yahoogroups.com Subject: Re: [flexcoders] Thanks again to Adobe Ah, sorry, we must have missed that one. Your quesiton was: "Just now, the majority of the functionality ItemEditor provides can be repeated by a ItemRenderer. With Gumbo giving better access to states, is it time to admit that Editing is just a state of the renderer?" I believe the answer is yes :-)
