What I learned from writing my first Chrome extension · EdGuiness/date-picker Wiki. Intro I wrote a Chrome extension to add a calendar (date picker) to any web page. Initially I just wanted to add a calendar to Google forms but then thought it might be useful on other pages as well. So I made it into an extension and published it in the Chrome web store.
How the extension works There are two ways of using the extension. The second way is to click on the extension icon, then pick a date which is copied it to the clipboard: What I learned You need to pay Google before you can publish on the Chrome web store It's just $5, I think they do this to minimise spam submissions. You can also publish outside the Google ecosystem on sites like chromeextensions.org, though I assume these sites are not curated and are less patronised than the Google web store. If you used the Chrome Developer Dashboard before the first developer preview release of the Chrome Web Store you don't need to pay the fee. The "Hello, World! " It takes literally five minutes. The tutorial really helped. Chart for Learning a Programming Langauge | Zappable.
Apps Script. Theory11 - Learn Magic Tricks, Card Tricks & Cardistry - theory11.com - theory11.com. Ukulelehunt.com. Mozilla Thimble Teaches You How to Code with a Side-By-Side HTML Editor. Using Local and Push Notifications. SSH tip: Automatic Reverse Tunnels for Workflow Simplification | codysoyland.com. I came up with a trick today to simplify the workflow of certain tasks with SSH. The problem this solves is largely driven by a particular annoyance I had with remote SSH file management. Consider the following workflow for locating a remote file and copying it back to the local machine: # Find the remote file: local:~$ ssh remote remote:~$ find . -name 'file.tar.gz' /home/cody/somewhere/deep/file.tar.gz # Ah, there it is! The reason I have to run scp on my local machine is because it is behind a firewall, so the remote machine can't see it directly.
There is a way to get around this limitation with DNS/firewalls, and the answer is by using SSH reverse tunnels to bind your local SSH daemon port to a remote SSH alias. On the local computer, the SSH configuration entry for the remote host should be given a RemoteForward option, specifying that localhost:22 (the local ssh daemon) should be tunnelled to remote port 8022: Host remote HostName remote.example.com RemoteForward 8022 localhost:22.