]> git.madduck.net Git - etc/awesome.git/blob - README.rst.orig

madduck's git repository

Every one of the projects in this repository is available at the canonical URL git://git.madduck.net/madduck/pub/<projectpath> — see each project's metadata for the exact URL.

All patches and comments are welcome. Please squash your changes to logical commits before using git-format-patch and git-send-email to patches@git.madduck.net. If you'd read over the Git project's submission guidelines and adhered to them, I'd be especially grateful.

SSH access, as well as push access can be individually arranged.

If you use my repositories frequently, consider adding the following snippet to ~/.gitconfig and using the third clone URL listed for each project:

[url "git://git.madduck.net/madduck/"]
  insteadOf = madduck:

Merge branch 'master' of https://github.com/copycat-killer/lain
[etc/awesome.git] / README.rst.orig
1 Lain
2 ====
3
4 --------------------------------------------------
5 Layouts, widgets and utilities for Awesome WM 3.5+
6 --------------------------------------------------
7
8 :Author: Luke Bonham <dada [at] archlinux [dot] info>
9 :Version: git
10 <<<<<<< HEAD
11 :License: GNU-GPLv2_
12 =======
13 :License: GNU-GPL2_
14 >>>>>>> upstream/master
15 :Source: https://github.com/copycat-killer/lain
16
17 Description
18 -----------
19
20 Successor of awesome-vain_, this module provides new layouts, a set of widgets and utility functions, in order to improve Awesome_ usability and configurability.
21
22 Read the wiki_ for all the info.
23
24 Contributions
25 -------------
26
27 Any contribution is welcome! Feel free to make a pull request.
28
29 Just make sure that:
30
31 - Your code fits with the general style of the module. In particular, you should use the same indentation pattern that the code uses, and also avoid adding space at the ends of lines.
32
33 - Your code its easy to understand, maintainable, and modularized. You should also avoid code duplication wherever possible by adding functions or using ``lain.helpers``. If something is unclear, and you can't write it in such a way that it will be clear, explain it with a comment.
34
35 - You test your changes before submitting to make sure that not only your code works, but did not break other parts of the module too!
36
37 - You eventually update ``wiki`` submodule with a thorough section.
38
39 Contributed widgets have to be put in ``lain/widgets/contrib``.
40
41 Screenshots
42 -----------
43
44 .. image:: http://i.imgur.com/8D9A7lW.png
45 .. image:: http://i.imgur.com/9Iv3OR3.png
46 .. image:: http://i.imgur.com/STCPcaJ.png
47
48 <<<<<<< HEAD
49 .. _GNU-GPLv2: http://www.gnu.org/licenses/gpl-2.0.html
50 =======
51 .. _GNU-GPL2: http://www.gnu.org/licenses/gpl-2.0.html
52 >>>>>>> upstream/master
53 .. _awesome-vain: https://github.com/vain/awesome-vain
54 .. _Awesome: http://awesome.naquadah.org/
55 .. _wiki: https://github.com/copycat-killer/lain/wiki