Actually, it can be done.... it depends on how complicated you want it to be. I wrote a brief script about 6 months ago, (a modified form of jump.cgi <G>) that took a LinkID from the database, and checked to see if there was a corresponding ProductID in the products database. If it did, it posted a link, that linked to a page that displayed the product, and a link to print out an order.
Because I need real-time order processing, of some sort, I put the product on hold. I've started to re-integrate it with PayPal, and have some basic system working.
I need a much more complex system, and I'm torn between making something that is targeted at my specific needs, or spending a bit more time and trying to make it more general.
I know once the script is released, people will want all sorts of changes, and there is no way I can do that for free scripts.
It's not an easy problem. Whatever the solution, the script is designed for one-of-a-kind products and real-time inventory management. It's geared to using the Link datbase as the "show room" and the "products" datbase to hold what's available. It's the type of thing that would work well for art, trading cards, garage sales, etc. It's not the sort of thing that would work for someone wanting to set up an inventory store -- there are already scripts out there that do that, and I'm not out to reinvent the wheel.
Once the new links comes out, hopefully we'll be able to start some collaborative projects, where plug-ins like this can be designed.
But, honestly, there is no reason to develop something like this for legacy systems. The added features in the new code will help cut design and maintennence time way down.
If you just want a small catalog, check out how
http://postcards.com works with the cards. A thumbnail is displayed on the catalog page, it links to a detailed page, and to a "send card" page (which could be an order page).
The _flow_ is the same.
PUGDOGŪ PUGDOGŪ Enterprises, Inc.
FAQ: http://postcards.com/FAQ
