I have to admit that while I'd read a few things about Cairngorm, it still seemed murky to me. The fog cleared when I read chapter 20 in Developing Rich Clients with Macromedia Flex. It's interesting that although the book predates Cairngorm, its description of techniques that Cairngorm later embodied made things click for me.
This book has cleared some other Flex fogbanks for me, too. I think it's truly a gem that's slipping into the sands of time.
Caveat emptor: the book is based on Flex 1.0/1.5, with ActionScript 2.0 -- you'll need do some translation as you read it, and some things simply no longer apply. But I think it's still well worth the money.
Wednesday, October 8, 2008
Getting Started with Adobe Flex
I hope to make it more presentable when time permits but FWIW, here are some rough notes on some resources to help people get started with Adobe Flex.
Saturday, October 4, 2008
Chick Magnet
While waiting in line at Subway yesterday, an attractive woman noticed the book I was reading and struck up a conversation with me. The book? "Official Rules of the NFL"
I've never gotten that sort of attention with "Java Persistence with Hibernate" or "JUnit in Action", to name two of many.
p.s.
Among many other things I learned that the ball must a Wilson. Period.
I've never gotten that sort of attention with "Java Persistence with Hibernate" or "JUnit in Action", to name two of many.
p.s.
Among many other things I learned that the ball must a Wilson. Period.
Sunday, March 30, 2008
Fun with Cygwin's /dev/clipboard
I'd say that /dev/clipboard is surely among one of the least known handy things on Cygwin. The idea is simple -- the Windows clipboard is accessible as a file, /dev/clipboard.
I often use /dev/clipboard to bridge the gap between GUI tools and line-oriented tools. For example, if you're wondering how many words are in a section of text in a document you're looking at, you can put that text on the clipboard and then do this:
You can save some typing by symlinking /cb to /dev/clipboard:
I got to wondering if a single script, call it "cb", could act like fromcb when on the left end of a pipeline, and act like tocb on the right end of a pipeline. Like this:
Maybe there is nothing new under the sun -- I just now noticed that xsel (c. 2001) apparently uses isatty to determine whether it should fetch or set clipboard contents. :)
I often use /dev/clipboard to bridge the gap between GUI tools and line-oriented tools. For example, if you're wondering how many words are in a section of text in a document you're looking at, you can put that text on the clipboard and then do this:
wc -w /dev/clipboardIf you want to insert the output of ls into a document you're editing, send it to the clipboard,
ls *.java > /dev/clipboardand then paste it in. (Yes, this task is simpler with Emacs, vi, et al.!)
You can save some typing by symlinking /cb to /dev/clipboard:
ln -s /dev/clipboard /cbSome non-Cygwin programs don't interact well with /dev/clipboard. For example, directing the output of javap to the clipboard leaves it unchanged:
% date > /cbTo compensate, I wrote a trivial script, tocb:
% javap Hello >/cb
% cat /cb
Sun Mar 30 15:23:24 USMST 2008
% cat tocbInstead of redirecting output to /cb, I pipe into tocb:
cat >/dev/clipboard
% javap Hello | tocbI also wrote a trivial counterpart for tocb named fromcb:
% cat /cb
Compiled from "Hello.java"
public class Hello extends java.lang.Object{
public Hello();
}
% cat fromcbIncidentally, Mac OS X has similar commands named pbcopy and pbpaste.
cat /dev/clipboard
I got to wondering if a single script, call it "cb", could act like fromcb when on the left end of a pipeline, and act like tocb on the right end of a pipeline. Like this:
% cal | cb # puts output of cal onto the clipboardCygwin supports the isatty(file_descriptor) library function, which queries whether the specified file descriptor is connected to a terminal. (Some programs, ls to name one, change their behavior depending on whether they're writing to a terminal.) Linux has isatty(1), which simply wraps isatty(3) in a program. My Cygwin installation doesn't have isatty(1), and I was too lazy to see if it's in some package I haven't installed, but it's trivial to write:
% cb | wc # puts the clipboard contents onto standard output
% cat isatty.cWith that in hand it's easy to write a cb that that reads or writes the clipboard depending on which end of a pipeline it's on. Here it is:
main(int argc, char **argv)
{
exit(!isatty(atoi(argv[1])));
}
% cat cbUsage:
if isatty 0
then
cat /dev/clipboard
else
cat >/dev/clipboard
fi
% cal | cbYou can put cb on both ends of a pipeline to transform the clipboard contents:
% cb | cat -n
1 March 2008
2 Su Mo Tu We Th Fr Sa
3 1
4 2 3 4 5 6 7 8
5 9 10 11 12 13 14 15
6 16 17 18 19 20 21 22
7 23 24 25 26 27 28 29
8 30 31
% date | cbp.s.
% cb | tr a-z A-Z | cb
% cb
SUN MAR 30 16:03:17 USMST 2008
Maybe there is nothing new under the sun -- I just now noticed that xsel (c. 2001) apparently uses isatty to determine whether it should fetch or set clipboard contents. :)
Subscribe to:
Posts (Atom)