Aral Balkan
Oh I am very excited about this! Just implemented very neat support for conditionals in Kitten¹ (not in main yet).
Kitten embraces vanilla HTML, JS, and CSS as much as possible but this little extension to HTML improves authoring/readability so much that I’ve made an exception. The <then> and <else> tags are optional, by the way, so the following is perfectly valid markup:
<if ${true}>
<strong>This is true!</strong>
</if>
Enjoy! (Soon.) 💕
Aral Balkan
Right, I just made the end tags for <then> and <else> optional so now you can also write your conditionals like this! :)
Aral Balkan
@bobwyman Hey Bob, as I mentioned in the post, the <then> tag is optional (as is the <else> tag). They’re there simply for clarity of intent during authoring.
(Insofar as parsing is concerned, as long as your <if> tag has two children or less, the first child will be the true condition and the the second child will be the false condition. I also just made the closing tags optional for those.)
If-else is supported via nesting, which feels natural to me given the context.
Bob Wyman
@aral Why do you have a <then> tag? Does it have any semantics? (Note: I see that it would reduce the number of children of the <if> tag and thus might slightly increase processing speed, but compiler sugar like this also tends to increase the size and apparent complexity of files.)
Also, will you be supporting<else-if>?
Niels Abildgaard
@martijn @aral they do, tho. <br> is valid HTML, but perhaps not valid XHTML – but XHTML was abandoned with HTML5.
Aral Balkan
@nielsa @martijn Yeah, Kitten uses HTML for authoring (not XHTML or JSX).
Optionally-closed tags are present elsewhere in HTML. e.g.,
<p>This is
<p>perfectly valid
<p>HTML (but please don’t do it even if you can).
But by all means, if it reads better for your with the end tags, then please do use them (hence the *optional* bit) :)
Sexybiggetje🐖
@aral
I'm not fond of that syntax. Saves some typing,. It it's only logical for programmers. The rest of your html document don't support that style.
Editor's have autoclosing tags already to fix the amount of typing problem, right?
Aral Balkan
@nielsa Yep, @zachleat showed me on here a little while back I believe… very neat but Kitten apps don’t have a build stage by design :)
Niels Abildgaard
@aral Have you seen the 11ty team's work on .webc btw?
Similar in doing templating/leaning into web standards, but a different approach? I think there could be some interesting cross-pollination here..
cc @zachleat
Aral Balkan
@nielsa @martijn PS. This is not in main yet. I’m going to merge it in either later today or over the weekend, after I’ve had a chance to update the examples and the documentation and smoke test it in Domain (https://codeberg.org/domain/app).
Aral Balkan
@severak Haha, good old ColdFusion. I got my first death threat online when I wrote an article in 2009 titled “Why learning ColdFusion today is a waste of time.” (https://ar.al/1864/) :)
PS. Went down a rabbit hole on Adobe’s site just now because apparently it’s still going. And, to be fair, it did do some very neat things back in the day :) (Still, there is zero reason to use a proprietary application server in this day and age but hey, enterprises gonna enterprise, amirite?)
Severák
@aral I got war flashbacks on using Adobe ColdFusion(tm). 😺
Bob Wyman
@aral In the example below, the <if> tag has three children, the third child is an <else> tag. Do you simply assume "First Child is for True, Second is for False?" or do you actually look for the <else> tag?
```
<if ${False}>
<span>Foo</span>
<span>Bar</span>
<else>
this is else
</else>
</if>
```
Aral Balkan
@bobwyman First child is true, second child is false. As long as your if tag has one or two children, it‘s valid. Otherwise, you get a syntax error.
０７６萌ＳＮＳ is a social network, courtesy of ０７６. It runs on GNU social, version 2.0.2-beta0, available under the GNU Affero General Public License.
All ０７６萌ＳＮＳ content and data are available under the Creative Commons Attribution 3.0 license.