Pages
Programs
Techniques
- py-struct -- usable "struct"-like classes in Python
- key-deck -- convert a 128 bit secret key into an arrangement of a deck of playing cards
- py-dir -- pure python reimplementation of dir()
Future
Easy
- bubblesim
- budget
- nounweave?
- tagpending.py
- canonize-vote
- metaparse?
- foafrss
- nexusdigital sms script
- confluence/spreadsheet-kpi-thingy
- confluence-import-thingy
- pastel/hsoft-import-thingy
- my communicate() hack
- la trac bits
- blosxom2wp
- x500?
Multiple file tangle support
- britney-cell
- my hackfest mandelbrot
- jigdodl
Real projects
- ifupdown
- debootstrap?
- prediction-market
- pageant
Notes
Code is a sputnik instance. It can be browsed (cgi/wiki, including revisions) or built (tangle to make/tar) and have bugs tracked. The result should be code that looks attractive, that's easy to edit, and that's usable.
This is my junkcode instance, which is meant to hold a bunch of lightweight modules. Larger projects should have their own wikis.
How this works
- Setup a sputnik wiki (done!)
- Use python-markdown to go from "wiki" markup to pretty-printed display (done!)
- Have an action to extract code from a page (done!)
What's still needed
- Some way to have multiple files in a single page (code and data, tests, examples, formal verification, etc)
- Some way to dump code in directly without having to mark it up or enclose it in lua on disk
- Some way to have a project of multiple files/pages (maybe can setup a tgz action on a page with links to other pages that creates a tarball of those pages, properly renamed and versioned?)
- Some way to do literate-programming-style tangling, for code that's rearranged into readable order, rather than the way the programming language wants it (cf pascal). This may not be worthwhile though...
What would be awesome
- bug tracking, somehow? should be orthogonal from the revision history of the code, which maybe means it might as well be entirely separate...