[x3d-public] Removal of Layout component in X3D v4
gpugroup at gmail.com
Thu Oct 10 06:08:46 PDT 2019
A few more thoughts that pop to mind
1) if v4 is supposed to be for html by design, then perhaps there could be
a v4B or named PROFILE for non-html
2) could/should there be a superformat /superprofile for authoring, that a
translator utility can reliably get into narrower profiles?
- for example author with Layout, can it get into CSS or vice versa?
On Wed, Oct 9, 2019 at 9:07 AM Andreas Plesch <andreasplesch at gmail.com>
> A new profile may be an option. In fact, FHG had proposed a HTML
> profile a while back: https://www.x3dom.org/nodes-2/ . This could
> serve as a basis.
> On another note, since I was not quite happy with the population globe
> example, I made some minor improvements:
> This has thicker lines, proper transparency for the atmosphere glow, a
> lighter globe background, and correct initial size for the year text.
> As an example, besides the css layout, this also shows how to push
> events into an Inline without EXPORT/IMPORT in x3dom., using a small
> script instead of a route.
> On Tue, Oct 8, 2019 at 10:26 PM GPU Group <gpugroup at gmail.com> wrote:
> > Does v4 have profiles and components? Could there be separate
> profiles/components for standalone and html variants?
> > -Doug
> > On Tue, Oct 8, 2019 at 5:10 PM Andreas Plesch <andreasplesch at gmail.com>
> >> I believe one reason why removal of the Layout component is considered
> >> is because it was not widely implemented and because it duplicates
> >> layouting functionality provided by HTML/DOM. That is why it will not
> >> make a lot sense to add a layout component to x3dom.
> >> Here is Holger's example ported to x3dom:
> >> This uses the original css based layout from
> >> http://globe.chromeexperiments.com/ directly.
> >> Using css and standard HTML/DOM layouting removes a lot of complexity
> >> from the x3d scene. It does then require tighter integration of HTML
> >> and X3D. Using x_ite-dom would be enough for the example to run in
> >> x_ite while using css layouting and standard HTML text [If there is
> >> interest, I could port the example to x_ite-dom as well]. There is a
> >> lot of technology available, the latest is CSS grid. Web developers
> >> are used to this kind of layout.
> >> Of course, standalone, eg. non-web X3D browsers like Castle or freeWrl
> >> certainly still benefit from a Layout component.
> >> The question then becomes if there should be an attempt to harmonize
> >> web based layouting and standalone layouting although good ideas would
> >> be needed.
> >> Cheers,
> >> -Andreas
> >> --
> >> Andreas Plesch
> >> Waltham, MA 02453
> >> _______________________________________________
> >> x3d-public mailing list
> >> x3d-public at web3d.org
> >> http://web3d.org/mailman/listinfo/x3d-public_web3d.org
> Andreas Plesch
> Waltham, MA 02453
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the x3d-public