[Kst] ASCII config patch

[Barth Netterfield]

On February 1, 2005 03:22 am, you wrote:
> This document describes a very generic CSV format. In all real-life
> cases I see around here that deal with _numerical data_ (the only case
> of interest for kst, where we won't have line breaks embedded in the
> fields !) the configurable ASCII source as I proposed works very well. I
> personally don't see the need to add a specialized CSV datasource but I
> don't mind if there is one, as long as it is still possible to use the
> configurable ASCII source to read formats not picked up by the CSV one.
>
A csv data source could read all csv files with basically only one 
configuration option: is the first row col. names?  Not having a UI makes the 
task easier for both the programmer and the user. 

>
> Adding automatic format detection is something I also considered. I
> believe it would not be overly difficult to find some heuristics to
> determine the major characteristics automatically. As you say, we'd
> still need a manual option in case we get it wrong. But I see that as a
> subsequent step: first, add the manual configuration options, then add
> further options, one being automatic format detection.

I suggest the opposite order, and only add the options you really need to add.