Re: attn: smitmicro - cart limitation
This WebDNA talk-list message is from 2002
It keeps the original formatting.
numero = 44459
interpreted = N
texte = 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 Design800 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/
Associated Messages, from the most recent to the oldest:
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 Design800 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/
Rob Marquardt
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:
PCS Frames (1997)
WC2b12: Yes, Formulas.db is for real (1997)
format crash! (1997)
Max Record length restated as maybe bug (1997)
Subdomain mapping for SSL (2002)
A quickie question (1997)
WebDNA update from Smith Micro (2002)
default value from Lookup (was Grant, please help me) (1997)
t or f (1997)
[ShowIf] and empty fields (1997)
textarea data entry and display (2000)
4.0 send email ticks. . (2000)
WC2f3 (1997)
[WebDNA] Stop & Start WebDNA Remotely (2011)
PCS Emailer's role ? (1997)
How to add product size choices to form? (1997)
Quit revisited (1997)
Multiple catalog databases and showcart (1997)
[WebDNA] Sales Tax on CUstom WebDNA Site (2008)
Multiple prices (1997)