On Mon, 2010-07-19 at 23:24 +0200, gabor papp wrote: > > It sounds great to prepare stuff with personalized commands or to > > show the fluxus capabilities. > my main reason to do this was not for livecoding but for other usage of > fluxus, where you cannot expect the users of your software to change the > code if they need to change some parameters. > > > The light part is very interesting, thing I never do because longer > > to code in. Should I? ^_^ > i rarely do it either, because it's cumbersome, although multiple lights > often bring very nice effects to the scene.
Lighting can be really important, and I don't think it's used enough. One way around this is to have some preset lighting environments we can call on from a library. It would also help if the interface for lighting in fluxus was a little more consistent with the rest of the code too... e.g. it would be nicer: (with-light (build-point-light) (diffuse (vector 1 0 0)) (translate (vector 0 100 0))) or something... cheers, dave
