[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Sat, 23 Dec 2006 19:32:44 +0000
On 23 Dec 2006, at 19:14, Gregory John Casamento wrote:
A quick analysis shows the following things:
1) They are missing many Cocoa classes
2) They do not use native widgets, they draw thier own, like we do.
3) Much of the nib decoding logic which is currently present in
GNUstep is not in Cocotron. That is to say... there are many cases
that the Cocotron code cannot handle properly when unarchiving
Cocoa nibs. There are other problems along these lines as well,
such as some classes are missing keys which are needed to function
4) Cocoa compatible keyed nib encoding is entirely missing
5) The only way you can build it is by using Xcode on a mac and
cross compiling it for other platforms, this is a major drawback.
6) Printing appears to be non-functional, or, at least severely
restricted... more so than GNUstep's printing functionality
7) The TextEditor example is completely bogus. None of the
connections in the nib are actually made... none of the menus
work. All it does is bring up a window with an NSTextField in it
and look halfway nice. Other than that the example is non-functional.
On the foundation side, much is missing too ... distributed objects,
xml parsing, streams, url handling etc and also large chunks of
functionality of a few classes I looked at.
I'm quite sure there's more, but the above is just from looking at
it for about 10 minutes. :) There are, however, a few things that
can be learned from the project... particularly how the code is
organized. I like the idea of having class clusters in thier own
directories/subprojects, it seems like the right thing to do.
I rather liked that too.
The only reason that Cocotron looks good under Windows, I suspect,
is because it was themed that way. It likely looks precisely the
same under Linux.
It's unfortunate that all of these efforts are going on in parallel
with GNUstep (libFoundation, Cocotron, AJRFoundation) instead of
people getting together and collaborating on one project.
I very strongly agree with that ... it always saddens me to see
people re-inventing what GNUstep already does and duplicating effort
rather than joining in. I wish I know how to persuade people to
contribute to a joint effort. Perhaps we should try posting requests
for volunteers to all these projects and to any other mailing lists
where objc developers might hang out? I guess we would need to
figure out *why* (assuming reasons other than simple ignorance)
people do their own thing rather than a group effort, and try to
address any mistaken impressions of the project in any email we sent
out. However, my impression is that unfortunately the reason is
often either religious differences over licensing/copyright or simple
desire for total control over their own project, and no reasoning
will convince people in those cases :-( Even so, it's probably worth
In conclusion, GNUstep is a much more mature and complete project
than Cocotron is.
Yes. We should try to get them on board.
Re: Cocotron, Andrew Sveikauskas, 2006/12/23
Re: Cocotron, Helge Hess, 2006/12/23
Re: Cocotron, Fred Kiefer, 2006/12/25
Message not available
- Cocotron, Helge Hess, 2006/12/23
- Re: Cocotron, Gregory John Casamento, 2006/12/23
- Re: Cocotron,
Richard Frith-Macdonald <=
- Re: Cocotron, Banlu Kemiyatorn, 2006/12/23
- Re: Cocotron, Helge Hess, 2006/12/23
- Re: Cocotron, Matt Rice, 2006/12/24
- Re: Cocotron, Helge Hess, 2006/12/24
- Re: Cocotron, Richard Frith-Macdonald, 2006/12/24