[creb fixes + opengl square + cube texturing
tom**20030620155749] {
hunk ./configure.ac 7
-PDP_VERSION=0.12-test-11
+PDP_VERSION=0.12-test-12
hunk ./doc/pdp.old/overview.html 13
-      by Miller Puckette and others. Its goal is to provide a way to use arbitrary data types (data packets) 
-      as messages that can be passed around inside PD, along side the standard PD numbers and symbol types and 
-      audio streams. In short it puts any data object on the same level as a float or a symbol.</p>
+      by <a href = "http://www-crca.ucsd.edu/~msp/software.html">Miller Puckette</a> and others. 
+      Its goal is to provide a way to use arbitrary data types (data packets) 
+      as messages that can be passed around inside PD, along side the standard PD numbers and symbol types. 
+      In short it puts any data object on the same level as a float or a symbol.</p>
hunk ./doc/pdp.old/overview.html 19
-      and usable as is. PDP runs on Linux and OS X. Currently, the focus is on images and video, but there is no 
-      reason it should stay like that. There is an extension library for binary cellular automata, and opengl render 
-      buffers and textures are in the making (like Gem). Some plans include general purpose matrices and tensors 
-      (like Gridflow / Jitter), audio buffers (like Vasp), ascii packets, text buffers, ...
-    </p>
+      and usable as is. PDP runs on Linux and OSX. The OSX version depends on <a href="http://fink.sourceforge.net/">Fink</a>, which is not 
+      in the "point & click" stage yet, so setting it up will require some efford. There is no windows version.
+      The reason for this is simple: i don't use windows myself. Porting would require
+      writing code for input/output and getting the libraries pdp depends on to work. If anyone is willing to do
+      this, just let me know.
+    <p>
+      Currently, PDP's focus is on images and video, but there is no 
+      reason it should stay like that. There is limited support for matrix processing included in the main library (like
+      Jitter or Gridflow). There is an extension library for 1D and 2D binary cellular automata, opengl rendering
+      (like Gem). Some plans include audio buffers (like Vasp), ascii packets, text buffers, ... Finally there's
+      a library that enables you to connect a scheme interpreter (guile) to pdp. For more image processing objects,
+      have a look at Yves Degoyon's <a href="http://ydegoyon.free.fr/pidip.html">PiDiP</a> library.
+
+    <h2>Getting Started</h2>
+
+    If you're used to working with PD, the the documentation and example patches should be enough to get you started. 
+    Have a look at the README file
+    in the distribution to find out how to compile and setup. The file doc/reference.txt contains a list of objects. If you have installed
+    pdp properly, you can just press the right mouse button on an object and select help to get a help patch. If
+    this doesn't work, look in the directory doc/objects for a collection of help patches. The directory doc/examples contains
+    some more demos. If you just want to do video, stop reading here and install it :)
+
+    <h2>Packets</h2>
+
+    <p> PDP is centered around the concept of packets and operations on packets. From the outside, all there seems to
+      be is video processing objects, but on the inside a type system and processor model is growing. One of the interesting
+      features in PD is the possibility of connecting everything with everything. If you want to generalize this to
+      all kinds of media objects, the complexity starts to grow quite fast. Therefore pdp has a type conversion system.
+      A packet always has a type description (a mime type if you want) that will enable it to be converted to another type
+      without to much bookkeeping. Most of this will become automatic later, but right now you can already do the conversions
+      manually.
+
+    <p> An example: You can use the basic pdp library together with the cellular automata library and the opengl rendering
+      library to use a cellular automaton as an input to a video processing chain. You can convert the processed image to
+      a texture that can be applied to a 3d object, which then can be drawn to the screen, captured as a texture, converted
+      back to an image, which can then be converted to a sound, processed and converted back to an image,  etc... 
+      You get the point. The possibilities are endless.
+
hunk ./doc/pdp.old/overview.html 58
-    <h2>Past, Present and Future</h2>
-    <p>PDP started out as a big hack, until the idea arose to improve and maybe even unify some media extensions 
-      to PD. Stability and  performance are fairly high, the clean and open design goal is where the most action is 
-      going on lately. The big roadblock right now is the type system. Once that is working, interfacing pdp to
-      other pd extensions (and other programs) should be straighforward.
hunk ./doc/pdp.old/overview.html 63
-Last modified: Wed May 14 02:02:58 CEST 2003
+Last modified: Fri Jun 20 17:01:39 CEST 2003
}