[production_coordinator]

I'm not a programmer, but this seems like it is a significant shift for Adobe. What could this mean for our platform. I realize it may not change much... but in the same breath, could it? I'm thinking of services, etc.

[Maflynn]

Originally Posted by production_coordinator

I'm not a programmer, but this seems like it is a significant shift for Adobe. What could this mean for our platform..

I am a programmer and It means that:
inorder to create universal binaries they will need to convert their code.
we will not see a universal binary version of CS 2
people who buy a mactel machine now or in 2006 will have issues running CS.
Adobe once again will be dragging their feet and hold Mac users hostage.

On the upside, I hope it will improve the performance of the application, be better effecient at system resources and faster turn around in bug fixes.

Most Mac applications are fairly mature so that means they contain some legacy code that dates back to System 7 (8 or 9) that now needs to be rewritten. You cannot just recompile when there's such a radical platform change. You need to rewrite sections/modules which means it will take time. I assume MS office will be in the same boat as that conains some pretty old code too.

Mike

[JLL]

Originally Posted by Maflynn

I am a programmer and It means that:
inorder to create universal binaries they will need to convert their code.
we will not see a universal binary version of CS 2
people who buy a mactel machine now or in 2006 will have issues running CS.
Adobe once again will be dragging their feet and hold Mac users hostage.

What else could they do? They started on CS3 last spring and why should they go back to CS2 and port it to Xcode?

[production_coordinator]

I don't feel like Adobe is dragging their feet. If they release in November-December, I think that is a fair turn around considering new shipping units just entered the market. Photoshop/InDesign/Illustrator/Acrobat/GoLive IMHO are a bit more complex than Word and Excel.

[TETENAL]

Originally Posted by production_coordinator

I'm not a programmer, but this seems like it is a significant shift for Adobe. What could this mean for our platform. I realize it may not change much... but in the same breath, could it? I'm thinking of services, etc.

Adobe CS3 is not going to use Xcode. It is going to be built with Xcode. It's not going to change anything at all for the feature set of the app (except being Universal).

[Millennium]

As far as I'm aware, there are only a few real changes which would be necessitated by the switch, and none of them would have any visible effect on the end-user:

• It is possible for CS3 to be a Universal Binary. This is not saying that it necessarily will be Universal, but it is now possible where it wasn't before.
• I don't know if previous versions of CS were in PEF or Mach-O format, but they will definitely have to be Mach-O now if they weren't before. This is unlikely to have any visible effect on end-users.

Of course, it is likely that there will be other features in CS3 which are visible to end-users. That's often the point of releasing a new version, after all. However, the move from CodeWarrior to XCode isn't relevant to those.

[OreoCookie]

Adobe has released a statement that the next release of all their Mac apps will be universal binaries.

Since Metrowerks abandoned the Mac platform and has no plans to release an Intel-compatible version in particular, the switch is a no-brainer. However, I also don't know what changes that will bring in terms of the app itself, I doubt it'll do very much. Just take a look at iView: they can't use certain Mac technologies to maintain a common codebase with their Windows version.

[tooki]

Threads about Applications belong in the Applications forum.

tooki