VTK/Charts/API: Difference between revisions
(Added some more details about possible API layout) |
(Added some more detail about the chart structure) |
||
Line 1: | Line 1: | ||
After looking at various other frameworks, tools and products out there here are some thoughts on the API. Employing a factory based interface seems like it would give us the most intuitive API. So a chart could be instantiated in the following | After looking at various other frameworks, tools and products out there here are some thoughts on the API. Employing a factory based interface seems like it would give us the most intuitive API. So a chart could be instantiated in the following way, | ||
<pre>vtkChart *chart = vtkChart::New(); // | <pre>// Instantiate a new chart | ||
vtkPlot *barPlot = chart->AddPlot(Chart::BAR); | vtkChart *chart = vtkChart::New(); | ||
// Add a bar plot | |||
barPlot-> | vtkPlot *barPlot = chart->AddPlot(Chart::BAR); | ||
// Set the data source to table, column 0 is x, column 2 is y | |||
linePlot-> | barPlot->SetData(table, 0, 2); | ||
linePlot-> | // Set the width of the bars | ||
barPlot->SetWidth(20); | |||
// Add a line plot | |||
vtkPlot *linePlot = chart->AddPlot(Chart::LINE); | |||
// Set the data source to table, column 0 is x, column 2 is y | |||
linePlot->SetData(table, 0, 2); | |||
// Set the line width | |||
linePlot->SetWidth(2);</pre> | |||
I could also overload the New() function to accept an argument such as vtkChart::New(vtkChart::LINE) which would create a new chart object with a line chart contained. The chart can iterate over the plots and paint each one in turn, this allows an intuitive interface where multiple plot types can be plotted on the same axes. | |||
There has been a lot of talk about API. Do we want a declarative API? This would make constructs such as, | There has been a lot of talk about API. Do we want a declarative API? This would make constructs such as, |
Revision as of 19:24, 19 October 2009
After looking at various other frameworks, tools and products out there here are some thoughts on the API. Employing a factory based interface seems like it would give us the most intuitive API. So a chart could be instantiated in the following way,
// Instantiate a new chart vtkChart *chart = vtkChart::New(); // Add a bar plot vtkPlot *barPlot = chart->AddPlot(Chart::BAR); // Set the data source to table, column 0 is x, column 2 is y barPlot->SetData(table, 0, 2); // Set the width of the bars barPlot->SetWidth(20); // Add a line plot vtkPlot *linePlot = chart->AddPlot(Chart::LINE); // Set the data source to table, column 0 is x, column 2 is y linePlot->SetData(table, 0, 2); // Set the line width linePlot->SetWidth(2);
I could also overload the New() function to accept an argument such as vtkChart::New(vtkChart::LINE) which would create a new chart object with a line chart contained. The chart can iterate over the plots and paint each one in turn, this allows an intuitive interface where multiple plot types can be plotted on the same axes.
There has been a lot of talk about API. Do we want a declarative API? This would make constructs such as,
vtkChart *chart = vtkChart::New(); chart->SetWidth(200) ->SetHeight(200); chart->AddPlot(vtkChart::BAR) ->SetData(table, 1, 2) ->SetWidth(20) ->SetLabel("My Data");
This would require setter functions that returned a pointer to the object, i.e.
vtkChart * vtkChart::SetWidth(int width); vtkPlot * vtkChart::AddPlot(enum); vtkPlot * vtkPlot::SetLabel(const char *label);
One nice thing about this approach is that ignoring the pointer returned allows traditional VTK syntax to be used.
vtkPlot *plot = chart->AddPlot(vtkChart::BAR); plot->SetData(table, 1, 2); plot->SetWidth(20); plot->SetLabel("My Data");
Admittedly it is not in keeping with the current pattern used in VTK, there are numerous examples of its use in other libraries and frameworks. It should possibly be more of a global change to the library API, rather than isolated to one or two components.