[x3d-public] draft X3D 4.1 prose for font files and libraries

[Holger Seelig]

I think a FontLibrary should be scene scoped and no more. An Inline scene should not have access to the parent scenes FontLibrary nodes registers fonts (via FontLibrary.family field).

In HTML there is a iframe element, the document in this element can’t get access to the parent document, It is completely separated. One reason is that an iframe is often used for advertising which comes often from a different provider and the advertising document should not have access to the parent document for security reasons.

I also think that FontStyle.fontLibrary is not necessary. It makes the code more readable if FontLibrary is a root node.

Best regards,
Holger

--
Holger Seelig
Leipzig, Germany

holger.seelig at yahoo.de
https://create3000.github.io/x_ite/

> Am 07.03.2025 um 21:13 schrieb John Carlson via x3d-public <x3d-public at web3d.org>:
> 
> 
> 
> On Fri, Mar 7, 2025 at 1:33 PM Brutzman, Donald (Don) (CIV) via x3d-public <x3d-public at web3d.org <mailto:x3d-public at web3d.org>> wrote:
>> separation of concerns, i.e. keeping url networking separate from FontStyle presentation,  not overwhelming FontStyle functionality.  Thus, FontStyle.url is simply incomplete design, and FontStyle.fontLibrary is a more-correct alternative, if we want font scope limited to a single FontStyle node.
> 
> I don't understand why the same argument doesn't also apply to ImageTexture.  I'm not seeing ImageTexture.url networking separate from ImageTexture presentation?  Do we need an ImageLibrary?
> 
> John
> _______________________________________________
> x3d-public mailing list
> x3d-public at web3d.org
> http://web3d.org/mailman/listinfo/x3d-public_web3d.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20250307/341ef46e/attachment.html>