Re: attn: smitmicro - cart limitation
This WebDNA talk-list message is from 2002
It keeps the original formatting.
numero = 44469
interpreted = N
texte = me too...On Tue, 29 Oct 2002, Stuart Tremain wrote:> Hey that looks like a winner :) > > > On Tuesday, October 29, 2002, at 11:13 AM, Alain Russell wrote: > > > What about having a headers.db - same principle as the formulas.db > > (but not > > case sensitive) > > > > In there you could have definitions > > > > HEADER NAME > > 1 my_custom_name > > 2 another_one > > 3 this_is_cool > > > > Then we can reference the header using either our own references - or > > we can > > keep using [header1]. I wouldn't imagine there would be much extra > > load to > > reference the extra db - perhaps I am wrong. > > > > Alain > > > > > >> on 10/27/02 7:36 PM, NovaDerm Skincare Science at > >> support@novaderm.com so > >> noted... > >> > >>> Gawd I'd love user defined headers, but I think this is beyond the > >>> limitations of the engine as designed, no? > >> > >> I've asked this one a few times over the years. Here's the last one > >> from the > >> beta list nearly two years ago and Scott's response. > >> > >> --------------------------------------------------------- > >> 2000/12/22 01:07:25 Rob Marquardt Request: user-defined cart > >> headers > >> > >>> For any site of any depth I've worked on, I also have a cheat sheet > >>> on hand > >>> with a long list of cart header field names on the left side, and an > >>> explanation of what they're being used for on the right (so when I > >>> have to > >>> rework a site in seven months time, I know just what the hell I was > >>> sticking > >>> into Header34 or CartPassword -- a situation I find myself in > >>> again right > >>> now). > >>> > >>> What I propose is similar in function to the .hdr files that were > >>> introduced > >>> for databases in WebCatalog 2.1. A tab-delimited file called, say, > >>> cart.hdrcontaining a list of custom field names would be placed in > >>> a site's > >>> ShoppingCarts folder. If no cart.hdr file is present, the > >>> standard cart > >>> header names as currently defined would be used (eliminating > >>> potential > >>> confusion for new users who'd be unlikely to use this feature > >>> immediately). > >>> > >>> Benefits of this system: > >>> > >>> * More legible code. I'd far rather see [bankAddress1] inside an > >>> [orderfile] > >>> than [Header14]. > >>> > >>> * More variables available. No longer limited to headers 1-40, you > >>> could > >>> assign as many header variables as needed. > >>> > >>> * Variable sets can be customized on a site-by-site basis. > >>> > >>> A generic cart.hdr file could be included that contains all the > >>> existing > >>> headers so those who need the original header names (so as not to > >>> break > >>> WebMerchant and the like) can still append new ones at the end. > >> > >> --------------------------------------------------------- > >> 2000/12/22 17:44:15 Scott Anderson Re: Request: user-defined > >> cart > >> headers > >> > >>> I'm not sure if that is worth the risk of having mis-matched WebDNA > >>> source > >>> and cart.hrd files. Also, the engine has these names hard coded in > >>> the > >>> commerce classes. I'm thinking that cheat sheets and code > >>> documentation are > >>> just fine for trackig what [HeaderX] is used for. > >> > >> --------------------------------------------------------- > >> > >> Maybe with WebDNA 5.0 the engine is flexible enough to allow this? > >> > >> > >> Rob Marquardt > >> Designer/Resident Wirehead > >> Toast Design > >> > >> 800 Washington Avenue North > >> Minneapolis MN 55401 > >> 612.330.9863 v > >> 612.321.9424 f > >> www.toastdesign.com > >> > >> > >> ------------------------------------------------------------- > >> This message is sent to you because you are subscribed to > >> the mailing list
. > >> To unsubscribe, E-mail to: > >> To switch to the DIGEST mode, E-mail to > >> > >> Web Archive of this list is at: http://search.smithmicro.com/ > > > > > > ------------------------------------------------------------- > > This message is sent to you because you are subscribed to > > the mailing list . > > To unsubscribe, E-mail to: > > To switch to the DIGEST mode, E-mail to > > > > Web Archive of this list is at: http://search.smithmicro.com/ > > > > > Regards > > Stuart Tremain > idfk web developments > 114a/40 yeo street neutral bay 2089 australia > t +612 9908 2134 > f +612 9908 4837 > > > > ------------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > To switch to the DIGEST mode, E-mail to > Web Archive of this list is at: http://search.smithmicro.com/ > ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/
Associated Messages, from the most recent to the oldest:
me too...On Tue, 29 Oct 2002, Stuart Tremain wrote:> Hey that looks like a winner :) > > > On Tuesday, October 29, 2002, at 11:13 AM, Alain Russell wrote: > > > What about having a headers.db - same principle as the formulas.db > > (but not > > case sensitive) > > > > In there you could have definitions > > > > HEADER NAME > > 1 my_custom_name > > 2 another_one > > 3 this_is_cool > > > > Then we can reference the header using either our own references - or > > we can > > keep using [header1]. I wouldn't imagine there would be much extra > > load to > > reference the extra db - perhaps I am wrong. > > > > Alain > > > > > >> on 10/27/02 7:36 PM, NovaDerm Skincare Science at > >> support@novaderm.com so > >> noted... > >> > >>> Gawd I'd love user defined headers, but I think this is beyond the > >>> limitations of the engine as designed, no? > >> > >> I've asked this one a few times over the years. Here's the last one > >> from the > >> beta list nearly two years ago and Scott's response. > >> > >> --------------------------------------------------------- > >> 2000/12/22 01:07:25 Rob Marquardt Request: user-defined cart > >> headers > >> > >>> For any site of any depth I've worked on, I also have a cheat sheet > >>> on hand > >>> with a long list of cart header field names on the left side, and an > >>> explanation of what they're being used for on the right (so when I > >>> have to > >>> rework a site in seven months time, I know just what the hell I was > >>> sticking > >>> into Header34 or CartPassword -- a situation I find myself in > >>> again right > >>> now). > >>> > >>> What I propose is similar in function to the .hdr files that were > >>> introduced > >>> for databases in WebCatalog 2.1. A tab-delimited file called, say, > >>> cart.hdrcontaining a list of custom field names would be placed in > >>> a site's > >>> ShoppingCarts folder. If no cart.hdr file is present, the > >>> standard cart > >>> header names as currently defined would be used (eliminating > >>> potential > >>> confusion for new users who'd be unlikely to use this feature > >>> immediately). > >>> > >>> Benefits of this system: > >>> > >>> * More legible code. I'd far rather see [bankAddress1] inside an > >>> [orderfile] > >>> than [Header14]. > >>> > >>> * More variables available. No longer limited to headers 1-40, you > >>> could > >>> assign as many header variables as needed. > >>> > >>> * Variable sets can be customized on a site-by-site basis. > >>> > >>> A generic cart.hdr file could be included that contains all the > >>> existing > >>> headers so those who need the original header names (so as not to > >>> break > >>> WebMerchant and the like) can still append new ones at the end. > >> > >> --------------------------------------------------------- > >> 2000/12/22 17:44:15 Scott Anderson Re: Request: user-defined > >> cart > >> headers > >> > >>> I'm not sure if that is worth the risk of having mis-matched WebDNA > >>> source > >>> and cart.hrd files. Also, the engine has these names hard coded in > >>> the > >>> commerce classes. I'm thinking that cheat sheets and code > >>> documentation are > >>> just fine for trackig what [HeaderX] is used for. > >> > >> --------------------------------------------------------- > >> > >> Maybe with WebDNA 5.0 the engine is flexible enough to allow this? > >> > >> > >> Rob Marquardt > >> Designer/Resident Wirehead > >> Toast Design > >> > >> 800 Washington Avenue North > >> Minneapolis MN 55401 > >> 612.330.9863 v > >> 612.321.9424 f > >> www.toastdesign.com > >> > >> > >> ------------------------------------------------------------- > >> This message is sent to you because you are subscribed to > >> the mailing list . > >> To unsubscribe, E-mail to: > >> To switch to the DIGEST mode, E-mail to > >> > >> Web Archive of this list is at: http://search.smithmicro.com/ > > > > > > ------------------------------------------------------------- > > This message is sent to you because you are subscribed to > > the mailing list . > > To unsubscribe, E-mail to: > > To switch to the DIGEST mode, E-mail to > > > > Web Archive of this list is at: http://search.smithmicro.com/ > > > > > Regards > > Stuart Tremain > idfk web developments > 114a/40 yeo street neutral bay 2089 australia > t +612 9908 2134 > f +612 9908 4837 > > > > ------------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > To switch to the DIGEST mode, E-mail to > Web Archive of this list is at: http://search.smithmicro.com/ > ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/
Kalin Mintchev
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:
Problems getting parameters passed into email. (1997)
apostrophe in search item (1997)
RequiredFields notes ... (1997)
Credit card types (1997)
checkout.tpl (1999)
[format 40s]text[/format] doesn't work (1997)
Friday night shopping site joke (1997)
Re1000001: Setting up shop (1997)
OT-Load balance (2004)
Stupid question (2003)
Bug in WebCat, (2000)
Multipart Form - Ascertain File Type (2007)
Attention SMSI - DOCS Error (2004)
Text data with spaces in them... (1997)
[WebDNA] Password Generator (2012)
Re:quit command on NT (1997)
Pull Down Search (2000)
Almost a there but..bye bye NetCloak (1997)
WebCat2b13MacPlugIn - [include] doesn't allow creator (1997)
Fun with dates (1997)