Slashdot Mirror
Adobe Universal Binaries... in 2007
bo peterberg writes "According to a pdf on Adobe's website, they remain committed to supporting Intel-based Macs. However, Intel-based Macs will not be supported until the next upgrade of all creative products. The current version will not be re-released."
Not sure if you're trying to be funny or what, but in case you didn't already hear, Steve Jobs singled out Quark in his keynote as already having a Universal Binary for QuarkXPress.
Yeah, I was shocked as well.
"Leo Fender was in a 'state of grace' when he designed the Stratocaster." -- Paul Reed Smith
So much for LightTable destroying Aperture!
Actually, LightTable is the exception. They announced they will have a beta of it available shortly. Now if only Apple would release a competitor to Photoshop, Illustrator, and Framemaker maybe they'd come out with new versions of those products as well.
Mozilla/Firefox: TargetAlert.
CSS3 compliant browser: a[href$=".pdf"]:after {content: "[PDF]"; font-size:smaller} in your user style sheet. Modify as needed for other types of "annoying" links.
Constitutionally Correct
Quit whining and install one of the plugins that labels non-HTML links for you.
Or uninstall the Acrobat plug-in from your browser, so the browser will ask you whether you want to open the PDF, download it, or cancel.
GCHQ Quantum Insert installed. If only our tongues were made of glass, how much more careful we would be when we speak
"but if you're a graphics artist in a Mac only shop, your IT department will have to buy you Photoshop for Intel Mac, whenever your machine gets upgraded"
It's funny. I work in a printshop, and we have to upgrade the minute something new comes out anyway, since someone out there always has the newest version. Our main production machines have CS, CS2, AI8/10, PS6/7, PM6/7, InD2, and QXP4/6 all installed at the same time. Just sayin'.
- Apple has ALWAYS made it clear their move to Intel would be in stages.
- Apple has ALWAYS said it would be done from their lower-end products to their upper-end.
- The iMac is Apple's entry-level product.
- Therefore the iMac being iNtelicized first is in line with Apple's announced plans.
- With the iMac being Apple's entry-level consumer product it doesn't have a large professional user base.
- Therefore professionals, who have large investments in hardware and software, are unlikely to be affected by the Intel transition until it reaches the products they use: The Professional-level Macs like the G5 line.
- So Adobe not shipping Universal Binary products for their professional level until the professional grade hardware is ready is surprising to who?
Seriously, if you're appalled that Adobe et al aren't shipping Universal Binaries right away only means you haven't been paying attention. If you really are a professional photographer or someone who honestly depends on these type products you'd have to have been comatose the past year not to be well aware of all of this.Instead what I hear are a buncha wannebe-geeks who went out 'n bought the newest and shiniest and are now whining because they chose to ignore what anyone with half a clue woulda and most likely did tell 'em. You shelled out over a grand for a new product and couldn't be bothered to find out if the software you want to run on it actually would anytime soon.
Get the hell off /., I'm sure there's some support chat group out there for you on AOL somewhere. Try keyword "12:00-Flasher"
Frankly I just hope there is someone out there clubbing you monkeys over the head with instructions on how to use a contraceptive.
I don't read ACs: If a post isn't worth so much as a nom de plume to its author then I wont bother either.
Plus, Apple has a low-end publishing competition: Pages.
Which competes with MS Publisher, not InDesign
Is there anything better than clicking through Microsoft ads on Slashdot?
Fuck X11 on OS X, it just doesn't cut it. I can't even input Japanese. So much for using the GIMP for anything here (I happen to live in Tokyo).
There are two rules for success:
1. Never tell everything you know.
Quick Google search has found at least two :
9 _4-10470005.html?v=1/
h e-day-foxit-pdf-reader-109741.php/
http://www.foxitsoftware.com/pdf/rd_intro.php#/
Reviewed at
http://www.download.com/Foxit-PDF-Reader/3640-207
Downside : won't work in a Tab in Firefox. Then again, Acrobat doesn't always like to play properly with Firefox also.
http://www.lifehacker.com/software//download-of-t
Also :
http://www.visagesoft.com/products/pdfreader/
Next step : Doing something like this that is integrated with the browser. It's just a shame that MS would rather produce a new 'standard' than do it with IE.
See - who said Mac users can't be helpful to PC users sometimes.
'Capitalists of the world, unite! Oh
The above reply seems to confuse the issues of ABI (which is what I was talking about) and code container format (which your reply seemed to be talking about). When C++ is used for loadable code libraries, getting your tools and interfaces set up right is a little more tricky. Changing the capabilities of the SDK without breaking compatibility is even more tricky. Where I was going to go was that with Objective-C, you do not have the same problem, but I didn't even start because Adobe probably can't do that, as they are cross-platform SDKs. :)
Perhaps you missed the point of why I would criticize Adobe for using CodeWarrior. It has nothing to do with the container format. When Adobe released Creative Suite 2 last year, they moved from CFM to Mach-O, but they were still using the same old tool... CodeWarrrior (a bad tool for creating native Mac OS X apps, IMO). Had they moved back then, we would probably have Intel builds of Creative Suite in short order.
I am sure there were good reasons for Adobe to have done things this way, but... Now not only will we have to move our plugins to XCode, but we will also have to move them to Intel afterwards, and we can't do diddly until we get their new SDKs. Foo!
Japanese has admittedly THE most complex writing system in the world. It makes use of TWO syllable "alphabets", Hiragana and Katakana (if you can call them "alphabets" at all) and at least 1945 officiall Kanji (characters from the Chinese writing system, but partly simplified) plus some more in daily use. A good font comes with about 10000 characters plus it also throws arabic numbers and the latin alphabet into the mix.
;-)
Now there is no way to input that using just a keyboard layout, so it is not a matter of switching keyboard layouts for Japanese. You need a thing called input method. Which takes either your romanized input and transforms it into hiragana which you then can further transform into Kanji ("on demand" by hitting space), or some professional writers type directly in hiragana (but you still need to transform some of the syllables into kanji). In the OSS world there are two input methods widely used one is kanna and the other is wnn if I recall properly.
Now OS X has its own input method for Japanese (kotoeri) which works fine and does the job favourably, the trouble is X11 does know nothing of kotoeris existence, so if you want to input japanese in X11 in OS X you'll have to install kanna or wnn (in X11, OS X again will not know of kanna or wnn at all either) and the problem is that this is a somewhat esoteric affair, and you definitely don't even want to try to get it running. Even under Linux where you don't have to deal with two layers like in OS X (Cocoa/Aqua and X11) it is a pain and you rather just use a distribution that comes with kanna or wnn preinstalled. To make a long story even longer...
On OS X just don't try to use Japanese in X11 it's not worth the hassle. Also partly because usually OS X is through and through Unicode whereas AFAIK X11 is not (don't stone me if I'm wrong), that's yet another thing you'd have to consider when trying to use Japanese in X11 apps that weren't written to handle it. In OS X Cocoa apps it's no problem. Regardless of the application natural language, Cocoa apps always can deal with Unicode so you don't have to worry whether your app is able to deal with Japanese or not, it will be able to handle Japanese. Always.
Bottom line for me is: before I have to fuck around doing "the geeky thing" in X11 I'd rather wait for Photoshop or get a Cocoa app instead or anything that'll do the job, because if I wanted to geek around instead of getting some work done on my computer I wouldn't have gotten a Mac, I would've started with Linux to begin with
There are two rules for success:
1. Never tell everything you know.