@mariuswatz websaver awe.sm/5daM6 is a great way to use a processing.js sketch as a screensaver. Here’s mine: viz.runningwithdata.com/boids/

— Jason Sundram (@jsundram) January 28, 2012

Websaver runs on MacOS and allows the user to specify a web page to load when the screensaver is active. And since it uses Safari to render the HTML (I assume), you can use HTML5 and Processing.js to run computational sketches on that web page.

It’s a nice hack to enable easy development of screensavers based on open web standards, without having to worry about interaction with the OS etc. In fact, it’s nearly as good as my Google Chrome screensaver idea, minus an app store etc.

Here are three examples showing a simple map display and two demos using geo data from OpenPaths in CSV format: 20120127_unfolding_map_examples.zip

Update: The lecture notes about infoviz and self-ethnography are online on Scribd, it’s basically the same lecture as two years ago.

Below is a more or less complete list. In summary, the arguments are roughly as follows:

• “Screensavers are outdated / unnecessary.” Well, yes. But that has never meant much in terms of deciding whether a cultural phenomenom succeeds or is banished to the Wasteland of Forgotten Memes. Tamagotchis or animated GIFs, anyone? 90% of all iPhone / Android apps are unnecessary for everyday living, yet the smartphone app culture is a runaway train.
• “Developing screensavers is currently way too hard.” I share this sentiment and suspect it to the main culprit along with its corollary: “Installing screensavers is too hard / scary / likely to mess with the rest of my computer.”
• “It’s impossible to improve on flying toasters.” This terrifying thought is exactly why I would suggest screensavers need revisiting.

In conclusion: Between being tricky to develop and just as tricky to install and successfully use, screensavers stand no chance of recovering ground as a cultural phenomenom. Despite their close link to the app culture that is currently dominating our lives, screensavers (aka “ambient software”) will get no love.

This might not seem like such a terrible loss, but I still posit that ambient data gadgets with possible integration to web / mobile apps would’ve been a great usage scenario. There are some ways this could still happen:

• Microsoft and Apple realize the lost potential and relaunch their screensaver frameworks complete with app stores for screensavers. (Unlikely.)
• Google develops a screensaver mode for Chrome as part of their Chrome apps initiative and allows sales of screensavers through the Chrome app store. (Entirely possible if a little optimistic. My favorite option by far, though. Google, are you listening?)
• In both these scenarios, new screensavers would be based on HTML5 with WebGL, allowing them to be cross-platform and based on open standards. Because you all understand that proprietary is stupid, right?

A sad footnote: I had to uninstall the brilliant Briblo screensaver after realizing it was interfering with the taskbar on Windows 7. So I’m back to the ever popular blank screen, like so much of the world population.

Update: After this was posted it got blogged on Creative Applications and I’ve received quite a few responses via Twitter. See the separate post “Screensaver Culture – Twitter responds” for a summary, as well as some further thoughts on the demise of the screensaver.

• Your task is to come up with a concept for a screensaver that is both suitable to the screensaver format and updated to a 2012 understanding of interaction design. We are looking for ideas that go beyond the traditional screensaver format, or which reinvent that format by applying design thinking to a field full of visual cliche.
• Two general directions are suggested (but not required):
  1. Ambient data gadgets – screensavers as data aggregators and visualizers.
  2. Computational graphics – parametric visuals.
• If your idea is too ambitious to realize in a 3-day time frame we want to see convincing screen mockups of how the screensaver would work. But we would rather see a real demo that’s rough around the edges than a slick Photoshop sketch. You must submit at least one Processing sketch illustrating part of your screensaver’s functionality.

• Yuji Adachi: Briblo – Lego style screensaver
• Twistori, visualization of tweets with certain keywords
• Smashing Magazine: Screensavers – Best Of (2007)
• Kuler Screensaver showing latest Adobe Kuler color palettes
• SETI @ Home distributed computing screensaver
• Scott Draves: Electric Sheep, massively distributed fractal image generator
• Twingly, blogosphere visualization
• Terence M. Welsh (Really Slick) – OpenGL 3D screensavers
• Stefan Trifan: Weather, City
• GeocodEarth, Flickr, GeoRSS mashup

I stupidly forgot to bring my USB stick, so please download from here. Also, download Processing 1.5.1 if you don’t have it on your computer.

Arc mesh tool created with Modelbuilder and ControlP5

I did a short lecture + workshop about digital fabrication and parametric modeling with Processing yesterday at NYU’s ITP program. Thanks to Dan Shiffman for the invite, it ended up being a lot of fun because of the great turnout of enthusiastic ITP’ers. It certainly made me even more regretful that I was unable to teach a fabbing course at ITP this semester, but with luck there will be other oppportunities.

