Hi Wagner,
The problem is that you can easily get circular references in the design - procedure A needs procedure B which needs Procedure C which in turn needs procedure A. No amount of analysis would determine a correct creation order.
But, if you create the domains/procedures without constraints/bodies then on a second round, populate them, you do not care about creation order as it all takes care of itself. It is easier to implement and can not be broken by complex designs.
As for the source, I agree with you in terms of the subscription, BUT as the code base would benefit from/require most of the components in the VCL subscription, it would be a benefit if the source was made available to those who have purchased the datamodeler AND the vcl subscription.
I just wish you had a single global license for your products. If I buy the subscription, I get one set of components, If I buy the component pack, I get a different set (notably the intraweb components).
Just a thought.
best regards
Dalton