Talk:REBOL Programming
From Wikibooks, the open-content textbooks collection
Contents |
[edit] Change Log
Since this wiki is shared with every other book under the sun, it is not clear how to see where new sections have been started. Make an entry here for new works so others can check it out.
- started on control structures, and on databases - Graham.
- Carl did a section on /Dialects
- Moved Language Features under TOC - Henrik
- Moved Design Guide under TOC - Henrik
- Doing a lot of work on PARSE under Language Features - Henrik
[edit] Requests
What should be in the book? You can find those section by hunting them, but gather them here for easier reference.
[edit] Problems
[edit] Size of Programming Section
The Programming chapter is likely to end up getting big (huge maybe). Should it be broken into new chapters now, or later? What's your suggested structure? G.
Post your solution here.
[edit] Design Guide
The Design Guide is very clear on many things, but is "stuck" behind the main programming guide. It will feel like all the best advice won't come until after you've spent time studying the language. - Henrik
Post your solution here.
[edit] Console
Carl says "Command Shell". The book says "Console". - Henrik
Post your solution here.
[edit] Function Writing Style
Some places functions are written as func, in other places as FUNC. - Henrik
Post your solution here.
Other documentation uses the FUNC form, but I think, that the func form is better. Moreover, it is requested by some readers. I propose to use this rule for other Rebol values like true, none, etc. When we are at it, I think, that we should write blocks with outer whitespace, but without inner whitespace, i.e.
[1 2] [3 4]
, and not
[ 1 2 ][ 3 4 ]
Another suggestion is to emphasize text like this - Ladislav
I've begun purging the inner-space-in-blocks style, though I'm still writing emphasized text both in bold and italic.
- Italic for something semi-important to underline a point
- Bold for something very important that could result in code loss if attempted.
I think it catches the eye easier and doesn't blend too much with using bold for values. - Henrik
[edit] Code Coloring
Not syntax coloring, but code coloring in the examples. I haven't studied whether it's hard or easy to do, but sometimes it can be nice to point out a word in a section of code with color, to let the viewer easier see what we are doing. - Henrik
Post your solution here.
[edit] Printing
The Wikibook is hard to print, since we have to print each chapter on its own. It would also be nice to get the size of the book at regular intervals. - Henrik
Post your solution here.
My solution is to use REBOL to pull down all the pages in the order you want, and print them out Graham.Chiu
