1 / 22

CS395 Internship

CS395 Internship. Company: Rohde & Associates Intern: Chris Kulhanek. A Very Brief Background. Rohde & Associates, Inc. Architects Commercial Grade Construction ASD, DOT, Private Contractors $1,000,000.00 A Year In Contracts Been In Business Since 1997 I Am 1 of 5 Employees. The Problem.

bozica
Download Presentation

CS395 Internship

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CS395 Internship Company: Rohde & Associates Intern: Chris Kulhanek

  2. A Very Brief Background • Rohde & Associates, Inc. Architects • Commercial Grade Construction • ASD, DOT, Private Contractors • $1,000,000.00 A Year In Contracts • Been In Business Since 1997 • I Am 1 of 5 Employees.

  3. The Problem • AutoCAD is primary tool for production • Always looking for ways to improve production • Out of date scripts written with out of date language. • Need to improve scripts and improve scripting language • Most important, make finished product easy to deliver and install.

  4. Starting Point • Existing scripts are written in AutoLISP, a dialect of the Lisp programming language. • Existing scripts are manual install. Cumbersome for those not familiar with how to install them into AutoCAD. • No user manual on scripts of things go wrong.

  5. Goal • Covert Scripts to modern HLL. VBA or if needed C++. • Wrapper into an easy to distribute and use self install pack. • No command entry, use toolbars and menus.

  6. How was this accomplished? • VBA was first chosen • VBA has no easy way to wrapper and install • Was decided to convert again to AutoCAD ObjectARX and C++ API

  7. AutoCAD and ObjectARX • You are basically creating a .dll • Compile creates an AutoCAD .dll called .arx • Every .arx is a specific new command for AutoCAD ie: stairs is stairs.arx

  8. How do we package up? • Could write our own package, but why? • Installshield was used • Easy to use once native scripting language was understood

  9. Problems Encountered • General hassle of C++ • Lack of knowledge on .dll operations • Needed to learn the windows registry • AutoCAD is not user friendly concerning beta testing • The company upgraded to AutoCAD 2006 mid development

  10. Concluding Outline • Rank existing scripts by order of need • Convert to VBA / C++ routines • Include in shortcut menu and toolbar • Package into .exe for distribution

More Related