Mark, Mike, Andrew, Sami, Elena, Kris, Nurdin, Rick, Phil, Tim.


Druid walkthrough:
-----------------
Cagney explaining his views on how the start up sequence should be for
the first time frysk is invoked. <conversation not aubible over the
phone>
Radio button to take you to a quick debug session. 

Current quick debug button could become a "finish" button when the
source window is integrated into the monitor.

How to start a process under frysk, instead of attaching to running
process.  Proposal floating around to have a different frysk startup
mode, using applications->programming->frysk-terminal that would bring
up a terminal window. 

Can we have the frysk terminal already there with cli? 
How many ways of starting a session are there? 

Starting with arguments is also a case, and I/O to/from process.

This will be discussed in mailing list. (cagney to post)


Monitor window walkthrough:
--------------------------
one single horizontal scrollbar for all the timelines they all scroll
together.  But it scrolls only the "inside part" of the timelines.

the vertical scrollbar wold scroll everything

Known bug: label of the points in the timelines can be cut out at the
top if they are too long.

Select single timelines and inidividual events, it's now possible.
Main thread with another thread: top timeline is the merge of the two,
and then there are two timelines one for each thread.

"summary" timeline for the process contains the union of the timelines
for the individual threads, labels are unclear.
cagney suggestion to remove the PID from the main timeline
elena suggestion to add some label to indicate that the top timeline
is a merge.  
elena suggestion to reverse the two, put the components
above the merge timeline.

Ticks are not visible at all times when resizing the window
vertically: known bug.  Text for events is also chopped off.

If event selected, there will be a backtrace appearing in "main Log"
window.  current output to the main log will not be there (just debug
for now). For each selection it will clear that window.  Also would be
possibe to go to the source window. Either with a menu or just
clicking on the event.

Summary tab (instead of main log): what should be displayed
there. Backtrace and source code?

Differing views: 

Cagney wants display of backtrace and sourcecode in the the monitor
window. His concern is easy navigation btw events. 

Elena, Rick: just bring up source window when one event is selected.
Multiple source windows if you want to look at multiple
events. Worried that too much functionality of the source window is
going to be duplicated here. Splitting debugging flow from monitor
flow could be a problem if we go down this way.

Idea (was that Nurdin?): have a mini monitor window in the source
window and vice versa. 

General topic of keeping windows in sync when changing source/browsing
location.  This applies to all windows. There should be a "lock"
option for the windows, so that they are not updated.

Should be possible to update this window by choosing a different
process and also different observers. Bring back to the same flow for
setting up the sessions (do this via menus).

Dropping the left process list window from the monitor window. Info in
there is redundant.

So the conclusion is? There was no agreement. Please discuss in
mailing list.