gryf/pentadactyl-pm
1
0
Fork 0
mirror of https://github.com/gryf/pentadactyl-pm.git synced 2026-01-01 09:02:26 +01:00
Code Issues Projects Releases Wiki Activity

Added lines to HACKING and vimp/TODO requesting testing/optimization info.

Browse Source
This commit is contained in:
Ted Pavlic
2009-01-04 22:02:26 -05:00
parent b644259f83
commit 166d60abd0
2 changed files with 9 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
HACKING
View File

@@ -30,3 +30,11 @@ We try to be quite consistent, but of course, that's not always possible.
Wrong: if (HACK) /* TODO: remove hack */
* Use UNIX new lines (\n), not windows (\r\n) or old Mac ones (\r)
== TESTING/OPTIMIZATION ==
TODO: Add some information here about testing/validation/etc.
Information about how/when to use :regressions might be nice.
Additionally, maybe there should be some benchmark information here --
something to let a developer know what's "too" slow...? Or general
guidelines about optimization?

1
vimperator/TODO
View File

@@ -96,5 +96,6 @@ FEATURES:
3 add a command-line window (:help cmdline-window in Vim).
3 Splitting Windows with [:sp :vsp ctrl-w,s ctrl-w,v] and closing with [ctrl-w,q], moving with [ctrl-w,w or tab]
have a look into the split browser extension
1 Add information to liberator/HACKING file about testing and optimization
- many other ideas are listed in the wiki