I dont know factory pattern design, so Ill need to read up on that. Of course this was to get rigicon to work, so I was just aiming the call abstractions to what I needed for the tool which probably isn't the best thing for a core library like this. I still think it would be a good idea to centralize all app specific calls in rigicon so you dont have to chase down the calls if/when porting to a different application. But this could just a different module within rigicon. What do you think?