I was recently working on a project in the latest beta release of the forthcoming Flash Builder 4 and wanted to point out the new contextual help feature. What's nice about this feature is that I had just added the highlighted event to the event class and was busy implementing it in a view class and because of FB4's new code-hinting muscle I was able to see everything that I had documented in the event class concerning the event without having to have the event class open.
This is definitely a much appreciated usability enhancement. Now, if we could just get editable code (not file) templates (think FDT, Zend Studio, etc), FB4 would be that much closer to being ready for prime time...
If you're a Flex developer that's recently upgraded to Apple's latest OS, Snow Leopard, you may run into this prompt when launching Flex Builder 3. This is saying that in order to use the Adobe Update Manager plugin for Flex Builder, you need to install Rosetta. Rosetta which was enabled by default in Leopard, is not in Snow Leopard as Apple tries to push the market towards 64-bit computing.
You're perfectly safe to launch/use Flex Builder without this plugin until Adobe releases an updated version. All other application functionality appears unaffected by a lack of Rosetta.
If you have experienced this issue since upgrading your Mac to OSX 10.6, here's the skinny on what's going on and what you can do about it. Basically, this occurs when attempting to access external drives (ie, USB, Firewire, iDisk, etc). Symptoms of this error include a missing menubar (unless an application is active and in focus) and no "active" indicator beneath Finder in the Dock. This particular error can prove to be extremely annoying since the majority of Mac GUI applications incorporate the Finder in the UX (ie, Open and Save dialogs). Luckily, it's not difficult to recover from, just depends on how you'd like to.
If you have running processes that you don't want to stop by rebooting your machine, open Terminal and issue this command:
press the Return key and Finder will be relaunched for you without a computer restart. If you don't mind rebooting, I'd suggest issuing the restart command from Terminal vs. using the Apple menu as the latter is prone to be blocked by the current issue. To restart from Terminal, issue the following command:
You can replace the -r flag with -h to shutdown instead of reboot. Once restarted, your computer should be back to normal. There are also other options ranging from unmounting the disks, rebuild LaunchServices, applying/reapplying the 10.6.1 combo update and ultimately reinstalling the OS but I believe these two to be the fastest to getting your machine back up and running...
..or vice-versa.
After starting my new gig with
Almer/Blank today, I changed my workflow a bit to incorporate my Macbook along with an external 21″ display. The primary development environment in our projects is Flex Builder.
Well, the first thing I noticed when going in to edit a file was that the line numbers weren’t tracking correctly with the page scrolling. I figured that this was a fluke, so I tried restarting Flex Builder. Nothing. Tried again. No go. With some tight deadlines, I kind of put that aside and pushed through without using line numbers (which really sucks, if you get used to relying on them like me). After things slowed down a little, I came across this bug ticket:
http://bugs.adobe.com/jira/browse/FB-23023
Basically, the problem arises when using Flex in an external display. Also, it seemed to crop up with the release of Snow Leopard.
So, if you’re reading this and have the same issue or know someone who does, please do us a solid and place a vote for that ticket
On another note, I’ve also noticed quite a lag when using Flex Builder on the mac lately. I had to force quit today when working on a fairly light project, and I’ve read that others have had performance issues with FB that are related to Snow Leopard. Furthermore, these issues seem to be relevant for both FB3 and FB4… interesting…
