🦋 Welcome to the MAIN() IRC channel of the Raku Programming Language (raku.org). Log available at irclogs.raku.org/raku/live.html . If you're a beginner, you can also check out the #raku-beginner channel!
Set by lizmat on 6 September 2022.
00:06 lichtkind left 00:54 kst`` left 01:16 kst`` joined 01:18 kjp left 01:19 kjp joined 01:20 kjp left, kjp joined 01:21 hulk joined, kylese left 02:05 apac joined 02:15 hulk left, kylese joined 02:44 apac left 02:55 Aedil joined 03:30 sourceable6 left, bloatable6 left, nativecallable6 left, committable6 left, linkable6 left, notable6 left, bisectable6 left, coverable6 left 03:31 unicodable6 left, unicodable6 joined, notable6 joined, coverable6 joined, bisectable6 joined, sourceable6 joined, linkable6 joined 03:32 bloatable6 joined, nativecallable6 joined 03:39 unicodable6 left, committable6 joined 03:40 bloatable6 left, nativecallable6 left, notable6 left, sourceable6 left, notable6 joined, nativecallable6 joined, sourceable6 joined, bloatable6 joined, unicodable6 joined
SmokeMachine weekly: dev.to/fco/a-raku-cromponent-to-re...kuast-2dhn 04:10
notable6 SmokeMachine, Noted! (weekly)
tellable6 2025-04-12T03:03:40Z #raku <Xliff> SmokeMachine Yes, but translate is a mouthful, given the number of nodes it has to cover. I'll see if there are any not covered by the existing alpha MySQL driver.
SmokeMachine .tell Xliff in theory, CommonSQL driver should handle most of (if not all) of them... 04:12
tellable6 SmokeMachine, I'll pass your message to Xliff
04:26 stanrifkin joined 04:30 kylese left 04:32 kylese joined 05:24 stanrifkin left 05:30 kylese left 05:32 kylese joined 05:44 Aedil left 05:51 Aedil joined 06:44 Sgeo left 06:55 derpydoo joined 08:03 dakkar joined 08:48 jpn joined 09:53 lizmat left 11:05 amaz0n joined 11:07 derpydoo left 11:12 lizmat joined 11:22 lizmat left 11:27 liztormato joined 11:33 liztormato left 11:52 jpn left 12:34 melezhik joined
melezhik o/ 12:34
tellable6 2025-04-09T15:32:23Z #raku <tonyo> melezhik: can you send me the dist and tell me, how are you bundling it?
melezhik yet another solution for SO issue using Raku and Sparrow - stackoverflow.com/a/79573154/5147708 , please vote IF you like it, thanks 12:35
.tell tonyo: I've already figured this out, looks like ( like i said ) this is my working environment issue, no problem from home laptop, anyway, thanks 12:36
tellable6 melezhik, I'll pass your message to tonyo
12:46 melezhik left 13:15 JimmyZhuo joined 13:21 jpn joined
tbrowder m: use Test; dies-ok { die "take that!" } 13:42
camelia ok 1 -
tbrowder m: sub f { die "arg"}; dies-ok { f } 13:46
camelia ===SORRY!=== Error while compiling <tmp>
Undeclared routine:
dies-ok used at line 1
tbrowder forgot use Test
13:47 JimmyZhuo left
tbrowder m: use Test; sub f {die "arg"}; dies-ok {f} 13:48
camelia ok 1 -
14:17 amaz0n left
SmokeMachine Hi! If anyone would like to give me their opinions: dev.to/fco/a-raku-cromponent-to-re...kuast-2dhn 14:27
[Coke] SmokeMachine: I would suggest showing a screen shot of some of the formatted code. 14:46
tellable6 2025-04-14T13:48:38Z #raku-dev <finanalyst> [Coke] i just sent you an email
SmokeMachine [Coke]: That makes sense… I added on README, but I forgot to add on the post. Good idea, thanks! 14:49
I don’t think it got very pretty… I just choose random colors… but because the user can create a css file an add any color they want, I think that’s ok for now… 14:51
14:56 lichtkind joined
[Coke] If you didn't mention that you can customize the colors, maybe add that too. 14:57
librasteve SmokeMachine: I just caught you RakuCode post - this is AWESOME(!) - thanks for making this. It makes it even more vital that Air can consume Cromponents since otherwise I will have to write it myself (actually I was considering Rainbow - but I was thinking that RakuAST in the mix meant that this would need to change down the line, RakuCode looks like a home run to me. 15:50
^^ this is a term used in Rounders btw 15:51
I have a couple of thoughts relating to Cromponent in general. 15:54
Would you be amenable to moving Cromponent into the Cro organisation as a Cro repo? Why? Well I think Cromponent is the clear choice for Cro components and to my mind it makes sense for it to be part of the Cro ecosystem. Anyway, your call. If you are happy then we can propose to add you to the Cro org members too. Obviously if you are in agreement then we can take the idea to the "powers that be" to get their
approval.
Second, unrelated thought. I am thinking that there would be many Cromponents in the future and that from a module curation point of view, it would make sense to call them names like Cromponent::Table or Cromponent::RakuCode or Cromponent::BaseLib::Widget::LightDark ... this is really just obsessive and preemptive tidyness creeping in - so again just an idea. 15:57
16:21 stanrifkin joined 16:38 yeahitsme joined 16:46 dakkar left
SmokeMachine librasteve: hi, thanks. I’m still not sure about RakuCode because it does not show YOUR code, but the deparsed version of your code’ RakuAST… so, for example, your indentation will probably be messed up (as my example on README was), if you use &[+] it will be replaced with &infix:<+>, etc… but I think that’s a good start at least… 17:22
librasteve oh, I see - the use cases I have in mind would be eg for raku documentation, so that notches RakuCode down a peg - nice all the same! 17:26
SmokeMachine I wouldn’t oppose to move cromponents to Cro organisation, but is yous suggestion for the organisation only or also the namespace? Are you suggesting something like Cro::Cromponent? In that case I would probably change its name to something like Cro::Component, or to maintain the joke: Cro::mponet (that doesn’t look good… on my mind it “sounded” better…). But I don’t like Cro::Cromponent 17:27
librasteve are there any unambiguously good reasons to have highlit RakuAST (eg would that be a handy tool to illustrate RakuAST "how tos" maybe?
SmokeMachine librasteve: sorry, I couldn’t understand your RakuAST question… 17:29
librasteve I agree that both Cro::Component and Cro::Mponent would be (much) worse than Cromponent - so (looks at org dashboard page) suggest repo name is cromponent and the modules name stays Cromponent
melezhik. If github.com/nxadm/rakudo-pkg is supported? I am helping rocky Linux team with installing Rakudo via conventional way of rpm packages . I see the last commit is 3 months ago, and probably does not include the latest versions 17:31
SmokeMachine About Cromponent::* components, I think that’s would work, but maybe too long to be used on templates…
And Cromponent already have “native” components with no Cromponent:: prefix: github.com/FCO/Cromponent/tree/main/lib of course it can be changed… but that’s how it is now… 17:34
17:34 jpn left
librasteve lemme rephrase more bluntly - RakuCode is not suitable for code highlighting, so would be a bad choice for a raku examples webpage, however it is ideal where you are working with RakuASt, for example a webpage that does XXXX <== is this phrase true for some XXXX, would you say it is true for XXXX == a webpage that shows examples of how to use RakuAST 17:34
or maybe some other XXXX? 17:35
yeah - take example StyledDiv I suggest to put the StyledDiv.rakumod file inside the Cromponent directory and namespace it as Cromponent::StyledDiv ... that's really not too long in the context of other Cro names - Cro::WebApp::Template for example 17:38
SmokeMachine I think I should rename RakuCode to something like RakuASTCode… but I’m not sure yet…
I feel that too long to: <:use Cromponent::Boilerplate> 17:39
librasteve well would be nice to have actual code highlighting based on Rainbow ;-) and that's gonna need a name also]
SmokeMachine: these are just suggestions from me - I 100% trust your instincts and decisions - but I do suggest you think about a future with 100s of cromponents ... maybe in libraries - the raku use and module management system is great for sharing, bundling and packaging - but the day you release any new module, its name is frozen for ever ... so if we get an extensible pattern now we maye have to deprecate a 17:44
handful of module names, but then the namespace will be cleaner for you and for other cromponent authors
patrickb SmokeMachine: Are you aware of the RakuAST based syntax highlighter lizmat and finanalyst developed?
If not I think it'd be a good idea to get in contact, so you can learn from their experience.
librasteve * well that s 86401 secs 17:46
patrickb: ++ 17:47
SmokeMachine patrickb: do you mean DEPARSE accepting a role for highlighting? If so, yes and I use it… otherwise: no and if you could send a link, I’ll take a look… 17:48
18:31 lizmat joined, lizmat left, lizmat joined 18:45 jpn joined
patrickb I'm not entirely sure, but I think that's it. Finanalyst built a highlighter around this. He used it for a while on docs.raku.org. 19:04
19:26 jpn left 19:36 jpn joined 19:39 Aedil left 20:04 jpn left 20:07 yeahitsme left 20:13 jpn joined 20:18 jpn left 20:50 jpn joined
SmokeMachine patrickb: github.com/FCO/RakuCode/blob/2ca32...akumod#L14 21:12
tbrowder i'm having trouble with testing with dies-ok. it seems 21:25
to captures some "die" statements and not others
ugexe there is an issue with your code, so you'd have to show it 21:27
tbrowder ok, i'll try to slim it down... 21:28
22:00 stanrifkin left 23:13 jpn left 23:14 jpn joined
[Coke] golfs are great but not always necessary - a git repo with a way to reproduce the error is a good 1st step 23:28
23:29 Sgeo joined 23:30 jpn left 23:59 jpn joined

Powered by Cro and the Raku® Programming Language.

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

Thank you!