Browse Source

Publishing

master
David Larlet 2 years ago
parent
commit
8300ff7c2f

+ 2
- 2
david/2021/11/02/index.html View File

@@ -63,7 +63,7 @@
<a href="/david/" title="Aller à l’accueil"><svg class="icon icon-home">
<use xlink:href="/static/david/icons2/symbol-defs.svg#icon-home"></use>
</svg> Accueil</a>
• <a rel="next" href="/david/2021/11/03/" title="Publication suivante : Composants">Suivant →</a>
</p>
</nav>
<hr>
@@ -81,7 +81,7 @@
<p class="center">
<a rel="prev" href="/david/2021/11/01/" title="Publication précédente : Inaccessible">← Précédent</a> •
<a href="/david/2021/" title="Liste des publications récentes">↑ En 2021</a>
• <a rel="next" href="/david/2021/11/03/" title="Publication suivante : Composants">Suivant →</a>
</p>
</nav>
</article>

+ 186
- 0
david/2021/11/03/index.html View File

@@ -0,0 +1,186 @@
<!doctype html><!-- This is a valid HTML5 document. -->
<!-- Screen readers, SEO, extensions and so on. -->
<html lang="fr">
<!-- Has to be within the first 1024 bytes, hence before the `title` element
See: https://www.w3.org/TR/2012/CR-html5-20121217/document-metadata.html#charset -->
<meta charset="utf-8">
<!-- Why no `X-UA-Compatible` meta: https://stackoverflow.com/a/6771584 -->
<!-- The viewport meta is quite crowded and we are responsible for that.
See: https://codepen.io/tigt/post/meta-viewport-for-2015 -->
<meta name="viewport" content="width=device-width,initial-scale=1">
<!-- Required to make a valid HTML5 document. -->
<title>Composants — David Larlet</title>
<meta name="description" content="Web Components had so much potential to empower HTML to do more, and make web development more accessible to non-programmers and easier for programmers. Remember how exciting it was every time we got new shiny HTML elements that actually do stuff? Remember how exciting it was to be able to do sliders, color pickers, dialogs, disclosure widgets straight in the HTML, without having to include any widget libraries?">
<!-- That good ol' feed, subscribe :). -->
<link rel="alternate" type="application/atom+xml" title="Feed" href="/david/log/">
<!-- Generated from https://realfavicongenerator.net/ such a mess. -->
<link rel="apple-touch-icon" sizes="180x180" href="/static/david/icons2/apple-touch-icon.png">
<link rel="icon" type="image/png" sizes="32x32" href="/static/david/icons2/favicon-32x32.png">
<link rel="icon" type="image/png" sizes="16x16" href="/static/david/icons2/favicon-16x16.png">
<link rel="manifest" href="/static/david/icons2/site.webmanifest">
<link rel="mask-icon" href="/static/david/icons2/safari-pinned-tab.svg" color="#07486c">
<link rel="shortcut icon" href="/static/david/icons2/favicon.ico">
<meta name="msapplication-TileColor" content="#f7f7f7">
<meta name="msapplication-config" content="/static/david/icons2/browserconfig.xml">
<meta name="theme-color" content="#f7f7f7" media="(prefers-color-scheme: light)">
<meta name="theme-color" content="#272727" media="(prefers-color-scheme: dark)">
<!-- Documented, feel free to shoot an email. -->
<link rel="stylesheet" href="/static/david/css/style_2021-01-20.css">
<!-- See https://www.zachleat.com/web/comprehensive-webfonts/ for the trade-off. -->
<link rel="preload" href="/static/david/css/fonts/triplicate_t4_poly_regular.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: light), (prefers-color-scheme: no-preference)" crossorigin>
<link rel="preload" href="/static/david/css/fonts/triplicate_t4_poly_bold.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: light), (prefers-color-scheme: no-preference)" crossorigin>
<link rel="preload" href="/static/david/css/fonts/triplicate_t4_poly_italic.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: light), (prefers-color-scheme: no-preference)" crossorigin>
<link rel="preload" href="/static/david/css/fonts/triplicate_t3_regular.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: dark)" crossorigin>
<link rel="preload" href="/static/david/css/fonts/triplicate_t3_bold.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: dark)" crossorigin>
<link rel="preload" href="/static/david/css/fonts/triplicate_t3_italic.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: dark)" crossorigin>
<script>
function toggleTheme(themeName) {
document.documentElement.classList.toggle(
'forced-dark',
themeName === 'dark'
)
document.documentElement.classList.toggle(
'forced-light',
themeName === 'light'
)
}
const selectedTheme = localStorage.getItem('theme')
if (selectedTheme !== 'undefined') {
toggleTheme(selectedTheme)
}
</script>

