On Mon, 2007-02-26 at 19:18 +0100, Pieter Palmers wrote: > In our attempt to help fulfilling 'the need for every single possible > hardware interface to work', we could use some helping hands. i suppose you are talking about freebob. what about writing a documentation on how to do this? i, for example, own an m-audio firewire 410 that does right now not work with freebob, but i consider myself to be unable to comprehend anything that relates to devices or the programming of them. how can you free me from my anxieties? give me information! > We should keep in mind that we're all doing it for fun (I hope) you call this fun? it's horrible! fun is a night of watching "dead like me" seasons! writing gallons of code to solve a problem is not fun! a solved problem is fun, yes! call it passion. and fame is a valid reward for passion. > To some extent, the developers are to blame too. How often does a > project lack (decent) source code documentation, while that is IMHO > necessary for cooperation? exactly! > PS: tell me that these already exist, so that I don't have to start > my > own private projects: 'AbletonLive4Linux', aldrin is supposed to progress towards a blend of ideas from buzz, live and reason. however i never used live much, so i need people to tell me what they'd like to see in the app. -- Leonard Ritter -- Freelance Art & Logic -- http://www.leonard-ritter.com
