Author Topic: Lets Build!  (Read 6859 times)

0 Members and 1 Guest are viewing this topic.

Bob Wahr

  • Guest
Re: Lets Build!
« Reply #30 on: September 14, 2005, 01:45:28 PM »
Looks as though this is going the way of LISP. :ugly:
 I have limited knowledge of that language so, I will be of limited help. I will do my best though. :mrgreen:
I'm personally going to ignore all efforts to lispify it.

Murphy

  • Guest
Re: Lets Build!
« Reply #31 on: September 14, 2005, 03:11:14 PM »
Sounds good to me.  :-D

Andrea

  • Water Moccasin
  • Posts: 2372
Re: Lets Build!
« Reply #32 on: September 14, 2005, 03:19:37 PM »
Keep smile...

deegeecees

  • Guest
Re: Lets Build!
« Reply #33 on: September 14, 2005, 03:32:14 PM »
Here's a thought:

..........................


No, really:

VBA vs. Lisp?

Bob Wahr

  • Guest
Re: Lets Build!
« Reply #34 on: September 14, 2005, 03:43:36 PM »
No holds barred?

Cage match??

Ladder match???

For the undisputed heavyweight championship of acad????

Nah, it's a crap battle that boils down to person vs person with rules too hard to define and an outcome that doesn't matter.  What I said wasn't intended to be a slam on lisp.  All I was saying was that my lisp sucks and if I was going to take part, the part that I take would have to be a VBAish part so IF the project took a turn towards lisp only, I would ignore the turn and keep contributing what I was able to contribute as I had time to contribute it.

whdjr

  • Guest
Re: Lets Build!
« Reply #35 on: September 14, 2005, 05:49:10 PM »
I would take the opposite stand from Bob as I only know Lisp and not VBA. :mrgreen:

deegeecees

  • Guest
Re: Lets Build!
« Reply #36 on: September 14, 2005, 06:35:41 PM »
Thats fine, I'll direct traffic as I know both.

Andrea

  • Water Moccasin
  • Posts: 2372
Re: Lets Build!
« Reply #37 on: September 14, 2005, 10:00:52 PM »
for my own...

I had bad experience with VBA...

all program made with VBA for AutoCAD...
AutoCAD need to load all the VBA module.

So this is a little heavy for AutoCAD.

Also, if you need to update MSOffice...Be careful..
because Office have a VBA module too...and re-install over the old release...
so after that, you can not load VBA module in AutoCAD....need to re-install-it.

I know that.....I'm paid to make tests !! ^-^
Keep smile...

MP

  • Seagull
  • Posts: 17750
  • Have thousands of dwgs to process? Contact me.
Re: Lets Build!
« Reply #38 on: September 14, 2005, 10:04:03 PM »
VBA is fine for casual programming but it's not suited to building utilities like the ones being suggested in this thread (IMO). Visual BASIC (Pro or Enterprise) on the other hand is perfectly fine, as is Delphi, VC ...
Engineering Technologist • CAD Automation Practitioner
Automation ▸ Design ▸ Drafting ▸ Document Control ▸ Client
cadanalyst@gmail.comhttp://cadanalyst.slack.comhttp://linkedin.com/in/cadanalyst

Murphy

  • Guest
Re: Lets Build!
« Reply #39 on: September 15, 2005, 06:02:13 AM »
I have created numerous stuff in VBA. Look at my sig for a Spanner-type program that runs in Excel.
I have also done 'batch' stuff in VBA. Only problems I have encountered is with referencing the correct versions of programs.
I do not have C++ or VB so, go forward with what you want.

Thanks for the ideas, though.

deegeecees

  • Guest
Re: Lets Build!
« Reply #40 on: September 20, 2005, 02:16:42 PM »
Okay, I'm keeping this thread alive so, bear with me here. I have a TON of grunt work to do here at my place of employment which is why I have been so sparse on the witty banter here in the swamp. As soon as I catch up at work, I'll catch up here  --><--

BTW, I really like this smiley  :ugly:

MvdP

  • Guest
Re: Lets Build!
« Reply #41 on: September 23, 2005, 12:29:03 PM »
Keeping this thread alive......!!!!!!!

deegeecees

  • Guest
Re: Lets Build!
« Reply #42 on: September 23, 2005, 01:13:19 PM »
It's gonna be a while till I get some "spare" time. I've just realized a project here that needs coding. We (at work) handle many different accounts, which in turn lends itself to multiple "groups", which in turn makes use of multiple CAD configurations (i.e. directory structures, titleblocks, and layout elements), as well as multiple disciplines. I'm undertaking the monumental task of creating custom AutoCAD, and (yes, I hate it) Microstation interfaces. This is no easy task as there is absolutley no rhyme or reason to what is currently in place.

I love Cad Management!