From: Jeff Pritchard <jp@...>
Date: 2006-06-05T00:01:48+09:00
Subject: Re: This is brain dead, but is it stupid?

True enough Patrick, but that doesn't use any new-to-me coolish aspects 
of the language.  :)

I'm a bit disappointed nobody bothered to respond to my library design 
questions.  I'll risk bad forum etiquette by reposting them here:

Some other thoughts:
* What's the best way to report parameter errors in a library intended 
for erb use?
* I'm thinking there are probably some other more convenient ways of
adding points
     - maybe add an array parameter as an optional last parameter to the
constructor
     - maybe provide a method for supplying an array of points
     - maybe optionally read a file full of CSV points
     - if it were a rails app with sql, what type of input method would
be most convenient for sticking the results of an sql query right into a
graph?
* I want to make labeling pretty simple.  I'm thinking just set it up
such that there are ten evenly spaced "slots" for placing a custom 'y'
label.  If none are supplied it would fill these ten spots in with
calculated values based on the min and max.
* I'm thinking an optional method that allows you to supply an array of
'x' labels - one per bar.  If nothing is supplied, nothing will be
"drawn"
* I'm thinking that "titling" of the graph can be done outside of the
graph and not handled by the library
* In 'erb' land, is there any advantage to making it a "one liner",
where the constructor is big and hairy and allows all possible
parameters to be filled in, and the constructor automatically provides
the html output?

thanks,
jp



Patrick Hurley wrote:
> On 6/2/06, Jeff Pritchard <jp@jeffpritchard.com> wrote:
>> > http://www.curi.us/blog/
>> Very cool language.
>>
>> thanks,
>> jp
>>
>> --
>> Posted via http://www.ruby-forum.com/.
>>
>>
> 
> Or you could just:
> 
> @htmlString = %Q(<img src="blublock.jpg" width="#{barWidth}"
> height="#{barHeight}">\n)
> 
> pth


-- 
Posted via http://www.ruby-forum.com/.