[WebDNA] WebDNA app store

This WebDNA talk-list message is from

2011

It keeps the original formatting. numero = 106470
interpreted = N
texte = Scott,I hope you get a flock of people wanting to use the new store app you =wrote (it sounds like it must be great).You deserve it. Webdna deserves it.Chris, Dan,=20looking forward to the tool for sharing modules! (the 'WebDNA app store' =you mentioned Dan). That sounds like a lot of fun! ..and I think it =will stimulate a creative atmosphere.-G> Govinda,>=20> Thank you for your response, you made excellent points. In fact, we =first mastered all the validation using *server side* WebDNA. Then used =progressive enhancements and unobtrusive Java scripting so that all =forms will work and validate even if Java script is not enabled.>=20> -Scott>=20>=20> On Wed, Mar 30, 2011 at 9:11 AM, Govinda = wrote:> Hi Scott,=20> this is great, and I am sure it will bring reassurance to everyone =following the thread, if not good business for you and whoever may =solicit your work.> :-)>=20> Let me just add one more point of professionalism.. that although it =is fairly common.. it is also considered not very robust to rely *only* =on javascript and/or flash to validate user data. I would recommend =both: keep the work you did to make it pretty and instant.. but *also* =validate user input *server side* (webdna) to be sure no =lame/malicious/edge case gets through. There are several ways an =intentional or unintentional user can get through the client side =validation routines.>=20> -Govinda>=20>=20> On 2011-03-30, at 7:36 AM, Scott Walters wrote:>=20>> Greetings Everyone!>>=20>> 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.>>=20>> 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.>>=20>> 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.>>=20>> 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???)>>=20>> 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>>=20>> 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.>>=20>> 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.>>=20>> Respectfully,>>=20>> Scott Walters>> WebDNA Lifer Associated Messages, from the most recent to the oldest:

Re: [WebDNA] WebDNA app store (Dan Strong 2011)
Re: [WebDNA] WebDNA app store (Scott Walters 2011)
[WebDNA] WebDNA app store (Govinda 2011)

Scott,I hope you get a flock of people wanting to use the new store app you =wrote (it sounds like it must be great).You deserve it. Webdna deserves it.Chris, Dan,=20looking forward to the tool for sharing modules! (the 'WebDNA app store' =you mentioned Dan). That sounds like a lot of fun! ..and I think it =will stimulate a creative atmosphere.-G> Govinda,>=20> Thank you for your response, you made excellent points. In fact, we =first mastered all the validation using *server side* WebDNA. Then used =progressive enhancements and unobtrusive Java scripting so that all =forms will work and validate even if Java script is not enabled.>=20> -Scott>=20>=20> On Wed, Mar 30, 2011 at 9:11 AM, Govinda = wrote:> Hi Scott,=20> this is great, and I am sure it will bring reassurance to everyone =following the thread, if not good business for you and whoever may =solicit your work.> :-)>=20> Let me just add one more point of professionalism.. that although it =is fairly common.. it is also considered not very robust to rely *only* =on javascript and/or flash to validate user data. I would recommend =both: keep the work you did to make it pretty and instant.. but *also* =validate user input *server side* (webdna) to be sure no =lame/malicious/edge case gets through. There are several ways an =intentional or unintentional user can get through the client side =validation routines.>=20> -Govinda>=20>=20> On 2011-03-30, at 7:36 AM, Scott Walters wrote:>=20>> Greetings Everyone!>>=20>> 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.>>=20>> 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.>>=20>> 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.>>=20>> 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???)>>=20>> 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>>=20>> 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.>>=20>> 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.>>=20>> Respectfully,>>=20>> Scott Walters>> WebDNA Lifer Govinda

DOWNLOAD WEBDNA NOW!

[WebDNA] WebDNA app store

2011

Top Articles:

Related Readings: