|
 |
On Sat, 01 Apr 2000 16:15:13 -0500, pk wrote:
>Peter J. Holzer wrote:
>>
>> On Thu, 30 Mar 2000 21:39:58 -0500, pk wrote:
[...]
>> <sphere location="12,34,56" radius="1" />
>there a > and a < missing
No, that line is correct. <tag/> is just an abbreviation of
<tag></tag>. Please see http://www.w3.org/TR/1998/REC-xml-19980210 for
details of the XML syntax.
>> >Definition language weren't made to support imbricked things/tags that
>> >work only in another tag
>>
>> It does. In HTML, for example, a <title> element can only occur inside a
>> <head> element.
>That's not what i meant, sorry...
>I meant that there isn't a tag(transformations come to mind) that work
>different way depending of the tag in which it's imbricked...
Tags don't "work" in XML. They just give structure to a document. The
meaning of the elements is completely up to the application. Besides,
transformations work quite the same regardless of where they are. They
just affect different things.
>Anyway, i'd be happier if instead of only having predefined shapes, you
>could extend the language with an interpreted language ala java, where
Interesting. There are people here who want to get rid of the
programming elements of POV-Script and others who want to turn it into a
full object-oriented programming language :-)
>there is, say:
>Primitive.Class
> |
> |-cube
> |
> |-cone
> |
> |-plane
> ...
>Where the primitive class contains everything you need to define an
>object, except the function that defines the object in itself(it parses
>everything and calls the good function in the class)
I don't see where this gives really an advantage over what you can do
with POV script. You can already define objects of any complexity and
handle them just like the primitive objects.
However, I sometimes miss the possibility do define methods which either
manipulate the object or return information about it. For example, if I
define an object "arm", I would like to write methods to set its
position in different ways (because sometimes I know where the wrist
should be and sometimes I know where the shoulder should be) and to
retrieve the position of the other pieces.
While I can write macros to do this, they are separate from the object,
which makes it difficult to keep them consistent. I think MegaPOV has
some features which make this easier.
hp
PS: Could you please quote only what is relevant to your answers? If my
newsreader didn't color quotes differently than normal text I wouldn't
even have seen that you put in one-line comments between dozens of lines
of my own text.
--
|_|_) | Sysadmin WSR \ Durchbruch in der Bionik, und Microsoft geht
| | | hjp### [at] wsr acat \ Pleite und Gardena bringt organische PC's
__/ | http://www.hjp.at/ \ auf den Markt. -- Stefan Schaefer
Post a reply to this message
|
|
