Development

Line 1:

+

這個頁面也要重新編輯哦～努力工作哦～

−

This page is the portal of sawfish developments.

+

叔叔看好你喲～

−

== Want to join? ==

−

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

−

* Read {{ML}}, or its archive. That's our main communication method.

−

* Use [[Download#GIT|git]] repository. Summary may be tracked via [http://git.gnome.org/cgit/sawfish/tree/ChangeLog Changelog] or [http://git.tuxfamily.org/sawfish/main.git?p=gitroot/sawfish/main.git;a=blob;f=man/news.texi;h=774c50577bddf5e3f1896114ec99e697dadbd985;hb=HEAD news.texi].

−

If you find an interesting item in [[Proposed Goals]], then declare it in the {{ML}}, and send us a patch. (Unless it's marked as assigned to someone, it's likely that none is working on that item. We're short of developers. Items in [[Long term todos]] are left untouched.)

−

== Todos ==

−

* [[Proposed Goals]] - todos for the coming release.

−

* [[Long term todos]]

+

無爲留筆

−

* [[:Category:Past todos|Past todos]] is a partial list of what is accomplished.

−

* [[Versioning scheme]]

−

=== If possible ===

−

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

+

2011.06.27

−

* [[Enhancements suggestion in sawfish core]]

−

==== 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:

−

*[[Future_Extensions]]

−

*[[Composite]]

−

*[[OpenGL]]

−

== Known difficulty ==

−

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

−

== Bug reports ==

−

* '''List of open bugs''' on bugzilla.gnome.org, of

−

** [http://bugzilla.gnome.org/buglist.cgi?product=sawfish&bug_status=__open__&order=Bug+Number sawfish]

−

** [http://bugzilla.gnome.org/buglist.cgi?product=librep&bug_status=__open__&order=Bug+Number librep]

−

** [http://bugzilla.gnome.org/buglist.cgi?product=rep-gtk&bug_status=__open__&order=Bug+Number rep-gtk]

−

* [http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=sawfish Debian bug reports]

−

* [https://bugs.launchpad.net/ubuntu/+source/sawfish Ubuntu bug reports]

−

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:

−

<pre>https://bugzilla.gnome.org/buglist.cgi?bug_status=__open__&order=Bug+Number&product=Sawfish&content=%s</pre>

−

If you want to '''receive notices''' of new bug reports, then

−

# Make bugzilla account.

−

# Log in, and go to 'Email preferences'

−

# Go to 'User Watching' section, in 'Add users to my watch list', add 'librep-maint@gnome.bugs, rep-gtk-maint@gnome.bugs, sawfish-maint@gnome.bugs'.

−

== Librep & rep-gtk ==

−

*[[librep]]

−

*[[Rep-GTK]]

−

=== 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.

−

Current Docs:

−

* [[Librep_Internals]]

−

== Window manager specs ==

−

* [[Window Manager Standards]]

−

Small window managers can be taken as tutorials for how to implement window managers. Examples are:

−

* [http://incise.org/tinywm.html tinywm] - this is the minimal. start here.

−

* [http://freshmeat.net/projects/failsafewm/ failsafewm] - then read this.

−

== Move to other hosts? ==

−

Update Jun 2011: We're almost done moving to Tuxfamily.

−

Migration to other development hosts were discussed several times. The latest one is [http://old.nabble.com/The-get-rid-of-gnome.org-sf.net-thing-%28chapter-3%29-to27227913.html here].

−

== See also ==

−

* [[Tips]]

[[Category:Development]]

Changes: Development

Revision as of 02:14, 27 June 2011

@@ Line 1: / Line 1: @@
+這個頁面也要重新編輯哦～ 努力工作哦～
-{{Development}}
-This page is the portal of sawfish developments.
+叔叔看好你喲～
-== Want to join? ==
-It's hard to tell the current status in short.
-* Read {{ML}}, or its archive. That's our main communication method.
-* Use [[Download#GIT|git]] repository. Summary may be tracked via [http://git.gnome.org/cgit/sawfish/tree/ChangeLog Changelog] or [http://git.tuxfamily.org/sawfish/main.git?p=gitroot/sawfish/main.git;a=blob;f=man/news.texi;h=774c50577bddf5e3f1896114ec99e697dadbd985;hb=HEAD news.texi].
-If you find an interesting item in [[Proposed Goals]], then declare it in the {{ML}}, and send us a patch. (Unless it's marked as assigned to someone, it's likely that none is working on that item. We're short of developers. Items in [[Long term todos]] are left untouched.)
-== Todos ==
-* [[Proposed Goals]] - todos for the coming release.
-* [[Long term todos]]
+無爲 留筆
-* [[:Category:Past todos|Past todos]] is a partial list of what is accomplished.
-* [[Versioning scheme]]
-=== If possible ===
-(Dec 2008) No one seems to be working on the items listed under this category.
+.06.27
-* [[Enhancements suggestion in sawfish core]]
-==== 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:
-*[[Future_Extensions]]
-*[[Composite]]
-*[[OpenGL]]
-== Known difficulty ==
-Some know difficulty in development can be found at [[Patches (suspended)]].
-== Bug reports ==
-* '''List of open bugs''' on bugzilla.gnome.org, of
-** [http://bugzilla.gnome.org/buglist.cgi?product=sawfish&bug_status=__open__&order=Bug+Number sawfish]
-** [http://bugzilla.gnome.org/buglist.cgi?product=librep&bug_status=__open__&order=Bug+Number librep]
-** [http://bugzilla.gnome.org/buglist.cgi?product=rep-gtk&bug_status=__open__&order=Bug+Number rep-gtk]
-* [http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=sawfish Debian bug reports]
-* [https://bugs.launchpad.net/ubuntu/+source/sawfish Ubuntu bug reports]
-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:
-<pre>https://bugzilla.gnome.org/buglist.cgi?bug_status=__open__&order=Bug+Number&product=Sawfish&content=%s</pre>
-If you want to '''receive notices''' of new bug reports, then
-# Make bugzilla account.
-# Log in, and go to 'Email preferences'
-# Go to 'User Watching' section, in 'Add users to my watch list', add 'librep-maint@gnome.bugs, rep-gtk-maint@gnome.bugs, sawfish-maint@gnome.bugs'.
-== Librep & rep-gtk ==
-*[[librep]]
-*[[Rep-GTK]]
-=== 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.
-Current Docs:
-* [[Librep_Internals]]
-== Window manager specs ==
-* [[Window Manager Standards]]
-Small window managers can be taken as tutorials for how to implement window managers. Examples are:
-* [http://incise.org/tinywm.html tinywm] - this is the minimal. start here.
-* [http://freshmeat.net/projects/failsafewm/ failsafewm] - then read this.
-== Move to other hosts? ==
-Update Jun 2011: We're almost done moving to Tuxfamily.
-Migration to other development hosts were discussed several times. The latest one is [http://old.nabble.com/The-get-rid-of-gnome.org-sf.net-thing-%28chapter-3%29-to27227913.html here].
-== See also ==
-* [[Tips]]
 [[Category:Development]]