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 = 106465
interpreted = N
texte = This is a multi-part message in MIME format.--------------050906060809080602090604Content-Type: text/plain; charset=ISO-8859-1; format=flowedContent-Transfer-Encoding: 7bitScott,This is excellent. I hope that people take you up on your offer to sell/license this new store app. Chris and/or I will contact you off-list in the very near future to discuss helping you to sell this offering in the yet-to-be-built WebDNA app store. To recap, the idea is to showcase each app/module, allow others to rate it, etc. There will be no charge for this, nor will we process payments for it, it is simply a directory of apps/modules and interested parties will contact you directly.We hope to see more of this from everybody.-DanOn 3/30/2011 4:36 AM, Scott Walters wrote:> Greetings Everyone!>> I haven't read through this entire thread yet but I believe I got the > gist of it. It seemed a good opportunity to chime in.>> My most recent project entailed taking a very old WEBDNA/WebMerchant > site and upgrading it to the latest standards. Every commerce tag was > replaced by a custom shopping cart, the site can now completely > operate using just the developer edition of WEBDNA. Also, the old > site utilized the customer email address to log in and to connect them > to the services they purchased. When users updated their email > addresses they would lose access to the site and had no way to > retrieve their log in info without contacting the company by phone.>> After logging in with a new email address, users often had corrupted > or missing information in their order histories. So, in addition to > replacing the entire shopping cart system, the user account system had > to be replaced too. Not to mention a massive data mining project to > master the exisiting data and to make it compatible with the new > systems. Users can now change their email address, login ID, and > password as often as they like with no issues.>> To accomplish this, I created a script making the process of migrating > out of WebMerchant and into custom databases turn key. I listed all > [orderfiles] and for each, appended a new database. Then, queried all > [orderfiles] for [listitems] and appended each to a new database. Then > upgraded the rest of the site to operate under these new conditions. > This process can now be easily adapted to any site that is looking to > migrate away from their Commerce Edition dependency. Personally, > I prefer CE only when large back end applications are needed. It's > great to be able to use commands in URLS and Posts when developing > Intranet applications. (still wishing corporate would re-enable this > feature in PE. Instead, I think they are removing this feature from > 7.0 all together???)>> The best part of the project is that we accomplished everything with > "Zero" interruptions to the clients. The site sells Online Continuing > Education Courses for CE credits in the field of Psychology and has > lots of regular users. Plus, the site features plenty of AJAX & J > Query integration. We used it throughout the site but primarily in the > areas of form validation. Forms never have to be reloaded to find > input errors, all fields are checked in real time and users are > prompted before proceeding. So now, every form guarantees perfect data > input. For example, when users create a new account or modify an > existing one, the User-ID and email address is verified to make sure > they are not already in use, and that the password meets minimum > requirements. Another example is the validation of credit card > information before it gets sent to the payment gateway. This upgrade > not only replaced the [validcard] tag, it is more accurate and > performs instantly as the user is typing the number. We also replaced > the [shownext] tag, our method displays the next set of results or can > resort them instantly and without reloading>> The payment gateway was customized to run internally through an API. > Also, we gave the client the ability to modify "anything" on the site > without ever having to use HTML or an FTP. CSS was used exclusively > for "all" cosmetics so that changes can be made globally to maintain > consistency with much more efficiency. Finally, we ensured that all > functions and features were cross browser compatible.>> If anyone is interested in this kind of work, I am available and > flexible with pricing depending on the circumstances. I can also > assist in any hosting, email, DNS, data mining, or registration needs. > You may view the site I discussed above at www.programservices.org > . The owners name is Karen Smith. Feel > free to contact her if you would like to verify the professionalism of > the work or her experience of working with me. You can use the number > listed on the site or the contact us page.>> Respectfully,>> Scott Walters> WebDNA Lifer>> Contact Info:> scott@ideassoftware.com > phone: 419-913-4594>> P.S. to Ken,> I have an entire ready to go system that I sell and support. It's > continually improved, highly customizable, and I am flexible and > competitive with pricing....>> 2011/3/26 Dan Strong >>> 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 >>> --------------------------------------------------------- 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 --------------050906060809080602090604Content-Type: text/html; charset=ISO-8859-1Content-Transfer-Encoding: 7bit Scott,

