Jagan,
RichEditableText already implements IEditableText which extends IDisplayText. Which explains why RichEditableText has all the methods of IDisplayText. In other words, what you asked seems to be already available. Thanks, Om On Sun, Jul 7, 2013 at 11:26 PM, Jagan Langa Sami Durai <jaga...@sybrant.com > wrote: > And I forget to say YES to the following question > > "It is best to describe the minimal thing you are looking for. Is it just > adding selectable text to RichText?" > > My skinners are going for RichEditableText just for selectable text. > > > On Mon, Jul 8, 2013 at 11:53 AM, Jagan Langa Sami Durai < > jaga...@sybrant.com > > wrote: > > > Hi Alex, > > > > IDisplayText interface does not have anything else other than the > > following declarations, > > > > function get text():String; > > function set text(value:String):void; > > function get isTruncated():Boolean; > > > > except TextInput and TextArea other text based components like Label, > > RichText, RichEditableText have the definitions for declarations found in > > the IDisplayText interface. And in depth TextInput and TextArea uses the > > "IEditableText" interface as its skinpart, which in tern extends the > > "IDisplayText". So it is not a big deal to add "isTruncated()" definition > > in these two components. > > > > > > > > > > On Mon, Jul 8, 2013 at 10:58 AM, Alex Harui <aha...@adobe.com> wrote: > > > >> Having RichEditableText implement IDisplayText so it can be used in > Labels > >> and other places would also require some other work to shutdown some of > >> the editing capabilities. > >> > >> It is best to describe the minimal thing you are looking for. Is it > just > >> adding selectable text to RichText? > >> > >> On 7/7/13 10:13 PM, "Jagan Langa Sami Durai" <jaga...@sybrant.com> > wrote: > >> > >> >Hi All, > >> > > >> >My Requirement is bit different, > >> > > >> >I'm creating a custom component where i have to show a text in it as > part > >> >of the component. Skinning team will create n-number of skin's for that > >> >component based on the user requirement. There they might use any text > >> >based components. So I prefer to use an interface as the SKIN_PART. As > I > >> >examined IDisplayText is the only interface which have very (very) > >> >minimal > >> >method declarations which suits the purpose. (Note: IMHO I thought It > >> will > >> >be better if all the text based components implements at least one > common > >> >interface.) > >> > > >> > > >> >On Fri, Jul 5, 2013 at 8:08 PM, Alex Harui <aha...@adobe.com> wrote: > >> > > >> >> Please file a bug about clickable links in RichText and we'll see if > we > >> >> can find a cheaper way of handling it. I doubt it will happen in > this > >> >> next release. > >> >> > >> >> Are you trying to display HTML or is the source text already in > >> TextFlow > >> >> format? Depending on the HTML, you can use TextField as the display > >> and > >> >> it should allow for clickable links. > >> >> > >> >> On 7/5/13 12:31 AM, "Jagan Langa Sami Durai" <jaga...@sybrant.com> > >> >>wrote: > >> >> > >> >> >I believe user cannot select the text in the RichText. > >> >> > > >> >> > > >> >> >On Fri, Jul 5, 2013 at 12:14 AM, jude <flexcapaci...@gmail.com> > >> wrote: > >> >> > > >> >> >> I don't believe RichText supports hyperlinks. > >> >> >> > >> >> >> On Thu, Jul 4, 2013 at 1:06 PM, Alex Harui <aha...@adobe.com> > >> wrote: > >> >> >> > >> >> >> > > >> >> >> > > >> >> >> > On 7/4/13 4:45 AM, "Jagan Langa Sami Durai" < > jaga...@sybrant.com> > >> >> >>wrote: > >> >> >> > > >> >> >> > >Hi All > >> >> >> > > > >> >> >> > >if the *RichEditableText *also implements *IDisplayText > >> *interface > >> >> >>as * > >> >> >> > >TextBase* class, It will be very handy while creating a custom > >> >> >>component > >> >> >> > >(which may have any kind of text based controls ) for skinning. > >> >> >> > > > >> >> >> > >P.S. RichEditableText class have all the method definitions for > >> >>the > >> >> >> method > >> >> >> > >declarations found in the IDisplayText interface. > >> >> >> > > > >> >> >> > > > >> >> >> > >can we expect this change in the upcoming sdk version ? > >> >> >> > Can I ask about the use case? IDisplayText was intended for > >> >> >>non-editable > >> >> >> > text display. Is there something RichEditableText can do that > >> >>RichText > >> >> >> > cannot? > >> >> >> > > >> >> >> > > >> >> >> > >> >> > > >> >> > > >> >> > > >> >> >-- > >> >> >* > >> >> >Regards, > >> >> >S. Jagan Langa* *|* *Team Lead* > >> >> >*Sybrant Technologies Pvt Ltd* > >> >> >*-------------------------------- > >> >> >* > >> >> >ŒShriram The Gateway (SEZ)¹, Block A1, > >> >> >3rd Floor, 16 GST Road, Perungalathur, > >> >> >Chennai - 600 063, India > >> >> >India | USA | Germany | China > >> >> > > >> >> >Mobile: +91 98430 50897 > >> >> >Skype: seesamjagan > >> >> > >> >> > >> > > >> > > >> >-- > >> >* > >> >Regards, > >> >S. Jagan Langa* > >> > >> > > > > > > -- > > * > > Regards, > > S. Jagan Langa* *|* *Team Lead* > > *Sybrant Technologies Pvt Ltd* > > *-------------------------------- > > * > > ‘Shriram The Gateway (SEZ)’, Block A1, > > 3rd Floor, 16 GST Road, Perungalathur, > > Chennai - 600 063, India > > India | USA | Germany | China > > > > Mobile: +91 98430 50897 > > Skype: seesamjagan > > > > > > -- > * > Regards, > S. Jagan Langa* *|* *Team Lead* > *Sybrant Technologies Pvt Ltd* > *-------------------------------- > * > ‘Shriram The Gateway (SEZ)’, Block A1, > 3rd Floor, 16 GST Road, Perungalathur, > Chennai - 600 063, India > India | USA | Germany | China > > Mobile: +91 98430 50897 > Skype: seesamjagan >
