That's called hardware engineering (arranging physical components). There are some good developments using paper and "ink" and various components shown on TED. But I agree with you on programming too, see Minecraft or ToonTalk or Scratch etc. I think the various domains of programming, String, Number, Date, Boolean, Branch, Collection, Program Recorder/Debugger etc. can be put into easily understandable visual components and programming can proceed by demonstration or example. 0 lenses is better. Just slow like I said in my message. Using a lens (to compile) speeds stuff up.
John On Wed, Dec 5, 2012 at 2:59 PM, David Barbour <[email protected]> wrote: > From this title, I was hoping for a subject on cameras as a user input > model for programming with pen and paper (and augmented reality). I did > blog on that recently. > > For live programming, it would be nice if programming was like arranging > physical components, no photography. > On Dec 4, 2012 6:17 PM, "John Carlson" <[email protected]> wrote: > >> Wouldn't it be best to make programming a bit like single lens >> photography instead of dual (or triple) lens photography? It would seem >> like the fewer lenses you use, the less likely it would be for one of them >> to be scratched. Unless somehow there was a compensating factor in the >> lenses. >> >> My 2 bits. Metaphor isn't quite right, but perhaps you see my point. >> >> Where's my post-mature optimization? >> >> John "Damn the torpedos, we're going full speed ahead and getting >> nowhere" Carlson >> >> _______________________________________________ >> fonc mailing list >> [email protected] >> http://vpri.org/mailman/listinfo/fonc >> > > _______________________________________________ > fonc mailing list > [email protected] > http://vpri.org/mailman/listinfo/fonc > >
_______________________________________________ fonc mailing list [email protected] http://vpri.org/mailman/listinfo/fonc
