X-Tag - a cross-browser web components library • Hacker News Board

Re: X-Tag - a cross-browser web components library

#41

Post by jblz » Sat, Jun 16, 2012, 4:45 AM UTC

dandonkulous wrote: post #16

If I can get it compatible with IE9, is that a big thing for people here? I don't think it would be too hard, thoughts?

Ideally, IE8 should be your minimum. There's a large contingent of web users still on Windows XP and IE9+ is not available for it. XP is in extended support until 2014-08-14 & yes, I'm counting down the days.

Re: X-Tag - a cross-browser web components library

#42

Post by [deleted] » Sat, Jun 16, 2012, 6:17 AM UTC

[deleted]

Re: X-Tag - a cross-browser web components library

#43

Post by neuroscr » Sat, Jun 16, 2012, 6:18 AM UTC

I think an oppertunity is lost here beig too js oriented. Instead of a data container (maybe json) that any serverside language could compile and prerender (thinking php). You could embed the required css/js and other possible resources in the container too.

Re: X-Tag - a cross-browser web components library

#44

Post by neuroscr » Sat, Jun 16, 2012, 6:25 AM UTC

I think an oppertunity is lost here beig too js oriented. Instead of a data container (maybe json) that any serverside language could compile and prerender (thinking php). You could embed the required css/js and other possible resources in the container too.

Re: X-Tag - a cross-browser web components library

#45

Post by hcarvalhoalves » Sat, Jun 16, 2012, 6:29 AM UTC

Ok, so is this like -vendor, but for HTML? Now browsers can implement their own components and, hopefully, push it as a standard?

Re: X-Tag - a cross-browser web components library

#46

Post by gliese1337 » Sat, Jun 16, 2012, 7:54 AM UTC

So, how does this impact Web Components? It seems to fill pretty much the exact same role, but with a rather different implementation. Should I expect to see this become the new standard because there's a polyfill for it so people will start using it already, or am I gonna end up with a bunch of legacy code when something else becomes standardized? And, again like Web Components, it's duplicating functionality that's been in Internet Explorer of all places since IE5.0 with DHTML Behaviors.

Re: X-Tag - a cross-browser web components library

#47

Post by rmc » Sat, Jun 16, 2012, 10:06 AM UTC

gliese1337 wrote: post #46

So, how does this impact Web Components? It seems to fill pretty much the exact same role, but with a rather different implementation. Should I expect to see this become the new standard because there's a polyfill for it so people will start using it already, or am I gonna end up with a bunch of legacy code when something else becomes standardized? And, again like Web Components, it's duplicating functionality that's…

I'm not sure, but I think this is 'Web Components'. The Mozilla page says so https://wiki.mozilla.org/Apps/x-tag

Re: X-Tag - a cross-browser web components library

#48

Post by dandonkulous » Sat, Jun 16, 2012, 11:13 AM UTC

gliese1337 wrote: post #46

So, how does this impact Web Components? It seems to fill pretty much the exact same role, but with a rather different implementation. Should I expect to see this become the new standard because there's a polyfill for it so people will start using it already, or am I gonna end up with a bunch of legacy code when something else becomes standardized? And, again like Web Components, it's duplicating functionality that's…

Actually I have been meeting with the W3 Web Components spec author for about 2 months while we readied this. The document.register method that was recently added to the spec was in large part a byproduct of X-Tag and when browsers implement it (Firefox soon) X-Tag will use it internally in browsers that support it, as a polyfill always does. Once one browser implements the JS mentod, X-Tag will truly polyfill the method on document as well.

Re: X-Tag - a cross-browser web components library

#49

Post by Navarr » Sat, Jun 16, 2012, 6:03 PM UTC

politician wrote: post #35

Navarr wrote: post #18

The steps seem pretty dishonest to me. Correct me if i'm wrong, but these are the real X-Tag steps: 1. Scour the web for a plugin 2. Add the plugin script include to your page 3. Copy/Type the new HTML tag 4. Customise the plugin with your own behavior 5. Wash, Rinse, & Repeat

X-Tags could be made self-hosting with a name registry and a simple "missing x-tag" tag. In other words, 1. Visit the registry for a tag. 2. Start using it in your markup. Assuming the registry's CDN is available, of course!

While I considered this approach to be plausible at first glance, it isn't.

For the tags to work for your users, they would also have to visit the registry for that tag.

Re: X-Tag - a cross-browser web components library

#50

Post by Navarr » Sat, Jun 16, 2012, 6:05 PM UTC

btown wrote: post #27

Navarr wrote: post #18

The steps seem pretty dishonest to me. Correct me if i'm wrong, but these are the real X-Tag steps: 1. Scour the web for a plugin 2. Add the plugin script include to your page 3. Copy/Type the new HTML tag 4. Customise the plugin with your own behavior 5. Wash, Rinse, & Repeat

Ah, but these are the X-Tag steps for 10 different tag types. 1. Scour the web for 1 plugin 2. Add 1 plugin script include to your page 3. Copy/type 10 new HTML tags (which you'd need to do anyways) 4. Add attributes, for which someone will release a Light Table plugin (eventually) to fetch standardized documentation. 5. Only repeat steps 3 and 4. I'm very excited to see something like NPM for tag handlers. We might…

No, you'd still have to scour the web for each individual library of tags. Since they require the .register() on the page, from what I understand.

Though your last part, with is fascinating and would greatly improve this.