TheSwamp
Code Red => AutoLISP (Vanilla / Visual) => Topic started by: JohnK on January 30, 2020, 07:07:50 PM
-
Do you have a folder with a bunch of different projects/files in it or do you like a folder for each different project?
Please share a description of how your programming directory looks like.
This poll will run for 10 days.
-
You didn't include a "Both" option, John. I don't have many 'projects' per se, with many files. I do have separate folders for plain Acad, Civil 3D, & Land Desktop tools. But, within each of those folders are a multitude of files, most of which don't rely on any others. Now, if I were still actually coding in lisp and creating Dialogs, I would likely go with the folder per project option.
-
A folder for each project. I use a local SVN
D:/Dev/Projects/...
-
... I use a local SVN
D:/Dev/Projects/...
*wow* SVN?! Now that's old-school!
-
I use a folder per project.
~/programming/<language>/projects/tools/<project>
-
... I use a local SVN
D:/Dev/Projects/...
*wow* SVN?! Now that's old-school!
Been using it for years, no reason to change as it has all the features I need
-
Can’t argue with that.
-
One folder with many subfolders and files for each project. With git ;)
-
what is a 'project'?
-
Glad I wasn't the first to post who didn't know what a lisp project was. Do you need to put every folder in the SFSP and Trusted Locations? What's the purpose?
For Civil 3D it makes sense to keep drawings and associated files in a project folder, but this is the first I've ever heard of an AutoLisp programming directory.
-
what is a 'project'?
Your daily job :)
Glad I wasn't the first to post who didn't know what a lisp project was. Do you need to put every folder in the SFSP and Trusted Locations? What's the purpose?
What for? Before loading lisp turn off secureload system variable, and restore it after loading codes.
-
what is a 'project'?
Glad I wasn't the first to post who didn't know what a lisp project was. Do you need to put every folder in the SFSP and Trusted Locations? What's the purpose?
For Civil 3D it makes sense to keep drawings and associated files in a project folder, but this is the first I've ever heard of an AutoLisp programming directory.
When you create a program to "Move all stuff to Layer X" (for example) you don't/didn't create a folder for that lisp file(s)?
-
One folder with many subfolders and files for each project. With git ;)
That's interesting. One git repo and many projects?
-
Glad I wasn't the first to post who didn't know what a lisp project was. Do you need to put every folder in the SFSP and Trusted Locations? What's the purpose?
What for? Before loading lisp turn off secureload system variable, and restore it after loading codes.
I got out of AutoCAD and AutoLisp before trusted locations came about but apparently you can add an ellipsis after the path to include all sub-folders to the trusted locations.
C:\AutoLisp\Program\Directory\...
-
One folder with many subfolders and files for each project. With git ;)
That's interesting. One git repo and many projects?
No. one repo for one project.
-
One folder with many subfolders and files for each project. With git ;)
That's interesting. One git repo and many projects?
No. one repo for one project.
Oh! You're a subfolder person too. I get it, sorry. I misread your post.
-
Many folders...
-
what is a 'project'?
Your daily job :)
easy to say. it'd be great if i could put my daily job in a 'Tycoon' folder :wink:
-
When you create a program to "Move all stuff to Layer X" (for example) you don't/didn't create a folder for that lisp file(s)?
no
i will append the function to LayersLib.lsp
i have around 20 lsp libraries
i compile them
i load all of them with every drawing
-
When you create a program to "Move all stuff to Layer X" (for example) you don't/didn't create a folder for that lisp file(s)?
no
i will append the function to LayersLib.lsp
i have around 20 lsp libraries
i compile them
i load all of them with every drawing
Very interesting.
-
Yes the trusted paths … un documented !
For me 40 years programming around 7 directories, plus a couple of temporary \compiled-client.
Re load them all by Vovka you can use Autoload function to load once command is typed, I use also (if (not xxx)(Load "correct lisp")) the xxx is defun name.
One directory has 116 lisps as a commercial product easier to maintain, written 30 years ago and keeps getting added to, need to join some to shrink that number but when you look at 30 year old code realise how wrong you did it then.
-
Folder for Shared Library files
Folder for each Project subdivided as needed.
All under Git
Then a test structure emulating the clients setup which represents deliverables.
but I haven't touched Lisp for a year or so.