Development

From Sawfish

This page is the portal of sawfish developments.

[edit] Status

It's hard to tell the current status in short.

Read mailing list, or its archive. That's our main communication method.
Use git repository. Summary may be tracked via Changelog or

news.texi.

[edit] Todos

[edit] Near future

Proposed Goals - todos for the coming release.
General todos

[edit] General

Past todos lists what is accomplished.
Versioning scheme

[edit] If possible

(Dec 2008) No one seems to be working on the items listed under this category.

Enhancements suggestion in sawfish core

[edit] Composite Extension, OpenGL and friends

Ostensibly the future of sawfish is have access to the new protocols. One key to implementing is understanding what they do and how they are supposed to be interacted with. To start these pages can be nothing more than links to the specs and basic tutorials.

Current Docs:

[edit] Known difficulty

Some know difficulty in development can be found at Patches (suspended).

[edit] Bug reports

Open bugs on bugzilla.gnome.org, of
All Sawfish bugs on bugzilla.gnome.org
Bugs reported in bugs.debian.org
Bugs in sourceforge.net tracker (visible only when logged it)

To report a bug at bugzilla.gnome.org, choose:

classification: Other
application: sawfish / librep / rep-gtk

If you're not sure of which the bug is, choose sawfish.

For search from browser (like Firefox smart keyword), use the following url:

http://bugzilla.gnome.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Other&product=sawfish&long_desc_type=substring&long_desc=%s&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=NEEDINFO&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=

[edit] Librep & rep-gtk

[edit] Librep internals

How to write a librep C modules is not documented. The documentation would have the API, the conventions and an skeleton example with a tutorial of sorts. The example would have all the other helper code like Makefiles and directory structure laid out. The reason for this documentation is so that new X protocols (and OpenGL) modules can be created.