What you have is correct for getting selectable, non-editable text. If you would like a helper class then you should create one for your projects. I don't think this belongs in the SDK.
Carol On 11/20/12 8 :40AM, "Sebastian Mohr" <flex.masul...@gmail.com> wrote: >Hi Maxime, > >Sure ... this code is ballshoot ;) It's just a personal Helper-class >because we are trying to avoid writing editable="false" everywhere: > > <s:RichEditableText > text="SELECT ME" > editable="false" > /> > >... and, for some reasons, this RichSelectableText >behaviour is needed fairly often in these projects :( > > >Sincerely Yours, > >Sebastian Mohr >Apache Flex Developer (PPMC), >Interaction Designer & Musician >http://www.linkedin.com/in/masuland > > > > >On Nov 20, 2012, at 2:23 PM, Maxime Cowez wrote: > >> To answer the question: I'm not sure I can see the point in creating a >> subclass just for the sake of automatically setting a property. The code >> you attached doesn't even prohibit the developer to set the 'editable' >> property back to 'true'. Is that what you're trying to achieve? >> >> >> On Tue, Nov 20, 2012 at 2:11 PM, Maxime Cowez >><maxime.co...@gmail.com>wrote: >> >>> I'll correct myself ;) >>> RichText doesn't appear to be selectable. >>> >>> >>> On Tue, Nov 20, 2012 at 2:08 PM, Maxime Cowez >>><maxime.co...@gmail.com>wrote: >>> >>>> Correct me if I'm wrong, but doesn't RichText do what you describe? >>>> >>>> >>>> On Tue, Nov 20, 2012 at 1:42 PM, Sebastian Mohr >>>><flex.masul...@gmail.com>wrote: >>>> >>>>> Hi, >>>>> >>>>> In a few projects I need the text to be selectable but not editable. >>>>> Therefore, I usually create a RichSelectableText-Component [1] >>>>> that should help me achieving this task. Obviously, this approach >>>>> is not optimal because it's extending from RichEditableText to block >>>>> functionality from its superclass. >>>>> >>>>> What about splitting up the functionality of RichEditableText into 2 >>>>> classes? The proposed new inheritance chain could look like this: >>>>> >>>>> RichEditableText < RichSelectableText < UIComponent >>>>> >>>>> If this proposal is not suitable, would you see a better way? >>>>> >>>>> >>>>> Sincerely Yours, >>>>> >>>>> Sebastian Mohr >>>>> Apache Flex Developer (PPMC), >>>>> Interaction Designer & Musician >>>>> http://www.linkedin.com/in/masuland >>>>> >>>>> >>>>> [1] RichEditableText-Component: >>>>> >>>>> package spark.components >>>>> { >>>>> import spark.components.RichEditableText; >>>>> >>>>> public class RichSelectableText extends RichEditableText >>>>> { >>>>> public function RichSelectableText() >>>>> { >>>>> super(); >>>>> >>>>> editable = false; >>>>> } >>>>> } >>>>> } >>>>> >>>>> >>>>> >>>>> >>>> >>> >
