Hi,
I'd make a gui release compatible with (ie implementing all of) an older
version of AppKit (probably OSX 10.2).
That is a very good idea and would provide a good milestone. 10.2
shouldn't be soo hard, I don't know what is missing. I do port quite
some code between 10.2 and gnustep, but granted I do not use much of
some Cocoa additions because I don't like them
Mostly I noticed is that our implementations are a bit raw or incomplete
but present
I'd not consider the state of the theme engine a show-stopper ... it's an extra
API and can be marked as unstable while still having the AppKit API be stable.
Not a show stopper in terms of features, but I'd consider bad bugs
stoppers.
Make a new 'stable' release (this year!) formally declared as OSX10.4
compatible ... possibly to be versioned as gnustep-base-10.4 for marketing
purposes.
Please don't do that, it sounds so bad! The naming I mean, not the
statement about compatibility.
It ties us too much to apple, it sounds ugly. Also it makes us...
immediateley appear obsolete and mark as such forever since we will
always be behind. When perhaps we already have 10.5 and 10.6 features...
In this release, move to compatibility with the Apple objc runtime as much as
possible.
What does this mean? are we going to require libobjc2 ??
Riccardo
_______________________________________________
Discuss-gnustep mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/discuss-gnustep
