"Mike Tuersley" wrote
>> My main point was exactly what you said, "No, it doesn't 'appear to be
object oriented', unless one does not understand what object oriented
really is and means." I was speaking of cad users who want to learn
programming and they don't have any idea what oop is at all. They also
don't want to pay to learn, they just want their 3day crash course to go
make whatever it is they want to make. <<
Mike - As I see it, that's a large part of the problem.
One can't effectively use an object-oriented API like
the .NET framework, and the managed wrapper API for
ObjectARX, without having a reasonable understanding
of fundamental OOP concepts. If the framework one
is using is object-oriented, then one must have some
conceptual understanding of OOP in order to use the
framework.
That's how we arrive at solutions like the one I posted
for the palette activation event problem. Because we
understand object inheritance and how overridden virtual
methods can be used to alter the behavior of existing
objects, we know how to deal with that sort of problem.
Bug since that kind of solution is not even possible in
VB 'Classic', chances are good that even an expert VB6
programmer is not going to see that solution, and so
they tend to gravitate towards hacking and dangerous
kludges like subclassing.
I've been working with real OOP for at least 10 years,
and it's come to the point where I can't even use VB
Classic any more. Writing even a short sample program
that shows how to use a component developed in ARX,
is like Chinese water torture.
I consider myself lucky that I chose the Delphi path
long ago, and that's mainly because so much of the
.NET framework was actually modeled after and/or
inspired by Delphi and its VCL framework (the same
person that invented Delphi, also happens to be largely
responsible for significant parts of the .NET framework,
as well as the C# and J++ languages). Because of
that, transitioning from Delphi to .NET was like a walk
in the park.
Delphi itself is now a first-class .NET language, and I
can compile much of my existing Delphi code to .NET
managed code, or native Win32 code, with little to no
change.
AcadXTabs: MDI Document Tabs for AutoCAD 2004/2005/2006
http://www.acadxtabs.com