Is there a Cocoa newsgroup?
Heinrich Beck
John C. Randolph
Heinrich Beck wrote:
>
> Is there a Cocoa newsgroup?
Try comp.sys.mac.programmer.help, and the mailing lists
macos...@omnigroup.com and coco...@lists.apple.com.
-jcr
Christopher Corbell
>
> Is there a Cocoa newsgroup?
I don't know of a usenet group but Apple hosts
a mailing-list, cocoa-dev:
http://lists.apple.com/mailman/listinfo/cocoa-dev
=========
Chris
Sean McBride
Christopher Corbell <ccor...@vernier.com> wrote:
> Heinrich Beck wrote:
> >
> > Is there a Cocoa newsgroup?
>
> I don't know of a usenet group...
There is all of comp.sys.mac.programmer.*
Erik M. Buck
there, it was full of mis-information and FUD about Cocoa, ... maybe it is
better now ?
"Sean McBride" <cwa...@cam.org> wrote in message
news:cwatson-7C3D02...@news21.bellnet.ca...
Luc Heinrich
<embass...@qwest.net> wrote:
> Last time I read comp.sys.mac.programmer.* they all hated Cocoa people
> there, it was full of mis-information and FUD about Cocoa
I've just downloaded your EMBQTImage sample class to have a look at it
but discovered that it was just your own personal mis-information and
FUD about what you comment in the code as "the Quicktime/Carbon crap".
So much for the professionnal attitude uh ? Oh well, I'll get back to
you in a while, maybe you will be better... :>
--
Luc - luc...@mac.com
Keith Ray
> Last time I read comp.sys.mac.programmer.* they all hated Cocoa people
> there, it was full of mis-information and FUD about Cocoa, ... maybe it is
> better now ?
Last time I looked into a Cocoa discussion on comp.sys.mac.programmer.*,
there was a Cocoa bigot saying spreading FUD about Carbon. :-)
--
C. Keith Ray
Erik M. Buck
"Luc Heinrich" <luc...@mac.com> wrote in message
news:lucsky-35F5B8....@news.noos.fr...
> In article <GuiB8.946$6R3.1...@news.uswest.net>, "Erik M. Buck"
> <embass...@qwest.net> wrote:
>
> > Last time I read comp.sys.mac.programmer.* they all hated Cocoa people
> > there, it was full of mis-information and FUD about Cocoa
>
> I've just downloaded your EMBQTImage sample class to have a look at it
> but discovered that it was just your own personal mis-information and
> FUD about what you comment in the code as "the Quicktime/Carbon crap".
I provided that code upon request. If you don't like it or don't find it
useful then don't use it. If you use it and finds bugs, let me know. I
provided sample code including comments. I posted the code on my iDisk. If
you have the code then you went out of your way to download it from MY
iDisk. I am entitled to my opinion in the comments of MY code. I did not
post negative comments about Carbon to a news group. I did not broadcast my
opinions to anyone. You made an effort to download my code an now your are
upset by comments in the code ?
I admit that I don't know much about Carbon. If my comments in the code are
factually wrong then let me know. I added the comments in an attempt to
understand the Byzantine API that I needed to use. My understanding will
surely be improved if you correct the comments. I just found it distasteful
that Carbon and Quicktime required more lines of code to load an image than
some entire Cocoa apps contain.
Rhetorical question: Why do I have to have FSRef, ComponentInstance ,
FSSpec, OSType, GWorldPtr, PixMapHandle, void *, Handle, and numerous casts
between types in order to load a single image from a file ? It makes me
miss [[NSImage alloc] initWithContentsOfURL:@"some URL"]; Don't bother
answering. The reason is because NSImage does not do what I want and
QuickTime does or else I wouldn't be using QuickTime directly. I just find
the proliferation of opaque types, frequent casting, completely loony file
system API, and Byzantine conventions of Carbon distasteful. Other people
make other aesthetic judgements.
Luc Heinrich
<embass...@qwest.net> wrote:
> I provided that code upon request. If you don't like it or don't find it
> useful then don't use it. If you use it and finds bugs, let me know. I
> provided sample code including comments. I posted the code on my iDisk. If
> you have the code then you went out of your way to download it from MY
> iDisk. I am entitled to my opinion in the comments of MY code. I did not
> post negative comments about Carbon to a news group. I did not broadcast my
> opinions to anyone. You made an effort to download my code an now your are
> upset by comments in the code ?
Uh, excuse me but this is just a plain lie. You DID post negative
comments and you DID broadcast negative comments, when you announced the
release of your code, here:
<http://cocoa.mamasam.com/MACOSXDEV/2002/05/1/33157.php>
There is one "Quicktime/Carbon ugliness" and two "Carbon crap".
> Rhetorical question... blah... blah... blah...
Erik, I don't care what you think, heck, I even somewhat agree with you
on those aestetic considerations but please, you are accusing people of
spreading mis-informations and FUD while you *are* doing the *same*.
That's all I wanted to point out... :)
--
Luc - luc...@mac.com
Greg Weston
<embass...@qwest.net> wrote:
> I admit that I don't know much about Carbon. ... I just found it distasteful
> that Carbon and Quicktime required more lines of code to load an image than
> some entire Cocoa apps contain.
>
> Rhetorical question: Why do I have to have FSRef, ComponentInstance ,
> FSSpec, OSType, GWorldPtr, PixMapHandle, void *, Handle, and numerous casts
> between types in order to load a single image from a file ?
Non-rhetorical answer: Last time I checked, you didn't. Loading images
of supported types with QT is something like 2-3 lines and certainly
does not required declarations of variables of all the types you've
listed. And no casting IIRC.
G