[Gnustep-cvs] gnustep/core/base ChangeLog Source/NSArray.m

[matt rice]

CVSROOT:/cvsroot/gnustep
Module name:gnustep
Branch: 
Changes by: matt rice <[EMAIL PROTECTED]>   05/05/21 05:16:19

Modified files:
core/base  : ChangeLog 
core/base/Source: NSArray.m 

Log message:
* Source/NSArray.m (NSArray -removeObject:): Fix macro conditional
so we release the object.

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/core/base/ChangeLog.diff?tr1=1.2528&tr2=1.2529&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/core/base/Source/NSArray.m.diff?tr1=1.145&tr2=1.146&r1=text&r2=text

Re: Windows port direction

[Alex Perez]

David Lázaro Saz wrote:

Hi there,

Yesterday I promised to begin explaining what is that I would like  
GNUstep do on the Windows side.  That's what this message is about.


Quick turn-around. It's very nice to see someone who has a commercial 
need for the GNUstep-win32 stuff to work properly. We've been in need of 
exactly someone like you for quite some time now.


What I would like it to be?  The quick answer would be everything to  
everybody!  But as agreeable as that would be, it won't be a very  clear 
goal. So let's begin defining those goals and explain the  current 
situation as I see it.

Sounds good.



First, I'd like to be capable of doing development both on Windows  and 
on Mac OS X.  That's because I'm usually on-the-go and the only  thing I 
have at hand is my PowerBook.  I've got the latest Virtual PC  version 
installed and running but it is very slow for full  recompiles.  Thanks 
God for incremental compilation, though.


During the last night I got the full MinGW toolchain working on Mac  OS 
X.  Is there any reference for cross-compiling GNUstep to contrast  what 
I am doing to see if I'm doing things right?  That way I can  correct 
any bad behaviour that appears.  The only thing that I found  was last 
July's responses from Nicola to this mailing list.


I'm not sure there's much info on cross-compiling GNUstep...good luck 
though...it may require some improvements to GNUstep-make.


GNUstep's mission statement says that its goal is to create a free,  
superior development environment based on OpenStep and some of  Cocoa's 
advances, taking into account the finer points of the display  model 
while remaining somewhat look and feel agnostic.  I agree  completely 
with these goals.  My intentions are only to try to define  some clearer 
goals for the Windows port so I can work with it in a  production 
environment.



Production quality apps for Windows are somewhat vaguely defined by  the 
Microsoft logo guidelines.  The technical part of those  guidelines are 
specified on the Windows Logo Program for Windows at  
 (sorry,  some 
of them are Microsoft Office documents).  I think that a  successful 
development environment should provide almost everything  covered on 
those guidelines automatically.  Granted that could mean a  long time of 
development but I think that, technically, GNUstep can  cover those and 
even more.


If it can one day, great, but I'd say it's better to focus in the short 
term on the immediate correct functioning of GS under win32, don't you 
agree?


 From the Designed for Windows XP spec v2.3, you can see that three  
areas are covered: Windows fundamentals, install/remove, and data and  
settings management.  I'll refer you to that spec for the details.


GNUstep still doesn't cover install/remove of specific applications  but 
in the future I think that it should be.  Maybe a way to  automatically 
generate installer packages (.msi) and merge modules of  the core 
libraries for ease of deployment.  There's a lot to say  about this but 
for I think that it should go to the back of the list.


Making MSIs are not difficult, but I think GNUstep on win32 should be a 
bit more mature before we create them. MSIs are also important for 
corporate deployment.


In relation with Windows fundamentals, what I need and think that  
GNUstep should cover is support for the Microsoft Windows User  
Experience guidelines and what is called _visual styles_ in the  Windows 
world.  Let's begin with the following list:


* Document the points where GNUstep doesn't respect the guidelines.   
Menus are, for example, currently in a NeXT-style panel while they  
should be on the top of each window.  The OpenStep API covers very  well 
that case so it should not be difficult.


Nope, there's already even a horizontal menubar hack  (which nets you OS 
X style global menus) and someone hacked that even further to do 
per-window menus, if I remember properly. So it's possible.


Adding support for system colours is another point.  I think that a  
complete list should be maintained somewhere.


It is, in the Windows Registry. Don't ask me where, I will have to look, 
and I will write a follow-up mail with that info later. It's not critical.


The "classic" Windows theme is also specified in the user experience  
book.  That is nice and should make it an easy and achievable first  
target.


I have had some discussions with Nicolas Roard (author of Camaelon, a 
GNUstep theming engine) about the possibility of making Camaelon support 
the Windows Theme format (the themes themselves live in 
%SYSTEMROOT%\resources\Themes) and actually use the information they 
contain to draw the UI. The reason for doing it this way is it is less a 
violation of the Steppish Way, where controls draw themselves). 
Extending Camaelon to use msstyle/mstheme files directly will of course 
only work for Windows XP. If your target organization u

Objective-C++ in GCC 4.1

[David Lázaro Saz]

Hi there,
I'm reviewing some of the docs of the makefile package and noticed  
the Objective-C++ question.  According to  GCC 4.1  
is coming with Objective-C++ support.  Should I add a notice and a  
link to that, or it's better to wait and test it?

I think that adding a notice would be nice.
Cheers,
David.

___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
http://lists.gnu.org/mailman/listinfo/gnustep-dev

Re: Bug database

[Adam Fedor]

On May 20, 2005, at 3:47 AM, Fred Kiefer wrote:
Savannah counts as open. My suggestion here is to move all the 
declined reports that are older than a month to the closed state. This 
will cause a bit of mail once, but show a more realistic statistic in 
Savannah.

Sounds good.
Ah and yes, lets work on the remaining 84 as well.
Yes :-)

___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
http://lists.gnu.org/mailman/listinfo/gnustep-dev

[Gnustep-cvs] gnustep/core/gui ChangeLog Source/NSWindow.m

[Fred Kiefer]

CVSROOT:/cvsroot/gnustep
Module name:gnustep
Branch: 
Changes by: Fred Kiefer <[EMAIL PROTECTED]> 05/05/20 14:33:43

Modified files:
core/gui   : ChangeLog 
core/gui/Source: NSWindow.m 

Log message:
Implemented animate resize.

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/core/gui/ChangeLog.diff?tr1=1.2523&tr2=1.2524&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/core/gui/Source/NSWindow.m.diff?tr1=1.325&tr2=1.326&r1=text&r2=text

[Gnustep-cvs] gnustep/core/back ChangeLog configure.ac config...

[Adrian Robert]

CVSROOT:/cvsroot/gnustep
Module name:gnustep
Branch: 
Changes by: Adrian Robert <[EMAIL PROTECTED]>   05/05/20 13:57:21

Modified files:
core/back  : ChangeLog configure.ac config.h.in 
core/back/Headers/xlib: XGGState.h 
core/back/Source/xlib: XGGState.m 

Log message:
changed some HAVE_LIBXFT #ifdefs to HAVE_XFT; clarified difference 
between the two in configure.ac and config.h.in comments

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/core/back/ChangeLog.diff?tr1=1.373&tr2=1.374&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/core/back/configure.ac.diff?tr1=1.29&tr2=1.30&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/core/back/config.h.in.diff?tr1=1.13&tr2=1.14&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/core/back/Headers/xlib/XGGState.h.diff?tr1=1.7&tr2=1.8&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/core/back/Source/xlib/XGGState.m.diff?tr1=1.29&tr2=1.30&r1=text&r2=text

[Gnustep-cvs] gnustep/core/gui ChangeLog Headers/AppKit/NSRes...

[Fred Kiefer]

CVSROOT:/cvsroot/gnustep
Module name:gnustep
Branch: 
Changes by: Fred Kiefer <[EMAIL PROTECTED]> 05/05/20 12:31:42

Modified files:
core/gui   : ChangeLog 
core/gui/Headers/AppKit: NSResponder.h 
core/gui/Source: NSApplication.m NSControl.m NSResponder.m 
 NSView.m NSWindow.m 

Log message:
Added new NSResponder method declarations and implemented 
shouldBeTreatedAsInkEvent:.

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/core/gui/ChangeLog.diff?tr1=1.2522&tr2=1.2523&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/core/gui/Headers/AppKit/NSResponder.h.diff?tr1=1.2&tr2=1.3&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/core/gui/Source/NSApplication.m.diff?tr1=1.277&tr2=1.278&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/core/gui/Source/NSControl.m.diff?tr1=1.65&tr2=1.66&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/core/gui/Source/NSResponder.m.diff?tr1=1.39&tr2=1.40&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/core/gui/Source/NSView.m.diff?tr1=1.231&tr2=1.232&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/core/gui/Source/NSWindow.m.diff?tr1=1.324&tr2=1.325&r1=text&r2=text

[Gnustep-cvs] GNUstep Testfarm Results

[Adam Fedor]

Test results for GNUstep as of Fri May 20 06:34:12 EDT 2005
If a particular system failed compilation, the logs for that system will
be placed at ftp://ftp.gnustep.org/pub/testfarm

If you would like to add your machine to this list, set up a cron job
(make sure you set up your PATH and other environment variables correctly)
to run the Startup/scripts/test-gnustep script (see the script comments 
for more info).

Success Compile i386-unknown-netbsdelf2.0.2 Fri May 20 03:58:10 CEST 2005
Success Compile powerpc-apple-darwin7.9.0 Fri May 20 04:25:13 MDT 2005
Success Compile sparc-sun-solaris2.7 Fri May 20 02:10:32 EDT 2005
Success Compile sparc64-unknown-netbsd2.0.2 Fri May 20 03:18:55 CEST 2005

Bug database

[Fred Kiefer]

Sorry for the pollution of the bug mailing list yesterday. I was doing a 
bit of cleanup in the savannah database. There are still some bug 
reports in the in-test state, with some of them I am not completely sure 
that they have been fully resolved. Perhaps everybody could have a 
second look on the bug reports he worked on?

There is still the huge amount of 121 unresolved bug reports in the 
first page of the Savannah GNUstep group, but when displaying only the 
open ones you get 84. The difference is not only caused by bugs in the 
test (14) or analysed (5) state, it mainly is constituted by declined 
bug reports (18), which Savannah counts as open. My suggestion here is 
to move all the declined reports that are older than a month to the 
closed state. This will cause a bit of mail once, but show a more 
realistic statistic in Savannah.

Ah and yes, lets work on the remaining 84 as well.
Cheers
Fred
___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
http://lists.gnu.org/mailman/listinfo/gnustep-dev