Summer Of Code 2009 - Revision history

Xgl: /* GAP : delete some too big projects */

2009-03-13T09:00:49Z

GAP : delete some too big projects

Xgl: /* More Ideas about CoreData */

2009-03-13T08:59:13Z

More Ideas about CoreData

Rio: /* GNUstep Ideas */

2009-03-13T00:50:54Z

GNUstep Ideas

Rio: /* Mentors */

2009-03-13T00:43:40Z

Mentors

Xgl: /* Mentors */

2009-03-12T16:07:54Z

Mentors

Xgl: /* GAP (GNUstep Application Project) Ideas */

2009-03-12T16:07:22Z

GAP (GNUstep Application Project) Ideas

Xgl: /* GNUstep Ideas */

2009-03-12T16:03:04Z

GNUstep Ideas

Multix: added myself

2009-03-12T11:26:48Z

added myself

Multix: /* OpenGroupware.org Ideas */

2009-03-12T11:25:17Z

OpenGroupware.org Ideas

Multix: porting

2009-03-12T11:21:59Z

porting

@@ Line 75: / Line 75: @@
 * Some miscellaneous applications that run a Cocoa GUI could be ported to GNUstep:
 ** ''Vim GUI'' : at least two cocoa-based gui projects already exist - [http://www.ohloh.net/p/vim-cocoa vim-cocoa] and [http://macvim.org/OSX mac-vim]
 ** [http://www.videolan.org/vlc VLC media player] : a Cocoa based interface exists for VLC.
 ** ''[http://www.sbrain.org/nethack3d NetHack3D]'' is a Cocoa port of [http://www.nethack.org NetHack] with 3D graphics.
 * ''OpenGL extensions management API'': before using an OpenGL extension a program must first determine its availability. The mechanism for doing this is platform-specific and libraries such as [[w:GLEW]] and [[w:GLEE]] exist to simplify the process. The target of this project is a multiplatform Objective-C wrapper around OpenGL platform-specific functions.
 * ''HID API'': GNUstep can only handle the usual ''human interface devices'' (HID) : keyboard and mouse. A multiplatform framework would allow  GNUstep application to handle joystick, graphic tablet or 3D device.

@@ Line 18: / Line 18: @@
 ** ''NSPersistentStore concrete classes'' based on SQLite, XML, binary, etc. backends.
 ** ''DataBuilder.app'' is a graphical application for designing data models. The GUI needs some improvement. Moreover DataBuilder should be turn into a true CoreData application.
 ** ''File formats compatibility'' with Cocoa, including model files.

@@ Line 51: / Line 51: @@
 ** ''NSMovie/QTMovie class'' : on Mac OSX, the NSMovie (now deprecated) and QTMovie classes are based on QuickTime Apple tecnologies. GNUstep compatible classes might be based on open source ans multiplatform technologies like [http://www.videolan.org VideoLAN]
 ** NSOpenGLPixelBuffer : this class has been introduced in Mac OSX 10.5. It might be useful for any modern OpenGL application.
+** Improve/clean the text system -- add temporary attributes, pango support
 * '''GNUstepWeb'''

@@ Line 106: / Line 106: @@
 * Riccardo Mottola (as co-Mentor, as Fred suggested)
 * Xavier Glattard
 === Students ===

@@ Line 105: / Line 105: @@
 * Fred Kiefer
 * Riccardo Mottola (as co-Mentor, as Fred suggested)
 === Students ===

@@ Line 70: / Line 70: @@
 * implement (Extract from Addresses) an iSync compatible framework, its corresponding managment application and then integrating it with AddressBook (which already has part of such framework). The goal would be to have syncronization of Addresses (but in future, perhaps calendar, Vespucci bookmarks) gnustep to gnustep, gnustep to mac and gnustep to .Mac/MobileMe by having such account.
 * porting of Applications from OpenStep or Cocoa abandonware. This needs to be checked on application-per-application: License and dependencies can be a problem as defining the scope of the project well.
 ''Feel to add ideas…''

@@ Line 14: / Line 14: @@
 ''Here are some ideas -- Feel free to add more''
 * '''WebKit / SimpleWebKit'''
@@ Line 21: / Line 27: @@
 * '''General Improvements'''
 ** Compare current API with Leopard's (Mac OS X 10.5) API, indicate which classes are missing, and summarize the current status of the existing ones, then work to complete them... ;) The best would be to have a tool which parses all headers (both from Cocoa and GNUstep) and outputs differences in HTML (XML probably too by the way). This would summarize missing classes, missing or partially implementated methods in existing classes and GNUstep-specific extensions. Eventually we should include links to the related documentation on both GNUstep and Cocoa web sites.
 ** Garbage Collection ... get this working reliably for all classes in the base library (mostly done already) and then make the gui and back libraries support garbage collection too.  The existing support consists of an option in gnustep-make to build everything with GS_WITH_GC defined and link with the Boehm garbage collecting library and the garbage collecting version of the runtime, and near complete support for the OSX10.5 garbage collection APIs in gnustep-base. the project would involve making sure that all classes handle memory management properly in a  GC environment, and would require the student to develop a thorough understanding of the benefits and pitfalls of using garbage collection, and how to alter existing design patterns to make classes operate efficiently in a garbage collecting environment.  existing code would need to be stress-tested in both single and multi-threaded use and on different platforms (at least gnu/linux and mswindows).
 ** Craft a system which allows to distribute GNUstep to the various packaging systems (rpm, debian, ports, etc.) on various distributions (Ubuntu, Red Hat, FreeBSD, etc.) with a snap and without knowledge of the specific packaging system. This system should be able to distribute GNUstep libraries, and existing or new applications written with it. The user should be able to choose how often this is done: on request, on each release, on in regular intervals, tracking a source code repository. Ideally, changes to the library/app's sources are minimized and/or calculated at runtime.
@@ Line 37: / Line 49: @@
 ** Themes for GNUstep. This includes the moving of all drawing code from the GUI classes into theme methods, replacing all hard coded panels with Gorm/NIB files, updating Thematic.app to support the new theming methods, and as the proof of the concept a native Windows theme (Or at least one theme that looks sufficiently different from standard GNUstep).
 ** Implement a test framework for the graphical part of the GNUstep AppKit implementation. We already have a great test framework for base and this is well suited for non-graphical tests.

@@ Line 63: / Line 63: @@
 Some ideas by Sebastian Reitenbach:
-(a) port SOPE/OGo to from libFoundation to gnustep-base
+(a) port SOPE/OGo from libFoundation to gnustep-base
 (b) implement the CalDAV/CardDAV REPORT operations in ZideStore