True, I wouldn't mind having to click that link either (in fact I am
running it way that right now) but I would feel pretty bad if one of
the examples in the "color" section used colors in such an obtuse way,
so probably better to hide that code.
On Mon, Jun 30, 2008 at 8:44 PM, Phlip <[EMAIL PROTECTED]> wrote:
> Evan Farrar wrote:
>
>> Shoes.app do
>> (Shoes::COLORS.keys.map{|sym|sym.to_s}.sort-["black"]).each { |color|
>> flow(:width => 175){
>> fill eval(color.to_s)
>> rect 0, 0, 160, 25
>> para color.to_s
>> }
>> }
>> end
>
> BTW many Ruby style guidelines suggest to use do..end on {} blocks that A>
> split lines and B> don't call .methods their return values.
>
>> I tried to make a diff adding this to the manual, but it looked
>> difficult to run ruby code in manual pages. Though, maybe doing this
>> in code is a little over-eager since the X11 color chart hasn't
>> changed in years. Perhaps, _why, you could make a beautiful PNG
>> containing all of the color swatches and their names and include it
>> statically?
>
> Note that manual.txt sez things like
>
> {{{
> #!ruby
> stack :margin_right => 20 + gutter do
> para "Insert fat and ratified declaration of
> independence here..."
> end
> }}}
>
> for ruboid segments. (Extra credit to anyone who syntax-hilites them!;)
>
> They each get a "Run this". I would not mind running that to spring your
> color
> table. Better, the table itself is indeed exemplary Shoes!
>
> --
> Phlip
>
>
>
