freedom is most important, and innovation is nice as long as we maintain our freedom

projects

system

frameworks
applications
documentation
  • GarmaKit
  • additional toolkit (CSTK) for Garma applications.

  • Window Manager Core
  • a special GNUstep backend designed to manage the desktop and can be used by any application that want to work as a window manager.

  • System Abstraction Layer
  • SAL is a wrapper for HAL for generating global notifications and accessing HAL's API in Objective-C space.

  • Maliwan
  • garma's color management system. Basicly this is a library that is being used in BluTulip, a multi-colormodel image edit program. Maliwan has a set of APIs to manage system color profiles and a set of basic Objective-C wrapper over LCMS.

  • DiagramKit
  • Multipurpose diagram editing framework, used in Figloo and ImageEdit.
  • Admiral
  • a simple display manager with support for XDMCP.

  • Gnock
  • a not so simple login system and a Preferences module.

  • SessionManager
  • a session manager daemon.

  • KiKa
  • a window manager built around Window Manager Core

  • Docklets
  • some nice dockapp programs. eg. clock, battery monitor, etc.
  • System Overview
  • object graph representing the architecture overview.

  • Lapis Interface Guidelines
  • all the reasons behind Lapis's ideas of human interface and guidelines for designing Lapis applications.



    common

    applications
    media
    people
  • Calendar
  • a calendar management program.

  • Shhh
  • an audio player and manager daemon that provides remote playlist management APIs over a host.

  • Figloo
  • A general diagram editor.

  • Blu Tulip
  • an imaging program, raster or vector, that can deal with color differences, color profiles managements.

  • ImageEdit
  • A simple raster image editor that will be comparable to GIMP but using Maliwan so it can deal with CMYK, RGBA, YUV, L*a*b* and etc. The file format will follow pippin's xcf2 idea.
  • Artworks
  • Image artworks, themes & tips.

  • Sounds & Musics
  • Musical and effects.
  • Project site
  • the development channel on GNA.org

  • Mailing lists
  • discussion channels.

  • Sponsor
  • how to sponsor and past donators.

    recommendation
  • LapisPuzzle
  • gap's game with no garma dependency.

  • Ladder
  • gap's gnu go frontend.


    news

    May 27 2005 :
  • Ladder
  • A simple GNU Go frontend.

    March 30 2005 :
  • garma is merging with Etoile
  • We are merging with Etoile. DiagramKit is now a part of gsimageapps project.

    January 7 2005 :
  • Figloo and DiagramKit are officially new garma projects.
  • Figloo and DiagramKit are application and framework for multipurpose diagram editor which will allow you to have and manipulate diagrams as NSViews in your applications.

    December 4 2004 :
  • Shhh project is annouced.
  • A simple XMMS2 client.

    October 18 2004 :
  • Maliwan got new documentation section.
  • The moving process has been completed. Now Maliwan's source is officially moved to GNA under System/Frameworks/Maliwan. The development mailing list was annouced. Helps are needed. If you want a really nice free software image editor on GNUstep (and Mac OS X), please join. See Maliwan for more information.

    September 28 2004 :
  • New News section
  • Maliwan is now a part of garma project.
  • It is in the process of moving from woom's CVS on Savannah to Gna.


    policy

    version:draft

    Garma Policy
    version : Draft
    
    0) FOUR FREEDOMS
    
    	FREEDOM IS MOST IMPORTANT, AND INNOVATION IS NICE
    	AS LONG AS WE MAINTAIN OUR FREEDOM. -- RMS
    
    1) Use X11
    
    	Garma's first goal will make windowing system portability
    	less concerned and focus on X11. Nevertheless, not that mean
    	Garma is going to take supporting X11 applications as priority.
    	For instance, session management. Garma needs to implement
    	a mechanism in x11-backend so the later logged session can
    	"pull" the older session's running applications over Display.
    	This mechanism won't work with other X11 applications that
    	aren't GNUstep application.
    
    2) Lapis
    
    	Lapis will be the only support theme. It isn't and won't be
    	very configurable. This is an attemp to make a brand look
    	and also to reduce total support task. Lapis will have an
    	issue with NSToolbar. In Lapis, an NSToolbar will sit on the
    	top of the screen, application's menu title will be an icon
    	not a text displaying application's name and will be listed
    	at the top left of the screen, by the left of toolbar items,
    	with clicking shows the application menu. This is an attemp
    	to improve mouse usage by fitt's laws.
    
    3) GNUstep
    
    	Since Garma is an effort to develop a proper desktop environment
    	with GNUstep. It has no intention to abuse GNUstep in any possible
    	way. Garma will try its best to corporate with other GNUstep desktop
    	enviroments such as Backbone and Etoile(?) as much as possible.
    	As long as it didn't conflict with Garma's interface goal "Lapis".
    
    4) Freedesktop.Org et al.
    
    	* Cairo backend.
    
    	* HAL.
    
    	* link DBUS with the global notification.
    
    	* make use of GNOME Storage.
    
    	* NSWindow transparency.
    
    	* No intention to rewrite everything in Objective-C. C, GObject,
    	C++ libraries are always welcome.
    
    5) I18N
    
    	* make use of IIIMF.
    
    	* Hyphenation, BiDi, Veritical text layout. (ordered by priorities)
    
    6) Living together - Garma Ain't RM (Removing My) Alternatives
    
    	Garma must makes sure for not trying to kill other (free) environments.
    	Living together is the only goal of Garma and we should request our
    	users to strictly follow and take care of this idea forever.
    	By this meaning, no killing device should be represented in any
    	Garma product. For instance, a debugger's icon should be a broom,
    	not a can of DDT. (Please do no take this part seriously.)