|
1
|
1 |
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
|
|
|
2 |
<html>
|
|
|
3 |
<head>
|
|
|
4 |
<title>Hotspot SA User Interface Notes</title>
|
|
|
5 |
</head>
|
|
|
6 |
|
|
|
7 |
<body>
|
|
|
8 |
<h1>Hotspot SA User Interface Notes</h1>
|
|
|
9 |
|
|
|
10 |
<h2>Workspace and Building</h2>
|
|
|
11 |
|
|
|
12 |
<p>
|
|
|
13 |
All the source code for the Serviceability Agent is in
|
|
|
14 |
<code>src/share/vm/agent</code> in the HotSport workspace
|
|
|
15 |
<code>/net/jano.sfbay/export/disk05/hotspot/ws/1.4/sa_baseline</code>
|
|
|
16 |
<p>
|
|
|
17 |
You can build the project by typing <code>gnumake</code> in the
|
|
|
18 |
<code>src/share/vm/agent</code> directory.
|
|
|
19 |
<p>
|
|
|
20 |
You can also use the default build target using the Ant build file (build.xml). You can download Ant from
|
|
|
21 |
<a href="http://jakarta.apache.org/ant">http://jakarta.apache.org/ant</a>. Documentation for Ant can be
|
|
|
22 |
found at <a href="http://jakarta.apache.org/ant/manual/index.html">http://jakarta.apache.org/ant/manual/index.html</a>
|
|
|
23 |
|
|
|
24 |
|
|
|
25 |
<h2>Running the project</h2>
|
|
|
26 |
|
|
|
27 |
<ul>
|
|
|
28 |
<li><code>java -cp classes sun.jvm.hotspot.HSDB</code>
|
|
|
29 |
</ul>
|
|
|
30 |
|
|
|
31 |
<h2>Feedback</h2>
|
|
|
32 |
<p>
|
|
|
33 |
Refactoring of package hierarchy. All user interface components should be in
|
|
15798
|
34 |
the ui package. Perhaps: sun.jvm.hotspot.ui.hsdb.Main for the HSDB.
|
|
1
|
35 |
<p>
|
|
|
36 |
The src\share\vm\agent area seems like a workspace so it should be organized like
|
|
|
37 |
one. In particular, I'd like to suggest the following directory layout:<br>
|
|
|
38 |
|
|
|
39 |
<ul>
|
|
|
40 |
<li>src: All sources that are curently under the sun directory.
|
|
|
41 |
<li>classes: compiled class files.
|
|
|
42 |
<li>lib: Resources like images, icons and jar files.
|
|
|
43 |
<li>docs: Documentation
|
|
|
44 |
<li>deploy: distribution bundles for Java Web Start.
|
|
|
45 |
</ul>
|
|
|
46 |
|
|
|
47 |
<p>
|
|
15798
|
48 |
Seems like there is a lot of redundant functionality. Perhaps
|
|
1
|
49 |
this can be consolidated with a <code>javax.swing.Actions</code> architecture.
|
|
|
50 |
|
|
|
51 |
<h2>Tasklist</h2>
|
|
|
52 |
|
|
|
53 |
<p>
|
|
|
54 |
<b>Stack memory pane</b>:
|
|
|
55 |
It's one of the more useful JVM debugging tools in the SA. However, it
|
|
15798
|
56 |
doesn't support any interaction with the text.
|
|
1
|
57 |
<p>
|
|
|
58 |
<b>Integrations with the NetBeans architecture (plug in).</b> See the
|
|
|
59 |
<a href="http://openide.netbeans.org">Netbeans Open APIs homepage</a>
|
|
|
60 |
|
|
|
61 |
|
|
|
62 |
<p>
|
|
|
63 |
HSDB: Object Histogram. Column sizes should be sized according the the
|
|
|
64 |
contents. i.e, The size and count columns should be narrow enought to
|
|
|
65 |
handle the largest window. Since there is a lot of data, sorting
|
|
|
66 |
and searching should be implemented.
|
|
|
67 |
<p>
|
|
|
68 |
|
|
|
69 |
<h2>Log</h2>
|
|
|
70 |
|
|
|
71 |
<i>Last modified: Tue Feb 05 19:15:12 Pacific Standard Time 2002</i>
|
|
|
72 |
<p>
|
|
|
73 |
sun.jvm.hotspot.oops.ObjectHistogram should be the underlying data
|
|
|
74 |
structure for the TableModels. It shouldnt bother with sorting the data -
|
|
|
75 |
the table model should do that. It should implement these methods:
|
|
|
76 |
|
|
|
77 |
<pre>
|
|
|
78 |
public int getSize()
|
|
|
79 |
public ObjectHistogramElement getElementAt(int row);
|
|
|
80 |
</pre>
|
|
|
81 |
<p>
|
|
|
82 |
ObjectHistogramElement should return the String that represents
|
|
|
83 |
the third column
|
|
|
84 |
|
|
|
85 |
|
|
|
86 |
<hr>
|
|
|
87 |
<address><a href="mailto:mark.davidson@sun.com">Mark Davidson</a></address>
|
|
|
88 |
<!-- Created: Mon Jan 28 14:33:47 Pacific Standard Time 2002 -->
|
|
|
89 |
<!-- hhmts start -->
|
|
|
90 |
Last modified: Tue Feb 05 20:05:13 Pacific Standard Time 2002
|
|
|
91 |
<!-- hhmts end -->
|
|
|
92 |
</body>
|
|
|
93 |
</html>
|