Well, I'm certainely gonna buy Links in Mysql, but I have one question:
- I used a lot of mods in my links 2 version, and I wanted to know if in could changes de LinksMysql files the same way or if not how hard it would be.
Thanx,

theuls

---------------------------------
surfootball.com your soccer index

It would be challenging...Any of the Mods that opens the database files, reads data from the database files, and writes data to the database files (which is a majority of the Mods) would have to be re-written to access, read, and write to the MySQL (or whatever DBI you are using) tables.

Some of the Mods have been re-written, like the following:

1) Recommend It!
2) Report Deadlink!
3) @Yahoo Subcategory Link
4) Subcategories like Yahoo!

The rest of the Mods would have to be re-written.

Good luck!

Regards,

The layout is very similiar (i.e. there still is a nph-build.cgi, same templates, etc), however it would probably need some work. See:

http://gossamer-threads.com/...links-sql/links2.htm

for a list of mods already in Links SQL.

Cheers,

Alex

--
Gossamer Threads Inc.

Hi Anthro,
How about Loopy's altcategories? (http://www.online-sweepstakes.com/links-mods/)Would you happen to know if anyone is working on that?

I wonder if this answers my question... I'll crossing my fingers that it does.

> True category structure, the category name won't be tied
> to a link anymore, and we won't have the Alternate
> Category headaches that many of you have now. Also,
> generating category stats will be a thing of the past.

This is why I keep saying -- patience!!! :)

I know it's hard, but there is no reason to work like dogs to make changes that have been completely reworked in the next release.

From what I've been led to believe, the flat-file origins of Links SQL are left even further behind, and there are more modular "tools" for building the site.

What that means is that making changes will be more like writing function calls and pseudo code than writing real perl code. Some of those changes are evident in the 1.11 version. You can also see some of the "logic" in MySQLMan (although it's very different from Links SQL).

With the release now 10 days away -- and I think that's realistic now, it really pays to design your site, and not worry about the implementation of code changes yet.

With SQL (and the properly designed engine) site design could be as simple as setting some parameters in a parameter file and writing your templates.

I know I've abstracted most of my functions into include files, global and local variables, and templates with nested if's and such. I'm looking at the next release to take this even further, so that all user-config changes are done in external files, while the "guts" and "engine" are untouched.

There are so many changes that are inevitable, it doesn't pay to do anything until they are released so you can see them.

By unlinking the categories and the build-stats you'll see more flexibility in generating category and subcategory lists. This leads to better site navigation, and everything gets better. Add to that the integrated banner system, and you have ways of following users, tracking data, customizing pages, etc.

Now, all of this will come at a price -- you can't do it all on a virtual server. The more you ask the program to do on each "click" or user access, the more power you need in your server to handle it.

The last 6 weeks of waiting have let me play with multiple ideas for sites, and I can't wait to get my hands on this to see what new features I'll have to play with :)



http://www.postcards.com
FAQ: http://www.postcards.com/FAQ/LinkSQL/

Thanks for the words of wisdom pugdog... I'll wait. But I'm chomping at the bits!