-I broke down today and looked into [Gentoo
-overlays](http://www.gentoo.org/proj/en/overlays/userguide.xml) and
-[layman](http://layman.sourceforge.net/). It seems much simpler now
-than it did when I last looked at it a year or so ago. I guess I'm
-just more familiar with how portage works...
+[[!template id=gitrepo repo=wtk-overlay]]
-Anyhow, I've posted my [personal
-overlay](http://www.physics.drexel.edu/~wking/code/git/git.php?p=wtk-overlay.git)
-and [layman XML describing
-it](http://www.physics.drexel.edu/~wking/code/layman.xml). It
-currently a fairly strange mix:
+I broke down today and looked into [Gentoo overlays][] and [layman][].
+It seems much simpler now than it did when I last looked at it a year
+or so ago. I guess I'm just more familiar with how portage works...
+
+Anyhow, I've posted my personal overlay and [[layman XML|layman.xml]]
+describing it. It currently a fairly strange mix:
- app-misc/lifelines
[Gentoo 42103](http://bugs.gentoo.org/42103)
- media-sound/abcmidi
[Gentoo 76017](http://bugs.gentoo.org/76017)
+[Gentoo overlays]: http://www.gentoo.org/proj/en/overlays/userguide.xml
+[layman]: http://layman.sourceforge.net/
+
[[!tag tags/linux]]
--- /dev/null
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE repositories SYSTEM "/dtd/repositories.dtd">
+<repositories version="1.0">
+ <repo quality="experimental" status="unofficial">
+ <name>wtk</name>
+ <description>W. Trevor King's Overlay</description>
+ <homepage>
+ http://www.physics.drexel.edu/~wking/code/git/git.php?wtk-overlay.git
+ </homepage>
+ <owner>
+ <email>wking@drexel.edu</email>
+ </owner>
+ <source type="git">
+ http://www.physics.drexel.edu/~wking/code/git/wtk-overlay.git
+ </source>
+ </repo>
+</repositories>
bit tricky to get things *just right*, but once you figure it out,
it's easy to reuse the code.
+[[!template id=gitrepo repo=thesis]]
+
Take a look at [my packages][code], the [Drexel Liki page][liki], the
source for most of my [papers][] (if you scroll to the bottom of a
-paper's HTML, there is a `source files` link), and my [thesis][] (in
+paper's HTML, there is a `source files` link), and my thesis (in
progress).
If you're interested in LaTeX and graphics, you'll probably be
[code]: http://www.physics.drexel.edu/~wking/code/#latex
[liki]: http://www.physics.drexel.edu/liki/index.php/Latex
[papers]: http://www.physics.drexel.edu/~wking/rsrch/papers
-[thesis]: http://www.physics.drexel.edu/~wking/code/git/git.php?p=thesis.git
[[!tag tags/latex]]
[[!tag tags/programming]]
[[!meta title="SiteCorePy"]]
[[!meta date="2010-06-24 19:52:08"]]
+[[!template id=gitrepo repo=sitecorepy]]
+
As the Physics webmaster, I'm in charge of transitioning most of the
static department content into SiteCore, as the powers that be get
wise to the ways of version control. Unfortunately, I'm not the
something that the designers hadn't planned for, like, oh, importing
data from a preexisting database.
-Anyhow, to overcome the major limitation, I'm [driving my browser
-through a
-script](http://www.physics.drexel.edu/~wking/code/git/git.php?p=sitecorepy.git).
-Thanks to the magic of
+Anyhow, to overcome the major limitation, I'm driving my browser
+through a script. Thanks to the magic of
[WebDriver/Selenium](http://code.google.com/p/selenium/wiki/GettingStarted)
for making this possible.
+[[!template id=gitrepo repo=call_graph]]
+
This script scans a Python file for function dependencies, and
generates code for [Graphviz dot][graphviz]. See [[depgraph]] for
scripts to generate dependency graphs *between* modules.
is good for giving you the "short view" for restructuring a single
module.
+[[!template id=gitrepo repo=calibrate_cantilever]]
+
As example, here is the callgraph of my cantilever calibration program
-[calibrate_cantilever.py][].
+`calibrate_cantilever.py`.
$ python construct_call_graph.py -i calibrate_cantilever.py | dot -T png -o call_graph.png
[graphviz]: http://www.graphviz.org
[original]: http://blog.prashanthellina.com/2007/11/14/generating-call-graphs-for-understanding-and-refactoring-python-code/
-[calibrate_cantilever.py]: http://www.physics.drexel.edu/~wking/code/git/git.php?p=calibrate_cantilever.git
-[call_graph]: http://www.physics.drexel.edu/~wking/code/git/git.php?p=call_graph.git
[[!tag tags/programming]]
[[!tag tags/python]]
+[[!template id=gitrepo repo=depgraph]]
+
This set of scripts scans a Python file for module dependencies, and
generates code for [Graphviz dot][graphviz]. See [[call_graph]] for a
script that generates dependency graphs *within* a module.
Originally by Toby Dickenson, the scripts are good for giving you the
-"long view" on how your project is organized. I've [altered][] the
+"long view" on how your project is organized. I've altered the
[originals][] a bit.
My `py2depgraph` also prints out path information for each module, so
to detect and configure the shared C libraries extending Python, so
you know where to look for the code your Python depends on.
-As example, here is the depgraph of my protein unfolding program [unfold.py][]
+[[!template id=gitrepo repo=unfold_protein]]
+
+As example, here is the depgraph of my protein unfolding program `unfold.py`
$ python py2depgraph.py unfold.py | python depgraph2dot.py | dot -T png -o depgraph.png
title="unfold.py dependency graph"]]
[graphviz]: http://www.graphviz.org
-[altered]: http://www.physics.drexel.edu/~wking/code/git/git.php?p=depgraph.git
[originals]: http://tarind.com/depgraph.html
-[unfold.py]: http://www.physics.drexel.edu/~wking/code/git/git.php?p=unfold_protein.git
[[!tag tags/programming]]
[[!tag tags/python]]
+[[!template id=gitrepo repo=dotfiles]]
+
Keep all those pesky config files in one place. Inspired by (and
sharing much code with) [Steve Kemp's implementation][SK] (Steve's
[blog post][] gives a bit of historical background).
-[dotfiles project code][code]
-
[SK]: http://repository.steve.org.uk/cgi-bin/hgwebdir.cgi/dotfiles/file/tip?file/tip/
[blog post]: http://blog.steve.org.uk/didn_t_i_kill_you_already_.html
-[code]: http://www.physics.drexel.edu/~wking/code/git/git.php?p=dotfiles.git
[[!tag tags/linux]]
[[!tag tags/code]]
[[!meta title="git-php"]]
[[!meta date="2010-05-02 21:42:34"]]
-[Peeter Vois's](http://people.proekspert.ee/peeter/)
-[git-php](http://people.proekspert.ee/peeter/git/git.php?p=git-php.git)
-is a nice PHP script which you can drop in to make your public Git
-repo's browsable. [Take a
-look](http://www.physics.drexel.edu/~wking/code/git/)!
+[[!template id=gitrepo repo=git-php]]
+
+[Peeter Vois's][PV] [git-php][] is a nice PHP script which you can
+drop in to make your public [[Git]] repo's browsable. [Take a
+look][look]!
+
+[PV]: http://people.proekspert.ee/peeter/
+[git-php]: http://people.proekspert.ee/peeter/git/git.php?p=git-php.git
+[look]: http://www.physics.drexel.edu/~wking/code/git/git.php
+[[!template id=gitrepo repo=ikiwiki]]
+
While writing the [[yacc2dot]] page I ran across some difficulties
inlining raw files (i.e. those whose type/extension ikiwiki doesn't
know about). Fixed with the following changes:
* New `raw.tmpl` to minimally format the raw contents (formatting
still needs work).
-Changes made in my [branch][] of the IkiWiki Git repository.
-
-[branch]: http://www.physics.drexel.edu./~wking/code/git/git.php?p=ikiwiki.git
+Changes made in my branch of the IkiWiki Git repository.
+[[!template id=gitrepo repo=ikiwiki]]
+
In my [[last post|MathML]] I plugged Jason Blevins' [mdwn_itex
plugin][plugin]. It turns out that it was harder than I'd expected to
get the plugin working with ikiwiki, so I'm recording the steps I took
markup.
Update: current versions of my patched files can be found in my
-[ikiwiki git branch][git].
+ikiwiki git branch.
[plugin]: http://jblevins.org/git/ikiwiki/plugins.git/plain/mdwn_itex.pm
[itex2MML]: http://golem.ph.utexas.edu/~distler/blog/itex2MML.html
[scrubber_strip]: http://ikiwiki.info/todo/svg/
[tidy_strip]: http://lists.w3.org/Archives/Public/html-tidy/2006JanMar/0052.html
[itex]: http://golem.ph.utexas.edu/~distler/blog/itex2MMLcommands.html
-[git]: http://www.physics.drexel.edu/~wking/code/git/git.php?p=ikiwiki.git
[[!tag tags/blogging]]