Well, suppose you enter someone's visual programming environment, all
ready to test it out, and it looks like a garden. Is it obvious that
the fruits on the trees are demo programs, that the various herbs by
the side of the path are operations, that you construct your program
by stirring them into a big iron pot while incanting some formulae,
and that the result will appear in the gazebo in the middle? Or suppose
you enter another environment, and it looks like a machine shop, with
a bunch of tools on the wall, a few filing cabinets to take them from, and a
workbench in the middle? Which of these is closer to things you would
find familiar, and know how to interpret? How much does that depend
on your culture, and the actual terminology I've used in describing
them? I don't think it's that objects in themselves will be a real
problem; it's that metaphors will differ, and we're going to have to
learn to dance among them, and synthesize our ideas with them, and
them with each other. Will you expect a box with a double helix
on it to contain a genetic algorithm? Will other people?
[This should probably be on the vrworlds mailing list, rather
than here; but I do think vrml should take into account that
people will want to customize their viewers so that standard
objects like files and directories fit into particular kinds
of themes. This is tied into the old discussion of logical
vs. physical descriptors, a la <strong>..</strong> instead
of <b>..</b>.]
------------------------------------------------------------------------------
<a href="http://www.cs.ncl.ac.uk/chris.holt/">Chris.Holt@newcastle.ac.uk</a>
------------------------------------------------------------------------------
Long is the web / And hard, that out of hell leads up to light.