[00:01] *** RaycatWhoDat joined [00:02] *** reportable6 left [00:04] *** reportable6 joined [00:23] *** RaycatWhoDat left [00:34] *** guifa left [01:34] *** bloatable6 left [01:34] *** committable6 left [01:34] *** notable6 left [01:34] *** linkable6 left [01:34] *** greppable6 left [01:34] *** squashable6 left [01:34] *** evalable6 left [01:34] *** reportable6 left [01:34] *** nativecallable6 left [01:34] *** benchable6 left [01:34] *** releasable6 left [01:34] *** shareable6 left [01:34] *** sourceable6 left [01:34] *** coverable6 left [01:34] *** bisectable6 left [01:34] *** tellable6 left [01:34] *** unicodable6 left [01:34] *** statisfiable6 left [01:34] *** quotable6 left [01:35] *** quotable6 joined [01:35] *** sourceable6 joined [01:35] *** bisectable6 joined [01:35] *** committable6 joined [01:35] *** unicodable6 joined [01:35] *** linkable6 joined [01:35] *** squashable6 joined [01:35] *** benchable6 joined [01:35] *** statisfiable6 joined [01:36] *** coverable6 joined [01:36] *** reportable6 joined [01:36] *** releasable6 joined [01:36] *** bloatable6 joined [01:36] *** evalable6 joined [01:36] *** notable6 joined [01:37] *** shareable6 joined [01:37] *** nativecallable6 joined [01:38] *** greppable6 joined [01:38] *** tellable6 joined [01:59] *** guifa joined [02:17] *** frost joined [03:17] *** coverable6 left [03:17] *** squashable6 left [03:17] *** bisectable6 left [03:17] *** releasable6 left [03:17] *** greppable6 left [03:17] *** committable6 left [03:17] *** evalable6 left [03:17] *** quotable6 left [03:17] *** reportable6 left [03:17] *** sourceable6 left [03:17] *** notable6 left [03:17] *** shareable6 left [03:17] *** tellable6 left [03:17] *** bloatable6 left [03:17] *** linkable6 left [03:17] *** unicodable6 left [03:17] *** statisfiable6 left [03:17] *** nativecallable6 left [03:17] *** benchable6 left [03:17] *** Doc_Holliwood joined [03:17] *** reportable6 joined [03:17] *** notable6 joined [03:17] *** tellable6 joined [03:18] *** committable6 joined [03:18] *** shareable6 joined [03:18] *** linkable6 joined [03:18] *** releasable6 joined [03:18] *** benchable6 joined [03:18] *** statisfiable6 joined [03:19] *** bloatable6 joined [03:19] *** squashable6 joined [03:19] *** coverable6 joined [03:19] *** quotable6 joined [03:19] *** sourceable6 joined [03:19] *** nativecallable6 joined [03:19] *** bisectable6 joined [03:19] *** unicodable6 joined [03:20] *** greppable6 joined [03:20] *** evalable6 joined [03:23] *** RandalSchwartz left [03:41] *** yewscion left [03:55] *** swaggboi left [04:10] *** swaggboi joined [04:16] *** guifa left [04:18] *** guifa joined [04:34] *** squashable6 left [04:34] *** squashable6 joined [04:37] *** alarix joined [04:47] *** AlexDaniel left [04:47] *** demostanis[m] left [04:47] *** juanfra left [04:47] *** ComplYue[m] left [04:47] *** CIAvash left [04:47] *** tyil[m] left [04:47] *** juanfra joined [04:48] *** guifa left [04:48] *** guifa joined [04:49] *** demostanis[m] joined [04:49] *** AlexDaniel joined [04:50] *** tyil[m] joined [04:50] *** ComplYue[m] joined [04:50] *** CIAvash joined [05:05] *** guifa left [05:08] *** guifa joined [05:17] *** Doc_Holliwood left [05:19] *** guifa left [05:31] *** jmcgnh left [05:33] *** jmcgnh joined [05:36] *** Sgeo left [06:04] *** reportable6 left [06:06] *** reportable6 joined [06:28] *** stoned75_ left [06:30] *** stoned75 joined [06:32] *** ufobat_ joined [07:09] *** alarix left [07:39] *** stoned75 left [07:54] *** morayj joined [08:01] *** stoned75 joined [08:10] *** Doc_Holliwood joined [08:49] *** patrickb joined [09:05] weekly: https://p6steve.wordpress.com/2021/06/09/can-raku-replace-html/ [09:05] lizmat, Noted! (weekly) [09:06] title hints about a category error :-| [09:07] that's a useful term [09:08] I feel like I'm constantly spotting logical errors in things people do, and I'm always sure I'm not the first one to see this sort of thing but I have no idea how to express it! [09:32] I'd suggest reading the article [09:33] I guess a better title would have been: "Can writing Raku replace writing HTML" [09:33] do you agree? [09:36] *** Woodi_ is now known as Woodi [09:37] Feels like one of several recent articles that are certainly interesting from an academic/learning exercise perspective, but I'm not sure I'd want to combine these worlds [09:38] TBH this is largely because whenever I write HTML it always turns out to be way more complex than I expected [09:39] Well, fwiw, Cro and specifically Cro::WebApp::Template *are* combining these worlds [09:40] I guess, starting with Computer Based Training in the late 70s, has made me more aware of the frontend aspects of programs than of the backend :-) [09:43] I have yet to find a templating system that I actually find helps me to write HTML! [09:43] But this is because most of them are actually *text* processing systems [09:43] and none of them acknowledges the structure of HTML and works with it [09:43] *** stoned75 left [09:43] This HTML-in-Raku concept could definitely address that [09:43] *** Doc_Holliwood left [09:45] I did a little lisp-syntax-ish html templating thing at one point [09:45] unlike other similar things, it didn't have a concept of interpolation. Instead, everything was represented using functions [09:46] What I like about Cro::WebApp::Template, is that it actually all becomes executable code at some point [09:46] *** Doc_Holliwood joined [09:46] e.g.: [p this [em is] text]. That calls the function 'em' with the word 'is' as an argument, then argues the words 'this ' 'is' ' text' to 'p' [09:46] so you can also call normal (computational) functions, but it's completely uniform [09:47] this is essentially what the § term does in the article [09:47] *** stoned75 joined [09:47] yes but it's ugly, you have to put quotation marks around everything :) [09:48] you mean the part ? [09:49] §

