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 = 106422
interpreted = N
texte = I wonder how many people, who do not read this list, would also like to = know about such new (proposed) code to help port their legacy sites to = v.7... ------------ Govinda > Ken, >=20 > I have a question to pose to you with the whole community listening: >=20 > Would you be willing to build this system, speculatively, on your own = time, with the purpose of selling and supporting it, or, would you be = willing to come up with a cost estimate and then let the list team up = and pay you for it? >=20 > If, for instance you think it will cost you, say, $10,000 of your = time, if 100 people pitched in $100 each then we'd have a commerce app. = You can count on your first $100 from me personally and I'm sure WSC can = be convinced to pitch in as well. >=20 > There are other modules like this that could be useful, and this is = the heart of our idea of a WebDNA "app store". >=20 > I would love to hear some thoughts on this. > -Dan >=20 > On 3/26/2011 2:29 PM, Kenneth Grome wrote: >>> 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. >>=20 >> One thing I learned from this exercise is that my solution >> ran FASTER than WebCatalog's internal commerce code! >>=20 >> 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. >>=20 >>=20 >>> 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. >>=20 >> 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. >>=20 >> This would be a system for the FUTURE. It would do nothing >> to remain backwards compatible with any existing WebDNA >> commerce sites. >>=20 >> 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. >>=20 >> Or perhaps there is one more possibly: >>=20 >> 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. >>=20 >> 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. >>=20 >> 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. >>=20 >> Sincerely, >> Kenneth Grome
Associated Messages, from the most recent to the oldest:
I wonder how many people, who do not read this list, would also like to = know about such new (proposed) code to help port their legacy sites to = v.7... ------------ Govinda > Ken, >=20 > I have a question to pose to you with the whole community listening: >=20 > Would you be willing to build this system, speculatively, on your own = time, with the purpose of selling and supporting it, or, would you be = willing to come up with a cost estimate and then let the list team up = and pay you for it? >=20 > If, for instance you think it will cost you, say, $10,000 of your = time, if 100 people pitched in $100 each then we'd have a commerce app. = You can count on your first $100 from me personally and I'm sure WSC can = be convinced to pitch in as well. >=20 > There are other modules like this that could be useful, and this is = the heart of our idea of a WebDNA "app store". >=20 > I would love to hear some thoughts on this. > -Dan >=20 > On 3/26/2011 2:29 PM, Kenneth Grome wrote: >>> 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. >>=20 >> One thing I learned from this exercise is that my solution >> ran FASTER than WebCatalog's internal commerce code! >>=20 >> 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. >>=20 >>=20 >>> 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. >>=20 >> 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. >>=20 >> This would be a system for the FUTURE. It would do nothing >> to remain backwards compatible with any existing WebDNA >> commerce sites. >>=20 >> 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. >>=20 >> Or perhaps there is one more possibly: >>=20 >> 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. >>=20 >> 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. >>=20 >> 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. >>=20 >> Sincerely, >> Kenneth Grome
Govinda
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:
locking variables? (2000)
using showpage and showcart commands (1996)
Windows 2.1b4 WebCatalog available (1997)
Bug Report, maybe (1997)
authenticate (2002)
email [title] (1997)
Problem (1997)
This list needs a digest: rant, rave... (1997)
Pithy questions on webcommerce & siteedit (1997)
[WriteFile] problems (1997)
[WebDNA] PCI Vulnerability testing (2009)
5.0 Preview Promotion Extension (2003)
[WebDNA] WebDNA 8.6 Ubuntu 16.04 (2018)
Serious bug writing to a database ... (2002)
Linux Beta4 problems with multirecord returns (2000)
Re[2]: New syntax feedback for 4.0 (2000)
Where is f2? (1997)
Running subtotal? (1998)
subtotal (2000)
Just Testing (1997)