Skip to content

Instantly share code, notes, and snippets.

View michael's full-sized avatar

Michael Aufreiter michael

View GitHub Profile

Entry Title

Paving the Way to an Open Health Information Knowledgebase

Summary (250 chars)

Collective use of open software facilitates the creation and exchange of data. Substance would like to introduce this concept to digital publishing in the health domain, enabling consumers to access the most current and accurate content and research.

Entry Title

Paving the Way to an Open Health-Information-Knowledge-Base

Summary (250 chars)

Collective use of open software facilitates the creation and exchange of data. Substance would like to introduce this concept to digital publishing in the health domain, enabling consumers to access the most current and accurate research and health-related content.

Entry Description (10000)

loading: function(state) {
var opts = {
lines: 17,
length: 5,
width: 4,
radius: 20,
rotate: 90,
color: '#000',
speed: 2,
trail: 100,

I wasn't 100 % sure from which angle to judge the paper: What's the intended audience?

It's dedicated to visualization developers. I'm focussing on the process of creating web-based visualizations, not on visualizations in general. That's why mapping isn't covered in detail. I'm not intending to cover many application scenarios. Just enough to get the idea.

Related: maybe this paper should cut faster to the meat and don't spend so much time explaining a methodological framework of analyzing information viz tools? How would this read as a large blog post or CT article? I'm aware that thesis have an expected format. Still, could the paper get faster to its point?

I'm afraid I can't leave that out. However, once I'm done, I'll probably publish a Substance article containing just the essentials. Deal? :)

In general, I'm missing geographical data vizualisation, mapping. I get that the paper focuses on graphing, but I'm missing at least the distinction.

@michael
michael / npm-graph
Created June 15, 2011 12:03
data.js playground
Data = require('data')
schema =
'/type/project':
'type': 'type'
'name': 'Project'
'properties':
'name':
'name': 'Name', 'unique': true, 'type': 'string', 'required': true
'tags':
@michael
michael / index.html
Created June 5, 2011 17:32 — forked from mbostock/.block
Matrix Layout (Michael Aufreiter)
<!DOCTYPE html>
<html>
<head>
<script type="text/javascript" src="http://mbostock.github.com/d3/d3.js"></script>
<script type="text/javascript" src="matrix.js"></script>
<style type="text/css">
rect.cell {
fill: red;
# configure these defaults based on Your needs :
JS_FILES_DIR = 'public/javascripts' # the javascripts base directory
EXCLUDED_JS_FILES = %W{ cache/* test/* } # excluded from compilation
OUT_FILE_JS_EXT_PREFIX = ".min" # override with `rake ... OUT_EXT=_pack`
COMPILER_JAR = "lib/jars/build/compiler.jar" # adjust the jar path !
# only required if running under JRuby - will compile multiple files
# faster as it does not need to run system `java -jar ...` commands.
COMPILER_MAIN_CLASS = "com.google.javascript.jscomp.CommandLineRunner"
/* Oscillator Signal Generator
*
* Usage: var sine = Oscillator(SINEWAVE, 440.0, 1, 2048, 44100);
* var signal = sine.generate();
*
*/
SINEWAVE = 1;
SQUAREWAVE = 2;
SAWWAVE = 3;
=== Epic Snow Leopard Upgrayyyyd Guide ===
Son, you’re now living in the land of 64-bit systems.
That means that some of your 32-bit shit is now broken.
Not all is lost.
== Fixing MySQL weirdness