Software

This is just a collection of some (useful?) software I have written and feel like sharing.

• HTTP Proxy Tunnel

  This is a proxy that I use to tunnel email access through an HTTP proxy (although it could proxy anything). I wrote it when an employer of mine decided that internet access means only port 80 through a proxy. As I don't have an external host where I could run the other end of an ssh tunnel, I went looking for http proxy solutions. There were several out there, but they didn't seem to work well for POP3. Rather than investigating exactly why those didn't work, I decided to write my own. Mine also proxies several hosts in a single process.
  The jar contains the source, and a README. I even have a plist to turn this into a Launch Agent on a Mac (so it starts up when you login).

• HTTP Proxy Tunnel 2

  This is the same as the above (except the config properties are slightly different). This version is written using Apache MINA (1.1.7). It performs exactly the same function as the above (java.io) version, but with many fewer threads. I also exposed the configuration via JMX MBeans, so you can browse (and update some things) via, for example, jconsole. I mainly updated it so as to learn MINA and get up to date on JMX.
  

• Perforce Scripts

  This zip contains a collection of (Ruby) scripts I use to simplify and automate some tasks with Perforce SCM. It contains the following:

  • p4pending - list of open files organized by changelist
  • p4changes - list open changelists and descriptions
  • p4cleanchanges - delete any empty pending changelists
  • p4default2change - move all open files to a given changelist
  • p4revertchange - revert all files in a given changelist (and delete the changelist)
  • p4sync - wrapper around p4 sync. Syncs immediate child directories separately (can reduce server load for large syncs). Also collects errors (i.e. can't clobber, etc) and prints them at the end where you can see them.
  • p4not - Find files that are out of sync with p4 (not in depot or in changelist, etc).

  There is also a perforce.rb containing a P4 class, which the above scripts all use to interact with Perforce.

• Script Growl View

  This is a Growl view to run a script, then forward on to another view.
  I no longer use this, but used to use it in conjunction with Hardware Growler to reset some things (printers, etc) when I switched between networks. If I still had to do that sort of thing, I'd probably look into Marco Polo.

• WLP on Rails

  This is a rails plugin that does the same thing as WebLogic Portal's <render:portalFacet .../> JSP tag. It allows you to embed a WLP portlet in a Rails template like this: <%= render :portlet=>'my.portlet' %>. The plugin also includes a controller to reverse-proxy requests to/from WLP.
  Download wlp_on_rails.zip and explode it into your vendor/plugins directory. Then run vendor/plugins/wlp_on_rails/install.rb and edit the config/weblogic_portal.yml file that it creates.
  This is still kind of experimental - I have not worked out all the kinks in the reverse proxy (cookies and other header trash).
  Update - it's actually worse than that :) I rewrote this after posting this version, and got many of the kinks worked out, but neglected to post that version. Interest (from the work side) wained, and all was lost. Sigh.

• ClickIR

  This is a little utility to allow you to control applications (via AppleScipt) using the IR Remote that is normally used for FrontRow.
  Get it here.

• SimpleP4 Plugin for Eclipse

  This is a simple Perforce plugin for Eclipse. I wrote it because with many large projects, and a huge p4 depot, the usual Team-based plugins get pretty well bogged down in all the p4 network traffic. This one:

  • doesn't do Team
  • doesn't support move/refactor/delete/etc
  • doesn't do file icon decoration
  • doesn't lock up your gui thread fstat'ing the p4 server to death
  • Does add a right-click popup menu to Navigator, Package Explorer, and your edit buffer views to let you do simple p4 commands like edit, diff, sync, revert, etc
  • Does show filelog history and fstat status in the file's properties dialog
  • and it has a console where useful logs go
  Simply drop the jar into your plugins directory.