Article note: Auf jeden Fall demnächst mal ausprobieren!

peek gif recorderOpen source animated screen recorder app Peek has hit version 1.0 — and added major new features to celebrate. Screen captures can be exported as animated GIFs, but Peek 1.0 adds WebM and MP4 exporting to the mix, making it a fully-fledged rival to other desktop screen recording apps like Green Recorder and Simple Screen Recorder. Other highlights in the […]

This post, Peek Screen Recorder Hits 1.0, Adds Stacks of New Features, was written by Joey Sneddon and first appeared on OMG! Ubuntu!.

Article note: Und ab in die read-it-later-App …

A couple of the projects I’m involved with at the moment are at a stage where there’s some thinking going on around how to best provide CSV files for users. This has left me thinking about what options we actually have when it comes to designing a CSV file format.

CSV is a very useful, but pretty mundane format. I suspect many of us don’t really think very much about how to organise our CSV files. It’s just a table, right? What decisions do we need to make?

But there are actually quite a few different options we have that might make a specific CSV format more or less suited for specific audiences. So I thought I’d write down some of the options that occured to me. It might be useful input into both my current projects as well as future work on standard formats.

Starting from the “outside in”, we have decisions to make about all of the following:

File naming

How are you going to name your CSV file? A good file naming convention can help ensure that a data file has an unambiguous name within a data package or after a user has downloaded it.

Including a name, timestamp or other version indicator will avoid clobbering existing files if a user is archiving or regularly collecting data.

Adopting a similar policy to generating