hackishly working OpenBlocks init

It's only working with hard-coded paths for lang_def.xml and lang_def.dtd; I've been staring hard at the sample code in the processing tool data folder README and haven't been able to match it up with what OpenBlocks is expecting for a filename.  

Hoping there's something there that can work as-is, but I'm not sure if there's something unique about how a processing tool loads files from the data folder or not.  Hopefully it's a small fix, otherwise we may have to modify the way OpenBlocks accesses the file(?).

That said, WOO this actually opened up an OpenBlocks window from within Processing!