or Connect
AppleInsider › Forums › Software › Mac OS X › Something I don't quite understand (especially Adobe)
New Posts  All Forums:Forum Nav:

Something I don't quite understand (especially Adobe)

post #1 of 13
Thread Starter 
Back to the pre 10.1 time we heard that Adobe was complaining about the API of X and they said it was crap and would be extremely difficult to port their apps.

But during that time we did see some big apps really ported to X. From high end apps in 3D (Maya, Lightwave, Cinema), Motion capture (FilmBox), to 2D stuff (Painter, Corel Draw, Freehand)

They all run fine.

I don't really understand why Adobe made that claim. There apps are not as complicated as Maya I think....therefore I really don't understand why they keep saying they were having tough time.

I am not a software engineer....if I really were making some false thought correct me
Mac Pro 2.66, 5GB RAM, 250+120 HD, 23" Cinema Display
MacBook 1.83GHz, 2GB RAM
Reply
Mac Pro 2.66, 5GB RAM, 250+120 HD, 23" Cinema Display
MacBook 1.83GHz, 2GB RAM
Reply
post #2 of 13
I think a big part of the problem is that they have so much legacy code, from way way back.

That, and they are lazy bastards.
This Post Disabled on PowerMac G5s
Reply
This Post Disabled on PowerMac G5s
Reply
post #3 of 13
Well, even Microsoft said that at MWNY that they needed around 20-25 specific bug fixes in order to run Office properly, so Office X would be released only for 10.1.

I don't think Adobe went so far as to say that the entire API was "crap"...
"If I were a younger man, I would write a history of human stupidity; and I would climb to the top of Mount McCabe and lie down on my back with my history for a pillow; and I would take from the...
Reply
"If I were a younger man, I would write a history of human stupidity; and I would climb to the top of Mount McCabe and lie down on my back with my history for a pillow; and I would take from the...
Reply
post #4 of 13
I think Ventral is right. Photoshop's code is extremely old and tied closely to the system (for optimizations and mac specific code) whereas Maya and whatnot were prolly made from scratch for X and most of their code is prolly inhouse stuff that works fine on any platform.

Just some theories...

CD
post #5 of 13
it can't be that closely tied to the system, as all Adobe apps have been fully cross-platform [in fact some people would say more windows friendly] for a couple of verisons now. Adobe also uses its own display and font libs for ALL apps.

BTW Adobe is blaming [at least on support forums for Illustrator] CarbonLib for some of its performance problems.
four more beers, four more beers
Reply
four more beers, four more beers
Reply
post #6 of 13
In the case of Maya, it was created for Unix. So I assume moving it from Unix to OSX was a much simpler task than moving Photoshop from Classic to X.
post #7 of 13
[quote]Originally posted by cowerd:
<strong>it can't be that closely tied to the system, as all Adobe apps have been fully cross-platform [in fact some people would say more windows friendly] for a couple of verisons now. Adobe also uses its own display and font libs for ALL apps.
</strong><hr></blockquote>

Photoshop is still a port to Windows. Move your cursor over a open document in Photoshop. Notice the cursor. Ive heard many people complain about Photoshop on Windows and how it sucks compared to Photoshop on the Mac.
The crucial memorandum will be snared in the out-basket by
the paper clip of the overlying memo and go to file.
Reply
The crucial memorandum will be snared in the out-basket by
the paper clip of the overlying memo and go to file.
Reply
post #8 of 13
This is why I don't expect an OS X native Quark for literally three years. Getting that code cleaned up and in some cases just plain replaced to get it to the level of a "dirty" Carbon port, let alone a good Carbon version (Mach-O? Ha!) will likely take that long considering who is doing it. It's all relative.
post #9 of 13
[quote]Originally posted by Sinewave:
<strong>

Photoshop is still a port to Windows. Move your cursor over a open document in Photoshop. Notice the cursor. Ive heard many people complain about Photoshop on Windows and how it sucks compared to Photoshop on the Mac.</strong><hr></blockquote>

What's the cursor supposed to do? Mines goes from my cursor to current tool when I mouse over an open file.
All Your PCs Are Belong To Trash
Reply
All Your PCs Are Belong To Trash
Reply
post #10 of 13
[quote]Originally posted by BuonRotto:
<strong>This is why I don't expect an OS X native Quark for literally three years. Getting that code cleaned up and in some cases just plain replaced to get it to the level of a "dirty" Carbon port, let alone a good Carbon version (Mach-O? Ha!) will likely take that long considering who is doing it. It's all relative.</strong><hr></blockquote>

By then it won't matter. InDesign will have swept up the market.
All Your PCs Are Belong To Trash
Reply
All Your PCs Are Belong To Trash
Reply
post #11 of 13
In Photoshop 6.0 for windows I get a special error occationally:
"Quickdraw could not be initialized"

Hmmmmm.......
post #12 of 13
[quote]Originally posted by KidRed:
<strong>

What's the cursor supposed to do? Mines goes from my cursor to current tool when I mouse over an open file.</strong><hr></blockquote>

In Windows the cursor changes from a PC one to a Mac looking one.
The crucial memorandum will be snared in the out-basket by
the paper clip of the overlying memo and go to file.
Reply
The crucial memorandum will be snared in the out-basket by
the paper clip of the overlying memo and go to file.
Reply
post #13 of 13
[quote]Originally posted by a holck:
<strong>In Photoshop 6.0 for windows I get a special error occationally:
"Quickdraw could not be initialized"

Hmmmmm.......</strong><hr></blockquote>

Heh.. more proof it's just a port.
The crucial memorandum will be snared in the out-basket by
the paper clip of the overlying memo and go to file.
Reply
The crucial memorandum will be snared in the out-basket by
the paper clip of the overlying memo and go to file.
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Mac OS X
AppleInsider › Forums › Software › Mac OS X › Something I don't quite understand (especially Adobe)