a quick example demonstrating how to get data from the system using AppleScript within Java:

import javax.script.*;

class Test {
  public static void main(String[] args) throws Throwable {
    // before running, select a contact with an image in Address Book.app
    String script = "tell application \"Address Book\"\n"
                  + "   set contacts to selection\n"
                  + "   set contact to item 1 of contacts\n"
                  + "   set photothing to image of contact\n"
                  + "end tell";

    ScriptEngineManager mgr = new ScriptEngineManager();
    ScriptEngine engine = mgr.getEngineByName("AppleScript");
    Object retval = engine.eval(script);

    // prints: java.awt.image.BufferedImage
    System.out.println(retval.getClass().getName());
  }
}

while the shipping product was largely written by Mike Swingler, this was my intern project in 2007.


after buying a typewriter for addressing envelopes in 2007 and watching it languish in storage for the years afterwards, I decided to turn it into something more useful—a teleprinter. keypresses are sent over serial, and it prints data received.

short story: it worked, but a project this size isn't without its gotchas.


figured I'd check in since the blog hasn't seen much love lately. I've been super-busy at home lately trying to put the finishing touches on the typewriter, and I've made some really good progress. feast your eyes on this:

the typewriter is printing data sent to it from the computer now. there are obviously a few problems, but the project is on the final stretch.


this blog generates its pages by shell script, and it's been a bit of a challenge to make the engine portable, so generated content and the code itself can be run anywhere.

one way this is made easier is by using <base href="<?= $blogroot ?>" />, which tells the user agent to prepend every source and reference with $blogroot. as I developed on Safari, everything worked.

then I asked for some friends to look at it, and it turned out that the base tag doesn't quite work like I'd hoped: you can't use a relative path as your base href, and Firefox enforces this strictly.

there's two options for fixing this: the blog engine itself has to know where it lives on the server, so it can populate the base href correctly, making generated content less portable -or- the output generation could be smarter and append the relative base href to the beginning of every source and reference it sees, making the output code messier.

luckily, if you're ok with requiring that your clients support javascript (which I am), there's a third option. behold:

<script type="text/javascript" id="base_href">
  Node.prototype.insertAfter = function(newNode, refNode) {
    if(refNode.nextSibling) {
      return this.insertBefore(newNode, refNode.nextSibling);
    } else {
      return this.appendChild(newNode);
    }
  }

  var newcontent = document.createElement('base'); 
  newcontent.href = document.baseURI.substring(0, 
    document.baseURI.lastIndexOf('/')) + '<?= $blogroot ?>';

  var here = document.getElementById('base_href');
  here.parentNode.insertAfter(newcontent, here);
</script>

put that in the beginning of your <head> and it will emit the correct absolute base href at runtime.

thanks to Christian Hammond for the idea.

edited on friday february 19th, 2010 at 21:38:

unfortunately this blog no longer uses this hack because the base href was interfering with document bookmarks.

edited on friday april 9th, 2010 at 15:26:

this post used to feature a version using document.write() that didn't work in Opera, IE, and Konqueror. while I haven't extensively tested this new version, I expect it to work better.

the PHP library makes me sad sometimes, like earlier tonight.

I've been working on the blog engine, trying to figure out how to get various bits of markup working that I don't want to have to write by hand every post1, and it requires doing XML manipulation in PHP.

if you take the time to look around on the internet (and I did), you'll see a lot of people who want to manipulate HTML or XML in PHP, and all the replies recommend things like SimpleXML, which can't remove or change tags, or DOM, which also didn't work for my needs2. exhausting these options, every thread ends with "use str_replace" or "use preg_replace". sigh. what's the point in having these libraries if they're not actually useful?

I want to do this right, damnit, and I'm going to use a tool that parses my pseudo-HTML fragments into a tree and allows me to add, change, or remove tags at will!

luckily, as I was resigning myself to writing a library from scratch, I discovered simplehtmldom. unlike other libraries I've tried using recently, simplehtmldom worked right out of the box with no issues whatsoever. code example follows.


1 especially footnotes
2 DOM only accepts properly formed XML or HTML with an all-containing root node and will only create output with a doctype and a single root node. I wanted something that would create output as close as possible to the input.