RSS feed

Linkedin Profile

Tags:
programming
seattle
things that bug me
wall art

Posts by month: 10/08 (2)
08/08 (1)
06/08 (2)
05/08 (1)
03/08 (3)
02/08 (1)
01/08 (2)
12/07 (2)
11/07 (1)
07/07 (1)
05/07 (2)
02/07 (1)
01/07 (1)
12/06 (1)
11/06 (1)
10/06 (1)
08/06 (1)
07/06 (1)
06/06 (2)
05/06 (1)
04/06 (2)
02/06 (1)
01/06 (2)
12/05 (3)
11/05 (2)
09/05 (5)
08/05 (5)
07/05 (7)
06/05 (3)
05/05 (6)
04/05 (8)
03/05 (7)
02/05 (7)
01/05 (6)
12/04 (2)
11/04 (3)
10/04 (5)
09/04 (3)
08/04 (5)
07/04 (5)
06/04 (4)
05/04 (4)
04/04 (9)
03/04 (4)
02/04 (3)
01/04 (5)
12/03 (1)
11/03 (14)
10/03 (8)


IDE Improvements
2005-02-13

A couple of people used my Concern Map tool for the first time last week. Both of them (I said a couple) recommended creating an intermediate screen between the diagram view and the source code view. So that's what I implemented today.

Concern Map tool
The first image shows a concern map and result list, displayed after double clicking on a concept node (orange rectangle). The second (below) is a detail of the result list.

Detail of result list

The screen shots above come from double-clicking the node labeled 'Read operations', associated with the code query: //methodCall[@type='System.Data.Common.DataAdapter'][@name='Fill'] ("match any call to a method Fill on type DataAdapter"). Two matches are displayed in the tool window to the right.

My System.Windows.Forms is rusty, and EnvDTE80.Windows2.CreateToolWindow2 is not all it is cracked up to be, so this took a lot longer than you might think.

Back to weblog