Thanks for info; can you expand on the <iterator> component a little please?

The use case that would be best served by runtime created controls is dynamic screens, i.e screens/forms/reports that are completely dynamic; we would just employ a similar workaround to what we did in Oracle Forms which is to have a Form with many items, say 100 or 200 items and only make those that are required visible.

1) You get to implement your screens declaratively.
2)You see the Panels and their logical dependencies in the IDE. This really helps for maintenance purposes. Otherwise your entire UI is in the code which can be very error prone and hard to maintain in the long run.

As a side note, Michiel uses our design time API's to have his users create custom screens for themselves. So you can have your users customize their own screens if you want. If you want to do something similar he can chime in I suppose.