Difference between revisions of "Wingo"

From ArchWiki
Jump to: navigation, search
(first cut)
 
(Add stub tag.)
(2 intermediate revisions by one other user not shown)
Line 1: Line 1:
 
[[Category:Stacking WMs]]
 
[[Category:Stacking WMs]]
 
[[Category:Tiling WMs]]
 
[[Category:Tiling WMs]]
 
+
[[Category:Dynamic WMs]]
 +
{{Stub}}
 
Wingo is a fully featured true hybrid window manager that supports per-monitor workspaces, and neither the floating or tiling modes are after thoughts. This allows one to have tiling on one workspace while floating on the other. Wingo can be scripted with its own command language, is completely themeable, and supports user defined hooks. Wingo is written in Go and has no runtime dependencies.
 
Wingo is a fully featured true hybrid window manager that supports per-monitor workspaces, and neither the floating or tiling modes are after thoughts. This allows one to have tiling on one workspace while floating on the other. Wingo can be scripted with its own command language, is completely themeable, and supports user defined hooks. Wingo is written in Go and has no runtime dependencies.
  

Revision as of 08:46, 27 October 2012

Tango-document-new.pngThis article is a stub.Tango-document-new.png

Notes: please use the first argument of the template to provide more detailed indications. (Discuss in Talk:Wingo#)

Wingo is a fully featured true hybrid window manager that supports per-monitor workspaces, and neither the floating or tiling modes are after thoughts. This allows one to have tiling on one workspace while floating on the other. Wingo can be scripted with its own command language, is completely themeable, and supports user defined hooks. Wingo is written in Go and has no runtime dependencies.

See also