So, it looks like I'm trying to test the application with a non-debug version of the flash player. Actually Google Chrome has in-build flash player, which is updated automatically. Even if you install the debug one, very soon Chrome will replace it.
!MESSAGE Commands should really have a category: plug-in='com.qnx.flashbuilder.multiplatform.qnx.ui', id='com.qnx.flashbuilder.multiplatform.qnx.ui.commands.OpenInfoCenter', categoryId='com.qnx.flashbuilder.multiplatform.qnx.ui.commands.category.help'
2) Toshe-de did indeed suggest a "workaround" to the Adobe requirements, and as noted, there may be risks to this down the road. This is just the way it is, however, when one wants to exceed a vendor's requirements or limitations. It is quite obvious to all that Eclipse is moving on, while Flashbuilder is not. Apparently, Adobe is not committed to continuing FB development, and so in the mean time...life goes on.
A little note for those using other IDE's then FB 4.7
I have been running Flex Builder 3 & do not want to invest in FB 4.7, a simple way to get up & running was to using external tool option
On the overlaid FlexJS SDK go to ide\flashbuilder folder & open the .launch file corresponding to type of project you want to build, for an application it would be FlexJS (Release Build).launch
Watch out for org.eclipse.ui.externaltools.ATTR_LOCATION & org.eclipse.ui.externaltools.ATTR_TOOL_ARGUMENTS variables, the former is the location of your java executable inside JDK & the latter is the argument you pass to it, copy the value part of org.eclipse.ui.externaltools.ATTR_TOOL_ARGUMENTS paste it inside a text editor & find/replace " with "
After seeing how this synergy of adobe and apache is for flex, I deleted all adobe flash builders and flex related products. We used adobe products because we expect a certain advantage from commercial products, but this is just bullshit. When in a time everything can be simplified and automated and we have to go back resorting classic ways of configuring/developing like 10 years ago. No, thank you.
For example this post tagged with flashbuilder and flashbuilder4 was edited to add the flex tag, presumably because they assumed Flash Builder must be about Flex; however, this post about the way the Eclipse platform displayed debug values of a pure ActionScript Date object - nothing to do with Flex.
A lot of effort small reward. You can port vectors from fireworks to flash if there's a chance you'll end up in flash world or not but I think fireworks is better than flash if rich prototyping is what you're after =2112
Wow. Quite a lot of anti flash-sentiment here. The answer is that it depends on your skill resource, if they are any good then they can present behaviour in flash to mimic any environment very quickly.