So your main beef is really with the w3c and the browser makers for not giving you the flexibility you wanted. Now that Macromedia has solved (or at least gone some way to solving) that problem you're saying that this solution is too expensive. Despite your claims to the contrary, the fact that no-one else has come up with anything near to Flex either as a standard, as an open source initiative, or as a product should give you and idea that it really isn't as easy as you're making out (I'm not counting Microsoft and windows forms/Avalon because that isn't a product yet).
The main power of Flex is not in how the UI renders. It's in how that ties into the back-end and is generated based on dynamic changes in the back-end. A lot of the widget type stuff you're asking for will be in Blackstone if Tim's blog is anything to go by, but the back-end probably won't. Again, I'm betting that it won't be quite what you're after so we'll be back to a round of questions like "why couldn't they have done it like this?" The answer is that there either aren't enough people asking for that to justify putting it in, or it isn't as simple as you think. Spike --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
