[x3d-public] [x3dom-users] bboxDisplay considerations; metadata nodes for new field extensions

[Holger Seelig]

Hello Don,

The use of metadata is in my opinion very straightforward and your example is almost like I would do it, except I would use MetadataDouble for number values. Your example would then rather look like this:

<Shape bboxDisplay='true'>
  <MetadataSet name='extension'>
	<MetadataDouble name='bboxColor' value='0.7 0.8 0.9'/>
	<MetadataDouble name='bboxMargin' value='0.1' />
  </MetadataSet>
  <Sphere/>
</Shape>

With the different Metadata* nodes, every field can be type save represented.

There is already a good working concept there to access these values. 

Holger Seelig
Leipzig, Germany
holger.seelig at yahoo.de



> Am 01.04.2023 um 21:57 schrieb Brutzman, Donald (Don) (CIV) <brutzman at nps.edu>:
> 
> Thanks for continuing news about this excellent progress.
> 
> Am thinking we might all agree to regularize addition of nonstandard fields in a way that still passes content validation.
> 
> For example, non-standard experimental example
> 
> <Shape bboxDisplay='true' bboxColor='0.7 0.8 0.9' bboxMargin='0.1' >
>   <Sphere/>
> </Shape>
> 
> Might be equivalently and validly expressed as
> 
> <Shape bboxDisplay='true'>
>   <MetadataSet name='extension'>
> 	<MetadataString name='bboxColor' value='0.7 0.8 0.9'/>
> 	<MetadataString name='bboxMargin' value='0.1' />
>   </MetadataSet>
>   <Sphere/>
> </Shape>
> 
> A little more verbose perhaps... However, note that not only is model content validatable, but metadata content might also be validated if we build a metadata vocabulary that lists experimental field names, types and default values.  That way common extensions might be more sharable and model content remains confirmably correct.
> 
> Seems like a useful good practice that isn't complex, so we could easily build <MetadataSet name='extension'> capabilities into our browser parsers and authoring tools.
> 
> The X in X3D is Extensible... looking forward to continued innovation and practice/progress together.
> 
> v/r Don
> 
> 
> -----Original Message-----
> From: Andreas Plesch <andreasplesch at gmail.com> 
> Sent: Saturday, April 1, 2023 6:43 AM
> To: X3D <x3d-public at web3d.org>
> Cc: x3dom mlist <x3dom-users at lists.sourceforge.net>
> Subject: Re: [x3dom-users] [x3d-public] bboxDisplay considerations
> 
> The bboxDisplay field is now available for bounded objects (grouping nodes and shapes) in the dev. version of x3dom.
> 
> The color of the displayed bounding box can be customized with the non-standard bboxColor field, and the size expanded with the bboxMargin field.
> 
> Enjoy ! Andreas
> 
> On Thu, Mar 30, 2023 at 2:19 PM Andreas Plesch <andreasplesch at gmail.com> wrote:
>> 
>> I think it will be very useful to allow different colors for different 
>> sets of bounding boxes. Here are the rotating cubes with two sets of 
>> bounding boxes. The yellow ones react to a TouchSensor, the orange 
>> ones do not:
>> [...]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20230402/8c4db17d/attachment.html>