note
stefp
<i>Trusting the principle A picture's worth one thousand words, I'd like to apply that to computer programming.</i>
<p>
I dont think that visual programming is the general way to go except
for specialized problems like automata. The real barrier to break is
the ASCII monofont, monosized, monocolor conventions for programming
languages. I call it the <i>teletype barrier </i>because these
conventions have been shaped by that physical device. Typographically
speaking, the only significant progress has been the generalization of
lower case letters.<p>
When a mathematician writes a formula (is that the right word in
English?), it is often an algorithm, almost a program. A mathematician
uses many alphabets and many fonts, indices and exponents. We
can't. These conventions have been improved by generations of
mathematician starting with <a
href="http://www-groups.dcs.st-andrews.ac.uk/~history/Mathematicians/Viete.html">Viéte</a>
(these starting date are often biased by nationality :)<p>
Such "formulae"
are certainly
not graphical in the sense you implied, but the
underlying conventions leads to a neat layout so that it
is "parsed by our eyes" instead of being slowly deciphered.<p>
I think Mathematica is an interactive environment that uses such
conventions but it is expensive (1000$) and mosttly specialized in
Mathematical rule based programming. I am not surprised when searching
on thenet pages about the history of mathematical notation to trip on
this <a
href="http://www.stephenwolfram.com/publications/talks/mathml/mathml_abstract.html">conference
by Steven Wolfram</a>. His concern is the one that motivates this node
<i> Given its historical basis, it might have been that mathematical
notation--like natural language--would be extremely difficult for
computers to understand.
But over the past five years we have developed in Mathematica
capabilities for understanding something very close to standard
mathematical notation. I will discuss some of the key ideas that made
this possible, as well as some features
of mathematical notation that we discovered in doing.</i><p>
There is a chicken an egg problem here in getting a real interactive literate programming environment:
which comes first, the typesetting rich language or the editing environment? But there is hope. Check <a href="http://www.texmacs.org">TeXmacs</a>, this is an WYSIWYG structural editor. Very roughly speaking, conceptually, this is a mix of TeX and
emacs. If correctly extended, it could provide such an environment. And the perl communauty, with its motto TMTOWTDI, is more prepared than any other to accept possibly different representations for the same program.<p>
As for classical litterate programming, the tools developped by
Knuth are not interactive enough. But they are fine to generate a documentation to be read off-linelike <a href="http://www1.fatbrain.com/asp/bookinfo/bookinfo.asp?theisbn=0201542757&vm=">The Stanford GraphBase; A Platform for Combinatorial Computing</a><p>
-- <a href="/index.pl?node=stefp&lastnode_id=1072">stefp</a>
59421
59421