| 27 Nov 2022 | |||
| [Coke] | i hear rsc is writing a job description. but I would imagine we'd want more volunteers than fewer, even if they can only do bits. | 21:17 | |
| coleman | I have lots of ops experience; link the job description when it's drafted and I'll take a look | 22:53 | |
| 28 Nov 2022 | |||
| [Coke] | thank you! | 00:53 | |
| CIAvash | I don't have lots of experience there, but I may be able to help with little things | 05:24 | |
| Nemokosch | Well well. Another example of how communication is key. Talking for myself, I have little to no idea what Roman was doing - I knew that he was doing something, and that it probably costed not just time but money as well. | 15:23 | |
| And now, kinda suddenly, it strucks that this is over - and we still don't know what the tasks are :\ | 15:24 | ||
| Anyway, I'd be optimistic. I can try to host a version of that site with CI on my VPS (there have been some updates since the published version by Oleksandr) | 15:26 | ||
| And I definitely wouldn't be worried that we don't have anything to work on. It's another thing who wants to contribute to what... there are the document issues as usual; some work on the new docs site I'd like to get done, then there is raku.org... | 15:28 | ||
| Yes, I know raku.org is not documentation per se but as I might have said - there doesn't seem to be anything like "raku website team", lol. And it's definitely a question of content as well, not just "infrastructure" | 15:29 | ||
| I'm trying to continue with what I pretentiously call "project mowyw6", i.e I want to migrate the templates from mowyw to a Template6-based solution. It's just... Template6 isn't documented all that well, and it doesn't fully cover TT2 | 15:31 | ||
| If I fail, I can still migrate to TT2 at least, I guess | |||
| Geth | ¦ doc: coke assigned to Altai-man Issue Runnable snippets using Rakudo-JS github.com/Raku/doc/issues/2454 | 16:37 | |
| [Coke] | this weekend bad for me for a call. let's plan for December 10th | 17:09 | |
| Hopefully there will be movement before then on infra support | |||
| Geth | ¦ doc: coke self-assigned Policy needed for incomplete snippets github.com/Raku/doc/issues/4138 | 17:32 | |
| [Coke] | is github.com/Raku/doc/issues/3773 still an issue in the new site? | 17:38 | |
| 29 Nov 2022 | |||
| Nemokosch | [Coke]: negative, the graphs of named types work | 00:24 | |
| By the way, I'm quite sure the highlighter relies on timing some way and fails for a cold runup. Only for the first occasion... | 00:25 | ||
| CIAvash | Would replacing "atom-language-perl6" with [chroma](github.com/alecthomas/chroma) for highlighting code be desired? I don't know how it correlates with `raku-mode.js`, `farabi6` and codemirror, but the benefits are better performance and less dependencies(node_modules) because you can use the chroma binary directly. cc Altai-man | 05:08 | |
| But maybe after RakuAST they won't be necessary? 🤷 | 05:10 | ||
| Nemokosch | I don't think RakuAST could magically solve this. If the idea is that this chroma will be just good enough not to worry about the source, then good luck; otherwise I'd vote against anything that involves migrating from a language I know to Go | 07:54 | |
| CIAvash | It would replace syntax highlighting currently done with JS. I mentioned RakuAST, because we may have our own syntax highlighter in Raku after it lands, not sure. Using chroma will be just giving the code to its CLI to generate the html. CSS class names need to change though. I saw mentions of `CodeMirror` and CSS classes that start with `.cm` and farabi6 in `raku-mode.js` for live code editing, so I wondered things might be more complicated than | 08:23 | |
| simply replacing "atom-language-perl6". If these are not related, then I think it would be easy to replace "atom-language-perl6" with chroma. | |||
| Nemokosch | I know how syntax highlighting works... more or less. It's based on the highlighter module created with Atom and it's just invoked from the webserver app - so yes, essentially "giving the code to CLI to generate the HTML" | 09:49 | |
| The thing is rather that currently, I think it's just a matter of communication and management to do anything with syntax highlighting based on atom-language-perl6. With Chroma, we would lose the management powers (because it's outside of the community) and I for one would lose much of the interest - because previously there was hope to work with familiar technologies like Node, JSON, the JS macroverse overall, and now all of a sudden | 09:52 | ||
| the lexer itself would be written in Go. | |||
| it would be probably easy to try chroma out, though | |||
| that's why I say if produces so good output that you can "set it and forget it", then I'm not against it | 09:53 | ||
| sena_kun | for syntax highlighting we want to wait for raku solution | 10:03 | |
| which comes after RakuAST work done | |||
| CIAvash | FWIW I made the Raku lexer for chroma, so I can make changes, and if necessary build a binary from it if timing of release would be an issue. | 10:05 | |
| Yeah that's why I asked before creating a PR | |||
| sena_kun | I'm sure it doesn't work with slangs? | 10:08 | |
| what about heredocs support? | |||
| CIAvash | (chroma is also being used in raku.land, if you want to see it in action, also in Gitea(which Codeberg) uses) | 10:09 | |
| It supports heredocs | |||
| No, for slangs you'd need an actual/real lexer, or at least a more complicated one | 10:12 | ||
| lizmat | I feel that jnthn's answer here: stackoverflow.com/questions/745433...ash-safely could be copied almost verbatim to some FAQ in the docs | 10:18 | |
| CIAvash | A few examples for highlighting: codeberg.org/CIAvash/APISports-Foo...ll.rakumod codeberg.org/CIAvash/Pod-Contents codeberg.org/CIAvash/Test-Run/src/...n.rakutest | 10:21 | |
| sena_kun | hmmm | 14:10 | |
| interesting | |||
| CIAvash, how do you integrate it with a website, is there a code sample? | 14:11 | ||
| is it lighter than what we do? did you compare features? | |||
| [Coke] | if someone can add lizmat's URL above to a doc ticket, that'd be great. | 16:24 | |
| Geth | ¦ doc: coke self-assigned Explanation on thread issues with hashes github.com/Raku/doc/issues/4143 | 16:35 | |
| [Coke] | Thanks, lizmat. | 16:39 | |
| lizmat | yw :-) | 16:40 | |
| [Coke] | One boring task that doesn't require a lot of raku knowledge: verify that items with label:docs are actually spec'd in Roast (if not, add label:NONSPECCED) | 16:46 | |
| (basically, use 'rak' or something to search for any usage of a requested method/class/sub to see if it's used in roast) | 16:51 | ||
| CIAvash | sena_kun: Using the chroma CLI I changed the `lib/Docky/Renderer/Node.pm6` file: gist.github.com/CIAvash/85bbbbd24c...-pm6-L7-L8 the first highlighted line generates the HTML with classes and the line that is commented out generates HTML with inline styles. Feature-wise I think the chroma lexer has better support for Raku, meaning detecting more tokens, if the chroma binary gets used, it means no dependencies | 19:38 | |
| (no downloading node modules), I have not compared the performance, but I'm going to guess chroma is faster. Considering the size, atom-highlight-perl6 with the node_modules directory is about 60MB and chroma binary file is 6.3MB. | |||
| sena_kun | CIAvash, extremely curious. what about color themes? we need at least two, light and dark. | 20:16 | |
| CIAvash | sena_kun: Current themes probably can be used, but CSS class names need to change and maybe added, but chroma comes with these styles: github.com/alecthomas/chroma/tree/master/styles demo of some of the styles(it doesn't include all themes, specially the ones I've added): xyproto.github.io/splash/docs/all.html | 20:22 | |