For me it is a hot topic because after researching this subject two
years ago and reading said archives I started relying on
NSMailDelivery and now the powers that be have decided that it should
no longer be available. (wondering why?)
So I have to rewrite functional code and use a third party framework
or the scripting bridge which by the way isn't backwards compatible
with Tiger.
Of course I could ignore the deprecation until OS-X 10.11 Meerkat
(actually not a feline but a mongoose) comes out and my clients start
calling because their mail no longer works...
Are there actually any guidelines for how long one might expect a
deprecated class to continue to exist?
(and thanks to those who responded to questions on the topic in recent
weeks - It's just that I have other things to do than go back and re-
solve an old problem)
buddy kurz
On Jun 3, 2008, at 8:15 PM, Kyle Sluder wrote:
On Tue, Jun 3, 2008 at 10:45 PM, Frederick C. Lee <[EMAIL PROTECTED]
> wrote:
I need to send data through the mail from within my Cocoa program.
This is
to be for general release; so it must be stable.
Why has every single person under the sun decided that they now need
to send mail using Cocoa? And why does everyone who asks this
question apparently never search the archives? I am very curious as
to why this is now such a hot topic.
--Kyle Sluder
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/buddykurz%40mac.com
This email sent to [EMAIL PROTECTED]
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
