The approach we finally used and seems to work fine is the following :
- we created each frame individually, sometimes adding new constructors if needed
- we created a "main" frame and in the free form surface of this we placed factory objects
- we changed the type of the factory objects to these of the frames we wanted and handled the instanciation with event to method(constructor) connections from the "main" frame

One way or another some handwritten code is unavoidable.

Hi!

I would recommend you to use one VCE surface for every sceen.

This is because VAJ sometime loses the meta information coupled to the generated classes and the VCE surface and presentation.

This way if something happens you'll lose just one screen and not all of them.

Furthermore, VAJ uses alot of extra memory when putting to much components inside one VCE.

Hope it helps

Shahram Khorsand

FAQ Manager's Comment:

The VCE metadata is only "lost" if you export/import the class in .java or .class file format without the proper options enabled. It is well-documented that you must export/import in repository format or enable the "Generate Metadata method" option if you need to retain the VCE data. That said, the recommendation to have relatively small-grained VCE screens is a good one.

You can use the "sticky" property of the VCE to generate multiple copies of the currently selected widget. If you want these screens to be managed as one window, you'll want to nest them in the Swing hierarchy and set the layout manager properties. If you actually want multiple windows (an MDI approach), you're going to have to use a top level container to manage them and set visibility properties under control of your application classes.



Michael Murphy