Re: [rdnzl-devel] in-process DLLs
Are you using Franz AllegroCL? Allegro has the ability to generate itself as an in-process COM dll. You can also make an ordinary DLL with Allegro. In either case, if Revit is based on AutoCAD, you can write a small ARX application with MSVC++ which loads the DLL into AutoCAD's process space. Once you have Allegro running inside AutoCAD, RDNZL will communicate with AutoCAD's .NET API. If Revit is not based on Autocad, I am sure the procedure would be similar. AKW ----- Original Message ---- From: františek štáfek <fstafek@noise.cz> To: rdnzl-devel@common-lisp.net Sent: Wednesday, August 22, 2007 3:36:07 PM Subject: [rdnzl-devel] in-process DLLs Hello everybody, I would like to use common lisp to program / script CAD application Autodesk Revit via its .NET API. API readme says: "API supports in-process DLLs only" What does it mean? Is there any chance to use RDNZL with this statement? (Sorry for dumb question..., I'm completely new in this area, I just wanted to use my quite good autolisp knowledge for scripting Revit application)? Regards Frantisek Stafek _______________________________________________ rdnzl-devel mailing list rdnzl-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/rdnzl-devel ____________________________________________________________________________________ Be a better Heartthrob. Get better relationship answers from someone who knows. Yahoo! Answers - Check it out. http://answers.yahoo.com/dir/?link=list&sid=396545433
On Wed, 22 Aug 2007 17:58:06 -0700 (PDT), Andrew Wolven <awolven@yahoo.com> wrote:
Allegro has the ability to generate itself as an in-process COM dll.
Right. And you can do the same thing with LispWorks and Corman Lisp as well. I think that should work fine. I've built in-process DLLs with LispWorks pretty often, but admittedly never one which deployed RDNZL. Cheers, Edi.
23. srpna 2007, 8:32:23, Edi: EW> On Wed, 22 Aug 2007 17:58:06 -0700 (PDT), Andrew Wolven <awolven@yahoo.com> wrote:
Allegro has the ability to generate itself as an in-process COM dll.
EW> Right. And you can do the same thing with LispWorks and Corman Lisp EW> as well. I think that should work fine. I've built in-process DLLs EW> with LispWorks pretty often, but admittedly never one which deployed EW> RDNZL. thanks for info. well maybe this is anyway too above my head. The "getting started" guide for REVIT API says, If I want to write application, I need to do this: "How to write an External Application: Implement support for a specific interface, in this case Autodesk.Revit.IExternalApplication." Is this doable with RDNZL? What would I need If I would like to expose a Common Lisp console as part of this "external application"? Is this doable, or does it require "a lot of work" and lot of .NET experience... (now I really think I don't know what I'm talking about:-) -- františek štáfek
participants (3)
-
Andrew Wolven -
Edi Weitz -
františek štáfek