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(+) (limited to 'HACKING') 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 ='/akkartik/mu/?h=hlt'>summary refs log blame commit diff stats
path: root/html/026assert.cc.html
blob: 685cf2e4b6ae5709a719ece05ba9773b31adc982 (plain) (tree) 
672e3e50 ^




f6b44306 ^

672e3e50 ^







e8b1d3ff ^


dbe12410 ^

4bbd3ded ^

672e3e50 ^

dbe12410 ^


672e3e50 ^

d44123ca ^

672e3e50 ^












4bbd3ded ^

672e3e50 ^











c5ffb6e1 ^


65361948 ^

dbe12410 ^

65361948 ^


672e3e50 ^






1
2
3
4

5

6
7
8
9
10
11
12

13
14

15

16

17

18
19

20

21

22
23
24
25
26
27
28
29
30
31
32
33

34

35
36
37
38
39
40
41
42
43
44
45

46
47

48

49

50
51

52
53
54
55
56
57