now I know what you meant, thank you for your explanation. RE views: we know it would be great to have such functionality in our product, but it’s relatively complicated, because we support multiple databases and every database allows you to use different range of commands in view definitions etc. We would need two different approaches, one similar to the current situation (views defined in text - users can define views in detail, without limitations, incl. all available database specifics etc.) and second similar to the one you request (visual definition of views). We will see if we manage to add the second possibility to the product in future (it depends on priorities, our capacity and other factors). Right now I cannot promise it will be added to the product. Thank you for understanding it.
In any case, TDM3 should allow you to define everything in your model and you should not be required to do manual changes in the final DDL script. And I think we are OK with this statement.
RE repository: yes, we have a plan related to internal repository, but it’s priority is relatively low (compared to other features). We need to tune the software and finish other requests with higher priority first.
Finally let me thank you for your feedback. We are glad you like our product and please feel free to send us other ideas, suggestions and requirements. Your feedback is appreciated!!!