This content has been marked as final. Show 3 replies
Well, reading Peter Ent's answer in another post (see answer below) makes some kind of sence. Shame. Thougt that Flex would replace the whole world of other tools for developing webapps (wishful thinking : ) ).
Answer from Peter Ent
The Flash Player has a very limited number of HTML tags it can handle - table is not one of them. Since Flex is just a way to build Flash Player content you are limited by what the Flash Player can do.
We don't supply a full browser/HTML rendering engine in the Flash Player because it would make the Flash Player a multi-megabyte download (eg, 11-12 MBytes); right now the Player has a small footprint which enables it to be downloaded by virtually everyone.
The Adobe AIR player (see labs.adobe.com) does have a full HTML component and can run Flex programs. The caveat is that the apps are not run in the browser, but on the local machine. The end-user has to download the AIR player in order to use it.
You can also check out Alex's blog ( http://blogs.adobe.com/aharui/) and scroll down to "HTML and Flex"
This is one of those threads that will likely get quite long, but here goes. As Peter described, the Flash Player does not have a full HTML rendering enigine as the player download would be much less compact. Also, Adobe AIR will provide a full HTML component.
You are trying to do something based on the way things have been done to date. Nothing wrong with that, and you could argue that Flex is deficient in this area. But looking at the bigger picture of what RIA UIs are looking like as they evolve to be more visually complex and "rich", I think in general HTML is in general being handed its hat and is being show to the door, in favor of Flex/AIR.
I'd have to agree on that one. I've been wondering for many years why we still (well, I know it's because of the lack of standards) handtweek html-code to get stuff into a browser. Back in the old days that's how you'd layout a print document (surrounding text with formatting tags). But with the wordprocessor that became sort of obsolete. We've had WYSIWYG editors around for quite some time now, but none that wouldn't let you tweek the code.
I think, being absolutely new to Flex, I tried to make it do what I'm used to be doing. I think I'll have to get my head around Flex, instead of getting Flex around my head.
I do see a great future for Flex development. Absolutely a path I'm taking.