I'm preparing to roll out ACA2013 in our office, and I'm trying to discover the best way to load our custom AutoLISP routines.
In our current setup, from ACA2008, I have a master LISP routine loaded and executed from Acaddoc.lsp. This demand-loads each of our custom routines via a defun statement, i.e. "(defun c:0 () (load "o.lsp") (c:0))".
In 2013, it appears that I have some more options, including loading through the CUI and using the ApplicationPlugins folder, assuming I can redirect it to the server in the file search path (though I may want to leave this local for users' customizations.) What I haven't found documented is how the CUI or ApplicationPlugins folder load the individual routines. Do they load on demand, or just dump everything into memory? I want to keep launch as light as possible, and avoid fully loading routines that a particular user may not be using.
My options, as I see them, are:
1 - Continue demand-loading routines via a master LISP executed from Acaddoc.lsp. Should I switch to using the Autoload function vs defun? Is there an advantage one way or the other?
2 - Demand load routines via a master LISP executed from the CUI.
3 - Load individual routines from the CUI.
4 - Load individual routines via the ApplicationPlugins folder.
Is there some other approach that I may be missing? Until I know the behavior of routines loaded in the CUI, I don't know which course to pursue.