2013-03-22 11:54:00 DNS G 1.05, DNS X 0.73 2013-03-22 11:55:00 DNS G 0.75, DNS X 0.77 2013-03-22 11:56:00 DNS G 1.54, DNS X 0.80 2013-03-22 11:57:00 DNS G 0.71, DNS X 0.69 2013-03-22 11:58:00 DNS G 0.67, DNS X 1.51 2013-03-22 11:59:00 DNS G 0.72, DNS X 0.73 2013-03-22 12:00:00 DNS G 0.75, DNS X 0.81 2013-03-22 12:01:00 DNS G 0.74, DNS X 0.78 2013-03-22 12:02:00 DNS G 0.82, DNS X 0.73 2013-03-22 12:03:00 DNS G 0.73, DNS X 1.54 2013-03-22 12:04:00 DNS G 0.68, DNS X 0.72 2013-03-22 12:05:00 DNS G 0.74, DNS X 0.76 2013-03-22 12:06:00 DNS G 0.74, DNS X 0.72 2013-03-22 12:07:00 DNS G 0.77, DNS X 0.87 2013-03-22 12:08:00 DNS G 0.79, DNS X 1.55 2013-03-22 12:09:00 DNS G 0.68, DNS X 0.70 2013-03-22 12:10:00 DNS G 0.71, DNS X 0.82 2013-03-22 12:11:00 DNS G 1.57, DNS X 0.78 2013-03-22 12:12:00 DNS G 0.82, DNS X 0.76 2013-03-22 12:13:00 DNS G 0.71, DNS X 1.49
Sample data. I want to treat the first two fields as a time stamp. DNS G and DNS X are fluff to keep the file readable for humans. So two requests: 1. The ability to import and plot time series data. Because a date can be 2013-03-22, 2013/22/03 03/22/2013, March 22, 2013, etc, etc, it would be useful to be able to define the date format to the importer. (Think building blocks like the excel custom date format builder) 2. This brings up the second issue: A regex parser would probably be needed in the date thingy anyway. Allow it to be used more generally. e.g. a window where you can define (timedate, googledns, xplornetdns) ~= /(yyyy-mm-dd hh:mm:ss) (DNS G) (\d+) (DNS X) (\d+)/$1,$3,$5 (using mostly perl syntax, probably mangled in the details) Respectfully, Sherwood of Sherwood's Forests Sherwood Botsford Sherwood's Forests Tree Farm http://Sherwoods-Forests.com Farm: 780-848-2548 Cell: 780-863-7311 50042 Range Rd 31 Warburg, Alberta T0C 2T0
_______________________________________________ Veusz-discuss mailing list Veusz-discuss@gna.org https://mail.gna.org/listinfo/veusz-discuss
