Apple becoming as bad as Microsoft with iApps
I am writing this because I am frustrated with the fact that I cannot do something with my Mac that I can with Windows.
I use iPhoto on my Mac which I consider to be a great program. However I use Outlook Express (via classic) and Mozilla for my email. (I just like them better)
Whenever I ask iPhoto to share my photo's via email, it will only load up Mail. It will do this regardless of what email program is set as preferred in the system preferences.
Thanks Apple, higher cost and more microsoftian everyday.
Nick
I use iPhoto on my Mac which I consider to be a great program. However I use Outlook Express (via classic) and Mozilla for my email. (I just like them better)
Whenever I ask iPhoto to share my photo's via email, it will only load up Mail. It will do this regardless of what email program is set as preferred in the system preferences.
Thanks Apple, higher cost and more microsoftian everyday.
Nick
Comments
<a href="http://www.macoshints.com" target="_blank">http://www.macoshints.com</a>
His point is that Apple is now using their "OS monopoly" to allow preferential treatment of Apple iApps, in the way that Microsoft apps instantly activate Explorer.
System Preferences -> Internet
Click on the Mail tab, set your mail app to whatever you wish... voila. ALL mail triggers(*) will now use the app you select, no matter what app it is.
* Assuming that the app doing the triggering was written according to Apple's guidelines. If, instead, it is hardwired to trigger a specific mailer application, then you're stuck.
This is nothing like what MS does, sorry. This is called playing fairly.
EDIT: Reread the original post... looks like iPhoto *doesn't* use the proper triggering guidelines. (Can't say as I've ever tried this.) My guess is that because of its OS9/Carbon background, this is one of those things they haven't gotten around to updating for X yet. Bad, BAD Apple. No biscuit.
Is this the only iApp that does this? If it is, it's a bug. If not, it's a disturbing trend. Right now it looks like a bug.
[ 12-29-2002: Message edited by: Kickaha ]</p>
iPhoto feels rushed in many respects. I see this issue as being evidence of that.
<strong>Check Mac OS X hints for a work around.
<a href="http://www.macoshints.com" target="_blank">http://www.macoshints.com</a></strong><hr></blockquote>
I couldn't find a workaround. Could you post a more specific link please?
Nick
<strong>iPhoto feels rushed in many respects. I see this issue as being evidence of that.</strong><hr></blockquote>
I think most of the iApps are really bad, but I've been over that a long time ago. I use iView Media Pro instead of iPhoto. (and lately I've just used Photshop's built in browser).
[ 12-29-2002: Message edited by: MacLuv ]</p>
I think he's just looking for something to complain about.
<strong>My guess is that because of its OS9/Carbon background, this is one of those things they haven't gotten around to updating for X yet. Bad, BAD Apple. No biscuit.</strong><hr></blockquote>
<img src="graemlins/lol.gif" border="0" alt="[Laughing]" /> <img src="graemlins/lol.gif" border="0" alt="[Laughing]" />
iPhoto? OS X ONLY
Mail? OS X ONLY
sorry, guess again...
<img src="graemlins/lol.gif" border="0" alt="[Laughing]" />
iPhoto? OS X ONLY
Mail? OS X ONLY<hr></blockquote>
Why bring up Mail--its iPhoto that has the hardwired trigger to Mail?
And iPhoto is a carbon app and technically has an OS9 background, from whence most Carbon APIs came.
[ 12-30-2002: Message edited by: cowerd ]</p>
only after did i find out how much it sucks...
i guess this is why <img src="graemlins/hmmm.gif" border="0" alt="[Hmmm]" />
they shoulda made an os 9 version, would have been faster...
<strong>
Why bring up Mail--its iPhoto that has the hardwired trigger to Mail?
And iPhoto is a carbon app and technically has an OS9 background, from whence most Carbon APIs came.
[ 12-30-2002: Message edited by: cowerd ]</strong><hr></blockquote>
Thank you cowerd. Paul missed the point, apparently.
Although in all fairness I will admit to having a brainfart when writing that and thinking that iPhoto was also an OS9/Carbon capable app, like iTunes. Silly me. I guess I can be forgiven though since I haven't run < X in, er... four years? (Beta tested Rhapsody, I did. )
The Carbon libs at the time iPhoto was produced had some serious sharp edges when it came to inter-app workings. (They were trying to replicate Internet Config in Carbon, and clean it up at the same time... almost worked.) Cocoa's support for such is pretty sweet, and Carbon has since been pretty well fleshed out in this arena, but until iPhoto is updated, it can't use the newer Carbon libs. (Silly non-dynamically bound languages.)
So the iPhoto team likely took a shortcut to get around the Carbon problems, and it stuck. Bad Apple. No biscuit.
But of course we've all sent feedback to the bug reporting page... riiiiiiiight?
<strong>...He complains about an (admittedly, on my side) Microsoft-like bug(?) in iPhoto, but is himself using Outlook Express, a Microsoft product, by choice.
I think he's just looking for something to complain about.</strong><hr></blockquote>
Yeah, I mean I made it up and all. iPhoto should follow and use whatever has been set in your preferences. If Apple doesn't use their own API's then why should anyone else?
Also when you talk about why I use Outlook Express it is to access my Hotmail account. See when I got free email Microsoft and Yahoo, they didn't turn around and tell me to grab my ankles a year later, Apple did.
Nick