--- In flexcoders@yahoogroups.com, "b_alen" <[EMAIL PROTECTED]> wrote: > > I can understand the concept of encapsulation, but we really do need > al the methods that belong to TextField. I would say > getCharBoundaries() is one of the most crucial features in our > everyday life. We do a lot of elearning content with lots of > operations on the text, highlighting, inserting proof reading marks, > changing type face, circling out the words, strike through, everything > has to be dynamic, has to move when deleting / inserting text, etc.. > > We started with Flash CS3 and it worked great. But we figured, Flex is > more the app guy, so let's port everything there. We ran into a lot of > problems with the text. We had to go for some pretty ugly workarounds > and we expected Flex to be better for app development than fancy Flash. > > I would expect TextArea just to decorate the TextField, not hiding > it's very useful features. > > Sorry for the other confusing comments, it's been a while since we ran > into those issues so I'd had to look into that code again to > elaborate. Maybe it's even fixed in the FB3, let's hope.
I think there is going to be a huge influx of people wanting to do eLearning development with Flex, since Authorware is no longer being developed. Most people who have been with Authorware for years recognize that Director is a good fit, but are afraid that a long- term legacy product like that is likely to reach EOD soon as well. While Captivate has its niche for certain applications, Flex has the fullest feature set that make sense to hardcore Authorware developers who have essentially been using Authorware for building applications that happen to show eLearning content. -Amy
