Beefy Boxes and Bandwidth Generously Provided by pair Networks
laziness, impatience, and hubris

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
There are a few cavets to GD::Graph. The most obvious is the lack of antialiasing, this makes for acceptable web graphics, but not brilliant. For example:

Displays a couple of charts from a custom graphics engine (the basis is actually imlib2), with antialiased lines and a nice semi-transparent underlay.

Displays a pretty extreme example, this one generated from perl through povray, I had standard, bar and stacked versions of that engine. Disadvantage is its pretty unreadable for real stats, but it looks nice :)

So basically you have a number of questions to answer:

1. Who is the target audience? are they going to require particularly impressive graphics?

2. Are the graphics for general trend information or precise analysis?

3. Are the graphics going to be require in realtime? near realtime? any old time?

4. Do you have a lot of time to muck about with it?

5. Is there going to be a lot of different composits on any given chart (ie, bars and a min/max/median line etc)?

Have a think about those, they should point you in the relevant direction in terms of work required. GD is by far the easiest, but you pay for that in terms of simple graphics. Moving to ImLib2 or OpenGL as your rendering basis makes for harder code but a nicer end result (and often faster). Going to povray/rib is really not recommended (from experience :) :)

In reply to Re: Drawing Graphs by PhiRatE
in thread Drawing Graphs by johnirl

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?

What's my password?
Create A New User
Domain Nodelet?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others about the Monastery: (4)
As of 2023-09-30 13:36 GMT
Find Nodes?
    Voting Booth?

    No recent polls found