Adobe

initial gripes with new Flash CS3 ui

I know – I’m turning into Victor Meldrew. I can’t seem to help it. Should Adobe sort out the current licensing and pricing nightmare I’m going through, I’m sure I will become more chilled.

While others have been hung up on the new icons, personally I have no issue with them. They remind me of Rowntrees Tooty Frooties – which is not a bad thing! My issues (admittedly minor) are with some of the work on the new user interface.

I can appreciate the general investment in improving the UI. However I find some of the additions odd, and on my system some seem poorly implemented?

1. Introduction of Windows style controls on the Mac.

Most of the palettes introduce a collapse control (-) and close control (x) in the top right-hand corner. Mac convention is for the close control to be top left control and in both cases I think aqua controls and positioning would have been better – more consistent with other (non Adobe) applications.

I also find it strange that most palettes introduce this new arrangement, but other ‘windows’ retain the standard Mac behaviour (e.g. document windows and the control window). Mixing it up in this way just feels odd.

DebugController

2. Palette drag

When dragging a palette, it will go semi-transparent. Potentially useful – being able to see what will be covered up before dropping the palette into position. This is also part of the softening of the UI and should enrich the user experience. But on my system, when the mouse is released, the palette disappears briefly before being re-drawn opaque. This ‘flicker’ when a palette is released is plain ugly and detracts hugely from the user-experience. Until it is fixed I would have rather not bother with semi-transparent efforts.

I guess this might be an issue with my system being quite old? (Mac G4 Dual 1GHz Mirror).

3. Welcome panel links to the Adobe site are not working as intended

I think this is just an issue of the Adobe site not having been updated to service the links. You’ll find that from the Flash Welcome window, clicking on either “Getting started ››” or “New features ››” simply dumps the user at the flash product page. The problem seems to be server-side. The pages which flash attempts to take you to, simply re-direct back to the product page.

We fare slightly better with “Resources ››”. However most of the content on that page is written for FlashMX 2004 or Flash 8. I think by now there should be some CS3 articles on there.

Hopefully that’s the end of today’s grumpiness. Although I just read the SaveAs Gotcha written up by Aral. 🙁

Posted by creacog in Adobe, CS3, Flash Platform, Mac OS, 2 comments

worth a view…

Video of Christian Cantrell demonstrating an Amazon S3 (which I didn’t know existed) library and client application in Apollo using the soon to exist Apollo Beta.

Not sure what he’s been drinking (cup of pink stuff) but even with the empties, his desk is far tidier than mine.

Posted by creacog in Apollo, Flex, 0 comments

CS3 trial versions now available for download

hurrah!

Not sure why they couldn’t have been ready when the product shipped? But they are there now.

Now I just need to persuade Adobe UK Licensing that my MVLP Studio 8, 24 month subscription sold to me when my DEVNET account expired does in-fact cover this upgrade to CS3 Web Standard. I’ve been playing email ping-pong with them over this for the past couple of weeks. Hopefully this will be resolved before my trial versions expire!

Posted by creacog in Adobe, CS3, DreamWeaver, Flash Platform, 0 comments

are adobe ripping off UK cusotmers?

If you read my earlier post, you’ll know I tend to think they are.

The software is great. I am happy to pay for it. I just don’t see why I should pay so much more for being British. My opinion of the reasons given: “Non Sequitur”.

El-reg are now highlighting this with respect to CS 3.

It’s just not cricket! 🙁

A question for Steve Burnard on the 17th I think.

Update (09/04/2007):

Update (19/04/2007):

Aral Balkan recently wrote an article around this subject. It and its comments are worth a read. I’m hoping that Adobe will listen and act, rather than trot out a stream of excuses.

Posted by creacog in Adobe, Flash Platform, Flex, 1 comment

i finally hot-fixed flex builder

The hotfix was published a few weeks ago. I had been suffering the debug problem on the Mac (193086), so it was time to apply the fix. (NOTE: Unless you are suffering any of the problems listed you are adivsed not to bother applying this fix)

I found the instructions more confusing than they needed to be. They essentially boil down to ‘make a backup copy of your current installation prior to applying the fix’. This is kind of vital, because if you do a straight replacement of the old “Flex SDK 2” folder with the fixed version, and you happen to use charting, you’ll find that the charts.swc is missing!

Also you need to be aware that first time you run the application after the fix, you will need to re-enter your serial numbers.

Posted by creacog in Flex, Mac OS, 0 comments

flash button sound disobeys master volume

Ok, this I am sure is an old one, and has probably been blogged countless times before, but it bit me for the first time last night and googling didn’t turn up any useful results.

The scenario:

I’ve been working on a container movie. It’s job is to hold a master navigation control and to load content movies developed by a third party, based on user actions. In addition it plays a sound track.

It contains a mute button which controls a Sound object created with a line such as mySoundControl = new Sound( this ); and then mySoundControl.setVolume();

On the face of it, it controls the volume very well. Including the time-line sounds within the content movies.

The problem: We found that certain items in the content movies triggered sounds independently of the master volume and simply disobeyed the volume. The common factor in each of these was that they were button symbols each with a sound applied directly to the over frame.

The solution: quite simply was to create movie-clip symbols containing the sounds, and replace the over frame sound with an instance of the new movie-clip.

Posted by creacog in Flash Platform, 0 comments

apollo book available for download

“Apollo for Adobe Flex Developers Pocket Guide” available to download here.

Includes a link to get it from Amazon. Personally I prefer to have the printed document at my side. This book at 108 pages, is just about small enough to print at home, and with 2up full duplex I get four document pages per sheet of A4. However without introducing some scaling, you will end up with tiny text surrounged by huge white margins.

Which brings me to something of bug-bear with Adobe Reader on the Mac. It doesn’t allow me to do a sensible print preview. Nor does it give me the level of control over the print that I require. Fortunately this book renders correctly in Apple Preview. From which setting scale to 140% in page setup, then printing layout at 2 per page, full duplex gives me good results!

So all that remains is to get hold of the Apollo alpha. Watching this space. (Update: download now available)

Posted by creacog in Apollo, Flex, Mac OS, 0 comments

apple update includes flash player (9.0.28)…

If, as suggested by JD’s post, the latest Adobe Flash Player will continue to be included in Apple System updates, this can only be a good thing for shoring-up and keeping the installed base current.

Unfortunately this morning’s update trampled over my debug player (already at version 9.0.28) replacing it with the standard plug-in. This is going to hit loads of developers similarly. It would be nice if Apple could add a rule to the updater to respect the presence of the debug player. That said, it isn’t a big deal to simply re-run the player’s installer from the Adobe Flex Builder 2 ‘Player’ folder.

Posted by creacog in Flash Platform, Flex, Mac OS, 7 comments