pcp
[Top] [All Lists]

Re: [pcp] Source and binary packaging - future directions

To: Nathan Scott <nscott@xxxxxxxxxx>
Subject: Re: [pcp] Source and binary packaging - future directions
From: Max Matveev <makc@xxxxxxxxx>
Date: Fri, 6 Feb 2009 21:05:31 +1100
Cc: Mark Goodwin <goodwinos@xxxxxxxxx>, kenj@xxxxxxxxxxxxxxxx, pcp@xxxxxxxxxxx
In-reply-to: <1233876585.19028.19.camel@xxxxxxxxxxxxxxxxxx>
References: <1233627045.5518.55.camel@xxxxxxxxxxxxxxxxxx> <18825.23091.63084.898574@xxxxxxxxxxxxxxxxx> <1233742073.10265.1.camel@bozo> <1233786804.24330.15.camel@xxxxxxxxxxxxxxxxxx> <498A6CD0.7010002@xxxxxxxxx> <18826.49390.974151.5980@xxxxxxxxxxxxxxxxx> <1233876585.19028.19.camel@xxxxxxxxxxxxxxxxxx>
On Fri, 06 Feb 2009 10:29:45 +1100, Nathan Scott wrote:

 >> Ok, WARs like counter-wrap detection in the fetchgroup code, GIF

 NS> It honours PCP_COUNTER_WRAP, if thats what you mean?

It was more then PCP_COUNTER_WRAP - I've had to fix a bug with gif
generation (I think sometime around 2007) for people who do things
which go "woooosh": pmchart was generating graphs with missing samples
and COUNTER_WRAP did not solve it for them. I cannot remember all
details.

 NS> How many of the last-of-the-mohicans^Wpmcharticans do
 NS> you really think rely on some particular counter-wrap
 NS> handling anyway?
A handful at best. And some of them are on irix, which makes the
arguments even less important.

 >> generation (can kmchart do that?),

 NS> kmchart^WThe new pmchart (qt, really) can generate 10+
 NS> different image formats, including gif.

In the batch mode too?

 >> graph layout.
 NS> Do you mean window sizing from the command line? 

No, I mean the way windows were layed out in pmchart - there were
people relying on this layout to insert the images generated by
pmchart into web pages.

 NS> At the end of the day, if you/a user worries about any piece
 NS> of functionality they need from the old pmchart which turns
 NS> out to not be there in the new pmchart, then you/they are
 NS> of course free to add it - or at the very least request it,
 NS> preferably after having actually tried out the new pmchart.

It's true but I really don't think that getting into the game of
implementing pmchart bugs in kmchart is a good idea but in the end
you're the one who does most (all?) of the work, so it's your call.

max

<Prev in Thread] Current Thread [Next in Thread>