Difference between revisions of "FieldTrip"
(Overhauled / simplified) 
m (tidied prose. typo fix.) 

Line 4:  Line 4:  
== Abstract == 
== Abstract == 

−  '''FieldTrip''' is a library for functional 3D graphics. 
+  '''FieldTrip''' is a library for functional 3D graphics, intended for building static, animated, and interactive 3D geometry, efficient enough for realtime synthesis and display. 
−  It is intended as an API for building static, animated, and interactive 3D geometry, efficient enough 

−  for realtime synthesis and display. 

Our first renderer uses OpenGL, with the usual visual limitations. 
Our first renderer uses OpenGL, with the usual visual limitations. 

Since FieldTrip is functional, it is about ''being'' rather than ''doing''. 
Since FieldTrip is functional, it is about ''being'' rather than ''doing''. 

Line 28:  Line 28:  
; <hask>Geometry2</hask> 
; <hask>Geometry2</hask> 

−  : 2D geometry. There's a <hask>flatG</hask> 
+  : 2D geometry. There's a function (<hask>flatG</hask>) to embed 2D into 3D. 
; <hask>Image o = (R,R) > o</hask> 
; <hask>Image o = (R,R) > o</hask> 

Line 35:  Line 35:  
== FieldTrip meets Reactive == 
== FieldTrip meets Reactive == 

−  FieldTrip contains no support for animation, because we envision it being used with the [[Reactive]] 
+  FieldTrip contains no support for animation, because we envision it being used with the [[Reactive]] functional reactive programming ([[FRP]]) library (and possibly other animation frameworks). 
By design, FieldTrip is completely orthogonal to any formulation or implementation of FRP. 
By design, FieldTrip is completely orthogonal to any formulation or implementation of FRP. 
Revision as of 17:43, 7 November 2008
Abstract
FieldTrip is a library for functional 3D graphics, intended for building static, animated, and interactive 3D geometry, efficient enough for realtime synthesis and display. Our first renderer uses OpenGL, with the usual visual limitations. Since FieldTrip is functional, it is about being rather than doing. One describes what models are, not how to render them.
Besides this wiki page, here are more ways to find out about FieldTrip:
 Read the library documentation.
 Get the code repository: darcs get http://code.haskell.org/FieldTrip.
 Install from Hackage.
 See the version history.
Please leave comments at the Talk page.
Basic types
The basic purpose of the core FieldTrip library is to allow a user build 3D geometry, from individual simple shapes to full 3D scenes. The principal types are as follows.

Geometry3
 3D geometry. These values can be spatially transformed in space (affinely: scale, rotate, translate) and combined (union).

Surf a = (a,a) > (a,a,a)
 Parametric surfaces, i.e., mappings from 2D to 3D. Normals are constructed automatically and exactly via derivatives, thanks to the vectorspace library. These normals are used for shading. For simplicity and composability, surfaces are curved, not faceted. Surface rendering tessellates adaptively, caching tessellations in an efficient, infinite data structure for efficient reuse. The mechanism for choosing tessellation is a very primitive placeholder. FieldTrip provides some basic shapes of surfaces (spheres, torus, cubes, etc) and many functions for manipulating surfaces, colors, etc.

Geometry2
 2D geometry. There's a function (
flatG
) to embed 2D into 3D.

Image o = (R,R) > o
 A primitive placeholder for functional imagery in the spirit of Pan. The intention is to use this type or something like it for texture mapping. Much design and implementation work to be done.
FieldTrip meets Reactive
FieldTrip contains no support for animation, because we envision it being used with the Reactive functional reactive programming (FRP) library (and possibly other animation frameworks). By design, FieldTrip is completely orthogonal to any formulation or implementation of FRP.