Re: 2nd WebCatalog2 Feature Request
This WebDNA talk-list message is from 1996
It keeps the original formatting.
numero = 10143
interpreted = N
texte = >Now I could hack in some code that assumes if you don't specify a >database, then it should look for a file called Catalog.txt and assume >it has the old 27 fixed fields in it. But I don't like this because I'd >rather have error-checking so that if you forget to specify a database it >can say Sorry, the SEARCH command requires that you specify a database >rather than just quietly assuming you _meant_ to use an old-style >Catalog.txt file. > >Personally I don't think it's too hard for webmasters to add that first >line of fieldnames, and I'd much rather keep the code clean, fast and >small. And I also like the new method of explicitly specifying the >database you plan to use, rather than having some hidden assumptions that >create tech support nightmares. >How tough would it be to script BBedit to do the necessary updates on the old catalog.txt file and perhaps even on html files containing the webcatalog.acgi statement. If I get to it myself before anyone else does I will offer it up to the group but I do not see that happening any time soon......but....perhaps if you Really cared about us you could do something like that in house???I'd rather see you retain the error checking features then bend the product too much to maintain backword compatability.Matt
Associated Messages, from the most recent to the oldest:
>Now I could hack in some code that assumes if you don't specify a >database, then it should look for a file called Catalog.txt and assume >it has the old 27 fixed fields in it. But I don't like this because I'd >rather have error-checking so that if you forget to specify a database it >can say Sorry, the SEARCH command requires that you specify a database >rather than just quietly assuming you _meant_ to use an old-style >Catalog.txt file. > >Personally I don't think it's too hard for webmasters to add that first >line of fieldnames, and I'd much rather keep the code clean, fast and >small. And I also like the new method of explicitly specifying the >database you plan to use, rather than having some hidden assumptions that >create tech support nightmares. >How tough would it be to script BBedit to do the necessary updates on the old catalog.txt file and perhaps even on html files containing the webcatalog.acgi statement. If I get to it myself before anyone else does I will offer it up to the group but I do not see that happening any time soon......but....perhaps if you Really cared about us you could do something like that in house???I'd rather see you retain the error checking features then bend the product too much to maintain backword compatability.Matt
matt@papersite.com (Matthew Steele)
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
RE: (1997)
Purchase Plugin Missing (1996)
Interfacing WebMerchant to www.fedex.com (1997)
[WebDNA] Array for Dummies (2010)
WebMerchant 1.6 and SHTML (1997)
WebDNA tables and commas - the fix (2004)
[WebDNA] Pretty URLS (2011)
Problems getting parameters passed into email. (1997)
carriage returns in data (1997)
system crashes, event log (1997)
The Solution to RE: Unexceling (was I need a smart quote...) (1999)
talking to MacAuthorize (1997)
Next X hits (1996)
Sendmail problem (2002)
I'm tired of all this! (2000)
PCS Frames (1997)
make a beep (2004)
Webcat issue (2006)
Requiring that certain fields be completed (1997)
Emailer (1997)