Re: Full view of a private partial view cannot be a subtype

["Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>]

On 04/12/2017 22:48, Jeffrey R. Carter wrote:

> With a composition approach you would at a minimum have a list of every 
> operation on every type right there with the type declaration.

Overloaded with the same operations from other widget types.

The fallacy of the argument comes straight from the point that the 
number of operation is just same. GPS is far worse in finding overloaded 
operations.

If Button, Toggle_Button, Radio_Button etc were unrelated then in each 
event handler within a monstrous case over all possible widgets emitting 
the event, good luck finding their operations, cutting and pasting same 
code, you cannot reuse because types are unrelated. Yes, generics they 
will serve the final stroke to this insanity.

> I have been looking at this for over 2 decades and have yet to see a 
> counterexample. If you think you know of one I'd like to see it. Maybe 
> I'm weird and most people have no problem understanding these things, 
> but I've seen plenty of other experienced people have similar 
> difficulties, so I doubt it.

There are no more GUI frameworks based on overloading. Aggregation is 
used only for parent-child widget relationship.

You are welcome to propose one. After all it is only the interface you 
have to design. All the implementation can be based on an existing 
framework with inheritance and overriding...

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de