then all you'd need to do is add a call to the list in nph-build.cgi to have this subroutine entered during each build.
You've illustrated the process for adding a new subroutine/page/feature to Link SQL pretty well!
The process is the same for adding any new "feature" page or item.
To add a new user-generated feature, you need to look at jump.cgi and search.cgi for the set up and calls, and for a frame work to insert your code.
There is a really good framework for adding features to Link SQL, and if you make sure all your calls go through DBSQL.pm and the HTML_Templates.pm files, then your subroutines should be portable from one version to the next.
I'm behind adding to the FAQ, and I need a new computer here before I'll have the resources to catch up. But, these are great ideas that are prime to help people start to make their own mods.
------------------
POSTCARDS.COM -- Everything Postcards on the Internet www.postcards.com
LinkSQL FAQ: www.postcards.com/FAQ/LinkSQL/
You've illustrated the process for adding a new subroutine/page/feature to Link SQL pretty well!
The process is the same for adding any new "feature" page or item.
To add a new user-generated feature, you need to look at jump.cgi and search.cgi for the set up and calls, and for a frame work to insert your code.
There is a really good framework for adding features to Link SQL, and if you make sure all your calls go through DBSQL.pm and the HTML_Templates.pm files, then your subroutines should be portable from one version to the next.
I'm behind adding to the FAQ, and I need a new computer here before I'll have the resources to catch up. But, these are great ideas that are prime to help people start to make their own mods.
------------------
POSTCARDS.COM -- Everything Postcards on the Internet www.postcards.com
LinkSQL FAQ: www.postcards.com/FAQ/LinkSQL/