Alex, pretty close :)
You still need to "use" the Links.pm file for the basic defaults of all the modules.
Depending on what your script is trying to do, look at the headers for jump.cgi, add.cgi and search.cgi for which ever is closest to the type of script you are creating.
Then, use those headers to "use" the various libs and modules in the Links subdirectory. You need to specify that, since the various routines are somewhat related. If you are not using the database utiltiles at all (like no SQL calls) you can probably not load the DBSQL.pm and DB_Utils.pm, but you'll have to see. There might be some linked code in that you need to use, or at least create a dummy value for. (I've never not written an SQL program since starting with Links <G>).
Once you include the modules, you can then use any of the existing output routines, or make your own output routines, or even call &load_template directly if you know what you are doing.
I've used the links template parser to move all my programs (except hamweather) into the central links database system, so It can be done :)
I've not taken the time to prune, pare down, the various files to eliminate the unnecessary to increase performance for some programs, since the new version of links is on the way.
Besides.... if the program gets modular enough, the various .pm files can be compiled/loaded into Apache on start up, and then you don't have to worry about performance penalties or anything :)
BTW... using the Links.pm file is only if you use the modules as-is. If you start to prune them, or tune them for non-links use, you can cut out a lot of fat, and still get template performance from the routines. But HTML_Templates.pm requires some $LINKS variables set in the Links.pm file to load/run right.
http://www.postcards.com FAQ:
http://www.postcards.com/FAQ/LinkSQL/