GNUstepWiki - User contributions [en]

3DKit

2008-07-10T14:14:32Z

MBc:

{{Framework|
shortdescription = The GNU 3DKit provides an object oriented graphics API for writing 3D graphics applications using GNUstep or Cocoa. |
currentversion = 0.4 |
releasedate = |
license = [http://www.gnu.org/copyleft/lesser.html GNU Lesser General Public License] |
overview = The GNU 3DKit is officially part of the GNU project! It is an extension to GNUstep, which provides an object oriented application development framework and tool set for use on a wide variety of computer platforms. GNUstep is based on the original OpenStep specification provided by NeXT, Inc. (now Apple). Additionally the GNU 3DKit may also be used on Mac OS X using the Cocoa API. |
features = Instead of developing yet another OpenGL based scene graph API the new GNU 3DKit will become an object oriented graphics framework based on global illumination concepts which will use OpenGL only for preview capabilities. More information will be reveiled as soon as the time is ready for it.|
maintainer = [http://www.nice.ch/~phip/ Philippe C.D. Robert] |
relatedlinks = * [http://www.gnu.org/software/gnu3dkit/ GNU 3DKit]
* [http://savannah.gnu.org/projects/gnu3dkit/ Savannah] |
category = [[Category:Graphics_Frameworks]]
}}

XMLRPC

2008-07-10T14:01:53Z

MBc:

{{Framework|
shortdescription = XMLRPC Framework: a framework implementing XML-RPC in Objective-C.|
currentversion = |
releasedate = 06/30/2003 |
license = GNU Lesser General Public License, version 2.1 |
overview = Mulle XMLRPC is a client/server implementation of the XML-RPC specification. In short, XML-RPC is a protocol for doing remote procedure calls on top of XML via HTTP. As such, XML-RPC does not depend on a specific programming language and in fact there are a lot of implementations for different languages. This implementation is written in Objective-C and fills that gap.|
features =
* If you want to implement XML-RPC (client or server) in Objective-C, sure here you are.
* If you're just looking for a cool, scalable server - again, here you are. Mulle XMLRPC implements several extensions (multicall, introspection) that most other servers do not have. Also, there are hooks (and documentation) for integrating Mulle XMLRPC into WebObjects, a highly scalable Application server.
* If you have a "legacy" app and want to replace/extend NSConnections with a similar but also language neutral interface. Here you go. By the way, that's my initial reason for writing this framework. Mulle XMLRPC's XRConnection class provides a very easy way to form "reliable" connections which are able to tell that the remote end has gone away. The whole interface of XRConnection is compatible with NSConnection and can be used as a drop in replacement.|
maintainer = * [http://www.mulle-kybernetik.com/~znek/ Marcus Müller]|
relatedlinks =
* http://www.mulle-kybernetik.com/software/XMLRPC/
* [http://cvs.mulle-kybernetik.com/ CVS] |
category = [[Category:Development_Frameworks]]
}}

EDFrameworks

2008-07-10T13:48:56Z

MBc:

{{Framework|
shortdescription = One framework that provides seamless extensions of Foundation and AppKit. Two more frameworks that provide services for Internet applications, style sheet driven export of your objects and message handling. |
currentversion = [[EDCommon]] V. 33; [[EDStyleSheet]] V. 3; [[EDMessage]] V. 16|
releasedate = 2003 |
license = BSD style |
overview = The [[EDCommon]] framework extends Foundation and AppKit in a natural way. It contains common methods you always need, like removing whitespace around a string, special collection classes such as stack or object pair, an object-oriented API for socket programming, some widgets, the chasing arrows to indicate background activity for example, a parser for markup languages and other nifty stuff.

The [[EDStyleSheet]] framework uses the parser from the EDCommon Framework to read stylesheets and create an "active model" of the style sheet that interacts with your classes to produce output in any text based language, e.g. XML or LaTeX. In a way, a very flexible kind of WebObjects component. You can also subclass existing model classes and add new ones.

The [[EDMessage]] framework contains classes to analyse and create Internet Messages with MIME extensions as well as a ready-to-use e-mail client class. |
features = All frameworks come with project files for XCode and makefiles for GNUstep. |
maintainer = Mulle Kybernetik |
relatedlinks = http://www.mulle-kybernetik.com/software/EDFrameworks/download.html |
category = [[Category:Development_Frameworks]]
[[Category:Networking_Frameworks]]
}}

EDFrameworks

2008-07-10T13:48:28Z

MBc:

{{Framework|
shortdescription = One framework that provides seamless extensions of Foundation and AppKit. Two more frameworks that provide services for Internet applications, style sheet driven export of your objects and message handling. |
currentversion = [[EDCommon]] V. 33; [[EDStyleSheet]] V. 3; [[EDMessage]] V. 16|
releasedate = 2003 |
license = BSD style |
overview = The [[EDCommon]] framework extends Foundation and AppKit in a natural way. It contains common methods you always need, like removing whitespace around a string, special collection classes such as stack or object pair, an object-oriented API for socket programming, some widgets, the chasing arrows to indicate background activity for example, a parser for markup languages and other nifty stuff.

The [[EDStyleSheet]] framework uses the parser from the EDCommon Framework to read stylesheets and create an "active model" of the style sheet that interacts with your classes to produce output in any text based language, e.g. XML or LaTeX. In a way, a very flexible kind of WebObjects component. You can also subclass existing model classes and add new ones.

The [[EDMessage]] framework contains classes to analyse and create Internet Messages with MIME extensions as well as a ready-to-use e-mail client class. |
features = All frameworks come with project files for XCode and makefiles for GNUstep. |
maintainer = Mulle Kybernetik |
relatedlinks = http://www.mulle-kybernetik.com/software/EDFrameworks/download.html#EDStyleSheet |
category = [[Category:Development_Frameworks]]
[[Category:Networking_Frameworks]]
}}

MusicKit

2008-07-04T09:26:46Z

MBc:

{{Framework|
shortdescription = object-oriented software system for building music, sound, signal processing, and MIDI applications. |
currentversion = V5.5.2 |
releasedate = 2005-05-14 |
license = [http://musickit.sourceforge.net/license.html MusicKit License] |
overview = The MusicKit is an object-oriented software system for building music, sound, signal processing, and MIDI applications. It has been used in such diverse commercial applications as music sequencers, computer games, and document processors. Professors and students in academia have used the MusicKit in a host of areas, including music performance, scientific experiments, computer-aided instruction, and physical modeling. The MusicKit was the first to unify the MIDI and Music V paradigms, thus combining interaction with generality (Music V, written by Max Mathews and others at Bell Labs four decades ago, was the first widely available "computer music compiler").

The NeXT MusicKit was first demonstrated at the 1988 NeXT product introduction and was bundled in NeXT software releases 1.0 and 2.0. Beginning with NeXT's 3.0 release, the MusicKit was no longer part of the standard NeXT software release. Instead, it was being distributed and supported as Version 4.0 by the Center for Computer Research in Music and Acoustics (CCRMA) of Stanford University. Versions 5.0 to 5.4.1 were then supported by tomandandy music, porting to several more popular operating systems.

The MusicKit Distribution is a comprehensive package that includes on-line documentation, programming examples, utilities, applications and sample score documents. The MusicKit is dependent on the SndKit distribution, originally written by Stephen Brandon, and both Framework collections are available at the same distribution site. The SndKit was written to be a complete open source implementation of NeXTs SoundKit. The re-write started and almost finished before the SoundKit itself was released in source code form.

Source code is available for everything, with the exception of the NeXT hardware implementation of the low-level sound and DSP drivers. This means researchers and developers may study the source or even customize the Music Kit and DSP tools to suit their needs. Enhancements can be committed to the CVS repository to have them incorporated for future releases. Commercial software developers may freely incorporate and adapt the software to accelerate development of software products.
|
features = * Applicable to composers writing real-time computer music applications.
* Applicable to programmers writing cross-platform audio/music applications.
* Extensible, high-level object-oriented frameworks that are a super-set of Music V and MIDI paradigms.
* Written in Objective C and C, using Apple's OpenStep/Cocoa API, the FoundationKit.
* Using the Python to Objective C bridge PyObjC enables applications and utilities to be written in Python, an interpreted object-oriented language.
* Functionally comparable (although architecturally dissimilar) to JMSL (Java Music Specification Language).
* Representation system capable of depicting phrase-level structure such as legato transitions.
* General time management/scheduling mechanism, supporting synchronization to MIDI time code.
* Efficient real-time synthesis and sound processing, including option for quadraphonic sound.
* Complete support for multiple MIDI inputs and outputs.
* Fully-dynamic DSP resource allocation system with dynamic linking and loading, on multiple DSPs.
* Digital sound I/O from the DSP port with support for serial port devices by all popular vendors.
* Non-real time mode, where the DSP returns data to the application or writes a sound file.
* Suite of applications, including Ensemble ― an interactive algorithmic composition and performance environment (including a built-in sampler), and ScorePlayer ― a Scorefile and standard MIDI file player.
* Library of instruments, including FM, wavetable, physical modeling and waveshaping synthesis.
* Library of unit generators for synthesis and sound processing.
* Documentation, programming examples, utilities, including a sound file mixer, sample rate converter, etc.
* ScoreFile, a textual scripting language for music.
* Connectable audio processing modules (“plugins”) including standard audio effects such as reverb.
* Sound data held in a specifiable variety of formats, i.e 8, 16, 24 bit or floating point. Allows trading off sample data size vs. processing time.
* MP3 file reading and writing. Decoding of MP3 can be done in a background thread after reading, or on-the-fly during playback, allowing selection of memory consumption versus processor load.
* MP3 and Ogg/Vorbis streaming of audio output to web servers using the libshout library. The libshout library license is LGPL, not GPL and so do not compromise the MusicKit license
|
maintainer = Leigh M. Smith |
relatedlinks = * [http://musickit.sourceforge.net/ The MusicKit Project]
* [http://www.jaffe.com/mk97.html David Jaffe's (the original author) MusicKit site.]
* [http://ccrma-www.stanford.edu/CCRMA/Overview/hardsoftware.html CCRMA's MusicKit site.]|
category = [[Category:Audio Frameworks]]
}}