https://mediawiki.gnustep.org/api.php?action=feedcontributions&feedformat=atom&user=Aperez 2026-08-25T14:09:26Z User contributions MediaWiki 1.35.7 https://mediawiki.gnustep.org/index.php?title=Summer_Of_Code_2006&diff=3038 2006-04-26T16:11:26Z

<p>Aperez: More updates on NSDatePicker, NSTextTable, Predicates entries (done by Quentin Mathé)</p> <hr /> <div>== Summer Of Code 2006 ==<br /> <br /> The [http://code.google.com/soc/ Summer Of Code] is a Google program that offers student developers stipends to create new freely available programs or to help currently established projects. It would be an excellent opportunity for GNUstep to fund some developments.<br /> <br /> <br /> Here are some ideas:<br /> <br /> * '''Bindings, KVO support'''<br /> ** We need NSController, NSArrayController, NSObjectController, NSTreeController, NSUserDefaultController, NSValueTransformer implementations. NSSortDescriptor has already been implemented by Saso Kiselkov. The current NSTreeController is known to be a bit buggy and have an API a bit flawed, as Apple rushed the release of this class in Mac OS 10.4. It is widely believed that these shortcomings will be fixed in Leopard (10.5), so perhaps we should wait a while. <br /> ** Key Value Observing implementation was written by Richard Frith-Macdonald, and is only about 80% finished. Needs completion and testing.<br /> <br /> <br /> * '''Porting'''<br /> ** Port WebCore to GNUstep using GCC 4.1<br /> <br /> <br /> * '''General Improvements'''<br /> ** Printing Support (better postcript generation, etc.)<br /> ** Cairo backend<br /> ** Windows support<br /> ** GNUstepWeb (add script language support, etc)<br /> ** Finish input server [http://svn.gna.org/viewcvs/gnustep/libs/gui/branches/kazunobu_input_management/ support]<br /> ** Compare current API with Tiger API, indicates which are missing, and the status of the existing ones, then work to complete them... ;) The best would to have a tool which parse every headers (both from Cocoa and GNUstep) and output differences in HTML (XML probably too by the way). This would summarize missing classes, missing or partial implementation methods in existing classes and GNUstep only extensions. Eventually we should include links to the related documentation on both GNUstep and Cocoa web sites.<br /> <br /> <br /> * '''AppKit'''<br /> ** PDFKit wrapper implementation around the Freedesktop Poppler library, probably by wrapping PopplerKit (used in ViewPDF/Vindaloo, a GNUstep PDF Viewer). Afterwards, providing support in AppKit trough NSPDFImageRep would be great.<br /> *** Here is a link to [http://home.gna.org/gsimageapps/ PopplerKit/Vindaloo] that works well, but is currently lacking a maintainer. <br /> ** Text System should be cleaned, profiled and finished. Many methods in NSLayoutManager are unfinished or unimplemented, so we currently cannot tweak the test system as much as the one provided by Cocoa. (Quentin Mathe)<br /> ** We need NSTypeSetter, NSGlyphStorage, NSGlyphInfo, and NSGlyphGenerator implementations. If NSTypeSetter and NSLayoutManager were implemented, they would probably be used in Etoile. (Quentin Mathe)<br /> ** NSTextTable, NSTextTableBlock, NSTextList, &amp; NSTextBlock implementations would also bring the GNUstep text system in line with that of Cocoa as of Mac OS 10.4. The classes could be useful to build a powerful word processor. (Quentin Mathe)<br /> ** Finish once and for all the NSTableView class, and have it work properly with any kind of cells. This is a big job, but sorely needed (Quentin Mathe)<br /> ** NSOpenGL Classes could be improved, made compatible with current Cocoa implementations, and further tested (Quentin Mathe)<br /> ** NSBitmapImageRep formats: Currenly, we support only reading and writing for TIFF, read-only for GIF, JPEG, PNG, PNM. We would like to have write support for these NSBitmapImageRep categories. Afterwards, SVG reading, then write support, would be nice. (Quentin Mathe)<br /> ** NSDatePicker, NSLevelIndicator (and obligatory companion NSCell subclasses) implementations.<br /> ** Updating NSDocument architecture with numerous modern methods which were introduced in Mac OS 10.4. In 10.4, Apple deprecated many methods in NSDocument in favor of a more flexible and well-designed implementation.<br /> ** NSFormatter isn't working very well at this time (Quentin Mathe)<br /> <br /> <br /> * '''Base'''<br /> ** NSError related improvements to allow better user messages (with the new error responder chain). In Mac OS 10.4, NSDocument version uses this.<br /> ** NSLocale-compatible locale implementation could be useful for internationalization.<br /> ** NSDateComponents implementation.<br /> ** NSCalendar implementation.<br /> ** Finish the NSPredicate implementation. This was partially done by Quentin Mathe, but is untested. The most important part is not done, which is to write a parser and lexer for the custom language used by NSPredicate. Also needed for this are NSComparisonPredicate, NSCompoundPredicate, and NSExpression implementations.<br /> ** Test the NSXMLParser Cocoa class wrapper around GSXML, written by Richard-Frith Macdonald. Once this is thoroughly tested, NSXMLDocument, NSXMLDTD, and NSXMLDTDNode, and NSXMLElement, and NSXMLNode implementations may be useful for compatibility.<br /> <br /> <br /> * '''Misc'''<br /> ** Create a AJAX Framework for GNUstepWeb<br /> <br /> <br /> Feel free to add other ideas !<br /> <br /> == Note ==<br /> <br /> We need [http://code.google.com/soc/mentorfaq.html mentor(s)] to manage the volunteers...<br /> <br /> <br /> === Mentors ===<br /> <br /> - David Wetzel (dave at turbocat dot de) could mentor GSWeb related projects<br /> <br /> - Quentin Mathé is willing to mentor GUI/AppKit and some Base related projects.<br /> <br /> - Adam Fedor (backup mentor)<br /> <br /> <br /> === Students ===<br /> <br /> Nicolas Roard</div>

Aperez https://mediawiki.gnustep.org/index.php?title=Summer_Of_Code_2006&diff=3037 2006-04-26T16:04:01Z

<p>Aperez: More on NSError and update PDFKit related stuff (done by Quentin Mathé)</p> <hr /> <div>== Summer Of Code 2006 ==<br /> <br /> The [http://code.google.com/soc/ Summer Of Code] is a Google program that offers student developers stipends to create new freely available programs or to help currently established projects. It would be an excellent opportunity for GNUstep to fund some developments.<br /> <br /> <br /> Here are some ideas:<br /> <br /> * '''Bindings, KVO support'''<br /> ** We need NSController, NSArrayController, NSObjectController, NSTreeController, NSUserDefaultController, NSValueTransformer implementations. NSSortDescriptor has already been implemented by Saso Kiselkov. The current NSTreeController is known to be a bit buggy and have an API a bit flawed, as Apple rushed the release of this class in Mac OS 10.4. It is widely believed that these shortcomings will be fixed in Leopard (10.5), so perhaps we should wait a while. <br /> ** Key Value Observing implementation was written by Richard Frith-Macdonald, and is only about 80% finished. Needs completion and testing.<br /> <br /> <br /> * '''Porting'''<br /> ** Port WebCore to GNUstep using GCC 4.1<br /> <br /> <br /> * '''General Improvements'''<br /> ** Printing Support (better postcript generation, etc.)<br /> ** Cairo backend<br /> ** Windows support<br /> ** GNUstepWeb (add script language support, etc)<br /> ** Finish input server [http://svn.gna.org/viewcvs/gnustep/libs/gui/branches/kazunobu_input_management/ support]<br /> ** Compare current API with Tiger API, indicates which are missing, and the status of the existing ones, then work to complete them... ;) The best would to have a tool which parse every headers (both from Cocoa and GNUstep) and output differences in HTML (XML probably too by the way). This would summarize missing classes, missing or partial implementation methods in existing classes and GNUstep only extensions. Eventually we should include links to the related documentation on both GNUstep and Cocoa web sites.<br /> <br /> <br /> * '''AppKit'''<br /> ** PDFKit wrapper implementation around the Freedesktop Poppler library, probably by wrapping PopplerKit (used in ViewPDF/Vindaloo, a GNUstep PDF Viewer). Afterwards, providing support in AppKit trough NSPDFImageRep would be great.<br /> *** Here is a link to [http://home.gna.org/gsimageapps/ PopplerKit/Vindaloo] that works well, but is currently lacking a maintainer. <br /> ** The Text System should be cleaned, profiled and finished. Many methods in NSLayoutManager are unfinished or unimplemented, so we currently cannot tweak the test system as much as the one provided by Cocoa. (Quentin Mathe)<br /> ** We need NSTypeSetter, NSGlyphStorage, NSGlyphInfo, and NSGlyphGenerator implementations. If NSTypeSetter and NSLayoutManager were implemented, I (Quentin Mathe) would use them in Etoile.<br /> ** NSTextTable, NSTextTableBlock, NSTextList, &amp; NSTextBlock implementations would also bring the GNUstep text system in line with that of Cocoa as of Panther. NSTextList could be useful to build a powerful word processor. (Quentin Mathe)<br /> ** Finish once and for all the NSTableView class, and have it work properly with any kind of cells. This is a big job, but sorely needed (Quentin Mathe)<br /> ** The NSOpenGL Classes could be improved, made compatible with current Cocoa implementations, and further tested (Quentin Mathe)<br /> ** NSBitmapImageRep formats: Currenly, we support only reading and writing for TIFF, read-only for GIF, JPEG, PNG, PNM. We would like to have write support for these NSBitmapImageRep categories. Afterwards, SVG reading, then write support, would be nice. (Quentin Mathe)<br /> ** NSDatePicker, NSLevelIndicator (and obligatory -Cell) implementations.<br /> ** Updating NSDocument architecture with numerous modern methods which were introduced in 10.4. In 10.4, Apple deprecated many methods in NSDocument in favor of a more flexible and well-designed implementation.<br /> ** NSFormatter isn't working very well at this time (Quentin Mathe)<br /> <br /> <br /> * '''Base'''<br /> ** NSError related improvements to allow better user messages (with the new error responder chain). In Mac OS 10.4, NSDocument version uses this.<br /> ** NSLocale-compatible locale implementation could be useful for internationalization.<br /> ** NSDateComponents implementation.<br /> ** NSCalendar implementation.<br /> ** Finish the NSPredicate implementation. This was mostly done by Quentin Mathe, but is untested. The most important part is not done, which is to write a parser and lexer for the custom language used by NSPredicate. Also needed for this are NSComparisonPredicate, NSCompoundPredicate, and NSExpression implementations.<br /> ** Test the NSXMLParser Cocoa class wrapper around GSXML, written by Richard-Frith Macdonald. Once this is thoroughly tested, NSXMLDocument, NSXMLDTD, and NSXMLDTDNode, and NSXMLElement, and NSXMLNode implementations may be useful for compatibility.<br /> <br /> <br /> * '''Misc'''<br /> ** Create a AJAX Framework for GNUstepWeb<br /> <br /> <br /> Feel free to add other ideas !<br /> <br /> == Note ==<br /> <br /> We need [http://code.google.com/soc/mentorfaq.html mentor(s)] to manage the volunteers...<br /> <br /> <br /> === Mentors ===<br /> <br /> - David Wetzel (dave at turbocat dot de) could mentor GSWeb related projects<br /> <br /> - Quentin Mathé is willing to mentor GUI/AppKit and some Base related projects.<br /> <br /> - Adam Fedor (backup mentor)<br /> <br /> <br /> === Students ===<br /> <br /> Nicolas Roard</div>

Aperez https://mediawiki.gnustep.org/index.php?title=Summer_Of_Code_2006&diff=3036 2006-04-26T15:22:55Z

<p>Aperez: More on API comparison (done by Quentin Mathé)</p> <hr /> <div>== Summer Of Code 2006 ==<br /> <br /> The [http://code.google.com/soc/ Summer Of Code] is a Google program that offers student developers stipends to create new freely available programs or to help currently established projects. It would be an excellent opportunity for GNUstep to fund some developments.<br /> <br /> <br /> Here are some ideas:<br /> <br /> * '''Bindings, KVO support'''<br /> ** We need NSController, NSArrayController, NSObjectController, NSTreeController, NSUserDefaultController, NSValueTransformer implementations. NSSortDescriptor has already been implemented by Saso Kiselkov. The current NSTreeController is known to be a bit buggy and have an API a bit flawed, as Apple rushed the release of this class in Mac OS 10.4. It is widely believed that these shortcomings will be fixed in Leopard (10.5), so perhaps we should wait a while. <br /> ** Key Value Observing implementation was written by Richard Frith-Macdonald, and is only about 80% finished. Needs completion and testing.<br /> <br /> <br /> * '''Porting'''<br /> ** Port WebCore to GNUstep using GCC 4.1<br /> <br /> <br /> * '''General Improvements'''<br /> ** Printing Support (better postcript generation, etc.)<br /> ** Cairo backend<br /> ** Windows support<br /> ** GNUstepWeb (add script language support, etc)<br /> ** Finish input server [http://svn.gna.org/viewcvs/gnustep/libs/gui/branches/kazunobu_input_management/ support]<br /> ** Compare current API with Tiger API, indicates which are missing, and the status of the existing ones, then work to complete them... ;) The best would to have a tool which parse every headers (both from Cocoa and GNUstep) and output differences in HTML (XML probably too by the way). This would summarize missing classes, missing or partial implementation methods in existing classes and GNUstep only extensions. Eventually we should include links to the related documentation on both GNUstep and Cocoa web sites.<br /> <br /> <br /> * '''AppKit'''<br /> ** A PDFKit wrapper implementation around the Freedesktop Poppler library, which is also used in ViewPDF, a GNUstep PDF Viewer. Afterwards, having a built-in NSImageRep for NSBitmapImageRep would be great.<br /> *** there is [http://home.gna.org/gsimageapps/ PopplerKit/Vindaloo] which works well, but is currently lacking a maintainer. <br /> ** The Text System should be cleaned, profiled and finished. Many methods in NSLayoutManager are unfinished or unimplemented, so we currently cannot tweak the test system as much as the one provided by Cocoa. (Quentin Mathe)<br /> ** We need NSTypeSetter, NSGlyphStorage, NSGlyphInfo, and NSGlyphGenerator implementations. If NSTypeSetter and NSLayoutManager were implemented, I (Quentin Mathe) would use them in Etoile.<br /> ** NSTextTable, NSTextTableBlock, NSTextList, &amp; NSTextBlock implementations would also bring the GNUstep text system in line with that of Cocoa as of Panther. NSTextList could be useful to build a powerful word processor. (Quentin Mathe)<br /> ** Finish once and for all the NSTableView class, and have it work properly with any kind of cells. This is a big job, but sorely needed (Quentin Mathe)<br /> ** The NSOpenGL Classes could be improved, made compatible with current Cocoa implementations, and further tested (Quentin Mathe)<br /> ** NSBitmapImageRep formats: Currenly, we support only reading and writing for TIFF, read-only for GIF, JPEG, PNG, PNM. We would like to have write support for these NSBitmapImageRep categories. Afterwards, SVG reading, then write support, would be nice. (Quentin Mathe)<br /> ** NSDatePicker, NSLevelIndicator (and obligatory -Cell) implementations.<br /> ** Updating NSDocument architecture with numerous modern methods which were introduced in 10.4. In 10.4, Apple deprecated many methods in NSDocument in favor of a more flexible and well-designed implementation.<br /> ** NSFormatter isn't working very well at this time (Quentin Mathe)<br /> <br /> <br /> * '''Base'''<br /> ** NSError improvements to allow better user messages. 10.4's NSDocument uses this.<br /> ** NSLocale-compatible locale implementation could be useful for internationalization.<br /> ** NSDateComponents implementation.<br /> ** NSCalendar implementation.<br /> ** Finish the NSPredicate implementation. This was mostly done by Quentin Mathe, but is untested. The most important part is not done, which is to write a parser and lexer for the custom language used by NSPredicate. Also needed for this are NSComparisonPredicate, NSCompoundPredicate, and NSExpression implementations.<br /> ** Test the NSXMLParser Cocoa class wrapper around GSXML, written by Richard-Frith Macdonald. Once this is thoroughly tested, NSXMLDocument, NSXMLDTD, and NSXMLDTDNode, and NSXMLElement, and NSXMLNode implementations may be useful for compatibility.<br /> <br /> <br /> * '''Misc'''<br /> ** Create a AJAX Framework for GNUstepWeb<br /> <br /> <br /> Feel free to add other ideas !<br /> <br /> <br /> == Note ==<br /> <br /> We need [http://code.google.com/soc/mentorfaq.html mentor(s)] to manage the volunteers...<br /> <br /> <br /> === Mentors ===<br /> <br /> - David Wetzel (dave at turbocat dot de) could mentor GSWeb related projects<br /> <br /> - Quentin Mathé is willing to mentor GUI/AppKit and some Base related projects.<br /> <br /> - Adam Fedor (backup mentor)<br /> <br /> <br /> === Students ===<br /> <br /> Nicolas Roard</div>

Aperez https://mediawiki.gnustep.org/index.php?title=Summer_Of_Code_2006&diff=3035 2006-04-26T15:16:32Z

<p>Aperez: Improve formatting and make clearer NSTreeController situation (done by Quentin Mathé)</p> <hr /> <div>== Summer Of Code 2006 ==<br /> <br /> The [http://code.google.com/soc/ Summer Of Code] is a Google program that offers student developers stipends to create new freely available programs or to help currently established projects. It would be an excellent opportunity for GNUstep to fund some developments.<br /> <br /> <br /> Here are some ideas:<br /> <br /> * '''Bindings, KVO support'''<br /> ** We need NSController, NSArrayController, NSObjectController, NSTreeController, NSUserDefaultController, NSValueTransformer implementations. NSSortDescriptor has already been implemented by Saso Kiselkov. The current NSTreeController is known to be a bit buggy and have an API a bit flawed, as Apple rushed the release of this class in Mac OS 10.4. It is widely believed that these shortcomings will be fixed in Leopard (10.5), so perhaps we should wait a while. <br /> ** Key Value Observing implementation was written by Richard Frith-Macdonald, and is only about 80% finished. Needs completion and testing.<br /> <br /> <br /> * '''Porting'''<br /> ** Port WebCore to GNUstep using GCC 4.1<br /> <br /> <br /> * '''General Improvements'''<br /> ** Printing Support (better postcript generation, etc.)<br /> ** Cairo backend<br /> ** Windows support<br /> ** GNUstepWeb (add script language support, etc)<br /> ** Finish input server [http://svn.gna.org/viewcvs/gnustep/libs/gui/branches/kazunobu_input_management/ support]<br /> ** Compare current API with Tiger API, indicates which are missing, and the status of the existing ones, then work to complete them... ;)<br /> <br /> <br /> * '''AppKit'''<br /> ** A PDFKit wrapper implementation around the Freedesktop Poppler library, which is also used in ViewPDF, a GNUstep PDF Viewer. Afterwards, having a built-in NSImageRep for NSBitmapImageRep would be great.<br /> *** there is [http://home.gna.org/gsimageapps/ PopplerKit/Vindaloo] which works well, but is currently lacking a maintainer. <br /> ** The Text System should be cleaned, profiled and finished. Many methods in NSLayoutManager are unfinished or unimplemented, so we currently cannot tweak the test system as much as the one provided by Cocoa. (Quentin Mathe)<br /> ** We need NSTypeSetter, NSGlyphStorage, NSGlyphInfo, and NSGlyphGenerator implementations. If NSTypeSetter and NSLayoutManager were implemented, I (Quentin Mathe) would use them in Etoile.<br /> ** NSTextTable, NSTextTableBlock, NSTextList, &amp; NSTextBlock implementations would also bring the GNUstep text system in line with that of Cocoa as of Panther. NSTextList could be useful to build a powerful word processor. (Quentin Mathe)<br /> ** Finish once and for all the NSTableView class, and have it work properly with any kind of cells. This is a big job, but sorely needed (Quentin Mathe)<br /> ** The NSOpenGL Classes could be improved, made compatible with current Cocoa implementations, and further tested (Quentin Mathe)<br /> ** NSBitmapImageRep formats: Currenly, we support only reading and writing for TIFF, read-only for GIF, JPEG, PNG, PNM. We would like to have write support for these NSBitmapImageRep categories. Afterwards, SVG reading, then write support, would be nice. (Quentin Mathe)<br /> ** NSDatePicker, NSLevelIndicator (and obligatory -Cell) implementations.<br /> ** Updating NSDocument architecture with numerous modern methods which were introduced in 10.4. In 10.4, Apple deprecated many methods in NSDocument in favor of a more flexible and well-designed implementation.<br /> ** NSFormatter isn't working very well at this time (Quentin Mathe)<br /> <br /> <br /> * '''Base'''<br /> ** NSError improvements to allow better user messages. 10.4's NSDocument uses this.<br /> ** NSLocale-compatible locale implementation could be useful for internationalization.<br /> ** NSDateComponents implementation.<br /> ** NSCalendar implementation.<br /> ** Finish the NSPredicate implementation. This was mostly done by Quentin Mathe, but is untested. The most important part is not done, which is to write a parser and lexer for the custom language used by NSPredicate. Also needed for this are NSComparisonPredicate, NSCompoundPredicate, and NSExpression implementations.<br /> ** Test the NSXMLParser Cocoa class wrapper around GSXML, written by Richard-Frith Macdonald. Once this is thoroughly tested, NSXMLDocument, NSXMLDTD, and NSXMLDTDNode, and NSXMLElement, and NSXMLNode implementations may be useful for compatibility.<br /> <br /> <br /> * '''Misc'''<br /> ** Create a AJAX Framework for GNUstepWeb<br /> <br /> <br /> Feel free to add other ideas !<br /> <br /> <br /> == Note ==<br /> <br /> We need [http://code.google.com/soc/mentorfaq.html mentor(s)] to manage the volunteers...<br /> <br /> <br /> === Mentors ===<br /> <br /> - David Wetzel (dave at turbocat dot de) could mentor GSWeb related projects<br /> <br /> - Quentin Mathé is willing to mentor GUI/AppKit and some Base related projects.<br /> <br /> - Adam Fedor (backup mentor)<br /> <br /> <br /> === Students ===<br /> <br /> Nicolas Roard</div>

Aperez https://mediawiki.gnustep.org/index.php?title=Summer_Of_Code_2006&diff=3034 2006-04-26T15:06:15Z

<p>Aperez: Removed NSIndexPath (done by Quentin Mathé)</p> <hr /> <div>== Summer Of Code 2006 ==<br /> <br /> The [http://code.google.com/soc/ Summer Of Code] is a Google program that offers student developers stipends to create new freely available programs or to help currently established projects. It would be an excellent opportunity for GNUstep to fund some developments.<br /> <br /> Here are some ideas:<br /> <br /> * '''Bindings, KVO support'''<br /> ** We need NSController, NSArrayController, NSObjectController, NSTreeController, NSUserDefaultController, NSValueTransformer implementations. NSSortDescriptor has already been implemented by Saso Kiselkov. The current NSTreeController is known to be buggy, as Apple rushed the release of this Class in 10.4. It is widely believed that these shortcomings will be fixed in Leopard (10.5), so perhaps we should wait a while. <br /> ** Key Value Observing implementation was written by Richard Frith-Macdonald, and is only about 80% finished. Needs completion and testing.<br /> <br /> * '''Porting'''<br /> ** Port WebCore to GNUstep using GCC 4.1<br /> <br /> * '''General Improvements'''<br /> ** The Printing Support (better postcript generation, etc.)<br /> ** The Cairo backend<br /> ** Windows support<br /> ** GNUstepWeb (add script language support, etc)<br /> ** Finish input server [http://svn.gna.org/viewcvs/gnustep/libs/gui/branches/kazunobu_input_management/ support]<br /> ** Compare current API with Tiger API, indicates which are missing, and the status of the existing ones, then work to complete them... ;)<br /> <br /> * '''AppKit'''<br /> ** A PDFKit wrapper implementation around the Freedesktop Poppler library, which is also used in ViewPDF, a GNUstep PDF Viewer. Afterwards, having a built-in NSImageRep for NSBitmapImageRep would be great.<br /> *** there is [http://home.gna.org/gsimageapps/ PopplerKit/Vindaloo] which works well, but is currently lacking a maintainer. <br /> ** The Text System should be cleaned, profiled and finished. Many methods in NSLayoutManager are unfinished or unimplemented, so we currently cannot tweak the test system as much as the one provided by Cocoa. (Quentin Mathe)<br /> ** We need NSTypeSetter, NSGlyphStorage, NSGlyphInfo, and NSGlyphGenerator implementations. If NSTypeSetter and NSLayoutManager were implemented, I (Quentin Mathe) would use them in Etoile.<br /> ** NSTextTable, NSTextTableBlock, NSTextList, &amp; NSTextBlock implementations would also bring the GNUstep text system in line with that of Cocoa as of Panther. NSTextList could be useful to build a powerful word processor. (Quentin Mathe)<br /> ** Finish once and for all the NSTableView class, and have it work properly with any kind of cells. This is a big job, but sorely needed (Quentin Mathe)<br /> ** The NSOpenGL Classes could be improved, made compatible with current Cocoa implementations, and further tested (Quentin Mathe)<br /> ** NSBitmapImageRep formats: Currenly, we support only reading and writing for TIFF, read-only for GIF, JPEG, PNG, PNM. We would like to have write support for these NSBitmapImageRep categories. Afterwards, SVG reading, then write support, would be nice. (Quentin Mathe)<br /> ** NSDatePicker, NSLevelIndicator (and obligatory -Cell) implementations.<br /> ** Updating NSDocument architecture with numerous modern methods which were introduced in 10.4. In 10.4, Apple deprecated many methods in NSDocument in favor of a more flexible and well-designed implementation.<br /> ** NSFormatter isn't working very well at this time (Quentin Mathe)<br /> <br /> * '''Base'''<br /> ** NSError improvements to allow better user messages. 10.4's NSDocument uses this.<br /> ** NSLocale-compatible locale implementation could be useful for internationalization.<br /> ** NSDateComponents implementation.<br /> ** NSCalendar implementation.<br /> ** Finish the NSPredicate implementation. This was mostly done by Quentin Mathe, but is untested. The most important part is not done, which is to write a parser and lexer for the custom language used by NSPredicate. Also needed for this are NSComparisonPredicate, NSCompoundPredicate, and NSExpression implementations.<br /> ** Test the NSXMLParser Cocoa class wrapper around GSXML, written by Richard-Frith Macdonald. Once this is thoroughly tested, NSXMLDocument, NSXMLDTD, and NSXMLDTDNode, and NSXMLElement, and NSXMLNode implementations may be useful for compatibility.<br /> <br /> * '''Misc'''<br /> ** Create a AJAX Framework for GNUstepWeb<br /> <br /> Feel free to add other ideas !<br /> <br /> == Note ==<br /> <br /> We need [http://code.google.com/soc/mentorfaq.html mentor(s)] to manage the volunteers...<br /> <br /> === Mentors ===<br /> <br /> - David Wetzel (dave at turbocat dot de) could mentor GSWeb related projects<br /> <br /> - Quentin Mathe is willing to mentor GUI/AppKit and some Base related projects.<br /> <br /> - Adam Fedor (backup mentor)<br /> <br /> === Students ===<br /> <br /> Nicolas Roard</div>

Aperez https://mediawiki.gnustep.org/index.php?title=Summer_Of_Code_2006&diff=3030 2006-04-25T23:35:45Z

<p>Aperez: </p> <hr /> <div>== Summer Of Code 2006 ==<br /> <br /> The [http://code.google.com/soc/ Summer Of Code] is a Google program that offers student developers stipends to create new freely available programs or to help currently established projects. It would be an excellent opportunity for GNUstep to fund some developments.<br /> <br /> Here are some ideas:<br /> <br /> * '''Bindings, KVO support'''<br /> ** We need NSController, NSArrayController, NSObjectController, NSTreeController, NSUserDefaultController, NSValueTransformer implementations. NSSortDescriptor has already been implemented by Saso Kiselkov. The current NSTreeController is known to be buggy, as Apple rushed the release of this Class in 10.4. It is widely believed that these shortcomings will be fixed in Leopard (10.5), so perhaps we should wait a while. <br /> ** Key Value Observing implentation was written by Richard Frith-Macdonald, and is only about 80% finished. Needs completion and testing.<br /> <br /> * '''Porting'''<br /> ** Port WebCore to GNUstep using GCC 4.1<br /> <br /> * '''General Improvements'''<br /> ** The Printing Support (better postcript generation, etc.)<br /> ** The Cairo backend<br /> ** Windows support<br /> ** GNUstepWeb (add script language support, etc)<br /> ** Finish input server [http://svn.gna.org/viewcvs/gnustep/libs/gui/branches/kazunobu_input_management/ support]<br /> ** Compare current API with Tiger API, indicates which are missing, and the status of the existing ones, then work to complete them... ;)<br /> <br /> * '''AppKit'''<br /> ** A PDFKit wrapper implementation around the Freedesktop Poppler library, which is also used in ViewPDF, a GNUstep PDF Viewer. Afterwards, having a built-in NSImageRep for NSBitmapImageRep would be great.<br /> ** there is [http://home.gna.org/gsimageapps/ PopplerKit/Vindaloo] which works well, but is currently lacking a maintainer. <br /> ** The Text System should be cleaned, profiled and finished. Many methods in NSLayoutManager are unfinished or unimplemented, so we currently cannot tweak the test system as much as the one provided by Cocoa. (Quentin Mathe)<br /> ** We need NSTypeSetter, NSGlyphStorage, NSGlyphInfo, and NSGlyphGenerator implementations. If NSTypeSetter and NSLayoutManager were implemented, I (Quentin Mathe) would use them in Etoile.<br /> ** NSTextTable, NSTextTableBlock, NSTextList, &amp; NSTextBlock implementations would also bring the GNUstep text system in line with that of Cocoa as of Panther. NSTextList could be useful to build a powerful word processor. (Quentin Mathe)<br /> ** Finish once and for all the NSTableView class, and have it work properly with any kind of cells. This is a big job, but sorely needed (Quentin Mathe)<br /> ** The NSOpenGL Classes could be improved, made compatible with current Cocoa implementations, and further tested (Quentin Mathe)<br /> ** NSBitmapImageRep formats: Currenly, we support only reading and writing for TIFF, read-only for GIF, JPEG, PNG, PNM. We would like to have write support for these NSBitmapImageRep categories. Afterwards, SVG reading, then write support, would be nice. (Quentin Mathe)<br /> ** NSDatePicker, NSLevelIndicator (and obligatory -Cell) implementations.<br /> ** Updating NSDocument architecture with numerous modern methods which were introduced in 10.4. In 10.4, Apple deprecated many methods in NSDocument in favor of a more flexible and well-designed implementation.<br /> ** NSFormatter isn't working very well at this time (Quentin Mathe)<br /> <br /> * '''Base'''<br /> ** NSError improvements to allow better user messages. 10.4's NSDocument uses this.<br /> ** NSLocale-compatible locale implementation could be useful for internationalization.<br /> ** NSDateComponents implementation.<br /> ** NSCalendar implementation.<br /> ** NSIndexPath implementation.<br /> ** Finish the NSPredicate implementation. This was mostly done by Quentin Mathe, but is untested. The most important part is not done, which is to write a parser and lexer for the custom language used by NSPredicate. Also needed for this are NSComparisonPredicate, NSCompoundPredicate, and NSExpression implementations.<br /> ** Test the NSXMLParser Cocoa class wrapper around GSXML, written by Richard-Frith Macdonald. Once this is thoroughly tested, NSXMLDocument, NSXMLDTD, and NSXMLDTDNode, and NSXMLElement, and NSXMLNode implementations may be useful for compatibility.<br /> <br /> * '''Misc'''<br /> ** Create a AJAX Framework for GNUstepWeb<br /> <br /> Feel free to add other ideas !<br /> <br /> == Note ==<br /> <br /> We need [http://code.google.com/soc/mentorfaq.html mentor(s)] to manage the volunteers...<br /> <br /> === Mentors ===<br /> <br /> - David Wetzel (dave at turbocat dot de) could mentor GSWeb related projects<br /> <br /> - Quentin Mathe is willing to mentor GUI/AppKit and some Base related projects.<br /> <br /> - Adam Fedor (backup mentor)<br /> <br /> === Students ===<br /> <br /> Nicolas Roard</div>

Aperez https://mediawiki.gnustep.org/index.php?title=Summer_Of_Code_2006&diff=3008 2006-04-20T15:33:04Z

<p>Aperez: </p> <hr /> <div>== Summer Of Code 2006 ==<br /> <br /> The [http://code.google.com/soc/ Summer Of Code] is a Google program that offers student developers stipends to create new open source programs or to help currently established projects. It would be an excellent opportunity for GNUstep to fund some developments.<br /> <br /> Here is some ideas:<br /> <br /> - Improve the Printing Support (better postcript generation, etc.)<br /> <br /> - Bindings, KVO support: We need NSController, NSArrayController, NSObjectController, NSTreeController, NSUserDefaultController, NSValueTransformer implementations. NSSortDescriptor has already been implemented by Saso Kiselkov. The current NSController is known to be buggy, as Apple rushed the release of this Class in 10.4. It is widely believed that these shortcomings will be fixed in Leopard (10.5), so perhaps we should wait a while. <br /> <br /> - KVO: The implementation was written by Richard Frith-Macdonald, and is only about 80% finished. Needs completion and testing.<br /> <br /> - Improve the Cairo backend<br /> <br /> - Improve Windows support<br /> <br /> - Improve GNUstepWeb (add script language support, etc)<br /> <br /> - Create a AJAX Framework for GNUstepWeb<br /> <br /> - Finish input server [http://svn.gna.org/viewcvs/gnustep/libs/gui/branches/kazunobu_input_management/ support]<br /> <br /> - Port WebCore to GNUstep using gcc4.1<br /> <br /> - Compare current API with Tiger API, indicates which are missing, and the status of the existing ones, then work to complete them... ;)<br /> <br /> - AppKit: A PDFKit wrapper implementation around the Freedesktop Poppler library, which is also used in ViewPDF, a GNUstep PDF Viewer. Afterwards, having a built-in NSImageRep for NSBitmapImageRep would be great.<br /> <br /> - AppKit: The Text System should be cleaned, profiled and finished. Many methods in NSLayoutManager are unfinished or unimplemented, so we currently cannot tweak the test system as much as the one provided by Cocoa. (Quentin Mathe)<br /> <br /> - AppKit: We need NSTypeSetter, NSGlyphStorage, NSGlyphInfo, and NSGlyphGenerator implementations. If NSTypeSetter and NSLayoutManager were implemented, I (Quentin Mathe) would use them in Etoile.<br /> <br /> - AppKit: NSTextTable, NSTextTableBlock, NSTextList, &amp; NSTextBlock implementations would also bring the GNUstep text system in line with that of Cocoa as of Panther. NSTextList could be useful to build a powerful word processor. (Quentin Mathe)<br /> <br /> - Finish once and for all the NSTableView class, and have it work properly with any kind of cells. This is a big job, but sorely needed (Quentin Mathe)<br /> <br /> - AppKit: The NSOpenGL Classes could be improved, made compatible with current Cocoa implementations, and further tested (Quentin Mathe)<br /> <br /> - NSBitmapImageRep formats: Currenly, we support only reading and writing for TIFF, read-only for GIF, JPEG, PNG, PNM. We would like to have write support for these NSBitmapImageRep categories. Afterwards, SVG reading, then write support, would be nice. (Quentin Mathe)<br /> <br /> - AppKit: NSDatePicker, NSLevelIndicator (and obligatory -Cell) implementations.<br /> <br /> - AppKit: Updating NSDocument architecture with numerous modern methods which were introduced in 10.4. In 10.4, Apple deprecated many methods in NSDocument in favor of a more flexible and well-designed implementation.<br /> <br /> - AppKit: NSFormatter isn't working very well at this time (Quentin Mathe)<br /> <br /> - Base: NSError improvements to allow better user messages. 10.4's NSDocument uses this.<br /> <br /> - Base: NSLocale-compatible locale implementation could be useful for internationalization.<br /> <br /> - Base: NSDateComponents implementation.<br /> <br /> - Base: NSCalendar implementation.<br /> <br /> - Base: NSIndexPath implementation.<br /> <br /> - Base: Finish the NSPredicate implementation. This was mostly done by Quentin Mathe, but is untested. The most important part is not done, which is to write a parser and lexer for the custom language used by NSPredicate. Also needed for this are NSComparisonPredicate, NSCompoundPredicate, and NSExpression implementations.<br /> <br /> - Base: Test the NSXMLParser Cocoa class wrapper around GSXML, written by Richard-Frith Macdonald. Once this is thoroughly tested, NSXMLDocument, NSXMLDTD, and NSXMLDTDNode, and NSXMLElement, and NSXMLNode implementations may be useful for compatibility.<br /> <br /> Feel free to add other ideas !<br /> <br /> == Note ==<br /> <br /> We need [http://code.google.com/soc/mentorfaq.html mentor(s)] to manage the volunteers...<br /> <br /> === Mentors ===<br /> <br /> - David Wetzel (dave at turbocat dot de) could mentor GSWeb related projects<br /> <br /> - Quentin Mathe is willing to mentor GUI/AppKit and some Base related projects.<br /> <br /> === Students ===<br /> <br /> Nicolas Roard</div>

Aperez https://mediawiki.gnustep.org/index.php?title=Summer_Of_Code_2006&diff=3007 2006-04-20T15:31:57Z

<p>Aperez: /* Summer Of Code 2006 */</p> <hr /> <div>== Summer Of Code 2006 ==<br /> <br /> The [http://code.google.com/soc/ Summer Of Code] is a Google program that offers student developers stipends to create new open source programs or to help currently established projects. It would be an excellent opportunity for GNUstep to fund some developments.<br /> <br /> Here is some ideas:<br /> <br /> - Improve the Printing Support (better postcript generation, etc.)<br /> <br /> - Bindings, KVO support: We need NSController, NSArrayController, NSObjectController, NSTreeController, NSUserDefaultController, NSValueTransformer implementations. NSSortDescriptor has already been implemented by Saso Kiselkov. The current NSController is known to be buggy, as Apple rushed the release of this Class in 10.4. It is widely believed that these shortcomings will be fixed in Leopard (10.5), so perhaps we should wait a while. <br /> <br /> - KVO: The implementation was written by Richard Frith-Macdonald, and is only about 80% finished. Needs completion and testing.<br /> <br /> - Improve the Cairo backend<br /> <br /> - Improve Windows support<br /> <br /> - Improve GNUstepWeb (add script language support, etc)<br /> <br /> - Create a AJAX Framework for GNUstepWeb<br /> <br /> - Finish input server [http://svn.gna.org/viewcvs/gnustep/libs/gui/branches/kazunobu_input_management/ support]<br /> <br /> - Port WebCore to GNUstep using gcc4.1<br /> <br /> - Compare current API with Tiger API, indicates which are missing, and the status of the existing ones, then work to complete them... ;)<br /> <br /> - AppKit: A PDFKit wrapper implementation around the Freedesktop Poppler library, which is also used in ViewPDF, a GNUstep PDF Viewer. Afterwards, having a built-in NSImageRep for NSBitmapImageRep would be great.<br /> <br /> - AppKit: The Text System should be cleaned, profiled and finished. Many methods in NSLayoutManager are unfinished or unimplemented, so we currently cannot tweak the test system as much as the one provided by Cocoa. (Quentin Mathe)<br /> <br /> - AppKit: We need NSTypeSetter, NSGlyphStorage, NSGlyphInfo, and NSGlyphGenerator implementations. If NSTypeSetter and NSLayoutManager were implemented, I (Quentin Mathe) would use them in Etoile.<br /> <br /> - AppKit: NSTextTable, NSTextTableBlock, NSTextList, &amp; NSTextBlock implementations would also bring the GNUstep text system in line with that of Cocoa as of Panther. NSTextList could be useful to build a powerful word processor. (Quentin Mathe)<br /> <br /> - Finish once and for all the NSTableView class, and have it work properly with any kind of cells. This is a big job, but sorely needed (Quentin Mathe)<br /> <br /> - AppKit: The NSOpenGL Classes could be improved, made compatible with current Cocoa implementations, and further tested (Quentin Mathe)<br /> <br /> - NSBitmapImageRep formats: Currenly, we support only reading and writing for TIFF, read-only for GIF, JPEG, PNG, PNM. We would like to have write support for these NSBitmapImageRep categories. Afterwards, SVG reading, then write support, would be nice. (Quentin Mathe)<br /> <br /> - AppKit: NSDatePicker, NSLevelIndicator (and obligatory -Cell) implementations.<br /> <br /> - AppKit: Updating NSDocument architecture with numerous modern methods which were introduced in 10.4. In 10.4, Apple deprecated many methods in NSDocument in favor of a more flexible and well-designed implementation.<br /> <br /> - AppKit: NSFormatter isn't working very well at this time (Quentin Mathe)<br /> <br /> - Base: NSError improvements to allow better user messages. 10.4's NSDocument uses this.<br /> <br /> - Base: NSLocale-compatible locale implementation could be useful for internationalization.<br /> <br /> - Base: NSDateComponents implementation.<br /> <br /> - Base: NSCalendar implementation.<br /> <br /> - Base: Finish the NSPredicate implementation. This was mostly done by Quentin Mathe, but is untested. The most important part is not done, which is to write a parser and lexer for the custom language used by NSPredicate. Also needed for this are NSComparisonPredicate, NSCompoundPredicate, and NSExpression implementations.<br /> <br /> - Base: Test the NSXMLParser Cocoa class wrapper around GSXML, written by Richard-Frith Macdonald. Once this is thoroughly tested, NSXMLDocument, NSXMLDTD, and NSXMLDTDNode, and NSXMLElement, and NSXMLNode implementations may be useful for compatibility.<br /> <br /> Feel free to add other ideas !<br /> <br /> == Note ==<br /> <br /> We need [http://code.google.com/soc/mentorfaq.html mentor(s)] to manage the volunteers...<br /> <br /> === Mentors ===<br /> <br /> - David Wetzel (dave at turbocat dot de) could mentor GSWeb related projects<br /> - Quentin Mathe is willing to mentor AppKit related projects.<br /> <br /> === Students ===<br /> <br /> Nicolas Roard</div>

Aperez https://mediawiki.gnustep.org/index.php?title=Summer_Of_Code_2006&diff=3006 2006-04-20T15:31:14Z

<p>Aperez: Additions made by Alex Perez on behalf of Quentin Mathe, who has no Wiki Account.</p> <hr /> <div>== Summer Of Code 2006 ==<br /> <br /> The [http://code.google.com/soc/ Summer Of Code] is a Google program that offers student developers stipends to create new open source programs or to help currently established projects. It would be an excellent opportunity for GNUstep to fund some developments.<br /> <br /> Here is some ideas:<br /> <br /> - Improve the Printing Support (better postcript generation, etc.)<br /> <br /> - Bindings, KVO support: We need NSController, NSArrayController, NSObjectController, NSTreeController, NSUserDefaultController, NSValueTransformer implementations. NSSortDescriptor has already been implemented by Saso Kiselkov. The current NSController is known to be buggy, as Apple rushed the release of this Class in 10.4. It is widely believed that these shortcomings will be fixed in Leopard (10.5), so perhaps we should wait a while. <br /> <br /> - KVO: The implementation was written by Richard Frith-Macdonald, and is only about 80% finished. Needs completion and testing.<br /> <br /> - Improve the Cairo backend<br /> <br /> - Improve Windows support<br /> <br /> - Improve GNUstepWeb (add script language support, etc)<br /> <br /> - Create a AJAX Framework for GNUstepWeb<br /> <br /> - Finish input server [http://svn.gna.org/viewcvs/gnustep/libs/gui/branches/kazunobu_input_management/ support]<br /> <br /> - Port WebCore to GNUstep using gcc4.1<br /> <br /> - Compare current API with Tiger API, indicates which are missing, and the status of the existing ones, then work to complete them... ;)<br /> <br /> - AppKit: A PDFKit wrapper implementation around the Freedesktop Poppler library, which is also used in ViewPDF, a GNUstep PDF Viewer. Afterwards, having a built-in NSImageRep for NSBitmapImageRep would be great.<br /> <br /> - AppKit: The Text System should be cleaned, profiled and finished. Many methods in NSLayoutManager are unfinished or unimplemented, so we currently cannot tweak the test system as much as the one provided by Cocoa. (Quentin Mathe)<br /> <br /> - AppKit: We need NSTypeSetter, NSGlyphStorage, NSGlyphInfo, and NSGlyphGenerator implementations. If NSTypeSetter and NSLayoutManager were implemented, I (Quentin Mathe) would use them in Etoile.<br /> <br /> - AppKit: NSTextTable, NSTextTableBlock, NSTextList, &amp; NSTextBlock implementations would also bring the GNUstep text system in line with that of Cocoa as of Panther. NSTextList could be useful to build a powerful word processor. (Quentin Mathe)<br /> <br /> - Finish once and for all the NSTableView class, and have it work properly with any kind of cells. This is a big job, but sorely needed (Quentin Mathe)<br /> <br /> - AppKit: The NSOpenGL Classes could be improved, made compatible with current Cocoa implementations, and further tested (Quentin Mathe)<br /> <br /> - NSBitmapImageRep formats: Currenly, we support only reading and writing for TIFF, read-only for GIF, JPEG, PNG, PNM. We would like to have write support for these NSBitmapImageRep categories. Afterwards, SVG reading, then write support, would be nice. (Quentin Mathe)<br /> <br /> - AppKit: NSDatePicker, NSLevelIndicator (and obligatory -Cell) implementations.<br /> <br /> - AppKit: Updating NSDocument architecture with numerous modern methods which were introduced in 10.4. In 10.4, Apple deprecated many methods in NSDocument in favor of a more flexible and well-designed implementation.<br /> <br /> - Base: NSError improvements to allow better user messages. 10.4's NSDocument uses this.<br /> <br /> - Base: NSLocale-compatible locale implementation could be useful for internationalization.<br /> <br /> - Base: NSDateComponents implementation.<br /> <br /> - Base: NSCalendar implementation.<br /> <br /> - Base: Finish the NSPredicate implementation. This was mostly done by Quentin Mathe, but is untested. The most important part is not done, which is to write a parser and lexer for the custom language used by NSPredicate. Also needed for this are NSComparisonPredicate, NSCompoundPredicate, and NSExpression implementations.<br /> <br /> - Base: Test the NSXMLParser Cocoa class wrapper around GSXML, written by Richard-Frith Macdonald. Once this is thoroughly tested, NSXMLDocument, NSXMLDTD, and NSXMLDTDNode, and NSXMLElement, and NSXMLNode implementations may be useful for compatibility.<br /> <br /> Feel free to add other ideas !<br /> <br /> == Note ==<br /> <br /> We need [http://code.google.com/soc/mentorfaq.html mentor(s)] to manage the volunteers...<br /> <br /> === Mentors ===<br /> <br /> - David Wetzel (dave at turbocat dot de) could mentor GSWeb related projects<br /> - Quentin Mathe is willing to mentor AppKit related projects.<br /> <br /> === Students ===<br /> <br /> Nicolas Roard</div>

Aperez https://mediawiki.gnustep.org/index.php?title=SVN_SSH_Setup&diff=2979 2006-03-15T05:13:03Z

<p>Aperez: just a redirect</p> <hr /> <div>#REDIRECT [[Svn_SSH_Setup]]</div>

Aperez https://mediawiki.gnustep.org/index.php?title=Using_Subversion&diff=2978 2006-03-15T05:11:09Z

<p>Aperez: /* Setting up Subversion for Developer Use */</p> <hr /> <div>== Anonymous GNUstep SVN Checkout ==<br /> <br /> Simply run: <br /> svn co http://svn.gna.org/svn/gnustep/modules<br /> <br /> You cannot use SVN+SSH unless you are a developer, and have a username and SSH public key registered at gna.org. See below for more detauls. You cannot check out /devmodules unless you are a developer. /modules is the same as devmodules, except the SVN external references work for anonymous SVN checkouts.<br /> <br /> == Setting up Subversion for Developer Use ==<br /> <br /> The first thing you will want to do is setup the ssh access to svn.gna.org. If you cannot type<br /> <br /> svn list svn+ssh://svn.gna.org/svn/gnustep/devmodules<br /> <br /> without having to type a password or in some way change the above command, you will need to visit the [[SVN SSH Setup]] page (this includes if you have to specify a different user).<br /> <br /> == Some background on repository layout ==<br /> <br /> To familiarize yourself with the layout, I would recommend looking at the [http://svn.gna.org/viewcvs/gnustep/ web-access to svn]<br /> for GNUstep. You will notice that every project is in its own portion of the repository. For example:<br /> <br /> /libs<br /> /libs/gui<br /> /libs/gui/trunk<br /> <br /> /libs/gui/branches<br /> /libs/gui/branches/dawn<br /> /libs/gui/branches/...<br /> <br /> /libs/gui/tags<br /> /libs/gui/tags/alex_last_semistable<br /> /libs/gui/tags/...<br /> <br /> This layout is very handy for having a per-project repository. I can easily branch or tag just /libs/gui and it all stays in its own namespace. However, what this DOES mean is that you cannot simply checkout /libs/gui or you will end up with several copies of the source. To get around this, we are using a nifty feature of Subversion called externals. Externals are metadata on a directory that basically tell the svn client to checkout some other url into a subdirectory when it is checked out. So if I type:<br /> <br /> svn proplist -v svn+ssh://svn.gna.org/svn/gnustep/devmodules/core<br /> <br /> It will tell me that the svn:externals property contains:<br /> <br /> gui svn+ssh://svn.gna.org/svn/gnustep/libs/gui/trunk<br /> back svn+ssh://svn.gna.org/svn/gnustep/libs/back/trunk<br /> base svn+ssh://svn.gna.org/svn/gnustep/libs/base/trunk<br /> make svn+ssh://svn.gna.org/svn/gnustep/tools/make/trunk<br /> <br /> So everytime I checkout /devmodules/core the svn client will automatically go to these URLs and check them out into subdirectories. When I make changes in gui/ and commit them, it will really commit to /libs/gui/trunk. For the most part if you checkout /devmodules, the externals have already been setup such that it will checkout something similar to checking out the whole repository before.<br /> <br /> == Tips, Tricks, and Resources ==<br /> <br /> * [http://svnbook.red-bean.com Version Control with Subversion]<br /> * [http://svnbook.red-bean.com/en/1.1/apa.html Appendix A: Subversion for CVS Users]<br /> * [http://gcc.gnu.org/wiki/SvnSetup GCC's SVN Setup page] - Look especially at the section on [http://gcc.gnu.org/wiki/SSH%20connection%20caching ssh connection caching].<br /> * [[Subversion_Migration]] - Some initial notes on the layout of the repository.<br /> * [http://www.aeruder.net/software/misc/softwarelist.html ZSH svn tab completion] - On this page is a tab completion module that can tab complete into subversion repositories. Very handy for ZSH users.</div>

Aperez https://mediawiki.gnustep.org/index.php?title=SVN&diff=2977 2006-03-15T05:10:33Z

<p>Aperez: </p> <hr /> <div>#REDIRECT [[Using_Subversion]]</div>

Aperez https://mediawiki.gnustep.org/index.php?title=Using_Subversion&diff=2976 2006-03-15T05:00:42Z

<p>Aperez: /* Checking GNUstep out of SVN Anonymously */</p> <hr /> <div>== Anonymous GNUstep SVN Checkout ==<br /> <br /> Simply run: <br /> svn co http://svn.gna.org/svn/gnustep/modules<br /> <br /> You cannot use SVN+SSH unless you are a developer, and have a username and SSH public key registered at gna.org. See below for more detauls. You cannot check out /devmodules unless you are a developer. /modules is the same as devmodules, except the SVN external references work for anonymous SVN checkouts.<br /> <br /> == Setting up Subversion for Developer Use ==<br /> <br /> The first thing you will want to do is setup the ssh access to svn.gna.org. If you cannot type<br /> <br /> svn list svn+ssh://svn.gna.org/svn/gnustep/devmodules<br /> <br /> without having to type a password or in some way change the above command, you will need to visit the [[Svn SSH Setup]] page (this includes if you have to specify a different user).<br /> <br /> == Some background on repository layout ==<br /> <br /> To familiarize yourself with the layout, I would recommend looking at the [http://svn.gna.org/viewcvs/gnustep/ web-access to svn]<br /> for GNUstep. You will notice that every project is in its own portion of the repository. For example:<br /> <br /> /libs<br /> /libs/gui<br /> /libs/gui/trunk<br /> <br /> /libs/gui/branches<br /> /libs/gui/branches/dawn<br /> /libs/gui/branches/...<br /> <br /> /libs/gui/tags<br /> /libs/gui/tags/alex_last_semistable<br /> /libs/gui/tags/...<br /> <br /> This layout is very handy for having a per-project repository. I can easily branch or tag just /libs/gui and it all stays in its own namespace. However, what this DOES mean is that you cannot simply checkout /libs/gui or you will end up with several copies of the source. To get around this, we are using a nifty feature of Subversion called externals. Externals are metadata on a directory that basically tell the svn client to checkout some other url into a subdirectory when it is checked out. So if I type:<br /> <br /> svn proplist -v svn+ssh://svn.gna.org/svn/gnustep/devmodules/core<br /> <br /> It will tell me that the svn:externals property contains:<br /> <br /> gui svn+ssh://svn.gna.org/svn/gnustep/libs/gui/trunk<br /> back svn+ssh://svn.gna.org/svn/gnustep/libs/back/trunk<br /> base svn+ssh://svn.gna.org/svn/gnustep/libs/base/trunk<br /> make svn+ssh://svn.gna.org/svn/gnustep/tools/make/trunk<br /> <br /> So everytime I checkout /devmodules/core the svn client will automatically go to these URLs and check them out into subdirectories. When I make changes in gui/ and commit them, it will really commit to /libs/gui/trunk. For the most part if you checkout /devmodules, the externals have already been setup such that it will checkout something similar to checking out the whole repository before.<br /> <br /> == Tips, Tricks, and Resources ==<br /> <br /> * [http://svnbook.red-bean.com Version Control with Subversion]<br /> * [http://svnbook.red-bean.com/en/1.1/apa.html Appendix A: Subversion for CVS Users]<br /> * [http://gcc.gnu.org/wiki/SvnSetup GCC's SVN Setup page] - Look especially at the section on [http://gcc.gnu.org/wiki/SSH%20connection%20caching ssh connection caching].<br /> * [[Subversion_Migration]] - Some initial notes on the layout of the repository.<br /> * [http://www.aeruder.net/software/misc/softwarelist.html ZSH svn tab completion] - On this page is a tab completion module that can tab complete into subversion repositories. Very handy for ZSH users.</div>

Aperez https://mediawiki.gnustep.org/index.php?title=Using_Subversion&diff=2975 2006-03-15T05:00:23Z

<p>Aperez: /* Checking GNUstep out of SVN Anonymously */</p> <hr /> <div>== Checking GNUstep out of SVN Anonymously ==<br /> <br /> Simply run: <br /> svn co http://svn.gna.org/svn/gnustep/modules<br /> <br /> You cannot use SVN+SSH unless you are a developer, and have a username and SSH public key registered at gna.org. See below for more detauls. You cannot check out /devmodules unless you are a developer. /modules is the same as devmodules, except the SVN external references work for anonymous SVN checkouts.<br /> <br /> == Setting up Subversion for Developer Use ==<br /> <br /> The first thing you will want to do is setup the ssh access to svn.gna.org. If you cannot type<br /> <br /> svn list svn+ssh://svn.gna.org/svn/gnustep/devmodules<br /> <br /> without having to type a password or in some way change the above command, you will need to visit the [[Svn SSH Setup]] page (this includes if you have to specify a different user).<br /> <br /> == Some background on repository layout ==<br /> <br /> To familiarize yourself with the layout, I would recommend looking at the [http://svn.gna.org/viewcvs/gnustep/ web-access to svn]<br /> for GNUstep. You will notice that every project is in its own portion of the repository. For example:<br /> <br /> /libs<br /> /libs/gui<br /> /libs/gui/trunk<br /> <br /> /libs/gui/branches<br /> /libs/gui/branches/dawn<br /> /libs/gui/branches/...<br /> <br /> /libs/gui/tags<br /> /libs/gui/tags/alex_last_semistable<br /> /libs/gui/tags/...<br /> <br /> This layout is very handy for having a per-project repository. I can easily branch or tag just /libs/gui and it all stays in its own namespace. However, what this DOES mean is that you cannot simply checkout /libs/gui or you will end up with several copies of the source. To get around this, we are using a nifty feature of Subversion called externals. Externals are metadata on a directory that basically tell the svn client to checkout some other url into a subdirectory when it is checked out. So if I type:<br /> <br /> svn proplist -v svn+ssh://svn.gna.org/svn/gnustep/devmodules/core<br /> <br /> It will tell me that the svn:externals property contains:<br /> <br /> gui svn+ssh://svn.gna.org/svn/gnustep/libs/gui/trunk<br /> back svn+ssh://svn.gna.org/svn/gnustep/libs/back/trunk<br /> base svn+ssh://svn.gna.org/svn/gnustep/libs/base/trunk<br /> make svn+ssh://svn.gna.org/svn/gnustep/tools/make/trunk<br /> <br /> So everytime I checkout /devmodules/core the svn client will automatically go to these URLs and check them out into subdirectories. When I make changes in gui/ and commit them, it will really commit to /libs/gui/trunk. For the most part if you checkout /devmodules, the externals have already been setup such that it will checkout something similar to checking out the whole repository before.<br /> <br /> == Tips, Tricks, and Resources ==<br /> <br /> * [http://svnbook.red-bean.com Version Control with Subversion]<br /> * [http://svnbook.red-bean.com/en/1.1/apa.html Appendix A: Subversion for CVS Users]<br /> * [http://gcc.gnu.org/wiki/SvnSetup GCC's SVN Setup page] - Look especially at the section on [http://gcc.gnu.org/wiki/SSH%20connection%20caching ssh connection caching].<br /> * [[Subversion_Migration]] - Some initial notes on the layout of the repository.<br /> * [http://www.aeruder.net/software/misc/softwarelist.html ZSH svn tab completion] - On this page is a tab completion module that can tab complete into subversion repositories. Very handy for ZSH users.</div>

Aperez https://mediawiki.gnustep.org/index.php?title=Using_Subversion&diff=2974 2006-03-15T04:59:13Z

<p>Aperez: added section on anonymous SVN checkouts</p> <hr /> <div>== Checking GNUstep out of SVN Anonymously ==<br /> <br /> (this is what 90% of you will want)<br /> Simply run: <br /> svn co http://svn.gna.org/svn/gnustep/modules<br /> <br /> Using SVN+SSH will not work unless you are a developer. You cannot check out /devmodules unless you are a developer. /modules is the same as devmodules, except the SVN external references work for anonymous SVN checkouts.<br /> <br /> <br /> == Setting up Subversion for Developer Use ==<br /> <br /> The first thing you will want to do is setup the ssh access to svn.gna.org. If you cannot type<br /> <br /> svn list svn+ssh://svn.gna.org/svn/gnustep/devmodules<br /> <br /> without having to type a password or in some way change the above command, you will need to visit the [[Svn SSH Setup]] page (this includes if you have to specify a different user).<br /> <br /> == Some background on repository layout ==<br /> <br /> To familiarize yourself with the layout, I would recommend looking at the [http://svn.gna.org/viewcvs/gnustep/ web-access to svn]<br /> for GNUstep. You will notice that every project is in its own portion of the repository. For example:<br /> <br /> /libs<br /> /libs/gui<br /> /libs/gui/trunk<br /> <br /> /libs/gui/branches<br /> /libs/gui/branches/dawn<br /> /libs/gui/branches/...<br /> <br /> /libs/gui/tags<br /> /libs/gui/tags/alex_last_semistable<br /> /libs/gui/tags/...<br /> <br /> This layout is very handy for having a per-project repository. I can easily branch or tag just /libs/gui and it all stays in its own namespace. However, what this DOES mean is that you cannot simply checkout /libs/gui or you will end up with several copies of the source. To get around this, we are using a nifty feature of Subversion called externals. Externals are metadata on a directory that basically tell the svn client to checkout some other url into a subdirectory when it is checked out. So if I type:<br /> <br /> svn proplist -v svn+ssh://svn.gna.org/svn/gnustep/devmodules/core<br /> <br /> It will tell me that the svn:externals property contains:<br /> <br /> gui svn+ssh://svn.gna.org/svn/gnustep/libs/gui/trunk<br /> back svn+ssh://svn.gna.org/svn/gnustep/libs/back/trunk<br /> base svn+ssh://svn.gna.org/svn/gnustep/libs/base/trunk<br /> make svn+ssh://svn.gna.org/svn/gnustep/tools/make/trunk<br /> <br /> So everytime I checkout /devmodules/core the svn client will automatically go to these URLs and check them out into subdirectories. When I make changes in gui/ and commit them, it will really commit to /libs/gui/trunk. For the most part if you checkout /devmodules, the externals have already been setup such that it will checkout something similar to checking out the whole repository before.<br /> <br /> == Tips, Tricks, and Resources ==<br /> <br /> * [http://svnbook.red-bean.com Version Control with Subversion]<br /> * [http://svnbook.red-bean.com/en/1.1/apa.html Appendix A: Subversion for CVS Users]<br /> * [http://gcc.gnu.org/wiki/SvnSetup GCC's SVN Setup page] - Look especially at the section on [http://gcc.gnu.org/wiki/SSH%20connection%20caching ssh connection caching].<br /> * [[Subversion_Migration]] - Some initial notes on the layout of the repository.<br /> * [http://www.aeruder.net/software/misc/softwarelist.html ZSH svn tab completion] - On this page is a tab completion module that can tab complete into subversion repositories. Very handy for ZSH users.</div>

Aperez https://mediawiki.gnustep.org/index.php?title=Cocoa&diff=2973 2006-03-13T05:18:21Z

<p>Aperez: /* Cocoa/GNUstep API Compatiblity map */</p> <hr /> <div>From the [http://developer.apple.com/cocoa/ Apple] site: '''Cocoa''' is an object-oriented application environment designed specifically for developing Mac OS X-only native applications. The Cocoa frameworks include a complete set of classes, and for developers starting new Mac OS X-only projects, Cocoa provides the fastest way to full-featured, extensible, and maintainable applications. You can bring applications from UNIX and other platforms to Mac OS X quickly by using Cocoa to build state-of-the-art Aqua user interfaces while retaining most existing core code.<br /> <br /> More detailed information can be found at http://developer.apple.com/cocoa/<br /> <br /> The Predcessor to Cocoa was [[OpenStep]].<br /> <br /> ===Cocoa/GNUstep API Compatiblity map===<br /> <br /> TBW - to be written - please contribute. What is envisioned for this section is a color-coded compatibility matrix listing all Cocoa API elements, with green for 'should be fully fully compatible', yellow for partially compatible, grey for 'currently incompatible', and red for 'not within the scope of GNUstep, with no current or future plans to implement'<br /> <br /> ===Cocoa/GNUstep relationship===<br /> <br /> [[Image:GNUstep_and_Cocoa.png|Created by [[http://mediawiki.gnustep.org/index.php/User:Stefan_Urbanek]]Stefan Urbanek]]</div>

Aperez https://mediawiki.gnustep.org/index.php?title=Cocoa&diff=2972 2006-03-13T05:17:56Z

<p>Aperez: </p> <hr /> <div>From the [http://developer.apple.com/cocoa/ Apple] site: '''Cocoa''' is an object-oriented application environment designed specifically for developing Mac OS X-only native applications. The Cocoa frameworks include a complete set of classes, and for developers starting new Mac OS X-only projects, Cocoa provides the fastest way to full-featured, extensible, and maintainable applications. You can bring applications from UNIX and other platforms to Mac OS X quickly by using Cocoa to build state-of-the-art Aqua user interfaces while retaining most existing core code.<br /> <br /> More detailed information can be found at http://developer.apple.com/cocoa/<br /> <br /> The Predcessor to Cocoa was [[OpenStep]].<br /> <br /> ===Cocoa/GNUstep API Compatiblity map===<br /> <br /> TBW - to be written - please contribute. What is envisioned for this section is a color-coded compatibility matrix listing all Cocoa API elements, with green for 'should be fully fully compatible', yellow for partially compatible, grey for 'currently incompatible', and red for 'not within the scope of GNUstep/no current or future plans to implement')<br /> <br /> ===Cocoa/GNUstep relationship===<br /> <br /> [[Image:GNUstep_and_Cocoa.png|Created by [[http://mediawiki.gnustep.org/index.php/User:Stefan_Urbanek]]Stefan Urbanek]]</div>

Aperez https://mediawiki.gnustep.org/index.php?title=Cocoa&diff=2971 2006-03-13T05:17:24Z

<p>Aperez: /* Cocoa/GNUstep relationship */</p> <hr /> <div>From the [http://developer.apple.com/cocoa/ Apple] site: '''Cocoa''' is an object-oriented application environment designed specifically for developing Mac OS X-only native applications. The Cocoa frameworks include a complete set of classes, and for developers starting new Mac OS X-only projects, Cocoa provides the fastest way to full-featured, extensible, and maintainable applications. You can bring applications from UNIX and other platforms to Mac OS X quickly by using Cocoa to build state-of-the-art Aqua user interfaces while retaining most existing core code.<br /> <br /> More detailed information can be found at http://developer.apple.com/cocoa/<br /> <br /> The Predcessor to Cocoa was [[OpenStep]].<br /> <br /> ===Cocoa/GNUstep relationship===<br /> <br /> [[Image:GNUstep_and_Cocoa.png|Created by [[http://mediawiki.gnustep.org/index.php/User:Stefan_Urbanek]]Stefan Urbanek]]<br /> <br /> ===Cocoa/GNUstep API Compatiblity map===<br /> <br /> TBW - to be written - please contribute. What is envisioned for this section is a color-coded compatibility matrix listing all Cocoa API elements, with green for 'should be fully fully compatible', yellow for partially compatible, grey for 'currently incompatible', and red for 'not within the scope of GNUstep/no current or future plans to implement')</div>

Aperez https://mediawiki.gnustep.org/index.php?title=Cocoa&diff=2970 2006-03-13T05:12:03Z

<p>Aperez: /* Cocoa/GNUstep relationship */</p> <hr /> <div>From the [http://developer.apple.com/cocoa/ Apple] site: '''Cocoa''' is an object-oriented application environment designed specifically for developing Mac OS X-only native applications. The Cocoa frameworks include a complete set of classes, and for developers starting new Mac OS X-only projects, Cocoa provides the fastest way to full-featured, extensible, and maintainable applications. You can bring applications from UNIX and other platforms to Mac OS X quickly by using Cocoa to build state-of-the-art Aqua user interfaces while retaining most existing core code.<br /> <br /> More detailed information can be found at http://developer.apple.com/cocoa/<br /> <br /> The Predcessor to Cocoa was [[OpenStep]].<br /> <br /> ===Cocoa/GNUstep relationship===<br /> <br /> [[Image:GNUstep_and_Cocoa.png|frame|Created by [[http://mediawiki.gnustep.org/index.php/User:Stefan_Urbanek]]Stefan Urbanek]]<br /> <br /> ===Cocoa/GNUstep API Compatiblity map===<br /> <br /> TBW - to be written - please contribute. What is envisioned for this section is a color-coded compatibility matrix listing all Cocoa API elements, with green for 'should be fully fully compatible', yellow for partially compatible, grey for 'currently incompatible', and red for 'not within the scope of GNUstep/no current or future plans to implement')</div>

Aperez https://mediawiki.gnustep.org/index.php?title=File:GNUstep_and_Cocoa.png&diff=2969 2006-03-13T05:11:34Z

<p>Aperez: object image map of the GNUstep/Cocoa relationship</p> <hr /> <div>object image map of the GNUstep/Cocoa relationship</div>

Aperez https://mediawiki.gnustep.org/index.php?title=Cocoa&diff=2968 2006-03-13T05:04:10Z

<p>Aperez: added section on Cocoa-GNUstep relationship</p> <hr /> <div>From the [http://developer.apple.com/cocoa/ Apple] site: '''Cocoa''' is an object-oriented application environment designed specifically for developing Mac OS X-only native applications. The Cocoa frameworks include a complete set of classes, and for developers starting new Mac OS X-only projects, Cocoa provides the fastest way to full-featured, extensible, and maintainable applications. You can bring applications from UNIX and other platforms to Mac OS X quickly by using Cocoa to build state-of-the-art Aqua user interfaces while retaining most existing core code.<br /> <br /> More detailed information can be found at http://developer.apple.com/cocoa/<br /> <br /> The Predcessor to Cocoa was [[OpenStep]].<br /> <br /> ===Cocoa/GNUstep relationship===<br /> <br /> [[Image:GNUstep_and_Cocoa.png|thumb|<br /> Created by [[http://mediawiki.gnustep.org/index.php/User:Stefan_Urbanek]Stefan Urbanek]]<br /> <br /> ===Cocoa/GNUstep API Compatiblity map===<br /> <br /> TBW - to be written - please contribute. What is envisioned for this section is a color-coded compatibility matrix listing all Cocoa API elements, with green for 'should be fully fully compatible', yellow for partially compatible, grey for 'currently incompatible', and red for 'not within the scope of GNUstep/no current or future plans to implement')</div>

Aperez https://mediawiki.gnustep.org/index.php?title=StepTalk&diff=889 2005-06-21T19:07:39Z

<p>Aperez: minor grammatical fixes, a couple of one-letter typos fixed</p> <hr /> <div>StepTalk is the official GNUstep [[Scripting|scripting]] framework. In fact, StepTalk is more than a scripting framework with an illusion of a single objective environment between objects of scriptable servers or applications. StepTalk, when combined with the dynamism that the Objective-C language provides, goes way beyond mere scripting. It is language independent - it uses [[Scripting language bundle|languages as separate bundles]]. <br /> <br /> Author: [[User:Stefan Urbanek|Stefan Urbanek]]<br /> <br /> == Introduction ==<br /> <br /> The Goal of StepTalk is to provide an environment for gluing applications together - one uses StepTalk to make apps cooperate on a single user defined task. Other major goals are:<br /> <br /> * simple and quick extensions of applications or tools<br /> * batch-processing of objects in applications or tools<br /> * fast prototyping of applications or new application features (play and tune a concept &quot;online&quot;)<br /> <br /> It does not mean that the framework should not be used for whole application development, however it was never designed for that purpose. StepTalk application development is a form of very fast prototyping of an application.<br /> <br /> The StepTalk package features a framework, set of tools, [[Scripting language bundle|language bundle]], modules and object finders. '''The framework''' provides an application interface for developers to make their products scriptable. For more information about the tools, see [[StepTalk tools]]. Concerning the scripting language, the StepTalk is a '''language independent framework''' It can be extended via &quot;language bundles&quot; to provide and support other scripting languages. An experimental language bundle for Guile is included in the sources package. <br /> <br /> The default scripting language in StepTalk is [[Smalltalk]]. This is because Smalltalk is a very simple language and it is easy to learn. There are just a few basic principles that the user has to know to be able to use the language and it is close to the natural language. [[Smalltalk]] uses a similar approach to that of [[Objective-C]], the language used in GNUstep itself. <br /> <br /> '''Object Finders''' are an illusion of single objective environment. Name of an object may me known, but the object itself not. The object may be an application or it may reside on other host. Object Finder is an object that will search for object by specified name. <br /> <br /> * '''Distributed Object Finder''' - This finder will try to look for a registered named object. It is possible to specify list of possible hosts where the object may reside and to specify a program that will provide the object if it cannot be found. <br /> * '''Application Finder''' - Looks for a locally installed application and tries to connect to it. If the application is not running, it will try to launch it.<br /> <br /> == Download ==<br /> <br /> * [ftp://ftp.gnustep.org/pub/gnustep/libs/ Source]<br /> * [http://packages.debian.org/cgi-bin/search_packages.pl?keywords=steptalk&amp;searchon=sourcenames&amp;version=all&amp;release=all&amp;exact=1 Debian packages]<br /> <br /> * [http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/dev-libs/StepTalk/ Browse CVS]<br /> <br /> Get it by CVS:<br /> <br /> export CVS_RSH=&quot;ssh&quot;<br /> cvs -z3 -d:ext:anoncvs@savannah.gnu.org:/cvsroot/gnustep co StepTalk<br /> <br /> == The Framework ==<br /> <br /> Classes:<br /> <br /> * [[STContext]]<br /> * [[STEnvironment]]<br /> * [[STScriptManager]]<br /> * [[STScriptObject]]<br /> <br /> <br /> == TODO ==<br /> <br /> For more information about what should be done in StepTalk see [[StepTalk TODO]].<br /> <br /> == Projects using StepTalk ==<br /> <br /> [http://www.moltalk.org/ MolTalk] - a computational environment for doing Structural Bioinformatics. It interprets PDB formatted files and creates an object representation of the structure-chain-residue-atom hierarchy. Through the use of MolTalk, the PDB suddenly becomes an object-oriented database. <br /> <br /> ----<br /> <br /> See also: [[Scripting]], [http://www.smalltalk.org/ Smalltalk.org]<br /> <br /> [[Category:Scripting]] [[Category:Frameworks]]</div>

Aperez https://mediawiki.gnustep.org/index.php?title=FOSDEM_2005&diff=1977 2005-02-28T21:45:11Z

<p>Aperez: </p> <hr /> <div>'''GNUstep Developer Meeting at Fosdem 2005'''<br /> <br /> == The event ==<br /> <br /> A GNUstep developer meeting was held in Bruxelles (Belgium), during [http://www.fosdem.org/2005/index/ Fosdem 2005] on 26-27 February 2005. Fosdem is the annual Free and Open source Software Developers' European Meeting, and provides a natural framework for GNUstep developers to meet.<br /> <br /> GNUstep and [[Image:OpenGroupwareLogo.gif]] (http://www.opengroupware.org/) will share a booth and a dev room.<br /> <br /> == Why you want to be there ==<br /> <br /> You want to be there to meet the GNUstep developers in person.<br /> <br /> The first GNUstep developer meetings, held during Fosdem 2002, [http://www.gnustep.it/fosdem2003/ Fosdem 2003], and [http://wiki.gnustep.org/index.php/fosdem%202004 Fosdem 2004] have been a [http://www.gnustep.de/Features/fosdem2003.en.php3 success]. GNUstep developers, programmers, users, fans, and curious had an occasion to meet and talk in a very friendly and informal atmosphere.<br /> <br /> We hope to repeat this succesful experience during Fosdem 2005.<br /> <br /> The focus of the meeting is more on meeting each other, rather than on formal conferences, but we still plan to organize a small agenda of talks about interesting GNUstep topics, to be held by major developers and contributors. They can be a starting point for further discussions, or simply an occasion to learn more about specific GNUstep topics. Stay tuned on these pages for more info.<br /> <br /> We'd also like to invite a wider public to our talks and conferences, but that's not necessarily easy.<br /> <br /> == Who will attend the meeting ==<br /> <br /> One of the main reasons people attend the meeting is that you can meet, and talk directly to, other developers, whom you would otherwise meet only virtually (on mailing lists, emails, newsgroups, irc etc). We expect many lead developers and contributors to be present, so if you have never met them, you can't miss this occasion!<br /> <br /> The following is a list of people of GNUstep fame (in alphabetical order) who have confirmed (or denied) that they will be able to join us at the GNUstep meeting at Fosdem 2005:<br /> <br /> {| border=1<br /> ! Name<br /> ! Presence<br /> ! Special comments<br /> |- <br /> | Marcus Müller || yes<br /> |-<br /> | Helge Hess || yes<br /> |- <br /> | Bjoern Stierand || yes ||<br /> |-<br /> | Quentin Mathé || yes || I will come to the Saturday dinner<br /> |-<br /> | Nicolas Roard || yes || I will be happy to go to the saturday dinner too :)<br /> |-<br /> | Gerold Rupprecht || yes || I will be happy to sponsor dinner again Saturday evening<br /> |-<br /> | Wim Oudshoorn || yes ||<br /> |-<br /> | Fabien Vallon || yes ||<br /> |-<br /> | Chris Vetter || yes || I'll be back err there (job permitting)<br /> |-<br /> | Lars S.-Helldorf || yes || looking forward to the dinner<br /> |-<br /> | Peter Cooper || yes ||<br /> |}<br /> <br /> If you plan to join us at the meeting, please let us know here in the wiki. Knowing how many people will attend will help in organizing the event, and will encourage other people to join.<br /> <br /> == Topics ==<br /> <br /> Proposed Talks :<br /> <br /> {| border=1 <br /> ! Name<br /> ! Subject<br /> ! Estimated length<br /> |+<br /> | Quentin Mathé, Nicolas Roard<br /> | Étoilé desktop environment ideas and frameworks (BookmarkKit, ExtendedWorkspaceKit, IconKit,etc.)<br /> | 45 mn<br /> |+<br /> | GNUstep contributors<br /> | GNUstep marketing : better GNUstep installation and development with GNUstep Kits, better look with new GNUstep icons and themes, etc.<br /> | 45 mn<br /> |+<br /> | Wim Oudshoorn &amp; others <br /> | GNUstep on Windows, presentation and discussion<br /> | 45 mn<br /> |+<br /> | Fabien Vallon<br /> | GNUstep image application project ,presentation<br /> | 15 mn<br /> |+<br /> | Helge Hess<br /> | Using OpenGroupware.org Frameworks, presentation<br /> | 45 mn ?<br /> |+<br /> | Marcus Mueller<br /> | SOPE, presentation<br /> | 45 mn ?<br /> |}<br /> <br /> Here is the proposed timing:<br /> <br /> === Saturday ===<br /> <br /> {| border=1<br /> ! Subject<br /> ! duration<br /> ! starting time<br /> ! who<br /> |-<br /> | presentation of GNUstep || 30 min || 15:00 - 15:30<br /> |-<br /> | talk about Étoilé || 30 min || 15:30 - 16:00 || Quentin Mathe and Nicolas Roard<br /> |-<br /> | presentation of OpenGroupware || 30 min || 16:00 - 16:30 || Helge Hess<br /> |-<br /> | talk about SOPE || 30 min || 16:30 - 17:00 || Marcus Muller<br /> |}<br /> <br /> === Sunday ===<br /> <br /> {| border=1<br /> ! Subject<br /> ! duration<br /> ! starting time <br /> ! who<br /> |-<br /> | presentation of Image apps || 15 min || 14:45 - 15:00 || Fabien Vallon<br /> |-<br /> | GNUstep installer and deployment on Windows || 30 min || 15:00 - 15:30 || Wim |+ Oudshoorn<br /> |-<br /> | talk about using OpenGroupware.org Frameworks || 30 min || 15:30 - 16:00 || Helge Hess<br /> |-<br /> | talk about GNUstep marketing || 30 min || 16:00 - 16:30<br /> |}<br /> <br /> It can be great if all presenations (or at least pre-final versions) are available few days before the event and burnt to a CD with other GNUstep marketing and non-marketing material. ''-- Stefan''<br /> <br /> == Survey ==<br /> <br /> See [[Survey]].<br /> <br /> == Marketing CD ==<br /> <br /> See [[Marketing CD]]<br /> <br /> == Additional Talks ==<br /> <br /> There will be additional quick public talks (not in the gnustep devroom) the Sunday about GNUstep, OpenGroupware.org and SOPE. See the lightning talks on the fosdem wiki:<br /> http://wiki.fosdem.org/tiki-index.php?page=LightningTalks<br /> <br /> == Contacts ==<br /> <br /> [[Nicola Pero]] and [[Nicolas Roard]] (nicolas at roard dot com),<br /> [[Helge Hess]] for OpenGroupware.org (hh at opengroupware dot org)</div>

Aperez https://mediawiki.gnustep.org/index.php?title=Roadmap&diff=455 2005-02-23T20:44:57Z

<p>Aperez: /* Unsorted TODO */</p> <hr /> <div>'''GNUstep has no roadmap...!'''<br /> <br /> Anyway, here is small list of what has to be done. Refine the list, prioritize and build the roadmap. Perhaps some checklist would help...<br /> <br /> == Version 1.0 ==<br /> <br /> ''What needs to be done for GNUstep 1.0? Can someone provide a check-list? In the checklist, please provide a severity of the task, whether it is a blocker or if we can live without that.''<br /> <br /> There are many parts of GUI that are not finished, though they do not come up as often in applications as the parts that are finished. They are marked in the code by &quot;//FIXME&quot; usually. One example is handling of scrollbars of multiple widths. OpenStep provides for both two fixed scrollbar widths (normal and small) and a variable-width option. Neither are supported in GUI (but are not used that often).<br /> <br /> Base is almost entirely complete, excepting some Number formatting capabilities and maybe a couple of other things listed in the bug tracker.<br /> <br /> == Version 1.1 ==<br /> <br /> == Unsorted TODO ==<br /> <br /> * ease installation process (see [[GNUstep Installation Process]])<br /> ** what are potential platforms?<br /> ** what are their possibilities of installation?<br /> ** how can installation be combined for several platforms (one installation package for more linux distros, for example)<br /> ** how to distribute binary packages?<br /> ** what should be in the binary package?<br /> ** how should be the binary package installed? where? what should be configurable during installation?<br /> ** how to cope with more than one GNUstep environments installed?<br /> <br /> * make GUI work on MS windows (see [[Portability]])<br /> ** what is broken?<br /> ** what needs to be done?<br /> ** who is working on it?<br /> <br /> * what is the objective of GNUstep GUI/AppKit 1.0?<br /> ** what is missing?<br /> ** what does not work?<br /> <br /> * what is the objective of GNUstep core 1.0?<br /> ** what is missing?<br /> ** what does not work?<br /> <br /> * Include distcc as part of the GNUstep developement environment, somewhat akin to XCode's distributed compilation.<br /> ** Put distcc in LiveCD for intel, then we can have a GNUstep compilation farm easily.<br /> <br /> [[Category:Project procedures]]</div>

Aperez https://mediawiki.gnustep.org/index.php?title=Release_Checklist&diff=183 2005-02-17T06:57:41Z

<p>Aperez: </p> <hr /> <div>This checklist details each step which needs to be taken in order to prepare a new version of apps and libs in the GNUstep repository for release.<br /> <br /> Special thanks to Larry Coleman, who sent me an e-mail asking what the release criteria was, so he could do his first release of RIGS (he's the new maintainer). He gave me the final impetus to type up this document which I'd been intending to do for a long time.<br /> <br /> 1) make sure it compiles against the latest ''RELEASES'' of GNUstep-core, not just CVS...this is a common problem and it's simply embarassing. If it does not, delay the release until the next GNUstep release that includes the fixes you need. If it is critical that you release a new version, you can always appeal to the release manager for a new release via the gnustep-dev@gnu.org mailing list. You can build a separate $PREFIX/GNUstep-Release dir or something which you can then execute the GNUstep.sh file from this tree, which will make it use those release libs without trouncing on your current (perhaps CVS) GNUstep build.<br /> <br /> 2) grep for the version number in the source tree.... and change it everywhere...it's very embarressing when you forget to change it somewhere, as has recently happened with the ProjectCenter 0.4.2 release (which was still marked as 0.4.1 in numerous places, including the info panel and framework version :[ )<br /> <br /> 3) Once you're actually ready for a release, make the tarball, RIGS-x.y.z, and upload it to ftp.gnustep.org/pub/incoming. You can do this anonymously.<br /> <br /> 4) Once the file is uploaded, send an e-mail to webmasters@gnustep.org, (which I am subscribed to, as well as others) and simply request that (A) the file be moved from the incoming directory on the FTP site to /pub/GNUstep/libs and (B) that we add a one-line news item to the GNUstep.org front page with a direct link to the latest tarball on the FTP site, and, OPTIONALLY, (C) add info to http://www.gnustep.org/experience/RIGS.html with what's new in the current version, etc.<br /> <br /> 5) Once the file has been moved to its permanent FTP directory (but you don't necessarily have to wait for the website to be updated to reflect this), send an e-mail to BOTH info-gnustep@gnu.org AND gnustep-announce@gnu.org with &quot;ANN: RIGS version x.y.z etc et&quot; in the subject, with a standard release-formatted e-mail (for a decent and recent ANN: example, see http://lists.gnu.org/archive/html/info-gnustep/2005-02/msg00000.html ) and be sure to include notable new changes. It's important to be informative about what has changed and why it's changed. Try to be as succinct as you can. (unlike /this/ e-mail ;-)<br /> <br /> 6) '''OPTIONAL:''' If you have CVS commit privelages to GNUstep, you also have the choice of updating GNUstep.org yourself via CVS. To check out the entire CVS GNUstep website, run:<br /> <br /> CVS_RSH=ssh cvs -z3 -d &lt;username&gt;@savannah.gnu.org:/webcvs/gnustep co gnustep<br /> <br /> you can choose to just check out the main index.html page if you'd like. There are a couple of large (~17MB) files on the GNUstep.org website which might take a while to download depending on the speed of your Internet connection.<br /> <br /> Don't feel obligated to do step 6. It's actually not going to buy us much until we have a way set up where any gnustep person with CVS commit can post stuff anywhere on the GNUstep ftp site, but until then you will have to email webmasters@gnustep.org to ask us to move stuff from incoming/ to libs/ on the FTP site itself. We are of course more than happy to update the website for you, and since there are webmasters in both europe and the USA, it usually happens fairly quickly. If you do elect to update the website yourself, please be sure you know what you're doing. GNUstep.org pulls from CVS checkouts at the bottom of every hour, so be sure to check that the page updated properly the next time it goes live. In a worst-cast scenario, you might have bogus stuff on the main page for one hour. I do this accidentally from time to time.</div>

Aperez https://mediawiki.gnustep.org/index.php?title=Release_Checklist&diff=182 2005-02-17T06:50:09Z

<p>Aperez: </p> <hr /> <div>This checklist details each step which needs to be taken in order to prepare a new version of apps and libs in the GNUstep repository for release.<br /> <br /> Special thanks to Larry Coleman, who sent me an e-mail asking what the release criteria was, so he could do his first release of RIGS (he's the new maintainer). He gave me the final impetus to type up this document which I'd been intending to do for a long time.<br /> <br /> 1) make sure it compiles against the latest ''RELEASES'' of GNUstep-core, not just CVS...this is a common problem and it's simply embarressing. If it does not, delay the release until the next GNUstep release that includes the fixes you need. If it is critical that you release a new version, you can always appeal to the release manager for a new release via the gnustep-dev@gnu.org mailing list. You can build a separate $PREFIX/GNUstep-Release dir or something which you can then execute the GNUstep.sh file from this tree, which will make it use those release libs without trouncing on your current (perhaps CVS) GNUstep build.<br /> <br /> 2) grep for the version number in the source tree.... and change it everywhere...it's very embarressing when you forget to change it somewhere, as has recently happened with the ProjectCenter 0.4.2 release (which is still marked as 0.4.1 in numerous places, including the info panel and framework bundle, due to Serg's sloppy work)<br /> <br /> 3) Once you're actually ready for a release, make the tarball, RIGS-x.y.z, and upload it to ftp.gnustep.org/pub/incoming. You can do this anonymously.<br /> <br /> 4) Once the file is uploaded, send an e-mail to webmasters@gnustep.org, (which I am subscribed to, as well as others) and simply request that (A) the file be moved from the incoming directory on the FTP site to /pub/GNUstep/libs and (B) that we add a one-line news item to the GNUstep.org front page with a direct link to the latest tarball on the FTP site, and, OPTIONALLY, (C) add info to http://www.gnustep.org/experience/RIGS.html with what's new in the current version, etc.<br /> <br /> 5) Once the file has been moved to its permanent FTP directory (but you don't necessarily have to wait for the website to be updated to reflect this), send an e-mail to BOTH info-gnustep@gnu.org AND gnustep-announce@gnu.org with &quot;ANN: RIGS version x.y.z etc et&quot; in the subject, with a standard release-formatted e-mail (for a decent and recent ANN: example, see http://lists.gnu.org/archive/html/info-gnustep/2005-02/msg00000.html ) and be sure to include notable new changes. It's important to be informative about what has changed and why it's changed. Try to be as succinct as you can. (unlike /this/ e-mail ;-)<br /> <br /> 6) '''OPTIONAL:''' If you have CVS commit privelages to GNUstep, you also have the choice of updating GNUstep.org yourself via CVS. To check out the entire CVS GNUstep website, run:<br /> <br /> CVS_RSH=ssh cvs -z3 -d &lt;username&gt;@savannah.gnu.org:/webcvs/gnustep co gnustep<br /> <br /> you can choose to just check out the main index.html page if you'd like. There are a couple of large (~17MB) files on the GNUstep.org website which might take a while to download depending on the speed of your Internet connection.<br /> <br /> Don't feel obligated to do step 6. It's actually not going to buy us much until we have a way set up where any gnustep person with CVS commit can post stuff anywhere on the GNUstep ftp site, but until then you will have to email webmasters@gnustep.org to ask us to move stuff from incoming/ to libs/ on the FTP site itself. We are of course more than happy to update the website for you, and since there are webmasters in both europe and the USA, it usually happens fairly quickly. If you do elect to update the website yourself, please be sure you know what you're doing. GNUstep.org pulls from CVS checkouts at the bottom of every hour, so be sure to check that the page updated properly the next time it goes live. In a worst-cast scenario, you might have bogus stuff on the main page for one hour. I do this accidentally from time to time.</div>

Aperez https://mediawiki.gnustep.org/index.php?title=Release_Checklist&diff=181 2005-02-17T06:42:49Z

<p>Aperez: </p> <hr /> <div>This checklist details each step which needs to be taken in order to prepare a new version of apps and libs in the GNUstep repository for release.<br /> <br /> Special thanks to Larry Coleman, who sent me an e-mail asking what the release criteria was, so he could do his first release of RIGS (he's the new maintainer). He gave me the final impetus to type up this document which I'd been intending to do for a long time.<br /> <br /> 1) make sure it compiles against the latest ''RELEASES'' of GNUstep-core, not just CVS...this is a common problem and it's simply embarressing. You can build a separate $PREFIX/GNUstep-Release dir or something which you can then execute the GNUstep.sh file from this tree, which will make it use those release libs without trouncing on your current (perhaps CVS) GNUstep build.<br /> <br /> 2) grep for the version number in the source tree.... and change it everywhere...it's very embarressing when you forget to change it somewhere, as has recently happened with the ProjectCenter 0.4.2 release (which is still marked as 0.4.1 in numerous places, including the info panel and framework bundle, due to Serg's sloppy work)<br /> <br /> 3) Once you're actually ready for a release, make the tarball, RIGS-x.y.z, and upload it to ftp.gnustep.org/pub/incoming. You can do this anonymously.<br /> <br /> 4) Once the file is uploaded, send an e-mail to webmasters@gnustep.org, (which I am subscribed to, as well as others) and simply request that (A) the file be moved from the incoming directory on the FTP site to /pub/GNUstep/libs and (B) that we add a one-line news item to the GNUstep.org front page with a direct link to the latest tarball on the FTP site, and, OPTIONALLY, (C) add info to http://www.gnustep.org/experience/RIGS.html with what's new in the current version, etc.<br /> <br /> 5) Once the file has been moved to its permanent FTP directory (but you don't necessarily have to wait for the website to be updated to reflect this), send an e-mail to BOTH info-gnustep@gnu.org AND gnustep-announce@gnu.org with &quot;ANN: RIGS version x.y.z etc et&quot; in the subject, with a standard release-formatted e-mail (for a decent and recent ANN: example, see http://lists.gnu.org/archive/html/info-gnustep/2005-02/msg00000.html ) and be sure to include notable new changes. It's important to be informative about what has changed and why it's changed. Try to be as succinct as you can. (unlike /this/ e-mail ;-)<br /> <br /> 6) '''OPTIONAL:''' If you have CVS commit privelages to GNUstep, you also have the choice of updating GNUstep.org yourself via CVS. To check out the entire CVS GNUstep website, run:<br /> <br /> CVS_RSH=ssh cvs -z3 -d &lt;username&gt;@savannah.gnu.org:/webcvs/gnustep co gnustep<br /> <br /> you can choose to just check out the main index.html page if you'd like. There are a couple of large (~17MB) files on the GNUstep.org website which might take a while to download depending on the speed of your Internet connection.<br /> <br /> Don't feel obligated to do step 6. It's actually not going to buy us much until we have a way set up where any gnustep person with CVS commit can post stuff anywhere on the GNUstep ftp site, but until then you will have to email webmasters@gnustep.org to ask us to move stuff from incoming/ to libs/ on the FTP site itself. We are of course more than happy to update the website for you, and since there are webmasters in both europe and the USA, it usually happens fairly quickly. If you do elect to update the website yourself, please be sure you know what you're doing. GNUstep.org pulls from CVS checkouts at the bottom of every hour, so be sure to check that the page updated properly the next time it goes live. In a worst-cast scenario, you might have bogus stuff on the main page for one hour. I do this accidentally from time to time.</div>

Aperez https://mediawiki.gnustep.org/index.php?title=Release_Checklist&diff=180 2005-02-17T06:38:51Z

<p>Aperez: This checklist details each step which needs to be taken in order to prepare a new version of apps and libs in the GNUstep repository for release.</p> <hr /> <div>This checklist details each step which needs to be taken in order to prepare a new version of apps and libs in the GNUstep repository for release.<br /> <br /> Special thanks to Larry Coleman, who sent me an e-mail asking what the release criteria was, so he could do his first release of RIGS (he's the new maintainer). He gave me the final impetus to type up this document which I'd been /intending/ to do for a long time.<br /> <br /> 1) make sure it compiles against the latest /RELEASES/ of GNUstep-core (not just CVS)...this is a common problem and it's simply embarressing. You can build a separate $PREFIX/GNUstep-Release dir or something which you can then execute the GNUstep.sh file from this tree, which will make it use those release libs without trouncing on your current (perhaps CVS) GNUstep build.<br /> <br /> 2) grep for the version number in the source tree.... and change it everywhere...it's very embarressing when you forget to change it somewhere, as has recently happened with the ProjectCenter 0.4.2 release (which is still marked as 0.4.1 in numerous places, including the info panel and framework bundle, due to Serg's sloppy work)<br /> <br /> 3) Once you're actually ready for a release, make the tarball, RIGS-x.y.z, and upload it to ftp.gnustep.org/pub/incoming. You can do this anonymously.<br /> <br /> 4) Once the file is uploaded, send an e-mail to webmasters@gnustep.org, (which I am subscribed to, as well as others) and simply request that (A) the file be moved from the incoming directory on the FTP site to /pub/GNUstep/libs and (B) that we add a one-line news item to the GNUstep.org front page with a direct link to the latest tarball on the FTP site, and, OPTIONALLY, (C) add info to http://www.gnustep.org/experience/RIGS.html with what's new in the current version, etc.<br /> <br /> 5) Once the file has been moved to its permanent FTP directory (but you don't necessarily have to wait for the website to be updated to reflect this), send an e-mail to BOTH info-gnustep@gnu.org AND gnustep-announce@gnu.org with &quot;ANN: RIGS version x.y.z etc et&quot; in the subject, with a standard release-formatted e-mail (for a decent and recent ANN: example, see http://lists.gnu.org/archive/html/info-gnustep/2005-02/msg00000.html ) and be sure to include notable new changes. It's important to be informative about what has changed and why it's changed. Try to be as succinct as you can. (unlike /this/ e-mail ;-)<br /> <br /> 6) '''OPTIONAL:''' If you have CVS commit privelages to GNUstep, you also have the choice of updating GNUstep.org yourself via CVS. To check out the entire CVS GNUstep website, run:<br /> <br /> CVS_RSH=ssh cvs -z3 -d &lt;username&gt;@savannah.gnu.org:/webcvs/gnustep co gnustep<br /> <br /> you can choose to just check out the main index.html page if you'd like. There are a couple of large (~17MB) files on the GNUstep.org website which might take a while to download depending on the speed of your Internet connection.<br /> <br /> Don't feel obligated to do step 6. It's actually not going to buy us much until we have a way set up where any gnustep person with CVS commit can post stuff anywhere on the GNUstep ftp site, but until then you will have to email webmasters@gnustep.org to ask us to move stuff from incoming/ to libs/ on the FTP site itself. We are of course more than happy to update the website for you, and since there are webmasters in both europe and the USA, it usually happens fairly quickly. If you do elect to update the website yourself, please be sure you know what you're doing. GNUstep.org pulls from CVS checkouts at the bottom of every hour, so be sure to check that the page updated properly the next time it goes live. In a worst-cast scenario, you might have bogus stuff on the main page for one hour. I do this accidentally from time to time.</div>

Aperez https://mediawiki.gnustep.org/index.php?title=GNUstep_Installation_Process&diff=79 2005-02-16T00:15:38Z

<p>Aperez: </p> <hr /> <div>Stefan Urbanek, please modify whatever you see fit, even delete this page.<br /> <br /> GNUstep installation process should be and could be as simple as &quot;pkg-inst GNUstep-1.0&quot; across GNUstep supported OS plaforms. Given GNUstep's cross-platform declaration on application development activities, so should the application mangement activies cross-platform united. But in oder to get there, following need to be done. <br /> <br /> GNUstep package creation automation project.<br /> <br /> * What?: This is a project to automate the process of creating GNUstep environment for a perticular OS platform. <br /> <br /> * Why?: <br /> ** Lots of time is spent by experienced GNUsteppers to assist new GNUsteppers with compiling the source, and this waste will continue to occur unless we resolve certain issues.<br /> ** Time should be spent on GNUstep developement, and not on the compling and packaging process.<br /> ** Installation/removal of GNUstep easily encourges the deployment of GNUstep in corporate environments.<br /> ** The pacakge creation process can be reproduced easliy by others with commands.<br /> ** Improves QA testing by generating GNUstep instances quickly.<br /> <br /> Plan<br /> <br /> * Introduce CPAM(Cross-Platform Application Management) tool implemented by TWW Inc. to GNUstep CPAD community<br /> ** Cross-Platform is easier said then done becuase each platform's features are barriers for others.<br /> <br /> * Release GNUstep package source implemented by TWW CPAM. <br /> ** I will release a working package source for others to try and review. <br /> ** The package soruces can generate native package format for RHAS rpm,Solaris pkgadd and HP-UX depot formats. <br /> <br /> * Write tutorial on learning TWW CPAM.<br /> ** I am willing to help/assist a few persons to get familliar with TWW tools if they promise me to write up what they learned in a tutorial article. As you can see I am really not good on documenation work.<br /> <br /> * Integrate GNUstep developement process with TWW CPAM.<br /> <br /> <br /> * More details TBA once I get familiar with mediawiki.<br /> <br /> * Following lines can be deleted later. <br /> I just want to make above out of nohere text not treated as spam.<br /> My name is T.J. Yang(tj_yang at hotmail dot com), <br /> I have been working as a system administator and I am intrested <br /> to bring the work experience to work on this task. <br /> Please email me if you have comment/questions. <br /> <br /> For detail about TWW, please see http://www.thewrittenword.com, <br /> I have used their CPAM at work to bring cross-platform open-source software support <br /> nightmare under control. <br /> All the TWW tools and sources of their supported packages are GPL open-source <br /> free of charge but not their support labor.</div>

Aperez https://mediawiki.gnustep.org/index.php?title=Contact&diff=92 2005-02-15T23:45:56Z

<p>Aperez: /* IRC */</p> <hr /> <div>==== Mailing Lists ====<br /> <br /> For mailing lists see: http://www.gnustep.org/information/gethelp.html<br /> <br /> ==== IRC ====<br /> <br /> You can talk to some (not all use IRC) GNUstep developers on IRC:<br /> <br /> '''Server:''' irc.freenode.net<br /> '''Channel:''' #gnustep<br /> <br /> Configure your IRC client and join the channel:<br /> <br /> /join #gnustep<br /> <br /> Examples of IRC clients you can use: xchat (linux and windows), gaim (linux and windows), mirc (windows)</div>

Aperez