TODO


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

welcome to the TODO file.

== short-range TODO ==

better handling of more exotic patch systems

  for example:
  - handling cpp processing of dpatch files
  - handling wierd configuration for simple-patchsys and recusrive dirs
  - handling when the directory looks like dpatch/quilt but isn't

code cleanup from really ugly stuff (look for XXX)

dead code removal/cleanup

  after switching a few design decisions, there's some code that's no longer
  used or should be removed

== medium-range TODO ==

review db design

  the db schema design is most likely less than optimal, the use of triggers
  to emulate foreign keys is novel but likely we can remove a few columns and
  use rowids instead, and possibly lower/optimise the remaining queries.

remove all the os.system calls

  lots of temporary ducttape via os.system that should go away

make prettier pages

  they're all xhtml compliant, using css, and based on a single skeleton
  page so it shouldn't be too much work

decide how much should be cgi-based and how much should be written

  there's no reason why the entire system can't be generated via cgi-based
  accessing, but the question is whether it should be, or whether certain
  componenets should remain static.

== long-range TODO ==

dynamic info?
external data sources?