00:04 librasteve_ left 00:35 topnep left 00:37 topnep joined 01:05 kjp left 01:14 kylese left 01:15 kylese joined 01:23 kjp joined 01:30 sibl joined 01:39 sibl left 01:41 sibl joined 02:08 itaipu joined 02:15 kylese left, kylese joined 02:41 topnep left 02:42 topnep joined 03:29 sibl left 03:46 sibl joined 03:52 sibl left 03:57 sibl joined 04:04 sibl left 04:17 Aedil joined 04:46 topnep left 04:49 topnep joined 04:52 apogee_ntv left 04:53 apogee_ntv joined 05:17 sorenson left 05:19 sorenson joined 05:46 sibl joined 05:57 librasteve_ joined 06:11 Aedil left 06:23 abraxxa joined 06:53 lichtkind joined 07:42 Sgeo left 07:51 dakkar joined 07:52 dakkar_ joined 07:56 dakkar left 08:05 dakkar_ is now known as dakkar
disbot2 <librasteve> ok - all is good with 187.77.178.93:3001/b7c99d042386b4db...033ee71644 -- gonna run with that! (btw hiliting in the STRING box would be even awesomer) 08:43
09:34 Aedil joined 10:25 sibl left
disbot2 <librasteve> I have made an issue for @melezhik. s proposed raku.org example github.com/Raku/raku.org/issues/316 ... please can folks who are more knowledgeable than me (a low bar) on CI-CD take a minute to help whip that into shape... 10:43
11:04 topnep left, sibl joined 11:05 topnep joined
disbot2 <melezhik.> @librasteve thanks , replied to the gh ticket 11:20
11:34 sibl left 12:01 disbot2 left 12:02 disbot3 joined
ab5tract librasteve_: I've finally figured out what my first Air app should be 12:12
I'm excited to dive into all of the resources you created on learning the framework 12:21
goal: a sort of "syntax annotation explorer" which allows for inlining syntax explanations so that the main blog text doesn't have to try (and often fail) to explore specific language features used in the code snippet 12:23
Such explanations are also often repetitive to more expert users 12:24
timo how would it differ from just a standard html <summary> / <details> thingie? 12:25
would it be like a shared repository of explanations for common features like that?
ab5tract personally, I would probably write them mostly fresh each time. You could still write cool contextual details 12:31
re: summary/details - I would almost certainly use these tags in the component
timo right, makes sense to have the explanations refer directly to the examples they are attached to. that should make it much more useful in most cases 12:33
ab5tract however, what would be wild is if any user could highlight some code, which could then be parsed to RakuAST, and then mapped to their respective docs.raku.org pages
but that can be a 2.0 feature :) 12:34
if there were an editor interface, I could also see having pre-written text availalble for some features, which you could select to be appended as a sub-section of the summary tag set 12:36
12:40 BooK2 joined 12:42 BooK left, BooK2 is now known as BooK
disbot3 <librasteve> ab5tract: glad to hear it - just shout if you need help ... sure you have found the Air::Examples and the Air docs by now ... 13:07
13:09 topnep left
disbot3 <librasteve> fwiw it would be a nice little project to make Air::Plugin::Editor - I have in mind wrapping the JS version of the VSCode editor (that can then be passed a JSON hilite file) ... sorry I forget the name 13:09
<librasteve> then you can ping the server with an HTMX request and have some server side code render the view pane 13:10
13:13 topnep joined
ab5tract btw, any users of RIP , I've finally bumped the version information manually that will allow it to run on 2026.1 13:16
Next time I promise not to take so long 13:17
SmokeMachine librasteve_: isn't the string highlighting to you? usercontent.irccloud-cdn.com/file/....15.15.gif 13:18
disbot3 <librasteve> SMokeMachine: I mean hilite the DSL source code in the STRING pane (which should maybe called the INPUT?) - so that the tokens, rules (and literals) declared in Grammar are coloured in the STRING pane 13:20
SmokeMachine Another subject: MemoizedDOM running completely on the browser that was not working for several yers, ai fixed it! Is it working for anyone else? fco.github.io/MemoizedDOM/todo6.html 13:22
disbot3 <librasteve> yep - works for me (Safari) 13:23
SmokeMachine I was trying to use that same thing to not need a backend for that. 13:24
But that has runtime only… no eval… 13:25
librasteve_: when you hover the trace or the match it highlights the string (good idea renaming that to input) 13:26
I tested that on safari and on zen(Firefox) 13:28
(The Raku tuning on the browser, I mean)
lizmat librasteve finanalyst did something like that, no, for the documentation ? 13:31
disbot3 <librasteve> yeah I can see the TRACE, MATCH lights up - that's a lovely effect ... I am just thinking about two kinds of user - the coder that writes the Grammar & Actions to make a simple DSL and then the DSL author (think someone - a non coder - entering an invoice) that only cares about their DSL code input and the MADE output - for them (as you can see on langium site) it is a big benefit to have DSL code hilites so that they get 13:34
feedback if eg they misspell a tag
SmokeMachine Ah! You mean highlight the DSL as if it was “real code”? 14:40
disbot3 <librasteve> yes! - if your a DSL writer it is the real code ;-) 14:43
15:16 topnep left 15:17 topnep joined
librasteve_ notable6: weekly 15:23
notable6 librasteve_, 4 notes: gist.github.com/9de1c3c0a44007ecbb...0432044bf6 15:24
SmokeMachine librasteve_: is something like this what you want? usercontent.irccloud-cdn.com/file/.../image.png 16:37
usercontent.irccloud-cdn.com/file/.../image.png 16:46
16:58 dakkar left 17:09 abraxxa left 17:10 abraxxa joined 17:21 topnep left, topnep joined
SmokeMachine librasteve_: can you see if that's better now, please? 17:25
lizmat librasteve_: nice module: FStrings wonder if we need to add a ^ flag to sprintf to indicate centering :-) 17:34
SmokeMachine Nice module indeed... 17:43
ab5tract SmokeMachine: this looks amazing 18:03
SmokeMachine Thanks! :) 18:04
ab5tract librasteve_: it seems like the hilite example isn't working for me. I tried FF and Chrome usercontent.irccloud-cdn.com/file/.../image.png 18:17
SmokeMachine Odd would you mind to share a link? 18:20
lizmat PSA: you probably should get rid of Chrome, as it builds a local LLM of your behaviour 18:22
without your consent 18:23
ab5tract lizmat: I only ever use it to sanity check Firefox behavior :)
but its worth noting
SmokeMachine: this screenshot is what I see when I run 16-hilite : usercontent.irccloud-cdn.com/file/.../image.png 18:24
perryprog ab5tract, you can use Chromium for that to be fair 18:29
librasteve_ rakudoweekly.blog/2026/05/11/2026-...f-failure/ 18:35
notable6: weekly reset
notable6 librasteve_, Moved existing notes to “weekly_2026-05-11T18:35:23Z”
disbot3 <librasteve> SmokeMachine: yes - exactly that! brilliant 18:38
<librasteve> now into the nitpicky zone - on the pane layout - generally all is good for the power coder - sources on the left, outcomes on the right etc etc - but for the DSL editor would be good to have the ability to turn off both GRAMMAR and ACTIONS so that can have just two panes: INPUT on the left and MADE on the right - which I guess you can do with one more button in the top bar 18:42
<librasteve> and, that said - you can maybe add two buttons to give <DSL GRAMMAR ACTIONS INPUT TRACE MATCH MADE PRO> ... idea being that DSL turns on INPUT and MADE only and PRO turns on everything ... I think the top bottom ordering you have now is perfect BTW so not asking to change any of that ;-) 18:47
<librasteve> oh and I slightly prefer the colour scheme you had before (picky, picky!) 18:49
<librasteve> ab5tract - please can you check your zef installs include latest Hilite and Air::Plugin::Hilite? can you share the version numbers? 18:51
<librasteve> ab5tract: also please go which sass to check your (Dart SASS) compiler is in the path 18:55
<librasteve> mine works with Hilite:ver<0.2.7>:auth<zef:librasteve> and Air::Plugin::Hilite:ver<0.0.10>:auth<zef:librasteve> 18:56
SmokeMachine About the TPRC, where is Greenville? There are many places in the world where Greenville SC could be… for a minute I thought: I didn’t know there was a city called Greenville in Santa Catarina, Brazil… 19:00
lizmat SC = South Carolina
SmokeMachine Yeah… I discovered that after googling it… but it would be good if it was explicit… not everyone is good at USA’s geography… 19:02
[Coke] to be fair, is anyone not from the US going? 19:05
I'll mention it to the planning committee, though
SmokeMachine I went to the vegas one…
And I can only decide if I’m going if I know the country where it’s going to be… (I decided to not go to USA again any time soon) 19:07
[Coke] done. also commented on tpf.rapid.app/post/tprc-2026-gsp-a...mment-2582 19:09
SmokeMachine [Coke]: thanks 19:12
[Coke] sure, very reasonable request. :) 19:16
I'm sure Util will get it sorted.
SmokeMachine librasteve_: I’m not sure about the pro/dsl… but about making it possible to hide inpot and grammar I’ll work on that as soon as my daughter returns my computer… :) 19:20
19:25 topnep left 19:26 topnep joined
disbot3 <librasteve> lol 19:46
SmokeMachine librasteve_: usercontent.irccloud-cdn.com/file/.../image.png 19:50
20:09 johnjay joined 20:22 jjido joined 20:27 jjido left
SmokeMachine librasteve_: 187.77.178.93:3001/8bd971a94b4e827e...e77d2001e0 20:34
20:41 jjido joined 20:48 jjido left, jjido joined 20:55 abraxxa left 20:58 jjido left, jjido joined 21:18 ShimmerFairy left, ShimmerFairy joined
SmokeMachine librasteve_: usercontent.irccloud-cdn.com/file/.../image.png 21:28
21:38 vrurg_ left 21:54 vrurg joined 22:02 vrurg_ joined 22:05 vrurg left 22:33 Sgeo joined
apogee_ntv SmokeMachine: wormhole.app/R8OBlA#C1v92YkY4iqkRH9o9uQYhg Viewport scrolling nearly done 22:37
I had to patch notcurses itself but we're nearly there :D 22:38
SmokeMachine apogee_ntv: thank you very much! :) 22:42
22:50 elcaro left 22:52 elcaro joined 23:05 jjido left, jjido joined 23:13 itaipu left 23:15 jjido left 23:36 topnep left 23:37 topnep joined
apogee_ntv SmokeMachine: Selkie 0.7.0 released, you should see a 9th example app with the new widget 23:51

Powered by Cro and the Raku® Programming Language.

Please report any issues / comments / feature requests as an issue on App::Raku::Log.

Thank you!