pcp
[Top] [All Lists]

pmview ....

To: "Scott, Nathan" <nathans@xxxxxxxxxx>
Subject: pmview ....
From: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Date: Fri, 15 Mar 2013 15:11:35 +1100
Cc: pcp@xxxxxxxxxxx
Delivered-to: pcp@xxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130308 Thunderbird/17.0.4
Nathan,

I'm back looking at pmview.

I've integrated the Aconex code (libapp and pmview) and my initial pmview changes into my pcp-gui workarea.

I can build images that include pmview.

I've fixed the Ubuntu desktop integration so that the icons appear (for pmchart and pmview).

Now my questions ...

1. Looks like libapp is the generalization of classes from pmchart (and some repeated in pmtime) that have common use ... I think pmchart and pmtime were converted to use those in the Aconex code, but Qt has moved on since then and they no longer build. Does this sound about right?

2. As of now, my pmview parses the scene description and launches the viewer with the correct objects and layout (in the few simple tests I've done), but
- lots of the UI components are inactive or missing
- I get 0, 1 or 2 timecontrol dialogs (sometimes _both_ live and archive) appearing ... this is non-deterministic (more debugging enabled seems to produce more dialogs, so a timing issue?)
- no metric values are ever fetched, so the objects stay grey
Does this match where you thought it was up to?

3. How do you turn on the diagnostics in a controlled manner ... there is a mix of fprintf's to stderr, cerr's and calls to console.post ... and I don't seem to be able to get them all enabled (I guess we need to accommodate the fprintf's because of libpcp diags, but I'm not sure what's the rationale for the other two diagnostic pipes).

4. I can't get a toe hold on starting to tackle pmview ... I don't understand how the time control is supposed to work, and in particular I am unconvinced that the "tabbing" from pmchart needs to be applied to pmview, which means (I think) pmview needs to run in either live or archive mode, but not both. And I have no clue how the main logic should be connected to the qmc classes to trigger fetching and scene modulation callbacks.

5. Would it make sense to start with the current t-o-t pmtime and get that working with libapp (and reintroduce the PM_TRACE_TIMECONTROL diags that seem to have not made it to the brave new pcp-gui world). Then do the same for t-o-t pmchart? So start with the t-o-t code for pmtime and pmchart, and selectively merge changes from the Aconex code, keeping all the newer features, Qt work and changes in the t-o-t code. And then use pmchart as the model for the missing pieces of pmview?

Any/all suggestions would be most welcome at this stage, as I'm thrashing about here and not making much progress.

Cheers, Ken.

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