Tags

employment
llc
xrp
redhat
ripple
interfaces
ncurses
ruby
refs
filesystems
retro gaming
raspberry pi
sinatra
3d printing
nethack
gcc
compiler
fedora
virtfs
project
gaming
vim
grep
sed
aikido
philosophy
splix
android
lvm
storage
bitcoin
projects
sig315
miq
db
polisher
meditation
hopex
conferences
omega
simulator
bundler_ext
rubygems
book review
google code in
isitfedoraruby
svn
gsoc
design patters
jsonrpc
rjr
aeolus
ohiolinuxfest
rome
europe
travel
brno
gtk
python
puppet
conference
fudcon
html5
snap
tips
ssh
linux
hardware
libvirt
virtualization
engineering expo
cloud
redmine
plugins
rpm
yum
rake
screencasting
jruby
fosscon
pidgin
gnome-shell
distros
notacon
presentation
rails
deltacloud
apache
qmf
passenger
syrlug
hackerspace
music
massive attack
backups
crypto
vnc
xsd
rxsd
x3d
mercurial
webdev
ovirt
qpid
haikus
poetry
legaleese
jquery
selenium
testing
xpath
git
sshfs
svg
ldap
autotools
pygtk
xmlrpc
slackware

Sep 9 2009

Announcing Motel Version 0.1

Movable Object Tracking Encompassing Locations is a library/utility written in ruby used to track the locations / coordinates of objects relative to each other in a 3D environment, moving them according to configurable movement strategies.

I actually was able to quickly bang this out, having started it only three weeks ago. Granted, I’d originally written in this in C++ over the last year and a half, my work on the romic and manic projects ultimately culminating in the C++ version of this project. So most of the design work was done, I was just dissapointed at the pace I was going towards even larger goals, and thus decided to switch languages to Ruby (using activerecord for my db stuff) and use Apache QPID to speed things up a bit.

So now I present Motel, an AGPL utility written in Ruby (but also provides an AMQP interface which can be used by a client written in any language) whose sole purpose is to provide a robust way which to track moving locations, configuring them and resolving queries when appropriate. Its still a work in progress, there are quite a few TODOs, and the documentation could use much love, and a user / developer manual written. In lieu of this in the meantime, I’m going to be looking at extracting certain choice snippets from my code, and pasting them to this blog to discuss my design and implementation methodology. Enjoy!

( and btw happy 09-09-09 :-D )