my favorite grep to mv pipe
grep –max-count=1 -l -r –include=*.txt –exclude-dir=fragments ‘pattern’ ./*|while read line; do mv “$line” newLocation; done
Categories
Dailies
My Links
woah
http://www.behance.net/Gallery/_quotMoominvalley_quot/238408
processing.js
It’s the processing API ported to javascript and implemented in canvas. Let the fun begin.
http://processingjs.org/
discovering YQL
A co-worker started using pipes, which is awfully cool, then someone else stumbled on YQL, which I think pipes is a front end for. YQL imagines the web as a giant database, with tables defined for diffferent web services, for search results, for HTML documents… it’s crazy.
- yql article at ajaxian
- rss aggregating query (console / json)
- select * from rss where url=’http://www.ncyoung.com/?feed=rss2′ or url=’http://hackaday.com/feed/’
- xhtml query (console / xml)
- select * from html where url=”http://cisco.com” and xpath=’//meta[@name="docType"]‘ limit 3
- search results query (console / json)
- select * from local.search where query=”falafel” and location=”portland,or”
- show tables (console / xml)
my favorite tar command
This archives and compresses a bunch of files in one step. tar czvf archiveName.tgz directoryToArchive Note that the 'f' option must come last.
processing for javascript
balldroppings, a philip glass constructor.
processing js samples. A lot were done as chrome experiments.
js unit testing follow up
I admit to being one of those people who has scratched their heads and said “javascript? How do you test it?” What that meant to me, of course was “how do you automate testing?”
Certainly as my client side code has increased in complexity, I’ve moved towards more structured and repeatable ad hoc testing, driven by requirements and a test plan. In some cases the win from automated testing was great enough for me to start to custom code some automated tests.
Long and the short of it, I’m evaluating javascript test automation and it’s starting to look good.
My first stop was qunit, which I’d heard about via jQuery. I quickly ended up looking into screwUnit and jspec and yui and others.
James Carr had a useful round up of testing libraries which had me thinking either screwUnit or jspec would be good. I like the ruby style of declaring tests … code.should_be(readable). I don’t like learning new vocabularies (javascript tests should be written in javascript?) screwUnit’s readme was more approachable for me so I started leaning that way.
This review was oddly helpful in narrowing me in one screwUnit as was this presentation. This email thread set me back a bit.
Late in the game I came upon jasmine, with a lot of what I liked about screwUnit plus good examples for spies, asynchronous and ajax testing. Plus this evidence of responsive maintaniers. So that’s where I’m starting.
css-like selectors to create html
http://code.google.com/p/zen-coding/
*3 means repeat 3 times
$ means “insert iteration number here”
div#thing>ul*3>li#it-$*3>a+
table>tr*2>td*3>table+
things to come back to
A classic for this category, wikipedia’s lamest edit wars. Made me realize how much time some people really have on their hands (even when I didn’t have enough time to read the whole thing).
Woah. Just woah. A 70 minute review of the phantom menace.
I personally know of someone who lost weeks of his life to just one of the games on this list. And he normally looks down on people who waste time on video games.