incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sebastian Mohr <>
Subject RichSelectableText-Component missing?
Date Tue, 20 Nov 2012 12:42:00 GMT

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

[1] RichEditableText-Component:

package spark.components
	import spark.components.RichEditableText;

	public class RichSelectableText extends RichEditableText
		public function RichSelectableText()
			editable = false;

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message