From: anthonypaulo@gmail.com   
      
   Hello world!   
      
   I'd like to gradually expose quite a bit of functionality on my card so I   
   expect the API is going to be pretty big, so I'd appreciate some advice on how   
   best to structure the API interface to make it really easy to program with.   
   The card has a Raspberry    
   Pi on it and I use bit-banging to create a bus between the Apple II   
   address/data bus and the Pi's GPIO pins, and the GPIO seems more than capable   
   of working at 1mhz speeds so it can 'keep up' with the Apple II. What I'd like   
   to do is gradually add API    
   support for things the Pi can provide, such as HDMI monitor and all the   
   resolutions a PI supports, 8gb of RAM, TCP/IP over wired/WIFI, USB   
   storage/audio/printer, 1.5ghz co-processor capabilities, etc...    
      
   Any thoughts on how best to expose this type of API for easy consumption?   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)