[X3D-Public] HTML inside X3D or X3D inside HTML. Layout help!
Joe D Williams
joedwil at earthlink.net
Sun Jan 2 10:24:11 PST 2011
> * perhaps we should first only support SVG Tiny, forbidding
> animation or event passing, in order to make implementation simpler
This would be a fine first step.
Joe
----- Original Message -----
From: "Don Brutzman" <brutzman at nps.edu>
To: <info at 3dnetproductions.com>; "John Carlson"
<john.carlson3 at sbcglobal.net>
Cc: <x3d-public at web3d.org>
Sent: Saturday, January 01, 2011 3:52 PM
Subject: Re: [X3D-Public] HTML inside X3D or X3D inside HTML. Layout
help!
> This capability and also SvgTexture have been proposed for X3D v3.3.
> Feedback welcome.
>
> From the Web3D member wiki:
>
> http://www.web3d.org/membership/login/memberwiki/index.php/X3D_v3.3_Specification_Changes#SvgTexture_node
>
>> SvgTexture node
>>
>> Perhaps we ought to add an SvgTexture node that allows application
>> of a Scalable Vector Graphics (SVG) image similar to an
>> ImageTexture.
>>
>> Functionality might be scoped by having 2D portrayal of SVG imagery
>> as one level, and behavior support as the next level. This would
>> allow a lightweight X3D plugin to either use the HTML/SVG browser
>> to render the SVG into an image file, or else connect to a server
>> to get the image.
>>
>> TODO steps to consider:
>>
>> * confirm that image size is defined by SVG image
>> * consider providing a mechanism to pass parameters, perhaps as
>> a MFString array of name="value" pairs
>> * map the event models for data passing, perhaps using <field>
>> definitions similar to Script or shader nodes
>> * why not simply use ImageTexture node to handle SVG images as
>> an image format accepted by the url? this approach handles imagery,
>> though event passing and behaviors might have to be via DOM in
>> anshared external HTML page
>>
>> 18.6 SvgTexture
>>
>> SvgTexture: X3DTexture2DNode, X3DUrlObject {
>> SFNode [in,out] metadata NULL [X3DMetadataObject]
>> MFString [in,out] url [] [URI]
>> SFBool [] repeatS TRUE
>> SFBool [] repeatT TRUE
>> }
>>
>> The SvgTexture node defines a texture map by specifying a
>> Scalable Vector Graphics (SVG)
>> file and general parameters for mapping to geometry.
>>
>> The texture is read from the URL specified by the url field.
>> When the url field contains
>> no values ([]), texturing is disabled. Details on the url field
>> can be found in 9.2.1 URLs.
>>
>> See 18.2 Concepts, for a general description of texture maps.
>>
>> See 17 Lighting component for a description of lighting
>> equations and the interaction
>> between textures, materials, and geometry appearance.
>>
>> * perhaps we should first only support SVG Tiny, forbidding
>> animation or event passing, in order to make implementation simpler
>>
>> * perhaps there is a server site that accepts SVG input and
>> provides PNG output? this would facilitate conversion for users who
>> are connected to the Internet
>
> http://www.web3d.org/membership/login/memberwiki/index.php/X3D_v3.3_Specification_Changes#Other_texture_types
>
>> Other texture types
>>
>> Consider HtmlTexture/BrowserTexture
>>
>> * Vivaty HtmlTexture
>> * Fraunhofer BrowserTexture
>>
>> Consider pros and cons of generalizing these various texture
>> extensions
>>
>> * does image size need to be retrievable somehow? perhaps an
>> SAI call or an outputOnly event?
>> * such features can be independently provided as images via a
>> server
>> * usability of an HTML page usually suffers if text is not
>> crisply rendered for easy reading and interaction
>> * should interactivity be preserved?
>> * Which profile?
>
> all the best, Don
> --
> Don Brutzman Naval Postgraduate School, Code USW/Br
> brutzman at nps.edu
> Watkins 270 MOVES Institute, Monterey CA 93943-5000 USA
> +1.831.656.2149
> X3D, virtual worlds, underwater robots
> http://faculty.nps.edu/brutzman
>
>
> _______________________________________________
> X3D-Public mailing list
> X3D-Public at web3d.org
> http://web3d.org/mailman/listinfo/x3d-public_web3d.org
More information about the X3D-Public
mailing list