Re: [WebDNA] [BULK] which of these tags exist in 7.0
This WebDNA talk-list message is from 2011
It keeps the original formatting.
numero = 106418
interpreted = N
texte = > I was under the impression that several of the gurus > hanging out in this forum had already created their own > e-commerce platforms without using the old WebCatalog > code. I created a generic system about 12-15 years ago. It ran on Typhoon (as well as WebCatalog). It was designed to turn Typhoon into an eCommerce system. All the commerce functions were contained in external templates. One thing I learned from this exercise is that my solution ran FASTER than WebCatalog's internal commerce code! Others have created similar systems, but I think they chose to customize their systems for the stores they were building for their clients, rather than building a generic system that everyone could start with. > If WebDNA is your love, like it is mine, then this is the > perfect opportunity to whip up something that will be > much better than the WebCatalog features, and a heck of > a lot more user friendly too. This is my dream -- but not to make it backwards compatible with the old file-based cart system. Instead I would prefer to build something new from scratch ... and make it even better than the system I created years ago. My current concept is a system that would be entirely based on templates, includes and database files, and easily customized with drop-in modules. Anyone can build the modules. We can even create a shared library of modules if we like. This would be a system for the FUTURE. It would do nothing to remain backwards compatible with any existing WebDNA commerce sites. If backwards compatibility is important to certain users, they should just stick with v6 or upgrade to the current v7 which still contains the old built-in commerce code. Or perhaps there is one more possibly: Ask WSC to leave the old built-in commerce code inside WebDNA, just like it currently exists in v7 -- provided they never have to modify it, support it, or even think about it any more. This might let old users upgrade to v7and beyond without the need to rebuild existing v6 sites. And at the same time it would relieve WSC of the burden of maintaining this part of WebDNA's built-in code. Note that I have no idea whether or not this is possible. It's just a thought ... but if it is possible (and reasonable and practical for WSC) then maybe it will satisfy all WebDNA users. Sincerely, Kenneth Grome
Associated Messages, from the most recent to the oldest:
> I was under the impression that several of the gurus > hanging out in this forum had already created their own > e-commerce platforms without using the old WebCatalog > code. I created a generic system about 12-15 years ago. It ran on Typhoon (as well as WebCatalog). It was designed to turn Typhoon into an eCommerce system. All the commerce functions were contained in external templates. One thing I learned from this exercise is that my solution ran FASTER than WebCatalog's internal commerce code! Others have created similar systems, but I think they chose to customize their systems for the stores they were building for their clients, rather than building a generic system that everyone could start with. > If WebDNA is your love, like it is mine, then this is the > perfect opportunity to whip up something that will be > much better than the WebCatalog features, and a heck of > a lot more user friendly too. This is my dream -- but not to make it backwards compatible with the old file-based cart system. Instead I would prefer to build something new from scratch ... and make it even better than the system I created years ago. My current concept is a system that would be entirely based on templates, includes and database files, and easily customized with drop-in modules. Anyone can build the modules. We can even create a shared library of modules if we like. This would be a system for the FUTURE. It would do nothing to remain backwards compatible with any existing WebDNA commerce sites. If backwards compatibility is important to certain users, they should just stick with v6 or upgrade to the current v7 which still contains the old built-in commerce code. Or perhaps there is one more possibly: Ask WSC to leave the old built-in commerce code inside WebDNA, just like it currently exists in v7 -- provided they never have to modify it, support it, or even think about it any more. This might let old users upgrade to v7and beyond without the need to rebuild existing v6 sites. And at the same time it would relieve WSC of the burden of maintaining this part of WebDNA's built-in code. Note that I have no idea whether or not this is possible. It's just a thought ... but if it is possible (and reasonable and practical for WSC) then maybe it will satisfy all WebDNA users. Sincerely, Kenneth Grome
Kenneth Grome
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:
WebCat2 - Getting to the browser's username/password data (1997)
SendMail - sending message to more than one person from form (2006)
Default contains WEBDNA (1998)
GoLive CyberStudio 1.0.1 (1997)
Followup question re: checksum for credit cards? (1997)
Finding unused SKU's in a database (2002)
PSC recommends what date format yr 2000??? (1997)
search comparison (2003)
CyberCash, Authorize.net, or ??? (2000)
WC1.6 to WC2 date formatting -FIXED! (1997)
WebCatalog/WebMerchant 2.1 (1998)
URGENT! ACGI Stopped!!!! (1997)
Sort Order on a page search (1997)
Associative lookup style? + bit more (1997)
re:check boxes (1997)
shoppingcart reload qty (1997)
[searchString] (1997)
Major Security Hole (1998)
what servers are supported for Typhoon? (1997)
missing records (1998)