GNUstepWiki - Recent changes [en]

User talk:Bubble.rogue

Bubble.rogue — Wed, 13 Mar 2013 21:09:23 GMT

Template:GNUstep News

Fred — Sun, 10 Mar 2013 13:46:18 GMT

Main Page

Fred — Sun, 10 Mar 2013 13:44:06 GMT

Success Stories

Bheron — Mon, 04 Mar 2013 17:44:58 GMT

/* Brilliant Service */

Report Bugs

Rfm — Thu, 28 Feb 2013 07:21:03 GMT

/* What to Report */

 I will put my own research for extending Objective-C and the GNUstep UI with SmallTalk in there.
+There is an iOS version in the works, available as separate tarball, versioned, at the download page.
 <b>GNUrbis et GNOrbis : </b><br>

+=== Mar 02 2013 ===
+* '''GNUstep [[Gui]]  0.23.0 stable release'''
+: ([ftp://ftp.gnustep.org/pub/gnustep/core/gnustep-gui-0.23.0.tar.gz Download Gui])
+* '''GNUstep [[Back]]  0.23.0 stable release'''
+: ([ftp://ftp.gnustep.org/pub/gnustep/core/gnustep-back-0.23.0.tar.gz Download Back])
+* '''GNUstep [[Make]]  2.6.3 stable release'''
+: ([ftp://ftp.gnustep.org/pub/gnustep/core/gnustep-make-2.6.3.tar.gz Download Make])
+* '''GNUstep [[Base]]  1.24.3 stable release'''
+: ([ftp://ftp.gnustep.org/pub/gnustep/core/gnustep-base-1.24.3.tar.gz Download Base])
 === Oct 21 2012 ===
 * '''[[MPDCon.app]]  1.3'''

 Sounds interesting? Have a look at the more in-depth [[Introduction to GNUstep|introduction]]!
-* '''Download Stable Core Packages :''' [http://ftpmain.gnustep.org/pub/gnustep/core/gnustep-make-2.6.2.tar.gz Make v2.6.2], [http://ftpmain.gnustep.org/pub/gnustep/core/gnustep-base-1.24.0.tar.gz Base v1.24.0], [http://ftpmain.gnustep.org/pub/gnustep/core/gnustep-gui-0.22.0.tar.gz GUI v0.22.0], [http://ftpmain.gnustep.org/pub/gnustep/core/gnustep-back-0.22.0.tar.gz Back v0.22.0]
+* '''Download Stable Core Packages :''' [http://ftpmain.gnustep.org/pub/gnustep/core/gnustep-make-2.6.3.tar.gz Make v2.6.3], [http://ftpmain.gnustep.org/pub/gnustep/core/gnustep-base-1.24.3.tar.gz Base v1.24.3], [http://ftpmain.gnustep.org/pub/gnustep/core/gnustep-gui-0.23.0.tar.gz GUI v0.23.0], [http://ftpmain.gnustep.org/pub/gnustep/core/gnustep-back-0.23.0.tar.gz Back v0.23.0]
 * '''Download Unstable Core packages : ''' (NOTE: Now only in the SVN software repository)

+= Brilliant Service =
+[http://www.brilliantservice.co.jp/viking/ Brilliant Service] is a vendor in Japan working on creating a platform for a Head Mounted Display.   They are using GNUstep as the basis for the Objective-C based programming environment.  Their press release is [http://hmdviking.blogspot.jp/ here].
 = Apportable =
 [http://www.apportable.com Apportable] is a mobile platform for porting applications from iOS to Android.   Apportable has used [http://www.apportable.com/open_source GNUstep] to port many well known apps from the iOS app store to all kinds of Android based devices.

 ** If you have a problem compiling a library or application, please send the complete output of make or at least enough to show what went wrong. If you are using sh or bash, do this: <tt>make messages=yes > output.txt 2>&1</tt>
-The provision of a test/demonstration program is very important for getting the bug fixed quickly. Often, with no test program, we will not do anything with the report for a long time unless it is immediately obvious what the problem is.
+The provision of a test/demonstration program is very important for getting the bug fixed quickly. Often, with no test program, we will not do anything with the report for a long time unless it is immediately obvious what the problem is.  If possible, the test program should be in the form of a testcase (to be built/run using the gnustep-tests script) for inclusion into the testsuites - such testcases can readily be run on MacOSX as a reference platform so that we can tell what the correct behavior is.
 If your problem is that some API from OSX 10.5 or later is unimplemented, please report it as a 'Change Request' rather than a 'Bug', and (ideally) contribute an implementation of the missing functionality.  In this case please provide documentation for the missing API and a test case to demonstrate what it does.
 Actually fixing problems is even more appreciated than sending in bug reports. To do this, first fix the bug and make sure it works. Then send in a diff file containing the differences between the old version of the file(s) you changed and the new version. Use the diff (<tt>diff -u oldfile newfile > file.patch</tt>) program to do this.
 For new APIs, provide header changes as well as source code changes, with macros bracketing the changes to specify which version of OSX they correspond to (see existing headers or examples) and comments in the headers documenting the behaviors of new methods etc.
-For both bugfixes and new functionality, please provide testcases (see the existing testsuite for examples) which demonstrate the correct behavior of the code.
+For both bugfixes and new functionality, please, please, PLEASE provide testcases (see the existing testsuite for examples) which demonstrate the correct behavior of the code.  Without testcases it's much harder to review patches, so if you don't provide testcases, your patch may simply be ignored.  Testcases are executed using the gnustep-tests script from the gnustep-make package.
-Then add a ChangeLog entry in front of this and send the whole thing to the bug database.
+Add a ChangeLog entry in front of the diff file, and send the whole thing (patch plus testcases) to the bug database.
 If you use emacs, it is easy to add a ChangeLog entry. Just edit the file you changed, and move the cursor to the function or method you changed, then type <tt>M-x add-change-log-entry</tt> and emacs automatically formats an entry in the ChangeLog file with the information on the file and function you changed. You just need to add a comment about what was fixed. Note: Don't send a diff of the ChangeLog file, just send a copy of your ChangeLog entry normally. Here is an example ChangeLog: