From 1881922fba437a3f2ba8f1392ba27b78c382e82f Mon Sep 17 00:00:00 2001 From: hut Date: Wed, 9 Jun 2010 10:17:39 +0200 Subject: HACKING: updated --- HACKING | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) 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 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 -- cgit 1.4.1-2-gfad0