So, I have an Arduino Duemilanove (wtf is wrong with those Arduino people and their board names?) and I decided it was time to get some progress with hacking the Dallas Semiconductor temperature monitors I got from Maxim IC.
The sensors are DS18S20 sensors, 1-Wire temperature monitors. Using them in ...
The king and his men,
Stole the queen from her bed,
And bound her in her bones.
The seas be ours,
and by the powers,
Where we will, we’ll roam.
Yo, ho, all hands,
Hoist the colours high.
Heave ho, thieves and beggars,
Never shall we die!
Yo, ho, haul together,
Hoist the colours high.
Heave ho, thieves and beggars,
Never shall we die!
Some men have died,
And some are alive,
And others sail on the sea
– With the keys to the cage…
And the Devil to pay,
We lay to Fiddler’s Green!
The bell has been raised
From its watery grave…
Do you hear its sepulchral tone?
A call to all,
Pay heed the squall
And turn your sail to home!
Yo ho, haul together,
Hoist the Colors high.
Heave ho, thieves and beggars,
Never shall we die!
Voor de mensen die ik heb laten zitten.
voor de mensen die al een tijdje niks hebben gehoord.
Voor de mensen die ik lief heb.
Voor de mensen die ik al LANG had willen zien.
4 y’all….
I've uploaded a new version of django-history-tables [1] to the mercurial repository. It now should run on Django 1.0 + 1.1 and finally supports (although basically) the Admin interface.
For those that don't know django-history-tables (guessing that's 99.9% of everybody reading this), it is a pluggable Django application to create addition tables inside the database recording the history of changes and deletion of Django models.
This in itself is not unique there are many more project out there doing basically the same but most implement this by serializing data (such as pickling, json, xml, etc). Big drawback of this approach is that when schema changes your serialized history does not change with it. Somewhere down the line when you have forgotten all the schema changes it will be most difficult to use this history data.
django-history-tables works by using one additional 'normal' database table to store history information; major benefit of this approach is that there's no pickling, no serializing, and it should be able to support anything that your database supports as well.
Schema changes in this approach needs to be applied to both tables. When you change your model, you will need to change the schema of the history table as well. <shameless-plug>By using my sqldiff extensions in django-extensions this process can be made pretty easy.</shameless-plug>
In the future I hope to support the major schema migration tools for Django so that we can make schema changes in the history models even less painful.
It has been a while since I've worked on django-history-tables and truth be told I kinda forgot about it :-) It's been lingering in a corner for a while now and I've been busy doing other things like maintaining django-extensions and writing news sites in Django.
But then something really cool happened, something which is really telling for Open Source projects and the Open Source community as a hole. Somebody contacted me, out of the blue, an email from a stranger with the message that they had updated my old proof-of-concept code to run on new versions of Django with the patch attached.
We started talking and found that other people had written patches for it as well and put them up on the issue tracker at Google code. A project which was, for all intents and purposes dead to me, suddenly sparked back to live.
This inspired me to get to work again and to try to get the project back into some kind of shape.
Now it's not perfect yet, it will have bugs and needs more work. I can also do with some help improving it, making it better and reviewing that the implementation works as expected.
So please try it, play with it, have fun with it. And if you like it leave a message :)
| [1] | Django History Tables: http://code.google.com/p/django-history-tables/ |
