Re: make help
Adrian Robert wrote: On 2006-09-27 23:04:07 -0400 Nicola Pero <[EMAIL PROTECTED]> wrote: This could be an interesting idea, but the main problem is that someone looking for help probably wouldn't know that to get help you need to use 'make help=yes'. Maybe whenever you type 'make' we could always print a line saying 'Please type 'make help=yes' for help' ... I like this one. In fact, you could have a msg like this: GNUstep make (version x.xx); please type "make help=yes" for help. That would serve 3 purposes -- tell invoker that GNUstep make is being used (in case they care), the version, and how to get help. Reading the make manual, it specifies for installed stripped versions: make install-strip, from this I find it more logical to use: install-strip install-nodebug and going on in the same logic: print-help # prints complete help print-targets # prints only the available targets print-options # prints the available options print-version # Source version print-gnustep-make-version # GNUstep-make version print-gnustep-base-version etc... Just my 2 cents. Dennis ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: make help
On 2006-09-27 23:04:07 -0400 Nicola Pero <[EMAIL PROTECTED]> wrote: This could be an interesting idea, but the main problem is that someone looking for help probably wouldn't know that to get help you need to use 'make help=yes'. Maybe whenever you type 'make' we could always print a line saying 'Please type 'make help=yes' for help' ... I like this one. In fact, you could have a msg like this: GNUstep make (version x.xx); please type "make help=yes" for help. That would serve 3 purposes -- tell invoker that GNUstep make is being used (in case they care), the version, and how to get help. ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: make help
>> I was thinking of adding a little bit of inline help for gnustep-make. >> What's the best way ? I was thinking of adding a target like >> >> $> make help > > I'm all for adding more documentation and help... > but... please *don't* make it a target! Eh, not many other options though ;-) I agree there is a risk of conflict with valid targets. :-/ Maybe we just leave it as it is. > Here are some other ideas you could use: > info Well, 'make info' is traditionally used to build texinfo documentation ... btw this probably is an excellent example in support of your point about conflicts with valid targets! ;-) > helpme > summary > options > gnustep-make-help > shortform ... and those are a bit too obscure > or make it an option > info=yes > summary=yes > shortform=yes This could be an interesting idea, but the main problem is that someone looking for help probably wouldn't know that to get help you need to use 'make help=yes'. Maybe whenever you type 'make' we could always print a line saying 'Please type 'make help=yes' for help' ... Not sure. :-( Suggestions welcome :-) Thanks ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: [Gnustep-cvs] r23599 - in /libs/gui/trunk: ChangeLog Source/NSTableView.m
--- Fred Kiefer <[EMAIL PROTECTED]> wrote: > HI Matt, > > could you please explain this change? When writing > this method I took > great care to implement it the way Quentin did > describe the behaviour of > Cocoa in his mail from the 8th of September. Was the > description wrong > or just my implementation? > I seem to have not recieved Quentin's description, and can't find it in the archives, so can't comment on it according to the documentation: "The delegate can implement this method to disallow editing of specific cells." this says nothing of allowing inedible cells to become editable, as it was implemented if a delegate did not respond to tableView:shouldEditTableColumn:row: and a table column was ineditable, it would allow editing it ignored editable columns entirely always returning yes, so it didn't actually allow you to do any disallowing, anyhow according to my testing this was how it worked, though maybe its changed in later releases, if it has changed and should allow editing of inedible columns it should probably be rolled into _shouldEdit... and return [tableColumn isEditable] for the case where the delegate doesn't respond > Cheers > Fred > > matt rice schrieb: > > Author: ratmice > > Date: Sat Sep 23 23:53:25 2006 > > New Revision: 23599 > > > > URL: > http://svn.gna.org/viewcvs/gnustep?rev=23599&view=rev > > Log: > >* Source/NSTableView.m > (_isCellEditableColumn:row:): Allow > >delegate to limit editablility of editable > columns. > > > > > > Modified: > > libs/gui/trunk/ChangeLog > > libs/gui/trunk/Source/NSTableView.m > > > __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: make help
Nicola Pero wrote: I was thinking of adding a little bit of inline help for gnustep-make. What's the best way ? I was thinking of adding a target like $> make help This is gnustep-make 1.13.0. Most common targets: make all (builds) make install (installs) make uninstall (uninstalls) make clean (deletes built files) make distclean (deletes all built files) make dist (creates a .tar.gz of the software sources) Most common options that can be used with any of the targets: debug=no (turns off generation of debug symbols) strip=yes (strips executables and objects before installing) shared=no (builds static executable and objects) messages=yes (prints verbosely all commands being executed) GNUSTEP_INSTALLATION_DIR=/usr/GNUstep/System (installs in the specified dir) $> I'm all for adding more documentation and help... but... please *don't* make it a target! $> make help is used to generate application help files. > Anyone has got a better idea ? The obvious one would be --help but that'd invoke 'make's own, of course ;) Here are some other ideas you could use: info helpme summary options gnustep-make-help shortform or make it an option info=yes summary=yes shortform=yes Regards, Sheldon ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
make help
I was thinking of adding a little bit of inline help for gnustep-make. What's the best way ? I was thinking of adding a target like $> make help This is gnustep-make 1.13.0. Most common targets: make all (builds) make install (installs) make uninstall (uninstalls) make clean (deletes built files) make distclean (deletes all built files) make dist (creates a .tar.gz of the software sources) Most common options that can be used with any of the targets: debug=no (turns off generation of debug symbols) strip=yes (strips executables and objects before installing) shared=no (builds static executable and objects) messages=yes (prints verbosely all commands being executed) GNUSTEP_INSTALLATION_DIR=/usr/GNUstep/System (installs in the specified dir) $> Anyone has got a better idea ? Thanks ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: [Gnustep-cvs] r23599 - in /libs/gui/trunk: ChangeLog Source/NSTableView.m
HI Matt, could you please explain this change? When writing this method I took great care to implement it the way Quentin did describe the behaviour of Cocoa in his mail from the 8th of September. Was the description wrong or just my implementation? Cheers Fred matt rice schrieb: > Author: ratmice > Date: Sat Sep 23 23:53:25 2006 > New Revision: 23599 > > URL: http://svn.gna.org/viewcvs/gnustep?rev=23599&view=rev > Log: >* Source/NSTableView.m (_isCellEditableColumn:row:): Allow >delegate to limit editablility of editable columns. > > > Modified: > libs/gui/trunk/ChangeLog > libs/gui/trunk/Source/NSTableView.m > ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
GNUstep Testfarm Results
Test results for GNUstep as of Wed Sep 27 06:34:17 EDT 2006 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-netbsdelf3.0 Wed Sep 27 03:56:10 CEST 2006 Fail Compile i686-pc-linux-gnu Tue Sep 26 22:23:57 CEST 2006 Success Compile powerpc-apple-darwin7.9.0 Wed Sep 27 03:08:33 MDT 2006 Success Compile sparc-sun-solaris2.7 Wed Sep 27 02:04:46 EDT 2006 Success Compile x86_64-unknown-linux-gnu Wed Sep 27 04:06:47 BST 2006 ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
