|
Re: Hybridizing Java
|
Posted: Feb 6, 2007 7:31 AM
|
|
Hugh, your concern about "bad flash apps from the past" is a common one that was addressed earlier in the comments. Most of those old "skip intro" style designs represent early bad design choices, much as some who get a word processor go crazy with fonts, or with presentation software go crazy with transitions.
Time and experience (and user backlash) has pushed a lot of that kind of Flash interface out of existence, though certainly it still exists and could still be created by one who "doesn't get it" why they're a problem.
More important, there are many ways in which Flash is being used in small segments of a web page--and people may not even notice as its so seamless.
Further, I think some would argue that Flex is itself going to lead to a difference in the likelihood of such interfaces as those bad ones of old, simply because of its approach to design. Still, it could happen, just as a Java developer could build without OO if they really missed the boat in their learning. That's where having someone like Bruce involved in Flex training will be such a blessing.
Finally, it's worth noting that as far as speed concerns go, a Flash app itself is usually very small, so should load fast. Still, that app could go back to the server for data (either on initial load or as the result of some event on the client), and so that could cause delay.
An important difference compared to a web page load, though, is that it should only be causing a load of the DATA it needs, not the entirety of the HTML (and possibly images, etc.) of a typical page refresh.
Still one more point should be made, as some may see a "Flex" app and it could load slowly. Prior to Flex 2, a Flex app was compiled on initial request on the server and then sent to the browser, which could also cause a lag.
In Flex 2, there is no longer a server compilation component or process. Instead, as Bruce explained in his article, Flex apps are compiled by the developer with the free SDK (or in the Flex Builder tool). Only the resulting SWF are placed on the server and downloaded upon request.
|
|