This is excellent. I hope that people take you up on your offer to sell/license this new store app. Chris and/or I will contact you off-list in the very near future to discuss helping you to sell this offering in the yet-to-be-built WebDNA app store. To recap, the idea is to showcase each app/module, allow others to rate it, etc. There will be no charge for this, nor will we process payments for it, it is simply a directory of apps/modules and interested parties will contact you directly.

We hope to see more of this from everybody.
-Dan

On 3/30/2011 4:36 AM, Scott Walters wrote:

Greetings Everyone!

I haven't read through this entire thread yet but I believe I got the gist of it. It seemed a good opportunity to chime in.

My most recent project entailed taking a very old WEBDNA/WebMerchant site and upgrading it to the latest standards. Every commerce tag was replaced by a custom shopping cart, the site can now completely operate using just the developer edition of WEBDNA. Also, the old site utilized the customer email address to log in and to connect them to the services they purchased. When users updated their email addresses they would lose access to the site and had no way to retrieve their log in info without contacting the company by phone.

After logging in with a new email address, users often had corrupted or missing information in their order histories. So, in addition to replacing the entire shopping cart system, the user account system had to be replaced too. Not to mention a massive data mining project to master the exisiting data and to make it compatible with the new systems. Users can now change their email address, login ID, and password as often as they like with no issues.

To accomplish this, I created a script making the process of migrating out of WebMerchant and into custom databases turn key. I listed all [orderfiles] and for each, appended a new database. Then, queried all [orderfiles] for [listitems] and appended each to a new database. Then upgraded the rest of the site to operate under these new conditions. This process can now be easily adapted to any site that is looking to migrate away from their Commerce Edition dependency. Personally, I prefer CE only when large back end applications are needed. It's great to be able to use commands in URLS and Posts when developing Intranet applications. (still wishing corporate would re-enable this feature in PE. Instead, I think they are removing this feature from 7.0 all together???)

The best part of the project is that we accomplished everything with "Zero" interruptions to the clients. The site sells Online Continuing Education Courses for CE credits in the field of Psychology and has lots of regular users. Plus, the site features plenty of AJAX & J Query integration. We used it throughout the site but primarily in the areas of form validation. Forms never have to be reloaded to find input errors, all fields are checked in real time and users are prompted before proceeding. So now, every form guarantees perfect data input. For example, when users create a new account or modify an existing one, the User-ID and email address is verified to make sure they are not already in use, and that the password meets minimum requirements. Another example is the validation of credit card information before it gets sent to the payment gateway. This upgrade not only replaced the [validcard] tag, it is more accurate and performs instantly as the user is typing the number. We also replaced the [shownext] tag, our method displays the next set of results or can resort them instantly and without reloading

The payment gateway was customized to run internally through an API. Also, we gave the client the ability to modify "anything" on the site without ever having to use HTML or an FTP. CSS was used exclusively for "all" cosmetics so that changes can be made globally to maintain consistency with much more efficiency. Finally, we ensured that all functions and features were cross browser compatible.

If anyone is interested in this kind of work, I am available and flexible with pricing depending on the circumstances. I can also assist in any hosting, email, DNS, data mining, or registration needs. You may view the site I discussed above at www.programservices.org. The owners name is Karen Smith. Feel free to contact her if you would like to verify the professionalism of the work or her experience of working with me. You can use the number listed on the site or the contact us page.

Respectfully,

Scott Walters

WebDNA Lifer

Contact Info:

scott@ideassoftware.com

phone: 419-913-4594

P.S. to Ken,

I have an entire ready to go system that I sell and support. It's continually improved, highly customizable, and I am flexible and competitive with pricing....

2011/3/26 Dan Strong <webdna@danstrong.com>

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<talk@webdna.us>.
To unsubscribe, E-mail to:<talk-leave@webdna.us>
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 <talk@webdna.us>.
To unsubscribe, E-mail to: <talk-leave@webdna.us>
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 --------------050906060809080602090604-- Associated Messages, from the most recent to the oldest:

Re: [WebDNA] [BULK] which of these tags exist in 7.0 (Scott Walters 2011)
Re: [WebDNA] [BULK] which of these tags exist in 7.0 (Scott Walters 2011)
Re: [WebDNA] [BULK] which of these tags exist in 7.0 (Govinda 2011)
Re: [WebDNA] [BULK] which of these tags exist in 7.0 (Dan Strong 2011)
Re: [WebDNA] [BULK] which of these tags exist in 7.0 (aoconnor@email.unc.edu 2011)
Re: [WebDNA] [BULK] which of these tags exist in 7.0 (Govinda 2011)
Re: [WebDNA] [BULK] which of these tags exist in 7.0 (Scott Walters 2011)
Re: [WebDNA] [BULK] which of these tags exist in 7.0 (Scott Walters 2011)
Re: [WebDNA] [BULK] which of these tags exist in 7.0 (sgbc cebu 2011)

