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 = 106427
interpreted = N
texte = A few questions for those following the thread. So are we talking about a full product catalog with the shopping cart features? Or are we just talking about the merchant checkout features? What do you think is more important? Having a product catalog database with the ecommerce module? Or just having an ecommerce module that can handshake with a products.db and take care of the checkout? I've discovered there is no pleasing every website owner when it comes to the functionality of the products database. They all want something different. But the merchant system is pretty standardized, no? Tying the merchant system into a customer accounts system is also another hurdle that needs to be considered. Should it be part of the merchant system? Matthew Perosi On 3/26/2011 6:21 PM, Dan Strong wrote: > Ken, > > I have a question to pose to you with the whole community listening: > > 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? > > 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. > > There are other modules like this that could be useful, and this is > the heart of our idea of a WebDNA "app store". > > I would love to hear some thoughts on this. > -Dan > > 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. >> >> 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 >> --------------------------------------------------------- >> This message is sent to you because you are subscribed to >> the mailing list
. >> To unsubscribe, E-mail to: >> archives: http://mail.webdna.us/list/talk@webdna.us >> Bug Reporting: support@webdna.us > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us > > -- Matthew A Perosi Corporate Consultant Mobile Marketing Expert Senior Web Developer SEO Analyst& Educator Psi Prime, Inc. 323 Union Blvd. Totowa, NJ 07512 Service: 973.413.8211 Training: 973.413.8214 Fax: 973.413.8217 http://www.perosi.com
Associated Messages, from the most recent to the oldest:
A few questions for those following the thread. So are we talking about a full product catalog with the shopping cart features? Or are we just talking about the merchant checkout features? What do you think is more important? Having a product catalog database with the ecommerce module? Or just having an ecommerce module that can handshake with a products.db and take care of the checkout? I've discovered there is no pleasing every website owner when it comes to the functionality of the products database. They all want something different. But the merchant system is pretty standardized, no? Tying the merchant system into a customer accounts system is also another hurdle that needs to be considered. Should it be part of the merchant system? Matthew Perosi On 3/26/2011 6:21 PM, Dan Strong wrote: > Ken, > > I have a question to pose to you with the whole community listening: > > 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? > > 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. > > There are other modules like this that could be useful, and this is > the heart of our idea of a WebDNA "app store". > > I would love to hear some thoughts on this. > -Dan > > 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. >> >> 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 >> --------------------------------------------------------- >> This message is sent to you because you are subscribed to >> the mailing list. >> To unsubscribe, E-mail to: >> archives: http://mail.webdna.us/list/talk@webdna.us >> Bug Reporting: support@webdna.us > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us > > -- Matthew A Perosi Corporate Consultant Mobile Marketing Expert Senior Web Developer SEO Analyst& Educator Psi Prime, Inc. 323 Union Blvd. Totowa, NJ 07512 Service: 973.413.8211 Training: 973.413.8214 Fax: 973.413.8217 http://www.perosi.com
"Psi Prime Inc, Matthew A Perosi "
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:
Simple Store (2000)
[WebDNA] thisAutonumber? (2011)
searching illegal HTML (2002)
can webcat determine an image's pixel dimensions? (2000)
Apache suffix mapping for .tpl (2000)
TeaRoom Order fields email account remain empty even though thewy are filled. (1997)
Same DB Same Time (2004)
using showpage and showcart commands (1996)
new cart IDs being assigned somehow (1997)
Return records from another (1997)
Resume Catalog ? (1997)
Add a field to the error log? (1997)
Remove a Field from a DB (2007)
WebCat2 - [SendNews] (1997)
retain raw [cart] submitted value (2004)
Include a big block of text (1997)
Comments in db? (1997)
Semi [OT]: Clustering for Apache/MySQL on OS X (2004)
[sendmail]- bcc? (1998)
Displaying xx number of characters (1997)