As promised I have uploaded the pre-written examples I demo’ed as well as the code I (frenziedly) wrote live during our 1.5 hour coding session. The focus was to demonstrate the logic of the Modelbuilder library, a set of utilities and aimed at abstracting and simplifying some common tasks in computational creation of 3D meshes.

The library is really not all that sophisticated, but it shifts the focus away from OpenGL drawing logic towards a more object-oriented way of imaging 3D forms based on UVertexList objects. In a typical situation it should simplify a lot of tasks, as well as save dozens of for() loops and repetitive code. It also allows some pragmatic coding (aka “lazy”) coding practices enabling easy reuse of geometries due to the assumption that operations like “new UVertexList(vl)” should always copy input data by content rather than by reference.

I’m pleased to say that Modelbuilder performed well in the demo session, there’s nothing like live coding to reveal weaknesses or inconsistencies in code. But the Modelbuilder logic proved consistent under stress testing and we were able to do some pretty decent mesh generation in a limited amount of time.

A ZIP with all the files shown (including the Modelbuilder and ContolP5 libraries) can be downloaded from http://db.tt/5Ehmn6uz. It includes the following code examples:

• simple_geo_arc_4 A tool for creating a composition of 3D arcs (w/ valid face normal orientation and passing the “waterproof” criteria for 3D printing), generating output to STL format. This was written live in around 30 minutes.
• mb_04_gui_parametric A parametric 3D form generator created for my Makerbot residency – results look valid on screen but for some reason export to STL results in flawed models. I’ll look into debugging this example.
• mb_04_gui_heightfield An example showing how to create a heightfield mesh from an image, allowing interactive control of mesh resolution and Z scaling. Potentially useful for geographical elevation maps and Kinect depth maps.
• A set of examples demonstrating the core Modelbuilder functions

Sketches made with Wblut’s Hemesh library

This blog has been quiet for a while, due not to laziness but rather lack of time. Some random notes to let you know what I’ve been up to:

• I just set up a Tumblr blog to post more theory-related thoughts that don’t fit this blog so well. First post: Things I’ve learned from disagreeing about (Media) Art on the Internet
• I’m working on some new objects for 3D printing, experimenting with interfacing Modelbuilder to Wblut’s Hemesh library. I have some promising results so far, but actual print tests remain. I will try to post more about this later, specifically providing a class that acts as a bridge between my UGeometry objects and the HE_Mesh data structure. Interchange of mesh data is the biggest issue for 3D libraries right now, hopefully the upcoming PShape3D structure will facilitate this.
• The Modelbuilder lib is due for an upgrade, I’ll do this when Processing 2.0 is out for good.
• I had a great time doing a solo show in San Francisco this summer, as part of the SF Film Society’s Kinotek series, see documentation on Flickr: SFFS Kinotek – Automatic Writing. Thanks to Sean Uyehara and the others at SFFS, as well as the excellent people I met during my stay.
• The SF show featured the biggest collection of Makerbot objects to date – about 25 pieces: Form studies (Makerbot). As always my thanks go to the Makerbot clan for excellent support, at the craziest I had 6 Makerbots printing at once.

Form studies (Makerbot) at the Automatic Writing show

Thus Christina had to get out of bed and provide me with passwords, with a view to do an emergency blog database backup. But then I checked the pages again and the Viagra spam was magically gone. A test on two other computers revealed the site to alive and well. Which leaves only one conclusion: My work laptop is infected, interestingly enough with a virus that is inserting its own toxic HTML into valid HTTP requests. I can only imagine what it might do to my entered passwords.

Ugh. I’m currently scanning disks with AVG Rescue on a USB stick and anticipating changing a lot of passwords, fair punishment for being too lax about security and maybe downloading the occasional file of ill repute.

Remember, kids: Scan and backup, duck and cover!

Update: Turns out the problem is on the Flux server after all. There is a nasty WordPress infection known as WordPress Pharma that will inject Viagra spam into web pages, but oddly enough only as they are presented to search engines. So the database etc. is untouched but I need to hunt down those rogue PHP files and exterminate them.

Ryoji Ikeda’s “The Transfinite” installation at the Park Avenue Armory.

If you’re fortunate enough to be in New York anytime between now and June 11, 2011 you should make every effort to see Ryoji Ikeda’s “The Transfinite” installation at the Park Avenue Armory. It’s a massive audiovisual experience in two parts which should convince the most sceptical of audiences that maybe this whole “new media” thing has something going for it after all.