|
brainstorming lists: gist.github.com/203173 paste.lisp.org/display/88288 IRC logs: irclog.perlgeek.de/perl6book/today source: github.com/perl6/book/ Set by moderator on 20 October 2009. |
|||
|
02:49
snarkyboojum_ joined
05:58
chromatic joined
06:18
colomon joined
09:03
mathw left
09:49
snarkyboojum_ joined
09:50
masak joined
|
|||
| moritz_ likes his example in the section about Match objects | 10:12 | ||
| masak looks | 10:29 | ||
| moritz_: aye, very nice :) | 10:39 | ||
| it's amazing that we have 27 pages after barely a month. | 10:41 | ||
| if we keep up that pace for two more months, all we have to do after that is cull and polish. :) | |||
| jnthn | That's not bad going. :-) | 10:42 | |
| masak | I just showed the book to a friend. we both agreed that the code snippeds could really use some syntax coloring, and the book needs more images overall. | 10:50 | |
| jnthn | masak: Printing the book in full color is probably way costly though. :-| | 11:01 | |
| Agree for a PDF version it's quite possible. | |||
| masak | jnthn: yes, I think so too. grayscale is fine. | ||
| jnthn | masak: Hmm, maybe. | 11:02 | |
| masak | I mean for the printed version. | ||
| jnthn | masak: Given that in terms of code editor features, syntax highlighting isn't something that bothers me much anyway, I'm probably not a good person to get an opinion from on this. | ||
| It's not something I ever go out of my way to have. | 11:03 | ||
| I can see how others value it, and know that how I see the world is quite possibly rather different from others, thanks to my collection of eyesight issues. :-) | 11:04 | ||
| masak | jnthn: I used to think that syntax highlighting wasn't very important. now I go to great lengths to tweak it into my sweet spot. | 11:06 | |
| jnthn | Curious. | ||
| I used to think it was important, then ended up discovering it made little to no difference to my productivity | 11:07 | ||
| On the other hand, I've one person I work with who advocates Resharper, a Visual Studio plug-in that he finds makes him more productive. | |||
| I just found it got in my way and annoyed me and made me less productive and more stressed, because I was fighting it, not writing code. | 11:08 | ||
| Equally, I will go to lengths to have a good graphical debugger. | 11:09 | ||
| And appreciate things like KCacheGrind which visualize stuff. | |||
| Guess I'm just quirky. :-) | |||
| masak | not arguing with that. :P | 11:11 | |
| moritz_ | I'm against syntax hilighting in the book | 11:15 | |
| I like it very much in my editor | 11:16 | ||
| but when I learn the language, I also have to learn how to parse it mentally | |||
| masak | and syntax highlighting would hinder that_ | ||
| ? | |||
| I'm not sure I agree. | 11:17 | ||
| moritz_ | if somebody does that for me (by providing syntax hilighting), I don't learn it myself | ||
| masak | wouldn't syntax highlighting also give subtle cues as to how to understand a piece of code? | ||
| moritz_ | yes, but the explanations should make that unncessary | 11:18 | |
| masak | I'm talking about simple things such as marking all 'keywords' in some way to show that they are special. | ||
| moritz_: people tend to pick things up if they recieve the same signals through different channels, in my opinion. | |||
| that's why it's a good idea to put the numbers in the table cells, and not just the colors. | 11:19 | ||
| that said, it might be that a slightly different kind of syntax highlighting is optimal for a book like this than for a programmer's editor. | 11:20 | ||
| moritz_ | there are things that make sense, for example making pieces of code bold | 11:22 | |
| either pieces that are changed from previous versions, or otherwise especially important | |||
| masak | nod. | ||
| moritz_ | I liked that very much in HOP | ||
| also Mastering Regular Expressions has nice markup | |||
| masak | haven't read that one. | 11:23 | |
| moritz_ | ohh, you should :-) | ||
| masak | I'd like the code snippets to stand out more than they do right now, at least. | ||
| perhaps using a light grey background or something. | |||
| moritz_ | there are other gripes I have with the current code formatting | ||
| for example that it preserves the leading spaces from the POD indention | 11:24 | ||
| masak | aye, that's ungood. | ||
| moritz_ thinks it might be necessary to subclass Pod::PsuedoPod::LaTeX | 11:25 | ||
| anyway, for me that's secondary to actually writing stuff | 11:26 | ||
| btw I received some feedback | 11:28 | ||
| people on IRC telling me that they liked the project | |||
| or even printed the PDF | |||
| I've also got on email which pointed out formatting and spelling mistakes | |||
| masak | nice. | 11:29 | |
| dalek | ok: acc87f8 | moritz++ | docs/TODO: [docs] add TODO file which holds a list of technical TODOs |
11:38 | |
| ok: fa5f59c | moritz++ | docs/TODO: [docs] one more technical TODO |
11:44 | ||
|
11:54
lichtkind joined
12:42
lichtkind_ joined
14:31
p6eval joined
15:50
masak joined
15:57
Util joined
16:01
masak joined
18:55
chromatic joined
18:58
Guest41369 left
|
|||
| colomon | Getting around to reading the regex section, something I have terribly neglected in p6. | 19:13 | |
| whoops, I see, the problem I was about to report is that (proper) << and >> aren't showing up in the LaTeX. | |||
| I had no idea those could be used in regexes now. | |||
| chromatic | I think I have to remove some escaping from text in C<> tags now. | 19:16 | |
| dalek | ok: faa1cec | duff++ | src/regexes.pod: [regex] Added some text about character classes * Use the word 'anchor' consistently * minor grammatical and other textual changes * Mention :sigspace on rules |
20:27 | |
| ok: 8f9db94 | (Solomon Foster)++ | src/regexes.pod: Fix typo: s/subrle/subrule/ |
20:39 | ||
| moritz_ | PerlJam++ | 22:22 | |
| colomon++ | |||
| dalek | ok: c0f92ed | moritz++ | src/regexes.pod: [RX] more nit-picking, trailing spaces |
22:24 | |
|
23:57
snarkyboojum_ joined
|
|||