[x3d-public] [X3D-Public] Prototype

[Dave A]

IF Protos are going to be implemented in some way by someone, I beg of 
you, do not use this 'export' business. Treat it like any other 
html/dom/javascript convention that it's all available. Perhaps by 
namespace too. But things should all just import and be available. 
Locking things up by needing to explicitly export them has been a real 
pain in the past with conventional players. I think this means we could 
drop ExternProto nodes completely. That would be sweet.

Dave A

On 2/14/2015 9:26 AM, Joe D Williams wrote:
>> Also the DOM is slow, Virtual DOM ftw :-)
>
> Not driven by Time, so slow or fast or order is ??
> Maybe time-based shadoms?
>
> Really, there may now be a few more good reasons to rethink 'standard' 
> Proto and ExtProto implementation for X3DOM. I recall early html where 
> an object could be defined in the head and reused but never played for 
> the public, so this is now emerging in this Virtual DOM(s) reusable 
> pattern stuffs which may be all put together so we can author a well 
> ordered time driven event system by DOM8?
>
> Of course as we step back and look at the glory that has been produced 
> we seek even greater transportability and fidelity between dedicated 
> and mixed interaction systems.
>
> Thanks to All,
> Joe
>
>
> ----- Original Message ----- From: "Cecile Muller" 
> <newsletter at wildpeaks.fr>
> To: <x3d-public at web3d.org>
> Cc: "Andreas Plesch" <andreasplesch at gmail.com>
> Sent: Friday, February 13, 2015 9:53 PM
> Subject: Re: [x3d-public] [X3D-Public] Prototype
>
>
>> Good morning,
>>
>>
>>> People on this thread should really be thinking about Web Components 
>>> for
>> this.
>>
>> I also hoped to use Web Components with X3DOM, but when native 
>> support will
>> be more widespread because if you want it now, you also have to decide
>> which polyfill (which adds overhead) to use because only Chrome 36+ (
>> https://twitter.com/addyosmani/status/489490560869490688) and Opera
>> currently support them completely (
>> http://caniuse.com/#search=web%20components).
>>
>> Web Component is made of four parts:
>> - Custom Elements (http://www.w3.org/TR/custom-elements)
>> - Shadow DOM (http://www.w3.org/TR/shadow-dom)
>> - HTML Imports (http://www.w3.org/TR/html-imports)
>> - HTML Templates (
>> https://html.spec.whatwg.org/multipage/scripting.html#the-template-element) 
>>
>>
>> Each part on its own can be somewhat polyfilled, but the standard way 
>> for
>> now is using one of those libraries:
>> - Polymer (https://www.polymer-project.org): by far the most known, 
>> IE10+,
>> and backed by Google
>> - X-Tag (http://www.x-tags.org): second most known, IE9+, and backed by
>> Mozilla
>> - webcomponents.js (https://github.com/webcomponents/webcomponentsjs):
>> IE11+ (IE10 without custom elements and imports), more a collection of
>> narrow-focus polyfills
>> - Bosonic (http://bosonic.github.io) is a newcomer, IE9+, I haven't 
>> tried
>> that one yet
>>
>> Also the DOM is slow, Virtual DOM ftw :-)
>>
>>
>> See you,
>> Cecile
>>
>
>
> -------------------------------------------------------------------------------- 
>
>
>
>> _______________________________________________
>> x3d-public mailing list
>> x3d-public at web3d.org
>> http://web3d.org/mailman/listinfo/x3d-public_web3d.org
>>
>
>
> _______________________________________________
> x3d-public mailing list
> x3d-public at web3d.org
> http://web3d.org/mailman/listinfo/x3d-public_web3d.org
>

-- 
Follow me! @thatvrguy