>So, that's why I'm currently exploring trying to put UIComponent on top of >UIBase. It should allow your skin files to work as is, but again, size >and performance may be an issue. And I might hit some other roadblock.
Cause my english is rather bad there sometimes may occur misunderstandings and confusion. So I'd like to clarify my point of view: I'm not sure if a spark-like component set is really needed, especially if it's hard to implement and perhaps less performant. I would go so far to say that I'll probably never port an existing app to FlexJS. Instead of this I'd take the opportunity to redesign and reimplement it. For very big code bases this is probably not an option. At the end it's a balancing act between satisfy Flex developers with its existing code base and inspire also new developers for FlexJS. IMO last could be easier if FlexJS provides minimum one fast and modern UI component set. Yes I know FlexJS depends on Volunteers... ;-) Thanks, Olaf -- View this message in context: http://apache-flex-users.2333346.n4.nabble.com/FlexJS-Some-general-questions-tp11765p11783.html Sent from the Apache Flex Users mailing list archive at Nabble.com.
