> The reason it got a consistently negative response is that it would
> require a graphical editor to comprehend the simplest scene written in
> that language. 

  Keep in mind that you're speaking from the point of view of
  having already made an investment in the current format.
  As pointed out already - it's recognisably like DKBtrace,
  the point being that the use of braces, tags or commas
  is really quite irrelevant.

> It just isn't the right tool for the job

  For text editing, perhaps not.  But for other things, it leaves
  POV script for dead.

> it would be even harder to program complex stuff in than it
> would be in POV-Script

  No, it wouldn't.  It would be more consistent, more flexible
  and more extensible.

> harder for non-programmers to write scenes in

  No, the data is the same, tags are arguably easier for 
  non-programmers to grasp than "sphere { <0,0,0> 1.0 }"
  which isn't informative in the slightest.

> file sizes would be much bigger...

  Mesh data aside, it is completely irrelevant.
  5k vs 8k?  Is it that important?

  You're right though, a hybrid text/tree/graphical editor
  would be the ideal incarnation of an XML based scene
  development tool.

--
Nigel Stewart (nig### [at] nigelscom)
Research Student, Software Developer
Y2K is the new millenium for the mathematically challenged.

Post a reply to this message