Source-derived document; reported behaviour, inference and evidence gaps are identified in the text.
Return to: C07 — System Context and Components — topic detail
Form and presentation layer
In this document
System: Form and presentation layer
The supplied classes are Java/Swing-oriented generated artifacts. They import or instantiate javax.swing.*, java.awt.*, and custom com.ais.fc.ix.* components, including JLabel, TextBox, MaskedTextBox, FieldGroup, ScreenRecord, and GridBagLayout. E0004
Orderform.java.svn-base integrates JXTable and a GridColumnModel for order-line presentation. State_List.java.svn-base similarly supports a state-code/name selection grid with a scroll pane. These are direct structural findings and are stronger than claims inferred solely from help text. E0005 E0006
P_Ordcur.java.svn-base represents an order-summary form, while Order.java.svn-base represents a broader customer/order form containing customer identity and address fields, order number/date, ship date, and line-item fields. The files should not automatically be treated as one screen. E0006
Several constructors, including those in Order.java.svn-base, Orderform.java.svn-base, and P_Ordcur.java.svn-base, catch Exception with empty bodies. This could suppress initialization failures, although the supplied range does not show whether the surrounding framework logs or handles them. E0006
Cust.java.svn-base creates FieldGroup objects containing disabled text fields and calls setFieldCount(4) even though only one field is visibly added to each group. The custom FieldGroup semantics are unavailable, so the significance of this structure is uncertain. E0004
Ordcur.java.svn-base creates a customer ScreenRecord and calls customer.setFields() without arguments. The evidence cannot determine whether this is valid framework behavior or an incomplete/generated artifact. E0004
Harten documentation of the Informix 4GL and Java source repository, from the retained 17 October 2026 export. The exact upstream revision analysed is not established. Source findings do not establish runtime behaviour or equivalence between the implementations.
Evidence identifiers are retained for traceability. The underlying analysis records are not included in this public edition; credential values are redacted. About this case study.