Explore >> Select a destination
|
You are here 
|
vasilis.nl | ||
| | | | |
www.gamesbytim.com
|
|
| | | | | wheeldemo.gamesbytim.com Source Code Here you'll find a tech demo of the wheel I intend to use for Wheel of Fortune for Web, the upcoming replacement for Wheel... | |
| | | | |
ericlathrop.com
|
|
| | | | | Sometimes it's fun to reinvent the wheel. Sometimes I sketch out an little idea for some code in a temporary file. I don't want to make a whole project with a git repo and package.json and NPM dependencies and all that baggage. I wanted to test out the code I wrote to make sure it worked correctly. I made a quick little test framework that I can paste into a file and write some quick assertions. See the code below: | |
| | | | |
arches.io
|
|
| | | | | From https://stripe.com/blog/stripe-checkout: It's unfortunate that everyone has to reinvent the wheel when the time comes to implement a payments UI. We decided to build something that you can just drop in as a single tag The script tag creates a "buy" button on your page. Clicking the button pops a modal payment form where the customer submits their info directly to stripe. It's a literally a 30 second integration. But here's the kicker: | |
| | | | |
eamonnsullivan.co.uk
|
|
| | | One huge and welcome change in the last decade or so for Web development is that secure connections are ubiquitous. Free certificates are available and most hosting providers make it very easy to obtain, use and renew the certificates automatically. This site, for example, runs on Amazon Web Services and enabling https took not much more effort than ticking a few checkboxes.Browsers, like Chrome, Firefox and Safari, have also played their part, by gently steering users toward secure connections, warning about sending sensitive information over plain text and switching to https automatically, when available. | ||
