Re: itunes for windows HOWTO ???
Re: itunes for windows HOWTO ???
- Subject: Re: itunes for windows HOWTO ???
- From: Alex Perez <email@hidden>
- Date: Mon, 10 Nov 2003 19:44:12 -0800
A reply to the FUDmaster follows...
[SNIP}
Important notes for GnuStep:
* There's no native Windows version - you'll have to use Cygwin or
Linux. So it's of no help to the original poster.
So what? it works (With Foundation only, and AppKit fetally, as I
disclosed in my original e-mail) just fine, using either cygwin or
mingw. There are howtos available.
* It's (apparently) unstable on Darwin.
Can't comment on this, as I don't run a strict darwin/gnustep
configuration, but AFAIR, someone had installed it just the other day
and was making serious progress making it work, so stay tuned. It's
also worth noting that you dont need to use GNUstep under OS X. You
just use Cocoa under OS X, and GNUstep elsewhere.
* It's incomplete (but improving all the time).
FUD. It's not perfect, but so much progress has been made in the last
year, and it really pisses me off when people assume that it has not.
* It's not based on Cocoa, but rather the much older OpenStep spec
from NeXT's days. Any Cocoa stuff which makes it in is purely
coincidental.
No, it's not, nor will it ever be, based on Cocoa. That being said,
it's probably 95% the same. We implement things from Cocoa we see as
useful. One of the things that will be implemented shortly is
NSToolbar, because many people find it useful.
* (Last I looked) it had very little GUI stuff available, so again,
it's probably not entirely suited to the original poster's
requirements
Wrong, wrong wrong. I use GNUstep's GUI daily, and it works just fine.
GNUstep's AppKit works, and is being improved by the week. This is pure
FUD, and I believe this kind of misinformed FUD-slinging is why more
people don't look into it.
* They sometimes deviate and do things their own way, because they
feel the OpenStep method is not good enough (which may be the case,
but still, lost compatibility...)
Wrong. The OpenStep Spec is not a Holy Grail. There are instances where
things were implemented in sub-optimal ways, and we fix those
instances. There are also instances where Apple has implemented certain
things in sub-optimal ways. For what it's worth, often times, if we
come across a compatibility issue, we choose to go with the way that
Cocoa has implemented it, even if there's a technically better way to
do it. That being said, we're not in lockstep with Apple's
implementations, nor do we intend to be.
* They sometimes can get lazy and don't do things "properly" (e.g.
their Distributed Objects implementation works differently to Apple's,
for better or worse)
There are technical reasons for this that are beyond the scope of this
e-mail, and beyond the scope of my ability to clearly explain. Someone
over in email@hidden would be happy to explain it to you if
you really do care.
Also note that since it's GPL'd, you might have trouble using it in
your program, unless you too adopt the GPL.
FUD FUD FUD FUD FUD!!!!! It's *L*GPLed. LGPL, not GPL. This is a huge
difference, as the LGPL allows you to use it without the whole
GPL-contamination issue that so many GPL-fudders love to go on about.
Read the license(s) some time if you don't understand.
--
Alex Perez
email@hidden
"Error of opinion may be tolerated where reason is left free to combat
it."
--Thomas Jefferson
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.