Coral Tree: WDS Screen shots


These are screen shots of a example test interface in different "look and feel" modes during the same running of a single execution. These modes are not constrained to compile or execution flags. The interface can instantaneously change while running. In this case, these changes are wired into the buttons along the right side of the interface.

These snapshot images may be fuzzy due to dithering in the image format or the browser. The pallettes and methods used in the actual interfaces are chosen to prevent dithering which would otherwise make details difficult to read. Also, some of the widgets are configured in unusual ways for testing. For example, the button in the left-most partitioned area is normal. Most of the rest use a variety of other border modes. The button on the bottom of the left vertical partition is clipped inside a form set to manual placement.


Motif Look and Feel

Motif-style


Win32 Look and Feel

Win32-style


Athena Look and Feel

Athena-style




"Hybrid"-style


For this example of a test GUI, the abbreviated hierarchy is shown by:

Coral Tree WDS Test Hierarchy

The source for this example is wds_test.cc. The second window, which tests menus and pop-ups, is not shown here.

The top two dials on a test widget run off EW timer events, set to different frequencies. The other dial is connected to the work-function event which is turned on and off coordinated by a timer.

The widget above the dialsis a hierarchy. Each hierarchy node has it own hierarchy form and can instantiate more hierarchy nodes within it. The hierarchy builds as containers of containers. This can be used to visualize and affect hierarchial information such as file systems. A derived file hierarchy class has been created to do this.

Most of the "Look-And-Feel" differences shown are basically "Look" differences. You may note that the Coral picture has two text entry widgets with cursors, one of which is highlighted. The layered scoping allows for multiple widgets to request exclusive access to the same subset of possible events. In this case, two widgets request all keyboard events. But since they are in different scopes, the position of the mouse relative to the bounds of the scopes determines who gets the event. With overlapping scopes, the child-most widget gets priority, but ancestral scopes can still get event when the mouse is outside the child-more scope. Since the Look-And-Feel modes are completely configurable, you can activate this ability with any look. But, by default, these other modes will use the root-most scopes in order to more closely emulate their namesakes.

Local users can see this demo by running /home/symhost/sym/appl/coral/stable//bin/wds_test or, potentially, in /vobs/coral/wds.

A more recent image (Win32 mode, November 1997) features a WDS_table and WDS_Divider. The brighter colormap is closer to the Win32 default. The 20 value in the upper left form is a WDS_PointerEntry directly tied to the value used by middle timer in the WDS_GfxTest widget in the lower left corner.