Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 361925

Summary: Window Builder fails to reverse-engineer simple JFrame program
Product: z_Archived Reporter: jrivers
Component: WindowBuilderAssignee: Project inbox <wb.swing-inbox>
Status: CLOSED FIXED QA Contact:
Severity: normal    
Priority: P3    
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard:
Attachments:
Description Flags
Example program that exposes the bug.
none
Stack Trace from in "design" tab none

Description jrivers CLA 2011-10-25 09:28:56 EDT
Created attachment 205914 [details]
Example program that exposes the bug.

I made a very simple JFrame class, and the Window Builder does not reverse-engineer it.  

I've attached the design-tab stack trace and example program.


The "Design" tab says:

Unknown GUI toolkit
The parser parsed the compilation unit, but can't identify any GUI toolkit, so WindowBuilder can't display any GUI to edit. This can be caused by one of the following reasons: 

This class is not an editable UI class and contains no UI components. 
WindowBuilder does not recognize the GUI toolkit or library used in this class. 
WindowBuilder does not understand this GUI type/pattern in a supported GUI toolkit. 
Problems exist with the classpath. For example, the compilation unit uses SWT classes, but the SWT/JFace libraries are not included into the classpath. 


Show stack trace.
Comment 1 jrivers CLA 2011-10-25 09:29:31 EDT
Created attachment 205915 [details]
Stack Trace from in "design" tab
Comment 2 jrivers CLA 2011-10-25 09:34:38 EDT
Found the problem.  At the time WB had never installed the Swing toolkit.  Once I started creating a new WB project, the Swing toolkit was installed, and after eclipse restarted, the reverse-engineering worked.

At the most, perhaps some slightly more friendly design tab error is appropriate, such as providing a list of installed toolkits with a button to install more.

Otherwise feel free to close.
Comment 3 Konstantin Scheglov CLA 2011-11-11 11:52:58 EST
Fixed in trunk.
Now we show better error message and suggest to use "Open UI Toolkits" button.