<body class="remarkdown h1-underline h2-underline h3-underline em-underscore hr-center ul-star pre-tick" data-instant-intensity="viewport-all">


<article>
<header>
<h1>Composants</h1>
</header>
<nav>
<p class="center">
<a rel="prev" href="/david/2021/11/02/" title="Publication précédente : Réflexion">← Précédent</a> •
<a href="/david/" title="Aller à l’accueil"><svg class="icon icon-home">
<use xlink:href="/static/david/icons2/symbol-defs.svg#icon-home"></use>
</svg> Accueil</a>
</p>
</nav>
<hr>


<blockquote lang="en">
<p>Web Components had so much potential to empower HTML to do more, and make web development more accessible to non-programmers and easier for programmers. Remember how exciting it was every time we got new shiny HTML elements that actually do stuff? Remember how exciting it was to be able to do sliders, color pickers, dialogs, disclosure widgets straight in the HTML, without having to include any widget libraries?</p>
<p>The promise of Web Components was that we’d get this convenience, but for a much wider range of HTML elements, developed much faster, as nobody needs to wait for the full spec + implementation process. We’d just include a script, and boom, we have more elements at our disposal!</p>
<p><cite><em><a href="https://lea.verou.me/2020/09/the-failed-promise-of-web-components/">The failed promise of Web Components</a></em> (<a href="/david/cache/2021/68cd338e37c60a8ed179222c6b1af01f/">cache</a>)</cite></p>
</blockquote>
<p>Le constat ne souffrait pas d’ambiguïté il y a un an. Qu’en est-il aujourd’hui&#8239;?</p>
<p>Il y a Simon Willison qui commente un <a href="https://til.simonwillison.net/web-components/understanding-single-file-web-component">Web Component tenant dans un seul fichier</a> (<a href="/david/cache/2021/8016f83f512107dd26e5780b08ea7305/">cache</a>). Et Dave Rupert qui <a href="https://daverupert.com/2021/10/html-with-superpowers/">parle de leurs super-pouvoirs</a> (<a href="/david/cache/2021/eb14bb1071cfe2bd952aa9280c6a4860/">cache</a>). Tout le monde espère pouvoir <a href="https://elisehe.in/2021/08/22/using-the-platform">les utiliser nativement</a> (<a href="/david/cache/2021/0f1f65d09181752916216e892bb192d8/">cache</a>).</p>
<p>En attendant, il y a des petits <em>frameworks</em> comme <a href="https://tonicframework.dev/">Tonic</a> ou <a href="https://lego.js.org/">Lego</a>. Des plus conséquents comme <a href="https://lit.dev/">Lit</a>.</p>
<p>Tout espoir n’est pas perdu. Juste <a href="/david/blog/2013/python-javascript/">une décennie</a>.</p>

<nav>
<p class="center">
<a rel="prev" href="/david/2021/11/02/" title="Publication précédente : Réflexion">← Précédent</a> •
<a href="/david/2021/" title="Liste des publications récentes">↑ En 2021</a>
</p>
</nav>
</article>


<hr>

