Time will tell.
--
<%= Clinton Gallagher
A/E/C Consulting, Web Design, e-Commerce Software Development
Wauwatosa, Milwaukee County, Wisconsin USA
NET csgallagher@REMOVETHISTEXTmetromilwaukee.com
URL http://www.metromilwaukee.com/clintongallagher/
LaGarde StoreFront 5 Affiliate: e-Commerce Software Development
SEE: http://www.storefront.net/default.asp?REFERER=-201499070
"Matt Stachoni" wrote in message news:gqo17v0d1k7epntemqasl2buidq3k6chq6@4ax.com...
> clintonG,
>
> You really need to lay off the NyQuil on this one.
>
> If you think that Web Services will integrate themselves into the
> design and CAD environments like you are thinking, you are simply
> mistaken.
>
> Not to be mean, but it sounds like you've read a smattering of OOP
> jargon without understanding the details of marrying programming
> technology with reality, and think it can be magically applied to an
> inherently unruly industry like Architecture or design in general.
>
> We've had object oriented programming for over 10 years. AutoCAD was
> rewritten over the courses of Releases 13 and 14 to complete a big
> phase of this transition. The concepts, trials and tribulations of
> polymorphism and inheritence are widely understood.
>
> However your 'namespace' concept may sound on paper, it's an empty
> idea, bereft a sound foundation in understanding how, say,
> polymorphism (to throw out an OOP term as you have) actually works.
>
> Your example is really talking about Proxy Objects, which have been
> around for some time. In fact, it sounds a lot like ADT, and the
> situation we have with Object Enablers.
>
> However, design firms don't create "graphic entities;" they create
> Objects. These Objects are simply instances of the AutoCAD classes
> that define how they work in AutoCAD - i.e., what properties and
> methods they have (to throw out some more OOP jargon).
>
> ADT objects (as an example) are created by ADT libraries, and can only
> be worked on in base AutoCAD with the inclusion of an ADT object
> enabler - which is pretty much about 80% of ADT's progamming base,
> BTW. Without the OE, you can see the Proxy Object, but cannot edit it
> in any way.
>
> They aren't "custom built" except for very specialized applications,
> and under very specialized circumstances, built by very specialized
> and highly skilled programmers.
>
> For another firm's AutoCAD to understand what's going on with these,
> and to react with these objects, it would need some sort of "object
> enabler" app that would provide the low level instructions for this.
>
> To abstract this to the Internet would mean that you don't actually
> need the Object Enabler, but have an open Internet connection that
> would grab the OE or parts of it as required to make your objects
> work. While Web Services does promise this (and more), you still need
> some sort of framework for developing your custom objects in the first
> place, to be able to publish the schema for these objects, and create
> a communications infrastructure for this.
>
> That takes serious and specialized programming skill and is not there
> in any run of the mill design firm. And it's not going to appear for
> something as pithy as layer management, either.
>
> Matt
> mstachoni@comcast.net
> mstachoni@bhhtait.com
>
> On Thu, 13 Mar 2003 09:34:37 -0800, "clintonG"
> wrote:
>
> >Jaime is having a hard time understanding the ramifications of how
> >Web Services will change design and drafting. I offer but one of many
> >aspects od design and drafting that will undergo change: layer management.
> >
> >A fundamental problem with layers occurs when drawings
> >are exchanged between different organizations. Right? All of this
> >will soon be history due to Object Oriented Programming, XML,
> >Web Services, and the .NET Framework. Java too for that matter.
> >
> >Using what is called a 'namespace' your drawings will be able to
> >contain graphic entities from another organization that will transform
> >themselves to your organization's standards while retaining their
> >own unique properties.
> >
> >That's the short version of what is called polymorphism in the
> >Object Oriented framework.
>
![Autodesk Design & Make Report](https://forums.autodesk.com/t5/image/serverpage/image-id/1350519iCB55845EBFC43016/image-size/large?v=v2&px=999" "Autodesk Design & Make Report")