travlr
16th February 2007, 04:55
Hi.
I'm a self taught programmer coming from a procedural coding perspective (iso c) and I'm still developing my oop style skills.
I wonder, generally speaking, if I have a .ui derived class (qdesigner), should I use that class as the aggregate for other (non .ui) component (related) classes, or would practical convention consider otherwise?
Let me generalize this question... conventionally, is there a structured approach to determining how related classes might be aggregated "artistically"?
thanks,
travlr
I'm a self taught programmer coming from a procedural coding perspective (iso c) and I'm still developing my oop style skills.
I wonder, generally speaking, if I have a .ui derived class (qdesigner), should I use that class as the aggregate for other (non .ui) component (related) classes, or would practical convention consider otherwise?
Let me generalize this question... conventionally, is there a structured approach to determining how related classes might be aggregated "artistically"?
thanks,
travlr