Don't forget though that 'time to refactor your code' will cost some Enterprises *a lot* of money. I am currently doing some work for a client who has literally thousands upon thousands of pages with Flash and Java on them to update - many are static.
 
Now this company needs to go back to their web teams and subcontractors and have them update a gazillion pages - how do you think they'll feel about this? Right, p*ssed off. It'll be a substantial cost. And next time when someone proposes Flash they'll remember this issue, for the right reasons or not. 
The clever ones will knwo better, the not so clever ones may avoid it.
 
I am not a fan of conspiracy theories but be aware that this is much more than 'just another click' or a bit of 're-factoring'... I actually find this whole issue quite scary. If MS really wanted to then it could make our lives pretty miserable (I'm not saying they are).
 
Granted, this issue affects (at least at the moment) their own tools too and this does provide an alibi of sorts.
 
Stefan
>

I'm certainly not suggesting that it's not to Microsoft's benefit to
release this patch. I was just saying that's why you see the frame
border. However, I will say that if you're a competent developer
("you're" meaning the developer community in general), you'll note
that there are several workarounds for this patch already, so it's not
like you're stuck. It's just a question of taking the time to
re-factor your code.

Regards,
Dave.


--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com




SPONSORED LINKS
Web site design development Computer software development Software design and development
Macromedia flex Software development best practice


YAHOO! GROUPS LINKS




Reply via email to