Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!think.com!paperboy!snorkelwacker.mit.edu!bloom-beacon!eru!hagbard!sunic!mcsun!ukc!tcdcs!bofin!cjmchale
From: cjmchale@cs.tcd.ie (Ciaran McHale)
Newsgroups: comp.windows.x
Subject: Re: Anyone got a graph widget (Athena and/or Motif)?
Message-ID: <1991Mar27.134929.27542@cs.tcd.ie>
Date: 27 Mar 91 13:49:29 GMT
References: <1991Mar26.073847.26457@melba.bby.oz.au>
Organization: DSG, Dept. of Comp. Sci., Trinity College, Dublin.
Lines: 27

In <1991Mar26.073847.26457@melba.bby.oz.au>
gnb@bby.oz.au (Gregory N. Bond) writes:

>[asks for a graph widget]
>What would be ideal is the ability to have a hierarchy of widgets,
>with a container widget that is the graph, does the scaling etc and
>there is one child for each dataset on the graph.  This would allow
>setting line colors/styles  etc as resources without imposing fixed
>limits on the numbr of data items (I think...).

Your suggestion is valid but to me sounds like you're confusing
requirements with implementation details. Another implementation
approach would be to use an OO graphics library (such as the one in
InterViews) and extend it to have a bar_chart_graphic, pie_chart_graphic
etc (each of which is a subclass of, say, graph_graphic). Using this
approach, each graph would be a graphic rather than a widget (window).
The advantage is that it would be easy to overlay several graphs. (If
each graph were a separate widow/widget then overlay one on another
would obscure the lower one.)


Ciaran.
-- 
Ciaran McHale		"Verbosity says it all"			      ____
Department of Computer Science, Trinity College, Dublin 2, Ireland.   \  /
Telephone: +353-1-772941 ext 1538	FAX: +353-1-772204	       \/
Telex: 93782 TCD EI			email: cjmchale@cs.tcd.ie