[x3d-public] Sharing X3D fields in gatherings

[John Carlson]

I am also considering a list of statements which are something like:

<Gathering name=“gathering1”/> … for validation of gathering names in
fields.

One could consider adding <Gathering>s to Scripts, ComposedShader, etc to
make all fields shareable.

I’m not prepared to do an implementation of gatherings or gathering names
as nodes or statements, but I can share and extend some JavaScript that
works with ProtoInstances and socket.io.  Ideally, there would be a layer
on top of socket.io calls to protect from socket.io specifics, but I’m not
quite there yet.

I’m also thinking about uploading multiple gathering name-> token mappings,
I’ll probably do it with multi-select, then a keystroke or a menu item.  I
currently think this opens up multiple browsers, but I’ve not tried it.

John

On Wed, Oct 9, 2024 at 9:54 AM John Carlson <yottzumm at gmail.com> wrote:

> I’m trying to figure out how to share fields within “gatherings,” when
> something like DIS is unavailable, as it is with X_ITE.  I currently use
> ProtoInstances and specify a list of gathering names in an MFString.  That
> works, but it involves a Goldberg contraption.  I would like something
> easy, like an extension to <field> which includes gathering names.  In a
> single user app, this would not be needed. But I feel something like this
> is needed for multiuser X3D.  Gathering names would point to security
> tokens on the client side to enroll users in gatherings on the server
> side.  At this point, I am not trying to defeat CORS.  A templating service
> with client provided data currently fills in a textarea with gathering
> information.  Ideally, filling in the textarea will be done on the client
> side with Selenium Java, and allow multiple gatherings.
>
> Note that mapping from gathering name to gathering token makes the scene
> available to many collaboration servers , and keeps the .x3d scene clear of
> tokens
>
> Your thoughts?  Can we subclass <field> perhaps?
>
> John
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20241009/bf393a02/attachment-0001.html>