This webpage lists
the screenshots for five open source applications, CrosswordSage,
Java-Chess, JMSN, GanttProject , and FreeMind.
For each application, we presented the screenshots of their main windows in
three different situations as following,
1. The Screenshot
from the application execution.
2. The Screenshot
from the Swing Designer GUI editor.
3. The Screenshot
from the Swing Designer GUI editor augmented with our dynamic analysis.
Furthermore, we
also identify the differences between the real execution result and the
rendering result from the Swing Designer augmented with dynamic analysis.
Finally, we give
the statistical result from another GUI editor, Jigloo
to present the size of dynamic main window model and the size of original
design model relative to dynamic model, which is just as we did in the Section
6.2 of our paper.
CrosswordSage V
Figure 1.
CrosswordSage Execution
Figure 2. Swing
Designer
From this figure,
we can see that the WordSolverPanel (the panel under the menu in Figure 1) is
missed. However, developers are still
able to find the WordSolverPanel component from the Property Editor of Swing
Designer. When they find the panel, they can open and edit it. So here, we say
that CrosswordSage can be rendered 100%. The only problem is that developers
cannot see a complete design view if they don’t use our dynamic analysis.
Figure 3. Swing
Designer augmented with dynamic analysis
Differences
1. The icon of the main window (JFrame) in Figure 1 is different with
Figure 3.
This is because the developer did not set icon for the main frame. When the
program is executed, the default icon (the coffee cup) is put on the JFrame by
JVM.
Java-Chess
(JChess) V
Figure 1.
Java-Chess Execution
Figure 2. Swing
Designer
Figure 3. Swing
Designer augmented with dynamic analysis
Differences
1. The icon of the
main window (JFrame) in Figure 1 is different with Figure 3.
This is because the
developer did not set icon for the main frame. When the program is executed,
the default icon (the coffee cup) is put on the JFrame by JVM.
JMSN
V
Figure 1.
JMSN Execution
Figure 2. Swing
Designer
From this Figure,
we can see that the main window cannot be rendered at all by Swing Designer.
However, in the Section 7.2 (View-Navigation Comparison) of our paper, we
counted the size of the COTS editor model ("main window") of JMSN as
50. This is because we counted the number of widgets, widget properties
set based on the content in the Property Editor (on the top left side of the
Figure 2). The reason we did that is because the items that can be displayed in
the Property Editor can also be used as navigation and editing purposes even
they cannot be rendered as a view in Swing Designer.
Figure 3. Swing
Designer augmented with dynamic analysis
Differences
1. The ComboBox in Figure 1 is different with Figure 3.
When Swing Designer renders JComboBox, it puts the "Combo item
1" there to help developers understand JComboBox
.
GanttProject V
Figure 1.
GanttProject Execution
Figure 2. Swing
Designer
Figure 3. Swing
Designer augmented with dynamic analysis
Differences
1. The JTables
(the component under the “Gantt project” picture) are different between Figure
1 and Figure 3. There are a few items in the JTable on Figure 3.
Just like JComboBox, Swing Designer renders JTable by offering some example
items to help developers understand. So this difference is because how Swing
Designer renders JTable.
2. Some buttons are grey in Figure 1, but they are colorful in
Figure 3, for example, save button.
This is because we have not yet implemented a pointcut for catching when
widgets are disabled (grayed out) as we said in Section 6.2.
3. There are two
fixed-width components (marked with red squares) between the buttons in Figure
3 as the following figure,
These two
components are invisible in Figure 1. Swing Designer makes them visible to help
developers edit them.
Besides the above
examples, the following figure illustrates that all the MenuItems in the
rendering result are
editable.
back to top
FreeMind V
1. FreeMind
Execution
2. Swing Designer
3. Swing Designer
augmented with dynamic analysis
Differences
1. The ComboBoxs
are different between Figure 1 and Figure 3.
As we said in JMSN, Swing Designer renders ComboBox by
offering a example item "Combo item 1". In this example, even the two
ComboBoxs have items, for example, 100% and the url. Swing Designer just
renders them as "Combo item 1".
2. Some
icons are grey in Figure 1, but they are colorful in Figure 3.
This
is because we have not yet implemented a pointcut for catching when widgets are
disabled (grayed out) as we said in Section 6.2.