[RkWard-devel] Pareto chart and Quality qontrol charts

[Thomas Friedrichsmeier]

On Sunday 25 February 2007 20:24, I. Soumpasis wrote:
> I believe that is should be left as is four 2 main reasons (apply to
> barplot too):

Ok, that makes sense.

> The above gave me one idea. In some time in the future we could do a set of
> plugins doing tabulate, transpose, changing properties of objects etc. In a
> case like this tabulate option should not be useful, as the user should do
> that from editing data. User should follow this more typical way so to
> understand and know what he is doing. First edit to data in a way that is
> meaningful and then plot it or generally make statistics with it.

Yes, we need a whole class of plugins doing various data transformations 
including tabulation. So the user always *can* first do the transformation 
and then the calculation (or the other way around) in two separate steps. On 
the other hand, there will also be cases, where a certain transformation or 
two are particularily "near by" to a function, and should be kept as options 
directly in the plugin for that function. So it'd probably be a decision on a 
case by case basis, where the trade-off is always between providing most 
useful options "in place", and keeping the GUI (and plugin code) simple.

I think tabulation in the case of barplot / pareto.chart may be good examples 
of a transformation which is particularily likely to be useful in a certain 
context. Another example of a "near by" transformation would be changing 
character encoding after importing data ;-). In contrast, e.g. doing a 
z-transformation before producing a barplot may be needed in some cases, but 
is probably a far less common need.

Regards
Thomas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/rkward-devel/attachments/20070225/11e14f93/attachment.sig>