[fluxus] Screen Recording?

[Artem Baguinski]

On 15 Feb 2006, at 11:05, Dave Griffiths wrote:

>> I'm also having a problem with going fullscreen - for some reason  
>> ctrl+f
>> just maximises the window, so I'm still left with the gnome panels  
>> and
>> fluxus titlebar. How do I get rid of all that and have fluxus in  
>> "true"
>> fullscreen?
>
> the only way I manage to get round that one was to run fluxbox

or macosnext :-p
>
>> I'm toying with an object oriented fork of fluxus using the Ruby  
>> scripting
>> language at the moment, I'll post again when I have some code that
>> actually
>> runs (my C++ isn't too hot!) - if anyone is interested, drop me a  
>> line!
>> Fluxus is a really great bit of software and I've really taken to  
>> it -
>> it's
>> just the scheme interface (and all that functional programming  
>> malarkey)
>> is
>> providing a bit of a barrier for me!
>
> I'd really recommend taking the time to learn Scheme, as it makes  
> you a
> better programmer to learn different languages, especially one that  
> is so
> different to the C based ones we mostly use these days.


it's better to call them algol based, that allows to split the world  
in roughly 3 parts: lisp based, algol based and others ;-)

another pro-lisp argument for fluxus could be that traditional lisp  
programming workflow IS livecoding. normally i have my source code  
open in emacs or drScheme, i edit it, send edited functions to the  
interpreter or compiler and try the bits of code in the repl window.

the P(rint) in REPL is the only bit i miss when coding in fluxu. hmm,  
no actually not the only one, but everything i can do in emacs, like  
(with fluxus inspired keybindings in stead of "Ctrl+x Ctrl+e", "Ctrl 
+x b", "Ctrl+j" etc):

  F7 - toggle editor / repl, where in repl mode:
   - current script is hidden
   - F5 evaluates the expression and prints the result below

  F6, while in the editor mode: evaluate current sexp, switch over to  
repl if there was error (and display the error, obviously). this way  
you could alter bits of the program while it is running, e.g. you  
could alter variables, change the global state, modify functions.

Also, if what you did was modify the function that gets called during  
rendering, and you have a syntactic error or something, the old  
function won't disappear and the program will continue running, while  
you'll endup in the repl with an error message, hopefully explaining  
what's up.

Even for the code that gets executed only on script start up (like  
bits that build the scene graph) it could be useful, even though you  
don't see you modifications altering the program output immediatelly,  
you have better chance to have a working version when you hit F5 in  
the editor and your scene won't be empty while you're figuring what  
you did wrong.

of course there will always be code that interpreter swallows but  
which only breaks when being used. but still ;-)

cheers,
artm