I think there's something fundamental missing from the documentation. I've looked at every tutorial, the PDF's, the example applications and, unless I'm not as thorough as I think, nothing tells me how the execution process operates on the application design. Since all views, data models and processes are splattered (well it's not pretty) onto the view screens, I see blocks of each group seemingly placed randomly. I'm looking at the Web Services - Weather example and see a couple of processes (actions) that set parameters and initialise screens - great. They also call the view itself!??! I also see blocks of view/display objects, again at 'interesting' positions. I have ABSOLUTELY no idea what the execution order is. The repository explorer would be my favourite place to see this, but no, it's just an alphabetic tree list.
Either this is a DOH! moment for me (well 25 years of app. design & dev may have hardened my perceptions) OR because you understand your own tool so well you imagine everybody will "just get it". My guess is, for every 100 people who try the tool, 99 think this looks like MS Visual Studio on acid and give up. That's a shame because you have something here. It's MUCH better than WaveMaker (they can't even open wsdl-based Web Services successfully, but at least the visual design side is 'normal').
For best results, use the Firefox browser..