Scheme-Uk-Fluxus
Dave Griffiths
1
Overview
• Fluxus introduction • What it's built from • Why Scheme • Livecoding • How it works - some examples • Functional Reactive Programming •Gamepad Livecoding
2
What is fluxus?
• Framework for various things: Playing/learning about graphics Workshops Performances Art installations • Game engine at heart... • With a livecodingeditor • Uses PLT Scheme • Source released under GPL • 4 or 5 developers working on it • Builds on Linux and sometimes OSX
3
Quick demo
4
I use fluxus for...
5
Live coding graphics,using live audio input
6
Live coding graphics and audio at the same time
7
As a framework for developing new livecoding languages
8
slub
9
What's inside?
10
BoringFeature List
• Immediate mode drawing • Scenegraph • Primitives Polys Particles NURBS patches Blobbies (implicit surfaces) Pixels (procedural texture access) • Unified access to primitive data (vertexarrays, texture data) • More advanced stuff GLSL Hardware shading ODE physics Shadows Skinning/Skeletons • Audio synthesis
11
Architecture
12
DrScheme integration
13
DrSchemeintegration
14
DrScheme integration
• Much better editor • Debugger • Profiler • Syntax highlighting • Less control over OpenGL No GLSL shader support No stencilmap shadows Slower • Not suitable forlivecoding performance
15
Why Scheme?
16
Fluxus philosophy
• 'Creative' code in Scheme • OpenGL grunt work in C++
17
Scheme for creative code
• Fast feedback (use an interpreter)• Expressive power • Few keypresses needed to get interesting results Functional roots Use of macros to shape the language Dynamic typing • Lots of interesting research going on with Scheme
18Livecoding
19
Livecoding
• Performance programming • Mainly a musical field • Reaction against the normal laptop performance • Showing the audience what you're doing
20
TOPLAP
•...
Regístrate para leer el documento completo.