2. Because of this modular design, Rubyk is made from the libraries
installed (objects compiled as dynamic libraries: Lua.rko, GLLua.rko)
and can therefore be used in very different environments (embeddable).
This means that we could have DSP or FPGA powered hardware running
Rubyk with specialized data processing objects.
3. And finally, Rubyk is made and meant for the network (clear and
simple API and protocols) so that we could have different user
interfaces, control surfaces, sequencers or whatever interacting with
Rubyk in many different ways.
4. Last but not least, Rubyk will compile and run on any OS supporting
POSIX threads and compiling C++ (Mac, Windows, Linux, BSD, uLinux,
etc). It is not limited to OSX (like Fields is now) or to platforms
that can compile Java (like Field will always be).
Cheers
Gaspard
PS: if possible, I'd like to keep this list in english because we have
non-french speaking members and it's nicer if they can understand all
the messages.
2010/6/9 Michael Lew <elephant...@gmail.com>
> --
> _______________________________________________
> rubyk mailing list
> ru...@rubyk.org
> http://rubyk.org/en/community