<footer>
<p>
<a href="/david/" title="Aller à l’accueil"><svg class="icon icon-home">
<use xlink:href="/static/david/icons2/symbol-defs.svg#icon-home"></use>
</svg> Accueil</a> •
<a href="/david/log/" title="Accès au flux RSS"><svg class="icon icon-rss2">
<use xlink:href="/static/david/icons2/symbol-defs.svg#icon-rss2"></use>
</svg> Suivre</a> •
<a href="http://larlet.com" title="Go to my English profile" data-instant><svg class="icon icon-user-tie">
<use xlink:href="/static/david/icons2/symbol-defs.svg#icon-user-tie"></use>
</svg> Pro</a> •
<a href="mailto:david%40larlet.fr" title="Envoyer un courriel"><svg class="icon icon-mail">
<use xlink:href="/static/david/icons2/symbol-defs.svg#icon-mail"></use>
</svg> Email</a> •
<abbr class="nowrap" title="Hébergeur : Alwaysdata, 62 rue Tiquetonne 75002 Paris, +33184162340"><svg class="icon icon-hammer2">
<use xlink:href="/static/david/icons2/symbol-defs.svg#icon-hammer2"></use>
</svg> Légal</abbr>
</p>
<template id="theme-selector">
<form>
<fieldset>
<legend><svg class="icon icon-brightness-contrast">
<use xlink:href="/static/david/icons2/symbol-defs.svg#icon-brightness-contrast"></use>
</svg> Thème</legend>
<label>
<input type="radio" value="auto" name="chosen-color-scheme" checked> Auto
</label>
<label>
<input type="radio" value="dark" name="chosen-color-scheme"> Foncé
</label>
<label>
<input type="radio" value="light" name="chosen-color-scheme"> Clair
</label>
</fieldset>
</form>
</template>
</footer>
<script src="/static/david/js/instantpage-5.1.0.min.js" type="module"></script>
<script>
function loadThemeForm(templateName) {
const themeSelectorTemplate = document.querySelector(templateName)
const form = themeSelectorTemplate.content.firstElementChild
themeSelectorTemplate.replaceWith(form)

form.addEventListener('change', (e) => {
const chosenColorScheme = e.target.value
localStorage.setItem('theme', chosenColorScheme)
toggleTheme(chosenColorScheme)
})

const selectedTheme = localStorage.getItem('theme')
if (selectedTheme && selectedTheme !== 'undefined') {
form.querySelector(`[value="${selectedTheme}"]`).checked = true
}
}

const prefersColorSchemeDark = '(prefers-color-scheme: dark)'
window.addEventListener('load', () => {
let hasDarkRules = false
for (const styleSheet of Array.from(document.styleSheets)) {
let mediaRules = []
for (const cssRule of styleSheet.cssRules) {
if (cssRule.type !== CSSRule.MEDIA_RULE) {
continue
}
// WARNING: Safari does not have/supports `conditionText`.
if (cssRule.conditionText) {
if (cssRule.conditionText !== prefersColorSchemeDark) {
continue
}
} else {
if (cssRule.cssText.startsWith(prefersColorSchemeDark)) {
continue
}
}
mediaRules = mediaRules.concat(Array.from(cssRule.cssRules))
}

// WARNING: do not try to insert a Rule to a styleSheet you are
// currently iterating on, otherwise the browser will be stuck
// in a infinite loop…
for (const mediaRule of mediaRules) {
styleSheet.insertRule(mediaRule.cssText)
hasDarkRules = true
}
}
if (hasDarkRules) {
loadThemeForm('#theme-selector')
}
})
</script>
</body>
</html>

+ 2
- 0
david/2021/index.html View File

@@ -607,6 +607,8 @@
<h2><a href="/david/2021/11/02/">Réflexion</a> (2021-11-02)</h2>
<h2><a href="/david/2021/11/03/">Composants</a> (2021-11-03)</h2>
</main>



+ 15
- 0
david/2021/sources/2021-11-03 - Composants.md View File

@@ -0,0 +1,15 @@
# Composants

