Plasmid 0.2.0 Released - API Stable And Tested

Plasmid is an in-browser database and I've been working on it for a few months, talked to many people about it, and finally reached a point where I can release an API stable version.

There are two main components to Plasmid, developed separately. PlasmidJS is the in-browser database, based on the IndexedDB specification and supports recent versions of Chrome, Firefox, and Internet Explorer. The second component is Plasmid Sync: a backend server that allows users to synchronize their in-browser databases between machines.

I'm really excited about this and I hope to see what people can do with it. There are other projects like this around, most notably the excellent PouchDB project, but I think Plasmid has properties that make it a better fit for many needs.

Download

This release is PlasmidJS 0.2.0 and is available at Github and on the Plasmid GitHub page.

0.2.0 on Github

0.2.0 on the Website

Jump Right In

If you'd like to jump right in, check out the Getting Started Guide and then the full PlasmidJS API Documentation.

Comments

Statement Functions

At a small suggestion in #python, I wrote up a simple module that allows the use of many python statements in places requiring statements. This post serves as the announcement and documentation. You can find the release here . The pattern is the statement's keyword appended with a single underscore, so the first, of course, is print_. The example writes 'some+text' to an IOString for a URL query string. This mostly follows what it seems the print function will be in py3k. print_("some", "text", outfile=query_iostring, sep="+", end="") An obvious second choice was to wrap if statements. They take a condition value, and expect a truth value or callback an an optional else value or callback. Values and callbacks are named if_true, cb_true, if_false, and cb_false. if_(raw_input("Continue?")=="Y", cb_true=play_game, cb_false=quit) Of course, often your else might be an error case, so raising an exception could be useful

CARDIAC: The Cardboard Computer

I am just so excited about this. CARDIAC. The Cardboard Computer. How cool is that? This piece of history is amazing and better than that: it is extremely accessible. This fantastic design was built in 1969 by David Hagelbarger at Bell Labs to explain what computers were to those who would otherwise have no exposure to them. Miraculously, the CARDIAC (CARDboard Interactive Aid to Computation) was able to actually function as a slow and rudimentary computer. One of the most fascinating aspects of this gem is that at the time of its publication the scope it was able to demonstrate was actually useful in explaining what a computer was. Could you imagine trying to explain computers today with anything close to the CARDIAC? It had 100 memory locations and only ten instructions. The memory held signed 3-digit numbers (-999 through 999) and instructions could be encoded such that the first digit was the instruction and the second two digits were the address of memory to operate on

How To Test

This is an index of different articles I've written covering techniques for testing specific software components. The number is small, but will grow in time. Initially, expect a heavier lean towards Django topics. How To Test Django Template Tags Parts One and Two

Developing Upwards

Search This Blog