Posts tagged jquery

Friday (ish) links – January 15th 2010

A few random selections from this week’s reading.

Discussions of online privacy continue to rumble on. ReadWriteWeb had a piece about (facebook’s) Mark Zuckerberg repeating the adage that “the age of privacy is over.” Zuckerberg’s comments would appear to continue the confusion around facebook and privacy. Facebook’s popularity is at least in part due to peoples’ perceptions that there is some privacy (or at least control) inherent in it, but they keep eroding that. I deleted my facebook account a few weeks ago, partly because I was tired of negotiating its plethora of options. Twitter’s “always public” or “private” are really so much easier to handle.

Jeremy Gould pointed out O2′s SIM only iPhone plan on twitter the other day. I really wish I could find an equivalent in the US. On our last trip I was carrying two iPhones and a Palm Pre, but ended up buying a $10 virgin mobile phone from Best Buy.

Perhaps the biggest news in web development this week was the release of jQuery 1.4. The full announcement is here. I’m particularly pleased about all events now supporting live(), the improved support for contexts for actions, and the performance speedups, but many of the API changes look very nice. It’s been great to see several meaty blog posts about how some of the new features/improvements were achieved, such as this one on how the live() support works and Ben Nadel’s piece on handling problems with mouseover/mouseout.

In a similar vein I continue to enjoy Yehuda Katz’ coverage of Rails 3, including this piece on ActiveModel. It’s great to finally have a simple way to use AR’s validations, callbacks, etc. outside of ActiveRecord without resorting to nasty tricks. Gabe de Silveira also deserves some credit, not only for his very useful looking validation_scopes gem, but also for a dissection of its writing.

I missed this month’s LRUG but have been reading up on Dragonfly, a ruby library to handle image uploads and produce resized versions on the fly based on directives in a view. Putting that logic in the view makes a lot of sense and I really like the rails integration being handled by inserting rack middleware. I’ll definitely be looking for a project to try it out on.

Ajaxian continues to be the best source for impressive efforts with javascript. This week I was especially taken by efforts to implement audio sampling in firefox.

Fresh from Silicon Roundabout’s appearance in the latest issue of Wired UK, Ben Terrett of RIG has been working on some merchandise. I guess this joke’s just going to keep going.

TinyMCE is now on github. Chances are it’ll remain a pain to use (as are all editors of its ilk) but at least it can be checked out more quickly now.

And of course it’s been impossible to miss the tragedy in Haiti. The past few years have seen really impressive efforts to harness open source tools and techniques for use in disasters. Andrew Turner’s blog is a good stopping off point to find out what the mapping community has been up to.

Friday Links – January 8th 2010

It’s time for me to take another stab at occasional link blogging. While I really appreciate those who blog individual links, I seem to keep coming back to ways of packaging links. Here’s a first installment for 2010:

Last month may have been the time for advent calendars—with Drew’s 24ways yet again containing many excellent articles that have me very excited about HTML5—but the jQuery team have decided to follow a similar model in the run up to the release of version 1.4. jQuery14.com kicks off on January 14th, but already has details of their new API website based on the contents of the jQuery Reference Guide.

The folks (downstairs from our new office) at the Really Interesting Group have been keeping busy. Not only can you now see the price list for Newspaper Club (want to make a newspaper like we did at Greenbelt? Newspaper Club should be your first port of call) but you can also read about the fun they had exposing data in Christmas presents. On the newspaper front, I found the idea of the Nashville Retrospect fascinating – it’s a free monthly newspaper devoted to Nashville nostalgia and history.

There’s all sorts of excitement around key-value store Redis. Simon Willison pointed out that the addition of BLPOP and BRPOP support over Christmas means you can use it to drive a queue server without polling. Ezra Zygmuntowicz has been working on an Actor library for ruby based on it. And there’s lots more. It’s good to see that the NoSQL/LessSQL movement is developing beyond simply replacing relational databases and opening up new possibilities and techniques.

For those of us who work with drupal, Project Verity could be quite a boon. Mark Boulton and Leisa Reichelt quite rightly point out that If you’re a company that takes pride in good design and user experience, handing over a Drupal backend can be a bit embarrassing and difficult to reconcile with your company philosophy. Project Verity is their response and while I’ve not actually seen it, I suspect those two are likely to be onto something. It certainly would be nice to be able to deliver a drupal site with a friendly face for admins. I’ve not really been tracking drupal 7 development, and hopefully it’ll reduce the need for such projects. If not, I imagine a port won’t take long to surface.

Given that I’ve been playing around with a Palm Pre and WebOS lately I’m delighted to see Palm using github. There’s a fair range of sample code that comes with the SDK, but this looks likely to be more comprehensive and it’ll be fascinating to see what develops as people begin to fork the code, throw in comments, etc.

Selected (belated, extended) Saturday Links

The past two weeks haven’t really left time to compile my selected links, though there have been many. A few days at SxSWi (on which more, later) followed by travelling with the family and the inevitable work backlog moved blogging way down the priority list. So here’s a mammoth selection to get me caught up. Particularly interesting has been the discussion around the future of newspapers (represented here by Clay Shirky, Steven Johnson and Russell Davies), which seem to have finally pushed beyond “how t ind a good business model for papers” to looking at where the real value for society lies and how we can preserve and extend that in a changing landscape.

Selected Saturday links

It’s always a little embarassing to realise that two or more consecutive blog postings are nothing more than a collection of links, but that’s the way it is at the moment. Busy-ness, illness and distractedness have all kept me from the blog this week. There aren’t any clear themes in this week’s links either. Chatter around OAuth has continued apace, as have musings about fuzziness, location, time, and the web (represented well by Matt Jones’ piece), but mostly this is the (to be) usual random assortment that have spent more than a few seconds open in my newsreader or web browser

Book Review: Learning Website Development with Django

Reviewing The Definitive Guide To Django a few months ago I noted that the key place that book lacked was in examples. As befits the work of the creators of a framework, it did very well at explaining the underlying philosophies and working through all manner of implementation details, but it wasn’t the book for those who just want to dive in and build something. If that’s how you like to use technical books, then Learning Website Development With Django may be more what you’re looking for.

Following the iterative development of a delicious/digg hybrid social bookmarking application, Ayman Hourieh’s book moves quickly through a range of Django features, from setting up your initial models, and using the built in user and admin sections, to supporting AJAX with jQuery, speeding up your app with caching and (briefly) writing automated tests. The pace is fairly measured and Ayman Hourieh does a good job of explaining what’s going on at each step. An experienced web developer should find most of the information they need to get up and running with django, ready to get to work on their own apps.

Perhaps appropriately, where this book is lacking is in explaining how the different parts of the framework fit together. There’s plenty you can pick up by inference, but there are no detailed explanations of, say, the routing system that maps URLs to code. This book’s weaknesses are the former volumes strengths, and while you’ll find much repeated between them a combination of the two is likely to be a good way to get a fully rounded sense of what django is and how you can use it.

Disclaimer: I was sent a copy of this book for review by the publisher. You can find it at packt, amazon US, amazon UK and all sorts of other places.