This is a multi-part message in MIME format.--------------050906060809080602090604Content-Type: text/plain; charset=ISO-8859-1; format=flowedContent-Transfer-Encoding: 7bitScott,This is excellent. I hope that people take you up on your offer to sell/license this new store app. Chris and/or I will contact you off-list in the very near future to discuss helping you to sell this offering in the yet-to-be-built WebDNA app store. To recap, the idea is to showcase each app/module, allow others to rate it, etc. There will be no charge for this, nor will we process payments for it, it is simply a directory of apps/modules and interested parties will contact you directly.We hope to see more of this from everybody.-DanOn 3/30/2011 4:36 AM, Scott Walters wrote:> Greetings Everyone!>> I haven't read through this entire thread yet but I believe I got the > gist of it. It seemed a good opportunity to chime in.>> My most recent project entailed taking a very old WEBDNA/WebMerchant > site and upgrading it to the latest standards. Every commerce tag was > replaced by a custom shopping cart, the site can now completely > operate using just the developer edition of WEBDNA. Also, the old > site utilized the customer email address to log in and to connect them > to the services they purchased. When users updated their email > addresses they would lose access to the site and had no way to > retrieve their log in info without contacting the company by phone.>> After logging in with a new email address, users often had corrupted > or missing information in their order histories. So, in addition to > replacing the entire shopping cart system, the user account system had > to be replaced too. Not to mention a massive data mining project to > master the exisiting data and to make it compatible with the new > systems. Users can now change their email address, login ID, and > password as often as they like with no issues.>> To accomplish this, I created a script making the process of migrating > out of WebMerchant and into custom databases turn key. I listed all > [orderfiles] and for each, appended a new database. Then, queried all > [orderfiles] for [listitems] and appended each to a new database. Then > upgraded the rest of the site to operate under these new conditions. > This process can now be easily adapted to any site that is looking to > migrate away from their Commerce Edition dependency. Personally, > I prefer CE only when large back end applications are needed. It's > great to be able to use commands in URLS and Posts when developing > Intranet applications. (still wishing corporate would re-enable this > feature in PE. Instead, I think they are removing this feature from > 7.0 all together???)>> The best part of the project is that we accomplished everything with > "Zero" interruptions to the clients. The site sells Online Continuing > Education Courses for CE credits in the field of Psychology and has > lots of regular users. Plus, the site features plenty of AJAX & J > Query integration. We used it throughout the site but primarily in the > areas of form validation. Forms never have to be reloaded to find > input errors, all fields are checked in real time and users are > prompted before proceeding. So now, every form guarantees perfect data > input. For example, when users create a new account or modify an > existing one, the User-ID and email address is verified to make sure > they are not already in use, and that the password meets minimum > requirements. Another example is the validation of credit card > information before it gets sent to the payment gateway. This upgrade > not only replaced the [validcard] tag, it is more accurate and > performs instantly as the user is typing the number. We also replaced > the [shownext] tag, our method displays the next set of results or can > resort them instantly and without reloading>> The payment gateway was customized to run internally through an API. > Also, we gave the client the ability to modify "anything" on the site > without ever having to use HTML or an FTP. CSS was used exclusively > for "all" cosmetics so that changes can be made globally to maintain > consistency with much more efficiency. Finally, we ensured that all > functions and features were cross browser compatible.>> If anyone is interested in this kind of work, I am available and > flexible with pricing depending on the circumstances. I can also > assist in any hosting, email, DNS, data mining, or registration needs. > You may view the site I discussed above at www.programservices.org > . The owners name is Karen Smith. Feel > free to contact her if you would like to verify the professionalism of > the work or her experience of working with me. You can use the number > listed on the site or the contact us page.>> Respectfully,>> Scott Walters> WebDNA Lifer>> Contact Info:> scott@ideassoftware.com > phone: 419-913-4594>> P.S. to Ken,> I have an entire ready to go system that I sell and support. It's > continually improved, highly customizable, and I am flexible and > competitive with pricing....>> 2011/3/26 Dan Strong >>> 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: