Maybe I should encapsulate each of the controls to a user control, and then make a virtual ActiveX control (no visual interface) to organize these controls into a united thing.
SlowGrace
2009-07-30 11:00:35
A:
+2
A:
- Create a ActiveX DLL (not control)
- Define a Interface for the form in
the DLL - Move all your logic into one or more class in the DLL and have the routines interact with the form through the interface
- Implement the Interface in the form
- One initialization of the app have the form register itself with the ActiveX DLL
This will effectively eliminate copy and paste between the different apps.
For example for my metal cutting application I have a Shape Form, a Shape Screen class, and a bunch of shape classes. Two of the methods of the shape class are DrawScreen which has a parameters of type ShapeScreen, and GetValues which also has a parameter of type ShapeScreen.
DrawScreen uses the method of ShapeScreen to setup the entry screen and Shape Screen setup the Form through the IShapeForm interface. The GetValues uses Shape Screen methods to get the entered shape values which in turns uses the IShapeForm to get the values from the form.
This setup proved useful when we had to develop different shape entry forms in response to customer requests. The new form just implemented the IShapeForm interface and the rest of the software was untouched.
RS Conley
2009-07-30 13:01:37
It sounds "graceful", thank you. As I am not quite acquainted with ActiveX dll and the concept of interface. Could you please give some further explanation? ShapeScreen is a class in the dll, and it has an interface called IShapeForm. And where are the shape classes? Are they in your dll also? In short, I just cant make out how to "Implement the Interface in the form "? Does it has anything to do with polymorphism?
SlowGrace
2009-07-30 17:54:16
Would you please give me several lines of codes to illustrate the whole architechture?
SlowGrace
2009-07-30 18:01:22
Or do you mean there is a class called IShapeForm in your dll? All classes in your dll will interact with IShapeForm when they need do so with the real form. And when I use the dll, I shall register a real form to the IShapeForm class. Yes, I guess this is your meaning.
SlowGrace
2009-07-30 18:04:13
Would you please give some peudo-codes to illustrate the below two tasks? (1)"Shape Screen setup the Form through the IShapeForm interface."(2)"uses the IShapeForm to get the values from the form."
SlowGrace
2009-07-30 18:08:23
If you google this, "vb6 activex control tutorial", it might help.
Gutzofter
2009-07-31 04:17:15
Dan Appleman's book *Developing COM/ActiveX components with Visual Basic 6* is excellent. Or just read the VB6 programmer's guide, it actually explains the basics very well. http://msdn.microsoft.com/en-us/library/aa240845(VS.60).aspx
MarkJ
2009-09-24 09:37:53
A:
It looks like what you have is a view, domain logic, and data. Your major problem I foresee is item two, it is not static in appearance and logic from app to app. Maybe what you need is two separate controls? Left panel and right panel. The right panel probably is going to implement some type array of controls, since they are not going to be static.
Gutzofter
2009-07-31 04:25:31