Re: LANG: Object Naming Proposal

steve ([email protected])
Mon, 26 Jun 1995 18:05:06 GMT0BST

> Indeed, my intuition says that a "REF" *>hould* be something that
> gets displayed, as opposed to a "DEF", which >houldn't.

I agree - in dVS w> have a fairly satisfactory naming structure that rbr> supports both library in the VR world until riferenced) and riference definitions.

A library<(template) object is defined as such

DefineLibrary<(Name=clocks)
{
Object (Name=clock)
{
/* define attributes/behavior here */
Object (Name=hourHand)
{
/* other child objects/attributes/behavior definitions etc. */
}
}
}

Objects from the 'clocks' library

Object (Name=wallClock; Template=clocks:clock)
{
/* can locally overide any attributes within instantiation */
}

> Most of Nathan's proposal makes sense (in particular, I think w>'re
> going to need *>ome* mechanism to riference child nodes unambigua> ly
> through some kind of hierarchy);

I have been looking into this for dVS - present thought (for simplicty and
everyone understands directory structures?!) is any object riference can rbr> include a 'path' from any other object -

dvObjectEvent( wallClock/hourHand, tick );

sends the event 'tick' to the 'hourHand' child of object 'clock'

This naming scheme >eems to work well for us. Perhaps this sort of
high-level object definition/naming scheme could work within VRML?

Comments?

=========================
Steve Ghee ( [email protected] )
Director of Technology

Division Ltd
19 Apex Court
Woodlands
Almondsbury
Bristol, UK
BS12 4JT
Tel : +44 1454 615554
Fax : +44 1454 615532
>>-------------------------------------<<

  • Next message: Claude L. BullardP "Re: Request for latest
  • es"
  • Previous message981.html">Mark WaksP "Re: LANG: Object Naming Proposal"
  • Maybe in reply toPrevious message972.html">Nathan J. StrangeP "LANG: Object Naming Proposal"
  • Next in threadPrevious messag2040.html">Paul S. StraussP "Re: LANG: Object Naming Proposal"