> [en] Web Components had so much potential to empower HTML to do more, and make web development more accessible to non-programmers and easier for programmers. Remember how exciting it was every time we got new shiny HTML elements that actually do stuff? Remember how exciting it was to be able to do sliders, color pickers, dialogs, disclosure widgets straight in the HTML, without having to include any widget libraries?
>
> The promise of Web Components was that we’d get this convenience, but for a much wider range of HTML elements, developed much faster, as nobody needs to wait for the full spec + implementation process. We’d just include a script, and boom, we have more elements at our disposal!
>
> <cite>*[The failed promise of Web Components](https://lea.verou.me/2020/09/the-failed-promise-of-web-components/)* ([cache](/david/cache/2021/68cd338e37c60a8ed179222c6b1af01f/))</cite>

Le constat ne souffrait pas d’ambiguïté il y a un an. Qu’en est-il aujourd’hui ?

Il y a Simon Willison qui commente un [Web Component tenant dans un seul fichier](https://til.simonwillison.net/web-components/understanding-single-file-web-component) ([cache](/david/cache/2021/8016f83f512107dd26e5780b08ea7305/)). Et Dave Rupert qui [parle de leurs super-pouvoirs](https://daverupert.com/2021/10/html-with-superpowers/) ([cache](/david/cache/2021/eb14bb1071cfe2bd952aa9280c6a4860/)). Tout le monde espère pouvoir [les utiliser nativement](https://elisehe.in/2021/08/22/using-the-platform) ([cache](/david/cache/2021/0f1f65d09181752916216e892bb192d8/)).

En attendant, il y a des petits *frameworks* comme [Tonic](https://tonicframework.dev/) ou [Lego](https://lego.js.org/). Des plus conséquents comme [Lit](https://lit.dev/).

Tout espoir n’est pas perdu. Juste [une décennie](/david/blog/2013/python-javascript/).

+ 2
- 1
david/index.html View File

@@ -77,7 +77,8 @@
<h3>Novembre 2021</h3>
<p>
<a href="/david/2021/11/01/">Inaccessible</a>,
<a href="/david/2021/11/02/">Réflexion</a>.
<a href="/david/2021/11/02/">Réflexion</a>,
<a href="/david/2021/11/03/">Composants</a>.
</p>

+ 20
- 19
david/log/index.xml View File

@@ -6,13 +6,32 @@
<link href="https://larlet.fr/david/" rel="alternate" type="text/html" />
<link href="https://larlet.fr/david/log/" rel="self" />
<id>https://larlet.fr/david/</id>
<updated>2021-11-09T12:00:00+01:00</updated>
<updated>2021-11-10T12:00:00+01:00</updated>
<author>
<name>David Larlet</name>
<uri>https://larlet.fr/david/</uri>
</author>
<rights>Copyright (c) 2004-2021, David Larlet</rights>
<entry xml:lang="fr">
<title type="html">Composants</title>
<link href="https://larlet.fr/david/2021/11/03/" rel="alternate" type="text/html" />
<updated>2021-11-03T12:00:00+01:00</updated>
<id>https://larlet.fr/david/2021/11/03/</id>
<summary type="html">

&lt;blockquote lang=&quot;en&quot;&gt;
&lt;p&gt;Web Components had so much potential to empower HTML to do more, and make web development more accessible to non-programmers and easier for programmers. Remember how exciting it was every time we got new shiny HTML elements that actually do stuff? Remember how exciting it was to be able to do sliders, color pickers, dialogs, disclosure widgets straight in the HTML, without having to include any widget libraries?&lt;/p&gt;
&lt;p&gt;The promise of Web Components was that we’d get this convenience, but for a much wider range of HTML elements, developed much faster, as nobody needs to wait for the full spec + implementation process. We’d just include a script, and boom, we have more elements at our disposal!&lt;/p&gt;
&lt;p&gt;&lt;cite&gt;&lt;em&gt;&lt;a href=&quot;https://lea.verou.me/2020/09/the-failed-promise-of-web-components/&quot;&gt;The failed promise of Web Components&lt;/a&gt;&lt;/em&gt; (&lt;a href=&quot;https://larlet.fr/david/cache/2021/68cd338e37c60a8ed179222c6b1af01f/&quot;&gt;cache&lt;/a&gt;)&lt;/cite&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Le constat ne souffrait pas d’ambiguïté il y a un an. Qu’en est-il aujourd’hui&amp;#8239;?&lt;/p&gt;
&lt;p&gt;Il y a Simon Willison qui commente un &lt;a href=&quot;https://til.simonwillison.net/web-components/understanding-single-file-web-component&quot;&gt;Web Component tenant dans un seul fichier&lt;/a&gt; (&lt;a href=&quot;https://larlet.fr/david/cache/2021/8016f83f512107dd26e5780b08ea7305/&quot;&gt;cache&lt;/a&gt;). Et Dave Rupert qui &lt;a href=&quot;https://daverupert.com/2021/10/html-with-superpowers/&quot;&gt;parle de leurs super-pouvoirs&lt;/a&gt; (&lt;a href=&quot;https://larlet.fr/david/cache/2021/eb14bb1071cfe2bd952aa9280c6a4860/&quot;&gt;cache&lt;/a&gt;). Tout le monde espère pouvoir &lt;a href=&quot;https://elisehe.in/2021/08/22/using-the-platform&quot;&gt;les utiliser nativement&lt;/a&gt; (&lt;a href=&quot;https://larlet.fr/david/cache/2021/0f1f65d09181752916216e892bb192d8/&quot;&gt;cache&lt;/a&gt;).&lt;/p&gt;
&lt;p&gt;En attendant, il y a des petits &lt;em&gt;frameworks&lt;/em&gt; comme &lt;a href=&quot;https://tonicframework.dev/&quot;&gt;Tonic&lt;/a&gt; ou &lt;a href=&quot;https://lego.js.org/&quot;&gt;Lego&lt;/a&gt;. Des plus conséquents comme &lt;a href=&quot;https://lit.dev/&quot;&gt;Lit&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Tout espoir n’est pas perdu. Juste &lt;a href=&quot;https://larlet.fr/david/blog/2013/python-javascript/&quot;&gt;une décennie&lt;/a&gt;.&lt;/p&gt;
&lt;hr/&gt;&lt;p&gt;&lt;a href=&quot;mailto:david@larlet.fr&quot;&gt;Réagir ?&lt;/a&gt;&lt;/p&gt;</summary>
</entry>
<entry xml:lang="fr">
<title type="html">Réflexion</title>
<link href="https://larlet.fr/david/2021/11/02/" rel="alternate" type="text/html" />
@@ -672,24 +691,6 @@
&lt;p&gt;Les pensées et fragments de mémoire publiés ici me semblent être difficilement falsifiables à mon insu. J’ai un historique, sur plusieurs machines, etc. En revanche pour des photos — qui plus est stockées sur l’ordinateur d’un·e autre — c’est bien plus compliqué à identifier et à prouver.&lt;/p&gt;
&lt;hr /&gt;
&lt;p&gt;En retournant le problème, cela pourrait être un métier d’aller effacer de mauvais souvenirs… plus ou moins à la demande de la personne.&lt;/p&gt;
&lt;hr/&gt;&lt;p&gt;&lt;a href=&quot;mailto:david@larlet.fr&quot;&gt;Réagir ?&lt;/a&gt;&lt;/p&gt;</summary>
</entry>
<entry xml:lang="fr">
<title type="html">Atelier</title>
<link href="https://larlet.fr/david/2021/09/25/" rel="alternate" type="text/html" />
<updated>2021-09-25T12:00:00+01:00</updated>
<id>https://larlet.fr/david/2021/09/25/</id>
<summary type="html">
&lt;p&gt;J’ai motivé une rencontre autour des &lt;a href=&quot;https://larlet.fr/david/2021/06/19/&quot; title=&quot;Échecs&quot;&gt;échecs&lt;/a&gt; entre enfants de sa classe. Quelques heures au parc et je peux déjà identifier qu’il y a trop d’attentes de la part des parents pour pouvoir aménager un espace d’apprentissage qui soit enthousiasmant.&lt;/p&gt;
&lt;p&gt;Comment divertir leur attention de manière non violente&amp;#8239;? Si je plaide en faveur d’un moment entre jeunes, quelle devient alors ma place&amp;#8239;? De quelle façon discuter de positions sans que les joueur·euses se sentent jugé·es&amp;#8239;?&lt;/p&gt;
&lt;p&gt;Quelques idées&amp;nbsp;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;faire jouer les adultes entre ell·eux, à côté&amp;#8239;;&lt;/li&gt;
&lt;li&gt;imaginer de nouvelles façons d’équilibrer les niveaux&amp;#8239;;&lt;/li&gt;
&lt;li&gt;me retenir de jouer.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Il n’y a pas que les jeunes qui ont à apprendre de leurs propres échecs…&lt;/p&gt;
&lt;hr/&gt;&lt;p&gt;&lt;a href=&quot;mailto:david@larlet.fr&quot;&gt;Réagir ?&lt;/a&gt;&lt;/p&gt;</summary>
</entry>

Loading…
Cancel
Save