Differences

This shows you the differences between two versions of the page.

--- project_qfwfq_notes [2011-11-10 12:23] – davegriffiths
+++ project_qfwfq_notes [2011-11-10 12:41] – davegriffiths
@@ Line 48: / Line 48: @@
   * Implications in other areas
   * Use of music
+  * Human time vs computer time
+    * Moving between these for tangibility
 ==Finding appropriate ways of programming with a limited interface==
@@ Line 61: / Line 63: @@
     * Amorphous programming, focus on parallel, spatially arranged small programs robust to fuzziness
       * Is this more suitable framework for less discrete/"gestural" interfaces?
-      * Multiple levels
+      * Multiple levels of process resolution (parallel with overall marshaling - scatter/gather approach?)
+==Novel approaches to creativity==
+  * Games as learning environments - well researched area
+    * Game world as "safe space" for experimentation/creativity
+    * Games as ways for people to see things from different perspectives
+  * "Game programming" as solid existing basis for creative learning
+  * Current examples lack integration of programming into the game world itself - treated as separate "layer"
+    * When programming "invades" gameworld currently, it's a hack - minecraft/little big planet CPUs
+    * We can make this hack a feature - designed in from the start
+  * Algorithms as world, processes as agents = very visible/tangible programming model
+    * As a solution to algorithmic malleability
+      * Easy to see whats going wrong and where
+      * It's realtime
+  * Games as environments filled with interacting agents (incl humans)
+    * Human level of understanding, rather than machine
+    * Current languages abstract machine process into human level metaphor (for/while loops etc -> assembler)
+    * Next languages need to also abstract machine time to human understanding?
+    * Remove the write, compile, run cycle - programming as interaction (see above)
+    * Debugging techniques
 ====Initial 2011 reset====