00:18 Pe_Elle left 00:52 Pe_Elle joined 00:53 Pe_Elle left, Pe_Elle joined 00:54 Pe_Elle left 01:00 Pe_Elle joined 01:05 Pe_Elle left 01:35 Pe_Elle joined 01:39 Pe_Elle left 02:10 Pe_Elle joined 02:15 Pe_Elle left 02:37 Pe_Elle joined 04:53 Pe_Elle left 05:23 Pe_Elle joined 06:29 Pe_Elle left 06:41 Pe_Elle joined 07:15 Pe_Elle left 07:22 Pe_Elle joined 08:50 sena_kun joined 09:24 Pe_Elle left 10:01 sena_kun left 11:16 Pe_Elle joined 12:37 Pe_Elle left 12:43 Pe_Elle joined 12:47 Pe_Elle left 13:01 Pe_Elle joined 14:03 Pe_Elle left 14:29 Pe_Elle joined 14:34 Pe_Elle left 15:02 Pe_Elle joined 15:07 Pe_Elle left 15:34 Pe_Elle joined 16:36 Pe_Elle left 16:40 guifa joined 16:42 Pe_Elle joined
librasteve SmokeMachine: I have finally got some concrete feedback onto your Cromponent proto - this is pretty much what I had in mind for functional composition of Cromponents, but using crotmp under the hood and optionally in assemblies depending on what floats you boat. I have offered as a PR hope this is a way to contribute. 17:43
/way/good way/ 17:44
17:45 Pe_Elle left
Next on my list is to elaborate the MyLib.rakumod to get CSS (SASS?) mixing in at the component level. I can be pretty self sufficient in that since I don't think that will need any changes to the existing prototype. (Although I epect you to be freely making any improvements you side so may have to reintegrate when you get to where you are going. Hopefully the form of the Cromponent classes/roles is stable since it 17:48
is nicely declarative already imo)
SmokeMachine Im currently trying to replace add-component with a trait `is cromponent` but I’m having a big problem of my trait not basing matched… :( 18:01
18:08 sena_kun joined 18:12 Pe_Elle joined 18:22 Pe_Elle left 18:35 Pe_Elle joined 19:10 japhb left 19:11 japhb joined
librasteve the trait meister 19:16
19:37 Pe_Elle left 19:52 Pe_Elle joined 19:58 Pe_Elle left 20:10 japhb left 20:29 japhb joined 20:38 Pe_Elle joined 20:50 japhb left 20:59 Pe_Elle left
SmokeMachine librasteve: I implemented 2 new features to Cromponent: now you can define a cromponent will use a macro instead of a sub and for every cromponent you create it creates the sub/macro with the name of the component, but now it also creates a sub/macro with the name <CromponentName>-new that instanciates the cromponent and uses it from inside the template: github.com/FCO/Cromponent/blob/mai...macro.raku 21:03
21:25 sena_kun left 21:40 Pe_Elle joined 22:43 Pe_Elle left 23:03 sena_kun joined 23:23 Pe_Elle joined 23:28 Pe_Elle left 23:33 sena_kun left 23:55 Pe_Elle joined