[BULK] 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 = 106428
interpreted = N
texte = This is a multi-part message in MIME format.--------------070506080000050404080700Content-Type: text/plain; charset=ISO-8859-6; format=flowedContent-Transfer-Encoding: 7bit"Ask WSC to leave the old built-in commerce code insideWebDNA, just like it currently exists in v7 -- provided theynever have to modify it, support it, or even think about itany more."yes- pretty please...this would allow moving existing to 7 and beyondand then to work on a modern system to replace the carts,without being forced to choose betweenbad options of staying put and non paying optionsof updating sites that are working..jymOn 3/26/11 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>-- Jym Duane - CTO - Purpose MediaCreating Your Success StoryMarketing : Television - Internet - PrintPhone: (877) 443-1323Email: jym@purposemedia.comWeb: www.purposemedia.comOregon - www.GuideToOregon.comPO Box 1725,Jacksonville, OR 97530California - www.OrangeCounty.netPO Box 2025,Capistrano Beach, CA 92624--------------070506080000050404080700Content-Type: text/html; charset=ISO-8859-6Content-Transfer-Encoding: quoted-printable

"Ask WSC to leave the old built-=in commerce code inside=20WebDNA, just like it currently exists in v7 -- provided they=20never have to modify it, support it, or even think about it=20any more."

yes- pretty please...

this would allow moving existing to 7 and beyond
and then to work on a modern system to replace the carts,
without being forced to choose between
bad options of staying put and non paying options
of updating sites that are working..

jym

On 3/26/11 2:29 PM, Kenneth Grome wrote:

I was under the impression that several of the gur=ushanging out in this forum had already created their owne-commerce platforms without using the old WebCatalogcode.

I created a generic system about 12-15 years ago.  It ran=20on Typhoon (as well as WebCatalog).  It was designed to turn=20Typhoon into an eCommerce system.  All the commerce=20functions were contained in external templates.One thing I learned from this exercise is that my solution=20ran FASTER than WebCatalog's internal commerce code!Others have created similar systems, but I think theychose to customize their systems for the stores they were=20building for their clients, rather than building a generic=20system that everyone could start with.

If WebDNA is your love, like it is mine, then this= is theperfect opportunity to whip up something that will bemuch better than the WebCatalog features, and a heck ofa lot more user friendly too.

This is my dream -- but not to make it backwards compatible=20with the old file-based cart system.  Instead I would prefer=20to build something new from scratch ... and make it even=20better than the system I created years ago. =20My current concept is a system that would be entirely based=20on templates, includes and database files, and easily=20customized with drop-in modules.  Anyone can build the=20modules.  We can even create a shared library of modules if=20we like. =20This would be a system for the FUTURE.  It would do nothingto remain backwards compatible with any existing WebDNA=20commerce sites. =20If backwards compatibility is important to certain users,=20they should just stick with v6 or upgrade to the current v7=20which 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=20WebDNA, just like it currently exists in v7 -- provided they=20never have to modify it, support it, or even think about it=20any more.This might let old users upgrade to v7and beyond without the=20need to rebuild existing v6 sites.  And at the same time it=20would relieve WSC of the burden of maintaining this part of=20WebDNA's built-in code.Note that I have no idea whether or not this is possible. =20It's just a thought ... but if it is possible (and=20reasonable and practical for WSC) then maybe it will satisfy=20all WebDNA users.Sincerely,Kenneth Grome---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list <talk@webdna.us>.To unsubscribe, E-mail to: <talk-leave@webdna.us>archives: http://mail.webdna.us/list/talk@webdna.usBug Reporting: support@webdna.us

Jym Duane - CTO - Purpose Media

Creating Your Success Story

Marketing : Television - Internet - Print

Phone: (877) 443-1323=A0 =A0

Email: jym@purposemedia.com=A0 =A0

Web: www.purposemedia.com

Oregon - www.GuideToOregon.com

PO Box 1725,=A0= Jacksonville, OR 97530

California - www.OrangeCounty.net

PO Box 2025,=A0= Capistrano Beach, CA 92624

--------------070506080000050404080700-- Associated Messages, from the most recent to the oldest:

This is a multi-part message in MIME format.--------------070506080000050404080700Content-Type: text/plain; charset=ISO-8859-6; format=flowedContent-Transfer-Encoding: 7bit"Ask WSC to leave the old built-in commerce code insideWebDNA, just like it currently exists in v7 -- provided theynever have to modify it, support it, or even think about itany more."yes- pretty please...this would allow moving existing to 7 and beyondand then to work on a modern system to replace the carts,without being forced to choose betweenbad options of staying put and non paying optionsof updating sites that are working..jymOn 3/26/11 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>-- Jym Duane - CTO - Purpose MediaCreating Your Success StoryMarketing : Television - Internet - PrintPhone: (877) 443-1323Email: jym@purposemedia.comWeb: www.purposemedia.comOregon - www.GuideToOregon.comPO Box 1725,Jacksonville, OR 97530California - www.OrangeCounty.netPO Box 2025,Capistrano Beach, CA 92624--------------070506080000050404080700Content-Type: text/html; charset=ISO-8859-6Content-Transfer-Encoding: quoted-printable

"Ask WSC to leave the old built-=in commerce code inside=20WebDNA, just like it currently exists in v7 -- provided they=20never have to modify it, support it, or even think about it=20any more."