CompuServe Thread

#third party management

2 messages in this thread
#28769From: Dave Devereaux-WeberJan 15, 1992 2:28 PM
Tony, Some time ago, I think you had a few things to say about third party LISP management. I am trying to set up the server version of ACAD for our company, and it would really be nice if you could dig that stuff out. If you need more of a memory tickle, the problem has to do with multiple third party apps all wanting to futz with ACAD.LSP. As I recall, you suggested an ACAD.LSP which kept its own list of apps to load at run-time. Ideally, I'd like to have one shared copy of ACAD.LSP which uses individually customized LISP configurations for each user. Is there some sort of Developer organization which attempts to coordinate such stuff? Dave Devereaux-Weber
#28888From: Tony Tanzillo [LISP TM]Jan 16, 1992 12:44 AM
Dave – Well, since I could give you the bottom line of that long discussion from memory, much faster than I could dig it up, I'll do that. The basic problem is multiple applications that contend for definition of C:XXXX and the S::STARTUP function. To put it simply, they can't coexist without some changes. In the case of S::STARTUP, what I recommend is that no application attempt to define it, and instead, each application puts the name of the file containing its startup code into an ascii file (call it 'INIT.LSP' if you wish) Along with that, the following is the only thing that needs to be placed in ACAD.LSP: (defun S::STARTUP () (cond ( (not (findfile "INIT.LSP"))) (t (setq init (open "init.lsp" "r")) (while (setq lspfile (read-line init)) (cond ( (or (findfile lspfile) (findfile (strcat lspfile ".lsp"))) (load lspfile)))) (close init))) ) In the case of two or more applications that attempt to redefine the same AutoCAD command and replace it with their own version, things are just not that simple, and this will require some intergration, to modify and/or to combine each application-defined command replacement into one. I can't give you any advice here, because each case must be dealt with individually, and there are no general guidelines to follow. If you have problems relating to the latter issue, than feel free to bring them up here, and I'm sure you'll get plenty of help and/or advice. -TonyT.