rdnzl-devel September 2007

rdnzl-devel@common-lisp.net

5 participants
6 discussions

[rdnzl-devel] Simple dialog app.
by Ken Perry 18 Sep '07

18 Sep '07

I am wanting to create a simple dialog based APP with RDNZL. None of the examples I have found show how to just create either a form based or dialog based APP. The apropos example ties into C# code to create the form. So is there a way to do this totally with lisp and rndzl with out doing it like the apropos example? For example I want to put two buttons, a listbox, a label, and an edit box on a dialog or form all in lisp with rndzl. If you have examples or someone has already done this that I can use as an example that would be great. Ken

1 0

[rdnzl-devel] Re: in-process DLLs
by Brian Connoy 14 Sep '07

14 Sep '07

(Apologies if I did not submit this reply correctly) I'm a certified neophyte where it comes to RDNZL and .NET generally, but to learn one "can't directly create new .NET classes from within RDNZL" kinda blows my hopes out of the water (I think). My interest (similar to another poster here) is to utilize Common Lisp in a CAD application known as AutoCAD; which boasts API's for COM, .NET and ObjectARX (C++). I'd sooner chew my own arms off than code with C++ (or even C#) and hoped to find some way to take advantage of the .NET API directly using RDNZL. Sadly my knowledgebase is lacking, what with this talk of stubs and interop layers. Driving AutoCAD using Lispworks COM is a breeze, however. I'd be glad to offer any support I can in understanding how AutoCAD thinks ... the RDNZL bridge still has me scratching my head. B^) Brian C. >>> <rdnzl-devel-request(a)common-lisp.net> 9/14/2007 12:02 PM >>> Send rdnzl-devel mailing list submissions to rdnzl-devel(a)common-lisp.net To subscribe or unsubscribe via the World Wide Web, visit http://common-lisp.net/cgi-bin/mailman/listinfo/rdnzl-devel or, via email, send a message with subject or body 'help' to rdnzl-devel-request(a)common-lisp.net You can reach the person managing the list at rdnzl-devel-owner(a)common-lisp.net When replying, please edit your Subject line so it is more specific than "Re: Contents of rdnzl-devel digest..." Today's Topics: 1. Re: in-process DLLs (Andrew Wolven) ---------------------------------------------------------------------- Message: 1 Date: Thu, 13 Sep 2007 09:59:43 -0700 (PDT) From: Andrew Wolven <awolven(a)yahoo.com> Subject: Re: [rdnzl-devel] in-process DLLs To: General interest list about RDNZL <rdnzl-devel(a)common-lisp.net> Message-ID: <541154.70024.qm(a)web62407.mail.re1.yahoo.com> Content-Type: text/plain; charset=iso-8859-2 ----- Original Message ---- From: Edi Weitz <edi(a)agharta.de> To: General interest list about RDNZL <rdnzl-devel(a)common-lisp.net> Sent: Thursday, September 13, 2007 3:25:58 AM Subject: Re: [rdnzl-devel] in-process DLLs On Sun, 9 Sep 2007 20:47:05 -0700 (PDT), Andrew Wolven <awolven(a)yahoo.com> wrote: >> Edi, do you have any suggestions for franti*ek? > >Nothing more specific, unfortunately. As you'll know, you can't >directly create new .NET classes from within RDNZL. You'll have to >create a stub in C# or some other "native" language and then start >from there. > >Cheers, >Edi. _ I was just imagining a day ago or so that one could create COM server components in lisp and then use the MS tools to wrap it in an interop layer (a little fuzzy on this). Client code could be RDNZL of course. -AKW ______________________________________________ rdnzl-devel mailing list rdnzl-devel(a)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 ------------------------------ _______________________________________________ rdnzl-devel mailing list rdnzl-devel(a)common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/rdnzl-devel End of rdnzl-devel Digest, Vol 22, Issue 4 ******************************************

2 1

Re: [rdnzl-devel] in-process DLLs
by Andrew Wolven 13 Sep '07

13 Sep '07

----- Original Message ---- From: Edi Weitz <edi(a)agharta.de> To: General interest list about RDNZL <rdnzl-devel(a)common-lisp.net> Sent: Thursday, September 13, 2007 3:25:58 AM Subject: Re: [rdnzl-devel] in-process DLLs On Sun, 9 Sep 2007 20:47:05 -0700 (PDT), Andrew Wolven <awolven(a)yahoo.com> wrote: >> Edi, do you have any suggestions for františek? > >Nothing more specific, unfortunately. As you'll know, you can't >directly create new .NET classes from within RDNZL. You'll have to >create a stub in C# or some other "native" language and then start >from there. > >Cheers, >Edi. _ I was just imagining a day ago or so that one could create COM server components in lisp and then use the MS tools to wrap it in an interop layer (a little fuzzy on this). Client code could be RDNZL of course. -AKW ______________________________________________ rdnzl-devel mailing list rdnzl-devel(a)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

1 0

Re: Re[2]: [rdnzl-devel] in-process DLLs
by Andrew Wolven 13 Sep '07

13 Sep '07

Autodesk.Revit.IExternalApplication, hrm. Sounds like a .NET type based on a COM interface. I really can't tell you without seeing the documentation, but I am sure it is possible My suggestion to you would be to read the microsoft documentation. First read about COM (interfaces, guid's & progid's, type-libraries, in-process & out-of-process servers, etc.). Then read about .NET (assemblies, managed code, common language runtime, common datatype system, jit compiler, ms intermediate language). Then read about how COM components can be wrapped to make pseudo-dotnet types (interop). Take advantage of MS visual studio express object browser, and the COM/OLE viewer from the SDK. You will begin to get an understanding of how microsoft arranges it's operating system, and how companies like autodesk comply to that. Don't give up!! Edi, do you have any suggestions for františek? -AKW ----- Original Message ---- From: františek štáfek <fstafek(a)noise.cz> To: General interest list about RDNZL <rdnzl-devel(a)common-lisp.net> Sent: Sunday, September 9, 2007 4:55:29 PM Subject: Re[2]: [rdnzl-devel] in-process DLLs 23. srpna 2007, 8:32:23, Edi: EW> On Wed, 22 Aug 2007 17:58:06 -0700 (PDT), Andrew Wolven <awolven(a)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 _______________________________________________ rdnzl-devel mailing list rdnzl-devel(a)common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/rdnzl-devel ____________________________________________________________________________________ Moody friends. Drama queens. Your life? Nope! - their life, your story. Play Sims Stories at Yahoo! Games. http://sims.yahoo.com/

2 1

Re: [rdnzl-devel] in-process DLLs
by Andrew Wolven 09 Sep '07

09 Sep '07

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(a)noise.cz> To: rdnzl-devel(a)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(a)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

3 2

[rdnzl-devel] Re: x64 RDNZL
by Edi Weitz 07 Sep '07

07 Sep '07

[Cc to mailing list.] Hi Andrew, On Thu, 6 Sep 2007 20:14:23 -0500, "Andrew Wolven" <awolven(a)gmail.com> wrote: > I am having preliminary success with RDNZL on Windows XP x64 with > AllegroCL 64bit. I recompiled rdnzl.dll with MSVS 2008 beta after > tweaking some settings. If nobody else is working on this, I will > keep track of my changes, but I do have a day job. Thanks for the info. I don't have a 64-bit Windows machine yet, but I'll keep that in mind. Cheers, Edi.

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

rdnzl-devel September 2007