Is Delphi a viable option

[Anonymous]

to drive autocad?
just wondering if Delphi (or java or ??? ) is as good or better an option
than dotnet
looking at the learning curve to convert from vb6 to dotnet and seeing the
moving target nature of that platform makes me wonder if there are other
better targets for investment of considerable time/effort?

if Tony is listening :-), are you still into delphi? if not why?

thanks
mark

[Anonymous]

VB6 & ActiveX API > VB.NET & .NET API = Large Learning Curve
VB6 & ActiveX API > VB.NET & ActiveX API = Small Learning Curve

[Anonymous]

Note this group is for targeting the managed AutoCAD API not .NET aware
languages. As such we don't care what language you use as long as you are
using it for managed AutoCAD programming.

Does Delphi or Java have an implementation that can target the managed .NET
Framework? If so - have at it - but remember what you need to learn is the
.NET Framework. Even if you know a language syntax you'll still have a large
curve applying that syntax to the .NET Framework.

If you are looking to keep using the ActiveX API via a COM aware language
like Delphi then the VBA group is the place for that. But keep aware that
ActiveX programming is the past and .NET programming is the future. Don't
confuse a language with the paradigms it supports. You can do both ActiveX
and managed .NET programming with all Microsoft languages - and probably all
languages that support the managed .NET Framework.

Since you are just starting my advice would be to first learn the language
you choose and how to target the .NET Framework with it. Once you get the
advanced basics down then start to learn the AutoCAD managed API. If you try
to both at the same time you'll end up fustrated and back here looking for
and easier way out ~).

There are many good groups out there which will help with learning the
language you choose and the .NET Framework. Accept that you have at least a
few months before you should be back here and you'll be well on your way!

"mp" wrote in message
news:6253460@discussion.autodesk.com...
to drive autocad?
just wondering if Delphi (or java or ??? ) is as good or better an option
than dotnet
looking at the learning curve to convert from vb6 to dotnet and seeing the
moving target nature of that platform makes me wonder if there are other
better targets for investment of considerable time/effort?

if Tony is listening :-), are you still into delphi? if not why?

thanks
mark

[Anonymous]

Delphi is not an option in my opinion. I haven't written anything new in
Delphi in about 5 years, and have only done a little maintainence/updating
of older Delphi code since then.

Borland sold it, and I don't see very many using it nowadays, and one
benefit of any programming language or API is its popularity.

--
http://www.caddzone.com

AcadXTabs: MDI Document Tabs for AutoCAD
Supporting AutoCAD 2000 through 2010

http://www.acadxtabs.com

Email: string.Format("{0}@{1}.com", "tonyt", "caddzone");

"mp" wrote in message
news:6253460@discussion.autodesk.com...
to drive autocad?
just wondering if Delphi (or java or ??? ) is as good or better an option
than dotnet
looking at the learning curve to convert from vb6 to dotnet and seeing the
moving target nature of that platform makes me wonder if there are other
better targets for investment of considerable time/effort?

if Tony is listening :-), are you still into delphi? if not why?

thanks
mark

[Anonymous]

Hi Tony,
Thanks for that update
mark

"Tony Tanzillo" wrote in message
news:6253579@discussion.autodesk.com...
Delphi is not an option in my opinion. I haven't written anything new in
Delphi in about 5 years, and have only done a little maintainence/updating
of older Delphi code since then.

Borland sold it, and I don't see very many using it nowadays, and one
benefit of any programming language or API is its popularity.

--

[Anonymous]

Thanks for the input
mark

"Paul Richardson" wrote in message
news:6253541@discussion.autodesk.com...
Note this group is for targeting the managed AutoCAD API not .NET aware
languages. As such we don't care what language you use as long as you are
using it for managed AutoCAD programming.

snip

[Anonymous]

Thanks Nathtay
Like paul said, since acad is moving away from ax - guess the curve just
keeps climbing
:-)
mark

wrote in message news:6253512@discussion.autodesk.com...
VB6 & ActiveX API > VB.NET & .NET API = Large Learning Curve
VB6 & ActiveX API > VB.NET & ActiveX API = Small Learning Curve

[Anonymous]

I would not be so quick to dismiss ActiveX. Just because VBA will be scrapped does not mean Autodesk do not plan to support the ActiveX API.

If you have functioning VBA or VB6 code it should be minimal effort to reuse this code in VB.NET compared to rewriting it using the .NET API let alone using the .NET API and learning another language syntax.

So if the curve keeps climbing it is only because of the decision you make.

[Anonymous]

np - And I in no way meant to totally dismiss ActiveX. Keep using your code
base by porting it if necessary while you learn the .NET api...

"mp" wrote in message
news:6253949@discussion.autodesk.com...
Thanks for the input
mark

"Paul Richardson" wrote in message
news:6253541@discussion.autodesk.com...
Note this group is for targeting the managed AutoCAD API not .NET aware
languages. As such we don't care what language you use as long as you are
using it for managed AutoCAD programming.

snip

[Anonymous]

the latest version is 2010

http://www.embarcadero.com/delphi


"mp" wrote in message
news:6253948@discussion.autodesk.com...
Hi Tony,
Thanks for that update
mark

"Tony Tanzillo" wrote in message
news:6253579@discussion.autodesk.com...
Delphi is not an option in my opinion. I haven't written anything new in
Delphi in about 5 years, and have only done a little maintainence/updating
of older Delphi code since then.

Borland sold it, and I don't see very many using it nowadays, and one
benefit of any programming language or API is its popularity.

--