So I had a complex class that seemed to be doing to much by itself. An order item class. So I refactored into two different classes. An order item class and an order size class.
In an instance like this what do you think about the order size class maintaining a reference to the interface of the order item class. There are several properties of the order item class that I consistently need access to in the order size class.
I know that a child is not supposed to know about the parent but what about in a case like this
Thanks,
Dean.
oop question-refactoring and two classes communicating
Hot Topic
- Why the interfaces (from a reference) are not accessible ?
- Very slow speed on displaying controls in a form
- Object Visibility
- textbox selectall not working
- Loops
- Delegates and KeyUp
- SignTool reported an error 'An internal certificate chaining error has occurred.
- Windows and Console Application
- How insure something runs when form is loaded
- removal microsoft.visualbasic namespace
Visual Basic
- Windows Media Player Control not working as it did with VB .NET Express
- Control Names
- Inputting Data in MS Access with vb.net
- Using the Ampersand
- Directx8
- VB Excel Worksheet
- Runtimeerror 429 ActiveX component cannot create object
- Address Of just got funkier!
- Calling a click event
- Drawing Lines on a form
oop question-refactoring and two classes communicating
Piotr Celej
It's tough to give detailed advice without seeing your object model, but my first reaction is why would OrderSize need to be a separate class I'd think that would just be a property on your Order class.
The way I usually implement something like this is have an Order class, made up of OrderItems, and if necessary that can be composed of OrderLineItems.
Hope that helps,
Jonathan Aneja
The VB Team