Rather than have various fibs coding projects sprinkled throughout sf.net and other places, I thought it might be a good idea to leverage a single source control tree and group of fibs coders using it. It removes a barrier for someone who might otherwise open source their fibs code if it weren't for all the admin involved in starting a new project. In any case, I plan on dumping various things in here until I am voted off this island and invite others to do the same.
A fork of the the sf.net cocoafibs project code that padski is playing with.
(padski says: actually it is neither a fork nor am I actively playing with it. it is simply the initial cuting from which stepfibs is grown. to make up for that here is an old mockup of a javafibs style interface for cocoa. perhaps one day I'll get around to coding it)
A inim's vectorboard code. inim is working on a java based vector board module.
FLiPS is a second generation implementation of the FibsCompanion concept, which is a local FIBS proxy server. The idea of a local proxy server, is that plugins can be developed that extend the features of whichever client is in use. This new approach abandons the java-centric class-loading plugin style of FC in favor of using ubiqutous socket streams, thus enabling plugins to be developed in any language. It could provide a backbone of a new modular client made entirely of plugins.
A README.txt and Roadmap.txt file may be found in the FLiPS directory of the stepfibs svn tree. Many other docs may be found in the doc subdirectory.
expect/tcl language example code. So far only a simple (non-playing) bot is shown.
