Function + Action = Interaction (2015)
0 likes484 views
The document discusses the balance between integrity and flexibility in production, emphasizing the need for transitions in creative processes. It highlights the role of programming languages like Lisp in achieving this balance and explores concepts related to functional programming such as monads and optional types. Additionally, it touches on the coherency of dimensions and automatic type deduction in programming for enhancing productivity and creativity.
![www.pineapple.cc
[Y]=F[X]](https://image.slidesharecdn.com/functionactioninteraction2015-150806150058-lva1-app6892/85/Function-Action-Interaction-2015-40-320.jpg)
![www.pineapple.cc
[Y, T]=F[X, S]](https://image.slidesharecdn.com/functionactioninteraction2015-150806150058-lva1-app6892/85/Function-Action-Interaction-2015-41-320.jpg)
![www.pineapple.cc
[Y, T]=F[X, S]; [Z, U]=G[Y, T]
[Z, U]=G•F[X, S]](https://image.slidesharecdn.com/functionactioninteraction2015-150806150058-lva1-app6892/85/Function-Action-Interaction-2015-42-320.jpg)
Function + Action = Interaction (2015)
- 2. www.pineapple.cc Function + Action = Interaction Ichiroh Kanaya*, Mayuko Kanazawa**, Masataka Imura*** *Graduate School of Engineering, Osaka University **Department of Image Arts, Kobe Design University ***School of Science and Technology, Kwansei Gakuin University
- 8. www.pineapple.cc Shooting A Moving Target Shiro Kawai, Square USA Proc. Japan Lisp User Group Meeting, 2000.
- 9. www.pineapple.cc –Shiro Kawai The balance of integrity and flexibility is subtle but important. In our size of production, sometimes you need to allow one part of the production to work inconsistently with another, during a transition (and if things keep changing, it is always a transition period!) If you emphasize integrity and consistency too much, things cannot change in a timely manner. If you emphasize flexibility too much and allow people work their own way, you lose integrity. In my opinion, Lisp itself keeps a good balance between these, and fits well into this type of project.
- 10. www.pineapple.cc Programmer 1 Programmer 2 Programmer 3 Code 1 Perl Code 2 Java Code 3 Visual Basic Domain Specific Language Phantom Query Language Foundation Common LISP Architect Not enough?
- 12. www.pineapple.cc Coherency of Dimensions (Types in Programming) Referential Transparency Linearity/Symmetry
- 13. www.pineapple.cc p(t) ClocktowerDisplay Python/OpenGL Sensor C++/OpenCV Server Scheme {x(t), p(t)} t u(p) x(t)+y(u) t t Assets JPEG y(u)u t {x(t), p(t)} u(p) x: live video y: animation p: status t: current time u: animation time HTTP R.T. R.T. R.T.
- 18. www.pineapple.cc data Maybe a = Nothing | Just a enum Optional<T> { case None case Some(T) }
- 20. www.pineapple.cc ==> fmap (+3) (Just 2) Just 5 Optional.Some(2).map{$0+3} // .Some(5)
- 21. www.pineapple.cc
- 22. www.pineapple.cc Optional.None.map{$0+3} // .None ==> fmap (+3) Nothing Nothing
- 23. www.pineapple.cc
- 25. www.pineapple.cc ==> let f=fmap (+3) (+2) ==> f 10 15 let f=map({$0+2}, {$0+3}) f(10) // 15
- 26. www.pineapple.cc
- 27. www.pineapple.cc
- 28. www.pineapple.cc half x | even x = Just (x `div` 2) | otherwise = Nothing func half(a: Int) -> Int? { return a%2==0 ? a/2 : .None }
- 29. www.pineapple.cc
- 30. www.pineapple.cc Optional.some(3).flatMap(half) // .None Optional.some(4).flatMap(half) // 2 ==> Just 3 >>= half Nothing ==> Just 4 >>= half 2
- 31. www.pineapple.cc
- 32. www.pineapple.cc
- 33. www.pineapple.cc
- 34. www.pineapple.cc
- 35. www.pineapple.cc
- 36. www.pineapple.cc
- 38. www.pineapple.cc p(t) ClocktowerDisplay Python/OpenGL Sensor C++/OpenCV Server Scheme {x(t), p(t)} t u(p) x(t)+y(u) t t Assets JPEG y(u)u t {x(t), p(t)} u(p) x: live video y: animation p: status t: current time u: animation time HTTP R.T. R.T. R.T. Almost R.T.
- 42. www.pineapple.cc [Y, T]=F[X, S]; [Z, U]=G[Y, T] [Z, U]=G•F[X, S]
- 43. www.pineapple.cc Coherency of Dimensions (Types in Programming) Automatic Deduction of Data Type (like C++14, Haskell) Referential Transparency Action in Function (like Haskell) Linearity/Symmetry …Future Work