If you are creating widgets or gizmos with Flex/Flash. I don't think you will ever hit the 'pain threshold.' However, if you are developing a substantive application - workforce management, crm, data management, repository, asset management or the like. realistically you can code up to release oblivious of what is happening with memory management and system performance. The difficulty is that developing in Flex is so freaking cool that you can easily get caught up in features and visual sweetness that you'll will forget to profile as you go to help you target bottlenecks. Frankly - if you save performance tuning til' the 11th hour. it's going to be rough.
It's not just about the size of the swf - it all about coding to the platform. most reasonably configured system will be fine. Here is a top five-ish list of things to think about. #. Modularize your app - you _can_eat a whale. one bite at a time. #. Profile as you go - if you start to see 'the signs' stop and figure out what the problem is. If you are patient the knowledge you gain in the process will provide a feedback loop re-injecting better approaches and broader understanding into your work. #. Training. there I said it. Spending a few bucks in a session with a guru will be incalculable. #. Source. Source. Source. It's all about looking into the Flex SDK source as much as you can. Building 'hot rods' is a process of developing (fanatical) deep understanding of your subject - to the point you know when to bend the rules and when not to. #. Become the solution. Let's face it. in order to be a Flex 'rockstar' you are going to need to understand enterprise architecture, drool in sql, pound (as in eat large quantities of) webservices/servlets/etc, and. well you get the point. Buy some books. lots of em. Take a (qualified) nerd/geek out to lunch. Ask to see cool things people 'talk' about and then ask to take a look at the source. Cheers, Rick Winscot From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Josh McDonald Sent: Thursday, May 08, 2008 10:51 PM To: [email protected] Subject: [flexcoders] How big does a SWF get before IE starts to worry? Hey guys, I've been reading a lot about explorer not being so nice with Flex / Flasg apps that use up a bit of memory, and I'm wondering at what kind of thresholds this starts to become a problem? Is it mainly about SWF size, or how loose you are with your allocations and leaving dead references around? -J -- "Therefore, send not to know For whom the bell tolls. It tolls for thee." :: Josh 'G-Funk' McDonald :: 0437 221 380 :: [EMAIL PROTECTED]
<<image001.jpg>>
<<image002.jpg>>
