You write a prompt, hit enter, and watch the console light up green. Code pours out. It feels like magic. Then you try to maintain the thing a week later, and you realize your shiny new AI agent just built a leaking bucket.
Today, let's get your iPad/iPhone printing from the HP LaserJet 1020. The 1020 isn't officially supported by Mac OS X but always has been able to print using the 1022 driver. In my case, I'll have it connected via an Airport Express, but this works fine also if it's connected directly to your Mac. Having it connected to the Airport Express another place in my house just makes it more fun. 
Kære alle
Kære alle
Wow, the libpd guys make it possible to put Pure Data patches in your iPhone app. I'm definitely going to make an app based on this, if nothing more then just for the heck of it. Time to brush up on my PD skills, I've been using Max/MSP for too long See the article
Hatim has written a very nice blogpost about Roo and Spring Security, including source and going into a good level of detail.
The guys at SpringSource have too many links to STS 3.5.0.M3, finding 3.5.0.RC1 was a bit hard, so if you're looking for it, go here: http://www.springsource.com/products/eclipse-downloads
I don't know if you've noticed yet, but I'm a big fan of both Roo and the guys behind Roo. Big thanks to Alan & James from the forum post, ROO-1537 and ROO-1538, as of git version a474dc7b95613fae564f0e0fa50d89a6818bd753, and tested today one day later, my scripts run flawlessly through the tests! 
Which means, we can continue with Tiles. Stay tuned!
<div id="mcePaste" Ever seen this before? <emGot fatal error 1236 from master when reading data from binary log: 'Could not find first log file name in binary log index file'</em I had that after a MySQL server in my replication loop went down. When it came up, the next server in line gave this replication state <em'Relay log read failure: Could not parse relay log event entry. The possible reasons are: the master's binary log is corrupted (you can check this by running 'mysqlbinlog' on the binary log), the slave's relay log is corrupted (you can check this by running 'mysqlbinlog' on the relay log), a network problem, or a bug in the master's or slave's MySQL code. If you want to check the master's binary log or slave's relay log, you will be able to know their names by issuing 'SHOW SLAVE STATUS' on this slave'</em, which was quite logical since the end of the binlog had been corrupted due to external circumstances. </div