>I think maybe a basic problem with this sort of interface lies within OOP itself. Suppose you have an scx with a number of vcx classes dropped on it. How do you go about setting up an interface with updateable code all in one place, without an awful lot of extra definitions? And even suppose you did, and updated classes from this, how would that affect other similar files with the same class code? How would they all be updated? How does Delphi handle this?


That's a good question. Basically any form/class only shows the code unique to it. So if you have a form with a dozen controls on it based on VCX's you have defined, you would only see methods you have overidden in your form in the file for that form. Each VCX would also have it's own form. So you don't end up with one file for all code in a project, or all code including inherited code, etc. You end up with a file for each form/class which has the specific code you have attached to it's methods. This doesn't cause any problem with controls you use in different forms, but if you have one basic form class that you base a lot of forms on you wouldn't see its code by opening up a form created with that class. You would have to open up the form class itself (or its program modules file) to see its code.

Basically, whatever code you find when you browse the scx/vcx memo fields would be accessable in one text file.

Hope this makes sense.