BTW, now that we've gotten into Flex and are quickly adopting it, I am still a little lost as to why we went this way. I like the familiarity of ActionScript and the ease of MXML, but if you don't mind me getting off topic, what is the advantage of Flash over Java FX and/or Swing and
Applets or even Swing and JNLP?
I have found that in order to use Flex, I have to have some helpers from time to time - whether the helper be JavaScript or some other helper. For instance, I wanted to automate an upload process where we need to ensure certain directories have certain things before we upload. Since Flash runs in a security sand-box, I found that what we were trying to do would not work. The only way to make it work is to use JavaScript to browse directories and build logic and then validate it all in Flex and then call back to JavaScript to do more work then back to flex... or use a technology that can be configured to allow directory browsing. So, I wound up writing a JFileChooser and JTable with a table-model and a JNLP file for web-start for this one exception process. As I did that, I wondered why we did not just make the whole thing Java since we all know it and it seems to be able to do anything that Flex can do plus not have security restrictions. Don't get me wrong... I like Flex and am comfortable with it. Just curious why you would select it over arguably more capable technologies like Java (especially now that there are layout tools in the
IDE for alternatives to Flex).
Maybe I should make this a new
thread. Apart from your thoughts on the advantages of Flash over other solutions, does your book discuss where Flex is going and do you believe that html 5 or any other technology is likely to change the relevance of Flash?