This is a tiny content strategy framework focused on goals, messages, and branding. This is not a checklist. Use what you need and scrap the rest. Rewrite it or add to it. These topics should help you get to the bottom of things with clients and other people you work with.
Give me feedback on Twitter (@nicoleslaw) or by email (nicole@nicolefenton.com).
| global targetDomain | |
| global folderName | |
| -- options | |
| set targetDomain to "dropcam.com" | |
| set folderName to (path to desktop as text) & "Dropcam" | |
| -- main code | |
| global recordingFile | |
| global newMovieRecording |
A friend recently asked me for some help with jQuery. He wanted to know how to store data on html elements from the JSON payload he was receiving. His initial approaches were much like some of my own early approaches, storing data on elements using data attributes, and then updating those accordingly.
I've since come to learn that these are considered bad practices, and for good enough reasons. Sure, it can work, but it will be slow, and difficult to implement, and if your UI gets very complicated, you'll find yourself juggling multiple sources of truth in your application.
There are several approaches available to the modern web app developer, and I'm sorry I don't believe I'm a grand enough authority to choose a specific one for a project that isn't mine, but I am aware of enough different approaches I think I can get you oriented with what to look for in a good solution.
| set dFolder to "~/Desktop/screencapture/" | |
| do shell script ("mkdir -p " & dFolder) | |
| set i to 0 | |
| repeat 960 times | |
| do shell script ("screencapture " & dFolder & "frame-" & i & ".png") | |
| delay 30 -- Wait for 30 seconds. | |
| set i to i + 1 | |
| end repeat |