Client-side javascript scripting solutions for the many problems developers face on a day-to-day basis.
By using existing code you reduce the likelihood of errors within your own script, solve problems you aren't aware of (yet), and save the most valuable resource you have: time.
Currently this section of Reliable Answers.com is rather limited, however, you may download Shawn's JavaScript Library for a few resource scripts included in every page on this site, and some are used elsewhere. The scripts in the library.js file include cookie management for different form field types, frame break-out, "privacy proxy" super-break-out, "selectively frame tolerant" pseudo-break-out, an email obfuscator and a couple other nifty tools.
JavaScript is an amazing tool. It is both a scripting language and a development tool. Major vendors have declared their support of javascript in many ways. Netscape created it as a means to manipulate objects on a webpage way back in 1995 for Netscape Navigator 2.0. Microsoft has included it in every browser since Internet Explorer 3.0.
But that's not all. Did you know that Adobe DreamWeaver used JavaScript for the vast majority of their internal application function? Or that javascript has been implemented in many operating systems and applications in all walks of life, and now includes other, now-necessity, tools like Regular Expressions?
A site on the internet today that does not at least attempt to comply with the scripting expectations of it's users will leave a lot to be desired. By sharing these scripts I hope to provide the tools necessary to enable your site to function cleanly and correctly for all of your visitors.
Unfortunately, as amazing as javascript is, it is not the be-all end-all of the internet. Every site relies on many other technologies as well, often including HTML, XML, CSS and more. Many sites now operate as services as well, providing interactivity on far more than a simple client level, which requires code to be processed on the server. This can be done in many languages, including PHP, ASP, ASP.NET, PERL and others. These languages, when operated on the server, are called "Common Gateway Interface" languages, or CGI for short.
As time permits I hope to provide samples of as many of these as possible. Keep checking back.
Regards,
Shawn K. Hall