Re: GNUstep ROADMAP
Richard Frith-Macdonald schrieb: I'm with Fred on this one ... certainly on partially implemented classes, but also (though less strongly) on completely empty ones. I think there is absolutely zero risk of someone wasting loads of time porting only to find something critical missing... as long as our documentation does not tell lies (and little chance of it even then). We do need to make sure that the documentation is up to date, so it says which methods of which classes are unimplemented. IMO partially implemented classes tell people that there is some hope of the classes being done in future ... or at least that the GNUstep project would look favourably upon people contributing in those areas. In fact it would probably be good if unimplemented methods actually generated an NSLog explicitly asking for an implementation to be contributed. Maybe I should add a macro to NSDebug.h to do that? Having a completely unimplemented class there gives us a good placeholder for the documentation that tells people that the class is unimplemented, and maybe what the current plans are for it. I can see the argument here for removing the class (people aren't likely to think the class exists if there is no trace of it), but I think that a header file that's clearly a shell, and documentation that states that the class is unimplemented, is equally clear. We could document such empty classes with a note to say that someone (or nobody) is working on them, and a pointer to the task list on the website for current status. FWIW, I agree. Cheers, David ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: GNUstep ROADMAP
Citát David Ayers [EMAIL PROTECTED]: Richard Frith-Macdonald schrieb: snip Having a completely unimplemented class there gives us a good placeholder for the documentation that tells people that the class is unimplemented, and maybe what the current plans are for it. I can see the argument here for removing the class (people aren't likely to think the class exists if there is no trace of it), but I think that a header file that's clearly a shell, and documentation that states that the class is unimplemented, is equally clear. We could document such empty classes with a note to say that someone (or nobody) is working on them, and a pointer to the task list on the website for current status. FWIW, I agree. How difficult it would be to hack autogsdoc objective-c parser to parse GNUstep sources and generate a list of unimplemented methods (either marked as not implemented or being only in @interface)? Simple html table (with css): | Class | Method | Description | Stefan -- http://stefan.agentfarms.net First they ignore you, then they laugh at you, then they fight you, then you win. - Mahatma Gandhi ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: GNUstep ROADMAP
On 28 Nov 2005, at 09:17, Stefan Urbanek wrote: How difficult it would be to hack autogsdoc objective-c parser to parse GNUstep sources and generate a list of unimplemented methods (either marked as not implemented or being only in @interface)? Simple html table (with css): | Class | Method | Description | Easy to get the parser to recognise empty implementations ... but what to do about it is not clear. I like the idea though. How about ... if the parser could warn about empty implementations, so we know when something needs doing, and if no documentation comment is provided for the method, it could generate standard stuff about the method not being implemented yet (in the place where is currently generates the 'documentation forthcoming' message. Generally, if a class is abstract/semi-abstract then subclasses are supposed to override methods ... so an empty implementation here could be quite OK ... but we could get the parser to check to see if it has seen the override-subclass / markup in the comment for the method, and accept an empty implementation as OK in that case. ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Mon Nov 28 06:34:13 EST 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.1.0. Mon Nov 28 03:58:26 CET 2005 Success Compile powerpc-apple-darwin7.9.0 Mon Nov 28 03:25:46 MST 2005 Success Compile sparc-sun-solaris2.7 Mon Nov 28 02:08:34 EST 2005
Re: GNUstep ROADMAP
Citát Richard Frith-Macdonald [EMAIL PROTECTED]: On 28 Nov 2005, at 09:17, Stefan Urbanek wrote: How difficult it would be to hack autogsdoc objective-c parser to parse GNUstep sources and generate a list of unimplemented methods (either marked as not implemented or being only in @interface)? Simple html table (with css): | Class | Method | Description | Easy to get the parser to recognise empty implementations ... but what to do about it is not clear. Put on the webpage: development wanted. I like the idea though. How about ... if the parser could warn about empty implementations, so we know when something needs doing, and if no documentation comment is provided for the method, it could generate standard stuff about the method not being implemented yet (in the place where is currently generates the 'documentation forthcoming' message. It can be good for documentation where target would be GNUstep-core developers. However, for GNUstep users (developers of gnustep frameworks or applications) it would be a noise in the documentation. On the other hand, it can serve as a signal for developers that are willing to contribute... Generally, if a class is abstract/semi-abstract then subclasses are supposed to override methods ... so an empty implementation here could be quite OK ... but we could get the parser to check to see if it has seen the override-subclass / markup in the comment for the method, and accept an empty implementation as OK in that case. Sounds good. Stefan -- http://stefan.agentfarms.net First they ignore you, then they laugh at you, then they fight you, then you win. - Mahatma Gandhi ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
[Gnustep-cvs] gnustep/core/base ChangeLog Tools/AGSOutput.h T...
CVSROOT:/cvsroot/gnustep Module name:gnustep Branch: Changes by: Richard Frith-Macdonald [EMAIL PROTECTED] 05/11/28 12:36:47 Modified files: core/base : ChangeLog core/base/Tools: AGSOutput.h AGSOutput.m AGSParser.h AGSParser.m Log message: Get parser to spot unimplemented methods. CVSWeb URLs: http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/core/base/ChangeLog.diff?tr1=1.2671tr2=1.2672r1=textr2=text http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/core/base/Tools/AGSOutput.h.diff?tr1=1.18tr2=1.19r1=textr2=text http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/core/base/Tools/AGSOutput.m.diff?tr1=1.64tr2=1.65r1=textr2=text http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/core/base/Tools/AGSParser.h.diff?tr1=1.23tr2=1.24r1=textr2=text http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/core/base/Tools/AGSParser.m.diff?tr1=1.75tr2=1.76r1=textr2=text
[Gnustep-cvs] gnustep/core/base ChangeLog Tools/AGSHtml.m Too...
CVSROOT:/cvsroot/gnustep Module name:gnustep Branch: Changes by: Richard Frith-Macdonald [EMAIL PROTECTED] 05/11/28 12:59:59 Modified files: core/base : ChangeLog core/base/Tools: AGSHtml.m AGSOutput.m autogsdoc.m gsdoc.gsdoc Added files: core/base/Tools: gsdoc-1_0_3.dtd Log message: Improve markup for overriding methods CVSWeb URLs: http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/core/base/ChangeLog.diff?tr1=1.2672tr2=1.2673r1=textr2=text http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/core/base/Tools/gsdoc-1_0_3.dtd?rev=1.1 http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/core/base/Tools/AGSHtml.m.diff?tr1=1.96tr2=1.97r1=textr2=text http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/core/base/Tools/AGSOutput.m.diff?tr1=1.65tr2=1.66r1=textr2=text http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/core/base/Tools/autogsdoc.m.diff?tr1=1.94tr2=1.95r1=textr2=text http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/core/base/Tools/gsdoc.gsdoc.diff?tr1=1.12tr2=1.13r1=textr2=text
[Gnustep-cvs] gnustep/core/base/Tools GNUmakefile
CVSROOT:/cvsroot/gnustep Module name:gnustep Branch: Changes by: Richard Frith-Macdonald [EMAIL PROTECTED] 05/11/28 13:44:15 Modified files: core/base/Tools: GNUmakefile Log message: Install dtd CVSWeb URLs: http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/core/base/Tools/GNUmakefile.diff?tr1=1.62tr2=1.63r1=textr2=text
Re: GNUstep ROADMAP
Richard, --- Richard Frith-Macdonald [EMAIL PROTECTED] wrote: I'm with Fred on this one ... certainly on partially implemented classes, but also (though less strongly) on completely empty ones. I think there is absolutely zero risk of someone wasting loads of time porting only to find something critical missing... as long as our documentation does not tell lies (and little chance of it even then). We do need to make sure that the documentation is up to date, so it says which methods of which classes are unimplemented. IMO partially implemented classes tell people that there is some hope of the classes being done in future ... or at least that the GNUstep project would look favourably upon people contributing in those areas. In fact it would probably be good if unimplemented methods actually generated an NSLog explicitly asking for an implementation to be contributed. Maybe I should add a macro to NSDebug.h to do that? Having a completely unimplemented class there gives us a good placeholder for the documentation that tells people that the class is unimplemented, and maybe what the current plans are for it. I can see the argument here for removing the class (people aren't likely to think the class exists if there is no trace of it), but I think that a header file that's clearly a shell, and documentation that states that the class is unimplemented, is equally clear. We could document such empty classes with a note to say that someone (or nobody) is working on them, and a pointer to the task list on the website for current status. Okay, you've convinced me. I agree. :) So long as the documentation is clear, I see no issue. Later, GJC Gregory John Casamento -- Principal Consultant, Open Logic Corp. (A MD Corp.) ## Maintainer of Gorm (IB Equiv.) for GNUstep. ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
[Gnustep-cvs] gnustep/core/base/Tools AGSIndex.m
CVSROOT:/cvsroot/gnustep Module name:gnustep Branch: Changes by: Richard Frith-Macdonald [EMAIL PROTECTED] 05/11/28 16:12:59 Modified files: core/base/Tools: AGSIndex.m Log message: Disambiguate methods in classes and protocols ... use the class version. CVSWeb URLs: http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/core/base/Tools/AGSIndex.m.diff?tr1=1.39tr2=1.40r1=textr2=text
[Gnustep-cvs] gnustep/core/base Source/NSSocketPortNameServer...
CVSROOT:/cvsroot/gnustep Module name:gnustep Branch: Changes by: Richard Frith-Macdonald [EMAIL PROTECTED] 05/11/28 17:14:47 Modified files: core/base/Source: NSSocketPortNameServer.m core/base/Tools: AGSHtml.m AGSIndex.m Log message: More documentation tweaks CVSWeb URLs: http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/core/base/Source/NSSocketPortNameServer.m.diff?tr1=1.10tr2=1.11r1=textr2=text http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/core/base/Tools/AGSHtml.m.diff?tr1=1.97tr2=1.98r1=textr2=text http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/core/base/Tools/AGSIndex.m.diff?tr1=1.40tr2=1.41r1=textr2=text
[Gnustep-cvs] gnustep/core/make ChangeLog GNUmakefile.in
CVSROOT:/cvsroot/gnustep Module name:gnustep Branch: Changes by: Richard Frith-Macdonald [EMAIL PROTECTED] 05/11/28 21:07:45 Modified files: core/make : ChangeLog GNUmakefile.in Log message: More backslash support. CVSWeb URLs: http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/core/make/ChangeLog.diff?tr1=1.1204tr2=1.1205r1=textr2=text http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/core/make/GNUmakefile.in.diff?tr1=1.134tr2=1.135r1=textr2=text
[Gnustep-cvs] gnustep/dev-libs/gdl2 ChangeLog EOControl/EOCon...
CVSROOT:/cvsroot/gnustep Module name:gnustep Branch: Changes by: David Ayers [EMAIL PROTECTED] 05/11/28 22:10:05 Modified files: dev-libs/gdl2 : ChangeLog dev-libs/gdl2/EOControl: EOControl.h EOEditingContext.h EOEditingContext.m EOUndoManager.h GNUmakefile Added files: dev-libs/gdl2/EOControl: EOSharedEditingContext.h EOSharedEditingContext.m Log message: * EOControl/EOSharedEditingContext.[hm]: New files. * EOControl/EOEditingContext.[hm]: Use EOSharedEditingContext. (sharedEditingContext, setSharedEditingContext:): New methods. (-initWithParentObjectStore:): Handle EOSharedEditingContext. (-dealloc, -faultForGlobalID:editingContext:): Ditto. (-objectForGlobalID:, -globalIDForObject:): Ditto. (-initializeObject:withGlobalID:editingContext:): Ditto. (-refaultObject:withGlobalID:editingContext:): Ditto. (-_processInitializedObjectsInSharedContext:): New method. (-_defaultEditingContextNowInitialized:): Ditto. (-_objectsInitializedInSharedContext:) Ditto. (-_defaultSharedEditingContextWasInitialized:) Ditto. * EOControl/EOControl.h: Added EOSharedEditingContext.h. * EOControl/GNUmakefile: Added EOSharedEditingContext.[hm]. CVSWeb URLs: http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/dev-libs/gdl2/ChangeLog.diff?tr1=1.252tr2=1.253r1=textr2=text http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/dev-libs/gdl2/EOControl/EOSharedEditingContext.h?rev=1.1 http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/dev-libs/gdl2/EOControl/EOSharedEditingContext.m?rev=1.1 http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/dev-libs/gdl2/EOControl/EOControl.h.diff?tr1=1.7tr2=1.8r1=textr2=text http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/dev-libs/gdl2/EOControl/EOEditingContext.h.diff?tr1=1.12tr2=1.13r1=textr2=text http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/dev-libs/gdl2/EOControl/EOEditingContext.m.diff?tr1=1.34tr2=1.35r1=textr2=text http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/dev-libs/gdl2/EOControl/EOUndoManager.h.diff?tr1=1.7tr2=1.8r1=textr2=text http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/dev-libs/gdl2/EOControl/GNUmakefile.diff?tr1=1.13tr2=1.14r1=textr2=text
[Gnustep-cvs] gnustep/dev-apps/test/Testsuite/gdl2/EOSharedEditingContext
CVSROOT:/cvsroot/gnustep Module name:gnustep Branch: Changes by: David Ayers [EMAIL PROTECTED] 05/11/28 22:11:32 gnustep/dev-apps/test/Testsuite/gdl2/EOSharedEditingContext Update of /cvsroot/gnustep/gnustep/dev-apps/test/Testsuite/gdl2/EOSharedEditingContext In directory savannah:/tmp/cvs-serv21962/EOSharedEditingContext Log Message: Directory /cvsroot/gnustep/gnustep/dev-apps/test/Testsuite/gdl2/EOSharedEditingContext added to the repository
[Gnustep-cvs] gnustep/dev-apps/test/Testsuite ChangeLog gdl2/...
CVSROOT:/cvsroot/gnustep Module name:gnustep Branch: Changes by: David Ayers [EMAIL PROTECTED] 05/11/28 22:16:56 Modified files: dev-apps/test/Testsuite: ChangeLog dev-apps/test/Testsuite/gdl2/EODataSource: test00.m Added files: dev-apps/test/Testsuite/gdl2/EOSharedEditingContext: EOSharedEditingContext00.m EOSharedEditingContext01.m Log message: * gdl2/EODataSource/test00.m: Make date reproducable. * gdl2/EOSharedEditingContext/EOSharedEditingContext00.m: New test. * gdl2/EOSharedEditingContext/EOSharedEditingContext01.m: Ditto. CVSWeb URLs: http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/dev-apps/test/Testsuite/ChangeLog.diff?tr1=1.27tr2=1.28r1=textr2=text http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/dev-apps/test/Testsuite/gdl2/EODataSource/test00.m.diff?tr1=1.3tr2=1.4r1=textr2=text http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/dev-apps/test/Testsuite/gdl2/EOSharedEditingContext/EOSharedEditingContext00.m?rev=1.1 http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/dev-apps/test/Testsuite/gdl2/EOSharedEditingContext/EOSharedEditingContext01.m?rev=1.1
[Gnustep-cvs] gnustep/core/gui ChangeLog Source/NSTabView.m S...
CVSROOT:/cvsroot/gnustep Module name:gnustep Branch: Changes by: Fred Kiefer [EMAIL PROTECTED] 05/11/29 00:16:10 Modified files: core/gui : ChangeLog core/gui/Source: NSTabView.m NSTextField.m Log message: GUI patches by Andreas Höschler. CVSWeb URLs: http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/core/gui/ChangeLog.diff?tr1=1.2627tr2=1.2628r1=textr2=text http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/core/gui/Source/NSTabView.m.diff?tr1=1.49tr2=1.50r1=textr2=text http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/core/gui/Source/NSTextField.m.diff?tr1=1.62tr2=1.63r1=textr2=text
