Why you should use Opera for debugging Adobe Flex applications on Mac OSX
The simple reason for this is: It is the only one that works well. I try to develop a small Adobe Flex app in eclipse 3.4 with the adobe flex plugin trial in it (v 3.2 of the flex sdk) - and am using OS X 10.5, Leopard.
Safari is a very nice and usually fast browser, but when it comes to debugging flex apps, and Safari being launched from eclipse it just uses whatever old cached version it still has. It also does not matter if you turn on the Developer menu, and deliberately switch off caching. I tried that, no luck, just frustration. For debugging Flex applications Safari is a sucking pig.
Also I still use Firefox -despite getting slower and slower as its newer versions come out - for debugging purposes, and reverse engineering css files (the excellent firebug tool + yahoo’s yslow comes to mind). For that it’s good. When I turn off its caching via the web developer plugin it is turned off for real (not like with Safari). However there’s one thing wrong with it when you want to debug in OSX 10.5 with eclipse 3.4+adobe flex plugin. When you set it up as the browser to use in eclipse and want to debug your app it just says “A copy of Firefox is already open. Only one copy of Firefox can be open at a time.” › Continue reading
Recent Comments