Sawfish
Register
(Undo my last edit. I don't think the cited argument is valid.)
 
(29 intermediate revisions by 3 users not shown)
Line 1: Line 1:
[[Category:Release todos]]{{Release todos}}
+
{{Release todos}}
 
This page lists todos which is of lower priority. Maybe wish items in bugzilla(s) should be collected here.
== Unsolved issues in the mailing list ==
 
  +
after sawfish-1.3.4
 
  +
See also
* [http://mail.gnome.org/archives/sawfish-list/2008-September/msg00067.html a doc patch] ([[User:Teika kazura]] Will take care)
 
  +
* [[Proposed Goals]] for the next coming release
* [http://mail.gnome.org/archives/sawfish-list/2008-September/msg00060.html autogen.sh fails on RHEL 5.2]
 
  +
* [[Development]] for even longer items, like xcb, OpenGL, etc.
* [http://mail.gnome.org/archives/sawfish-list/2008-October/msg00018.html themes Makefile from sawfish-1.3.4 has installation issues]
 
  +
* [http://mail.gnome.org/archives/sawfish-list/2008-October/msg00019.html Sawfish-1.3.4 and vanishing themes]
 
 
== Documentation ==
 
== Documentation ==
  +
(This item needs cleanup.)
* In general, the document needs improvements:
 
  +
  +
* In general, the document needs improvements. See [http://mail.gnome.org/archives/sawfish-list/2009-February/msg00083.html this post] for detailed account. (The gap between 1.3.0 and 1.5.0 pointed out there is already filled.)
 
** needs update.
 
** needs update.
 
** both in volume and in order.
 
** both in volume and in order.
 
** both for users and developers.
 
** both for users and developers.
 
** the online and the distributed. (may be better to be united to one?)
 
** the online and the distributed. (may be better to be united to one?)
  +
** In which module the functions / variables lie.
* [[Developer tips]] will help a lot. Perhaps 'Developer guideline' is desirable.
 
  +
* How sawfish is initialized.
** How to search for functions and variables? (Needs description for ''ack''. Emacs tags?)
 
  +
** How sawfish uses librep.
*** Maybe unification to 'define' will help?
 
** How to test patches gracefully.
+
* How to test patches gracefully.
* What exactly is 'deprecated' feature? No doc at all now.
 
 
* Terminology; clarification, replacement to better ones, description.
 
* Terminology; clarification, replacement to better ones, description.
 
* At least, complete GUI doc.
 
* At least, complete GUI doc.
  +
* Sawfish event system: To aid in development and understanding, there needs to be documentation the X event model and how Sawfish interacts and deals with it.
* Librep intro, at least [http://mail.gnome.org/archives/sawfish-list/2008-September/msg00023.html Sep 2008 thread in the ML]
 
  +
* Crawl thru the web, find articles on sawfish, and compile them.
 
* Better to have heavy comments in the source.
  +
  +
=== Print command doc in window operation menu ===
  +
  +
In the window operation menu, print the command description in tooltip.
   
 
=== info ===
 
=== info ===
* How to merge sawfish and librep info, seamlessly if possible.(but keeping sawfish and librep distinct package)
 
 
* Maybe keep only core lisp part in info, and others written in HTML.
 
* Maybe keep only core lisp part in info, and others written in HTML.
== coding ==
 
* Better to have heavy comments in the source.
 
   
== Wish list==
+
== Themes ==
  +
Much is desired. First investigation & questionnaire is necessary.
Maybe wish items in bugzilla(s) should be collected here...
 
  +
  +
Change themes-engine so that tabs are supported by default.
  +
  +
== Scripts ==
  +
  +
=== Merge good scripts into the trunk ===
  +
Merge good [[scripts]] into the trunk.
  +
  +
In adoption, notice following points:
  +
* Name (of feature, function, variable ...) is good?
  +
* It should work & merge smoothly with already existing design and codes.
  +
* User contributed codes are often slack. Make loose ends meet.
  +
  +
=== Review user contributed scripts ===
  +
  +
The title says all.
  +
  +
== Configurator ==
  +
  +
=== Search box ===
  +
A search box which allows to quickly find an option that has string in its description or name.
  +
  +
=== Keybinding ===
  +
  +
All commands are listed, which is clumsy to search. Ideas are:
  +
  +
* Organization by categories, maybe using a treeview.
  +
* Commands name search by key types.
  +
  +
If it's possible to optionally hide keymaps which are not supported by the current theme, it's good.
  +
  +
=== Edit history ===
  +
A list of recently modified variables in the UI. This would make it simpler to find, like this: "I just changed one option, but I don't remember where it was?".
  +
  +
=== Window Rules ===
  +
  +
"Grab all". It sets all properties of grabbed window, and what user do
  +
is to uncheck what they don't want.
  +
  +
Grabbing window size and position.
  +
  +
=== Configurator and process ===
  +
  +
* If you restart Sawfish with the configurator open, the configurator instance becomes useless.
  +
  +
== Tiling feature ==
  +
Implement tiling feature. Steal from [http://www.nongnu.org/stumpwm/ StumpWM], common lisp fork of [http://www.nongnu.org/ratpoison/ ratpoison]?
  +
  +
== Gtk dialogbox ==
  +
  +
It's possible to have a dialogbox made of Gtk. This will add many new features to Sawfish. See [http://old.nabble.com/gtk-dialog-box-td27283612.html here] for more.
  +
 
== Icon ==
  +
*Sawfish returns only one icon for each application, but often several are available. Support them.
  +
*Allow override of icons displayed in window cycling. Read [http://old.nabble.com/Icons-in-the-wininfo-when-cycling-p26964993.html this patch] and [http://old.nabble.com/Re%3A-Icons-in-the-wininfo-when-cycling-p27415541.html this reply].
  +
  +
== Startup ==
  +
  +
=== Failure in loading application menu ===
  +
This is fixed in Sawfish-1.6.3:
  +
  +
Sawfish used to fail with a file error if any link in /usr/share/applications is not valid.
  +
  +
=== Add --replace option ===
  +
(This will be added in 1.8.0)
  +
  +
Add --replace option to sawfish, for replacing the current window-manager.
  +
  +
== Focus ==
  +
=== Focus revert in enter-exit mode ===
  +
When the focused window disappears, Sawfish emits 'focus-revert'.
  +
Refinements of the behavior to handle it by 'enter-exit' focus mode
  +
is desired. See [http://old.nabble.com/Broken-enter-exit-focus-behavior-in-1.5.3-to26568449.html#a26601751 this thread].
  +
  +
== Workspace ==
  +
=== Grouping Workspace ===
  +
Group workspace. Some people like tree-like structure.
  +
  +
=== Partial workspace layer ===
  +
(This is not exactly a workspace feature, but let's put it here.)
  +
  +
Some users want something like 'partial workspace layer'. It can be
  +
smaller then the workspace. Windows can be confined inside of it.
  +
  +
Layers can make groups of the same size, for example of a head size. User can interchange a layer with another in the same group, so it looks like as if workspace were changed only in that area.
  +
  +
[[Sticky-head]] script tries to switch workspace per head.
  +
  +
Workspace is the notion defined in ewmh as 'virtual desktop'. So layer
  +
is a new, different thing, not the extension to workspace.
  +
  +
=== 3D style like Compiz ===
  +
Stack workspaces in "3D", with OpenGL/compiz. Zooming out to see
  +
whole workspace on a single screen, with all the viewports being much
  +
smaller, and windows being smaller, everything squeezed on a single
  +
screen.
  +
  +
== Menu ==
  +
In the window-list, a right-click to pop-up a window operation menu.
  +
  +
See also [[#Print command doc in window operation menu]].
  +
[[Category:Release todos]]
  +
[[Category:Development]]

Latest revision as of 04:22, 1 October 2011

Release todos quick access

This page lists todos which is of lower priority. Maybe wish items in bugzilla(s) should be collected here.

See also

Documentation[]

(This item needs cleanup.)

  • In general, the document needs improvements. See this post for detailed account. (The gap between 1.3.0 and 1.5.0 pointed out there is already filled.)
    • needs update.
    • both in volume and in order.
    • both for users and developers.
    • the online and the distributed. (may be better to be united to one?)
    • In which module the functions / variables lie.
  • How sawfish is initialized.
    • How sawfish uses librep.
  • How to test patches gracefully.
  • Terminology; clarification, replacement to better ones, description.
  • At least, complete GUI doc.
  • Sawfish event system: To aid in development and understanding, there needs to be documentation the X event model and how Sawfish interacts and deals with it.
  • Crawl thru the web, find articles on sawfish, and compile them.
  • Better to have heavy comments in the source.

Print command doc in window operation menu[]

In the window operation menu, print the command description in tooltip.

info[]

  • Maybe keep only core lisp part in info, and others written in HTML.

Themes[]

Much is desired. First investigation & questionnaire is necessary.

Change themes-engine so that tabs are supported by default.

Scripts[]

Merge good scripts into the trunk[]

Merge good scripts into the trunk.

In adoption, notice following points:

  • Name (of feature, function, variable ...) is good?
  • It should work & merge smoothly with already existing design and codes.
  • User contributed codes are often slack. Make loose ends meet.

Review user contributed scripts[]

The title says all.

Configurator[]

Search box[]

A search box which allows to quickly find an option that has string in its description or name.

Keybinding[]

All commands are listed, which is clumsy to search. Ideas are:

  • Organization by categories, maybe using a treeview.
  • Commands name search by key types.

If it's possible to optionally hide keymaps which are not supported by the current theme, it's good.

Edit history[]

A list of recently modified variables in the UI. This would make it simpler to find, like this: "I just changed one option, but I don't remember where it was?".

Window Rules[]

"Grab all". It sets all properties of grabbed window, and what user do is to uncheck what they don't want.

Grabbing window size and position.

Configurator and process[]

  • If you restart Sawfish with the configurator open, the configurator instance becomes useless.

Tiling feature[]

Implement tiling feature. Steal from StumpWM, common lisp fork of ratpoison?

Gtk dialogbox[]

It's possible to have a dialogbox made of Gtk. This will add many new features to Sawfish. See here for more.

Icon[]

  • Sawfish returns only one icon for each application, but often several are available. Support them.
  • Allow override of icons displayed in window cycling. Read this patch and this reply.

Startup[]

Failure in loading application menu[]

This is fixed in Sawfish-1.6.3:

Sawfish used to fail with a file error if any link in /usr/share/applications is not valid.

Add --replace option[]

(This will be added in 1.8.0)

Add --replace option to sawfish, for replacing the current window-manager.

Focus[]

Focus revert in enter-exit mode[]

When the focused window disappears, Sawfish emits 'focus-revert'. Refinements of the behavior to handle it by 'enter-exit' focus mode is desired. See this thread.

Workspace[]

Grouping Workspace[]

Group workspace. Some people like tree-like structure.

Partial workspace layer[]

(This is not exactly a workspace feature, but let's put it here.)

Some users want something like 'partial workspace layer'. It can be smaller then the workspace. Windows can be confined inside of it.

Layers can make groups of the same size, for example of a head size. User can interchange a layer with another in the same group, so it looks like as if workspace were changed only in that area.

Sticky-head script tries to switch workspace per head.

Workspace is the notion defined in ewmh as 'virtual desktop'. So layer is a new, different thing, not the extension to workspace.

3D style like Compiz[]

Stack workspaces in "3D", with OpenGL/compiz. Zooming out to see whole workspace on a single screen, with all the viewports being much smaller, and windows being smaller, everything squeezed on a single screen.

Menu[]

In the window-list, a right-click to pop-up a window operation menu.

See also #Print command doc in window operation menu.