Paul,
Well what I'm working on is a little more involved then a single flex
app running inside a website...
It's more of a flex/flash app player/environment...
It allows for you to find flex apps run them build your own custom
tailored environments with apps you like and switch between them...
And the overlay/child indexing is where it become an issue
For an example see http://cupid.ubixos.com/reddawg
-Christopher
Paul deCoursey wrote:
Tom Chiverton wrote:
On Thursday 07 Jun 2007, Christopher Olsen wrote:
Well if we want to add bloat an html render would be nice since the
IFRAME hack is above the player itself
Why does the Flash player (that runs in a browser) need a HTML renderer ?
OK, so RichTextEditor has issues, but no one is seriously that bothered, are
they ?
I think there are a lot of people who don't get that the Flex
application doesn't need to take up the whole screen. It, like Flash,
can just be a part of the page and can communicate with other bits on
the page. One Flex app can even talk to another on the page. With that
in mind I don't think an HTML renderer is important. I also think that
the RTE is fine, if you need complex HTML then you should be coding it
and not using a WYSIWYG anyway.
--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com
Yahoo! Groups Links
