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
1) Mozilla is generating a stock set of components that you wont have to "scour" for. 2) The components can be easily included using an app bootstrap builder that the Mozilla Marketplace dev hub will feature 3) You write the tags like you would any other in HTML, there is not complex copy or paste operation... 4) You can use components without modifying them, #4 is a red herring Another huge benefit: the polyfill is…
X-Tag - a cross-browser web components library
21–30 of 54 posts
Re: X-Tag - a cross-browser web components library
#22The 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
1) Mozilla is generating a stock set of components that you wont have to "scour" for. 2) The components can be easily included using an app bootstrap builder that the Mozilla Marketplace dev hub will feature 3) You write the tags like you would any other in HTML, there is not complex copy or paste operation... 4) You can use components without modifying them, #4 is a red herring Another huge benefit: the polyfill is…
Re: X-Tag - a cross-browser web components library
#23Earlier quoted context omitted.
1) Mozilla is generating a stock set of components that you wont have to "scour" for. 2) The components can be easily included using an app bootstrap builder that the Mozilla Marketplace dev hub will feature 3) You write the tags like you would any other in HTML, there is not complex copy or paste operation... 4) You can use components without modifying them, #4 is a red herring Another huge benefit: the polyfill is…
Maybe I'm misunderstanding, doesn't this mean I can use x-foo without including its js if x-foo is in the marketplace? That would be amazing.
Re: X-Tag - a cross-browser web components library
#24Earlier quoted context omitted.
Maybe I'm misunderstanding, doesn't this mean I can use x-foo without including its js if x-foo is in the marketplace? That would be amazing.
The Marketplace is just the "app store" -- it's where you buy apps. You can run the apps on any supported HTML5 device after buying them. So the supported device would not provide anything more than a browser rendering engine (and some navigator.* JS methods). It won't include x-tags.
I'm confused about what he meant about the marketplace having a "bootstrap builder" for x-tags.
Re: X-Tag - a cross-browser web components library
#25Earlier quoted context omitted.
1) Mozilla is generating a stock set of components that you wont have to "scour" for. 2) The components can be easily included using an app bootstrap builder that the Mozilla Marketplace dev hub will feature 3) You write the tags like you would any other in HTML, there is not complex copy or paste operation... 4) You can use components without modifying them, #4 is a red herring Another huge benefit: the polyfill is…
@MatthewPhillips - That's not what I meant. Mozilla will offer a bootstrap builder with which you can add as many of the stock tags/components as you want to your app's pages. It will output a skeleton of an app that is development-ready. We will be actively working on getting the stock set of components prominently offered in other app bootstraps and store dev areas.
Re: X-Tag - a cross-browser web components library
#26Earlier quoted context omitted.
1) Mozilla is generating a stock set of components that you wont have to "scour" for. 2) The components can be easily included using an app bootstrap builder that the Mozilla Marketplace dev hub will feature 3) You write the tags like you would any other in HTML, there is not complex copy or paste operation... 4) You can use components without modifying them, #4 is a red herring Another huge benefit: the polyfill is…
Maybe I'm misunderstanding, doesn't this mean I can use x-foo without including its js if x-foo is in the marketplace? That would be amazing.
Re: X-Tag - a cross-browser web components library
#27The 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
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 even see something like tags that transform into tags that pull things like jQuery from CDNs. And if they use either the NPM model (unilateral publishing) or the Homebrew model (pull requests), and if they are half-decent moderators (to avoid squatting on common tags if they use the NPM model), I can see this transforming the way we write websites (although I'll always be a browserify fan myself).
Re: X-Tag - a cross-browser web components library
#28Earlier quoted context omitted.
The Marketplace is just the "app store" -- it's where you buy apps. You can run the apps on any supported HTML5 device after buying them. So the supported device would not provide anything more than a browser rendering engine (and some navigator.* JS methods). It won't include x-tags.
I'm aware, I submitted an app already :-). I'm confused about what he meant about the marketplace having a "bootstrap builder" for x-tags.
So the bootstrap gets you up and running quickly, and the builder is a web-based tool that lets you optimize your build of x-tags when it goes into production.
Re: X-Tag - a cross-browser web components library
#29The 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