2011/9/22 Michael Barton <[email protected]>: > At the moment, only the text dialog is the same between Histogram2 and > Profile. The options dialog in Profile could be made to work like that in > Histogram2, but not the other way around. The raster input dialogs are quite > different and probably need to remain so. > > Profile works on the assumption of having 3 maps to profile. And it needs > code for drawing the profile transect on the map display and > creating/modifying segment marker points. > > Histogram2 can have a variable number of maps to histogram (from one > theoretically up to the maximum number supported by i.group) and doesn't need > transect drawing code or code for segment markers. Hence, the dictionaries > for tracking parameters like line color and width are a bit simpler in > Histogram2 (one less level so that the raster name rather than an index > number main key) making it easier to keep track of a potentially larger > number of raster maps. > > Code for overall plot parameters (e.g., axes, grids, title fonts, etc) are > identical across both histogram2 and profile because they use standard PyPlot > calls.
everything leads to the suggestion that ProfileFrame and histogram2.HistFrame should be inherited from the common super-class, probably same for settings dialogs except of RasterSelect. Martin -- Martin Landa <landa.martin gmail.com> * http://geo.fsv.cvut.cz/~landa _______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
