|
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
|
|||