(:id, 'Your Message (required)'). There are quotation marks around 'Your Message (required)' [09:50] which makes it more of a pain to e.g. emphasize a single word in long-form prose [09:52] well, you could e.g. apply markdown semantics on strings in the § handler [09:53] §

(:id, 'Your Message (*required*)'). [09:53] or just do: [09:53] §

(:id, 'Your Message (required)'). [09:53] perhaps ? [09:57] *** patrickb left [10:02] lizmat: Does that mean there is, in theory, scope for Cro::WebApp::Template to have a "Skip this tag" function? Such that, if you've already started a tag, and later you find it's not required, you can bail on the whole thing? [10:02] This is one of two features I really need any HTML template language to offer me [10:02] The other one is a wrap-this-tag-if-condition sort of feature [10:03] well, Cro::WebApp has ... [10:04] but for wrapping something, you'd need two of them atm [10:04] afaik [10:05] Altreus: could you give an example, so we're on the same page ? [10:08] well basically what you said [10:09] I never want to have to do something like [% IF link %][% END %] [% IF link %][% END %] [10:09] I would MUCH rather do [% IF link %]wrap [% END %] [10:10] tt2 syntax cos I'm not familiar enough with cro's :) [10:10] But if your template language is for HTML and not just text in general, you can make use of the fact that you can assume a DOM [10:12] A good example would be something like:

[10:12] then you get page_number except for the current page, as is common on many pagination navs [10:13] where does the come from ? [10:13] or did you mean s/a/div ? [10:14] *** holly_ left [10:15] fwiw, I could envision something like: [10:16] <§div $condition>foobar [10:16] generating "
foobar
" if $condition is true, and "foobar" if it is false [10:20] another common thing is: generate an