summary refs log tree commit diff stats
diff options
context:
space:
mode:
authorhut <hut@lavabit.com>2010-06-09 10:17:39 +0200
committerhut <hut@lavabit.com>2010-06-09 10:17:39 +0200
commit1881922fba437a3f2ba8f1392ba27b78c382e82f (patch)
tree5c166c7b5fd55faff07987293d1f49b3467e3f5c
parent85fd52880db93c6cd01f2c459eb46e6dd35d777c (diff)
downloadranger-1881922fba437a3f2ba8f1392ba27b78c382e82f.tar.gz
HACKING: updated
-rw-r--r--HACKING16
1 files changed, 16 insertions, 0 deletions
diff --git a/HACKING b/HACKING
index b184150c..3d35190e 100644
--- a/HACKING
+++ b/HACKING
@@ -10,6 +10,7 @@ Coding Style
     http://www.python.org/dev/peps/pep-0008/
 * Although this guide suggests otherwise, tabs are used for indentation
     of code and docstrings.  In other documents (readme, etc), use spaces.
+* Test the code with unit tests where it makes sense
 
 
 Patches
@@ -23,6 +24,20 @@ If you plan to do major changes, or many changes over time, I encourage
 you to create a fork on GitHub, Gitorious or any other site.
 
 
+Starting Points
+---------------
+
+Good places to read about ranger internals are:
+ranger/core/actions.py
+ranger/core/environment.py
+ranger/fsobject/fsobject.py
+
+About the UI:
+ranger/gui/widgets/browsercolumn.py
+ranger/gui/widgets/browserview.py
+ranger/gui/defaultui.py
+
+
 Common Changes
 --------------
 
@@ -41,6 +56,7 @@ assuming <self> is a "SettingsAware" object.
 
 * Changing commands, adding aliases:
 ranger/defaults/commands.py
+or ~/.ranger/commands.py
 
 * Adding colorschemes:
 Copy ranger/colorschemes/default.py to ranger/colorschemes/myscheme.py