|
07:04
Pe_Elle left
07:14
Pe_Elle joined
07:15
Pe_Elle left,
Pe_Elle joined
10:04
Pe_Elle left
10:09
Pe_Elle joined
10:14
Pe_Elle left
10:18
sena_kun joined
10:28
Pe_Elle joined
11:29
Pe_Elle left
11:50
timo1 is now known as timo
11:57
Pe_Elle joined
12:01
Pe_Elle left
12:16
Pe_Elle joined
13:18
Pe_Elle left,
Pe_Elle joined
14:21
Pe_Elle left
14:41
Pe_Elle joined
15:26
librasteve_ joined
|
|||
| librasteve | .seen SmokeMachine | 15:26 | |
| SmokeMachine: just wanted to give you a heads' up that I did include some cromponent code in my demo (tomorrow's advent post) - the code I made just finished today (and it was done in a hurry as the original date was 21st) here github.com/librasteve/raku-Cro-Web.../02-sharc1 (not main branch). This is about halfway to an MVP - I need to put in Red (ie data model inside the component), merge in | 15:35 | ||
| your latest Cromponent updates and fix some things I broke and distinguish between installable libraries and site specific libraries... but I thnk that the sample site is pretty much in the form of my idea of how to build a website (which may be very different to your idea ?!) | |||
|
15:35
kawaii joined
|
|||
| It would suit me to have Cromponent be an external module dependency - better than duplicating the code - but I see that you have not been able to be as active on the Cromponent prototype recently so I am happy to keep that code within these site level examples for now, but with the idea that I would maybe release and support as a raku module. Please can you give me an idea of your thoughts for this? When Cromponent | 15:41 | ||
| does become a module in its own right, then I would probably break out the library of crompoments to also be external dependencies - maybe one for HTMX examples and one for Pico CSS examples. | |||
|
15:43
Pe_Elle left
15:44
Pe_Elle joined
|
|||
| PS. maybe a module name like HTML::Components or Cro::WebApp::Components would be better than Cromponents?[yeah I like that Cromponents is funny ... but the rest of the Cro naming is quite straight-laced ...] | 15:45 | ||
|
16:46
Pe_Elle left
16:47
Pe_Elle joined
16:51
Pe_Elle left
17:05
Pe_Elle joined
17:45
kawaii left
18:08
Pe_Elle left
18:22
Pe_Elle joined
|
|||
| lizmat | colloquially cromponents could continue to be used :-) | 18:52 | |
| scullucs | "Cromponents" sounds perfectly cromulent. | 18:56 | |
|
19:24
Pe_Elle left
19:39
Pe_Elle joined
|
|||
| SmokeMachine | librasteve_: Hi! So would it help you if I released what we have now? | 19:39 | |
| I wouldn't say `the rest of the Cro naming is quite straight-laced`, once its name came from `my Cro $service` (at least that's what I remember). I'm not a big fan of straight-laced names... | 19:42 | ||
| it have no tests yet, but if it will help you, I can release it now... | 19:43 | ||
| ans sorry for not being very active the last days... I'm working too much... | 19:44 | ||
| librasteve_: can you see if this helps you? github.com/FCO/Cromponent/pull/6 | 20:28 | ||
|
20:40
Pe_Elle left
20:55
Pe_Elle joined
21:00
Pe_Elle left
21:28
Pe_Elle joined
21:33
Pe_Elle left
22:00
Pe_Elle joined
22:05
Pe_Elle left
|
|||
| librasteve | your module - your name :-) | 22:09 | |
| please do release what you wrote as early experimental - that would be very helpful | 22:10 | ||
| i can try and write some tests and PR if you like | 22:11 | ||
|
22:33
Pe_Elle joined
|
|||
| oh - we do need to work out the “reentrency” issue i posted please | 22:47 | ||
| SmokeMachine | have you tried that with this new version? | 22:48 | |
| I don't see why that would break and I could't reproduce.. | 22:49 | ||
|
22:54
sena_kun left
|
|||
| SmokeMachine | it's released... let's see if it will go to raku.land... | 22:55 | |
| librasteve_: you need your version of cro webapp to make that work... | 23:00 | ||
| librasteve | I tried with the old version… will merge and close issue if fixed | 23:07 | |
| &afk | 23:08 | ||
| SmokeMachine | If that’s not fixed, if you could share a code to reproduce the error, I can try to fix | ||
|
23:37
Pe_Elle left
23:52
Pe_Elle joined
|
|||