Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
visual_programming_notes [2007-07-12 09:32] – external edit 127.0.0.1 | visual_programming_notes [2007-07-12 09:51] (current) – nik | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | visual programming notes | + | ==== visual programming notes ==== |
thinking in diagrams, flows or partial processes (notes to be gradually merged with [[Visual Programming]]) | thinking in diagrams, flows or partial processes (notes to be gradually merged with [[Visual Programming]]) | ||
- | aims/ | + | ==== aims/ |
is it possible to create an environment which facilitates prototyping, | is it possible to create an environment which facilitates prototyping, | ||
Line 16: | Line 18: | ||
understandable by a range of people, programmers (familiar with the env, and unfamiliar), | understandable by a range of people, programmers (familiar with the env, and unfamiliar), | ||
- | notes to expand | + | ==== notes to expand |
problems of representations, | problems of representations, | ||
Line 51: | Line 54: | ||
* dataflow ' | * dataflow ' | ||
- | protyping environment vs production systems | + | ==== protyping environment vs production systems |
a good prototying environment enables rapidly testing of ideas, which usually involves throwing away a lot of test code and making many modifications to a range of more-or-less working programs. getting something working easily is more important than it working efficiently and/or accurately and/or elegantly. not that this is inherently the case; prototyping can help reveal an effcient, elegant acurate algorithm. the level of detail is at the algoritm/ | a good prototying environment enables rapidly testing of ideas, which usually involves throwing away a lot of test code and making many modifications to a range of more-or-less working programs. getting something working easily is more important than it working efficiently and/or accurately and/or elegantly. not that this is inherently the case; prototyping can help reveal an effcient, elegant acurate algorithm. the level of detail is at the algoritm/ | ||
Line 93: | Line 97: | ||
* close to hardware | * close to hardware | ||
- | visual programming in lisp | + | ==== visual programming in lisp ==== |
as a possible candidate for a visual language based on extending an existing lang.., (either CL, scheme or a future dialect). | as a possible candidate for a visual language based on extending an existing lang.., (either CL, scheme or a future dialect). | ||
Line 109: | Line 114: | ||
" | " | ||
- | metaprogramming | + | ==== metaprogramming |
- | "The Transition of Context-free Textual Languages into a Visual Programming Notation via Graph Techniques and a Meta Tool" Frank Bíhler, Mike Callaghan and Paul Luker Copyright 1998 IEEE. Published in the Proceedings of Compsac' | + | "The Transition of Context-free Textual Languages into a Visual Programming Notation via Graph Techniques and a Meta Tool" Frank B�hler, Mike Callaghan and Paul Luker Copyright 1998 IEEE. Published in the Proceedings of Compsac' |