The purpose of this package is to make it easy to use FOM the Fluid Object Mapper to define models for Django based applications that need to make use of Fluidinfo as a meta-data backend (instead of a traditional relational database).
Django-fluidinfo works by wrapping the FOM based classes in Django-esque classes so you can do the following:
from django_fluidinfo import models
class foo(models.Model):
bar = models.CharField('test/namespace/bar_tag')
baz = models.IntegerField('test/namespace/baz_tag')
These models can then be used with specially created ModelForms that function in a similar fashion to the traditional Django ModelForms:
from django_fluidinfo.forms import ModelForm
class FooForm(ModelForm):
class Meta:
model = Foo
This work is unfinished. Here’s what needs doing:
Fluidinfo is a radical approach to creating, storing, sharing and finding information. There is only one instance of Fluidinfo that all users and applications share, so everyone’s data is stored in the same place. However, there is a unique yet powerful permissions system so everyone still has control over the information they put into Fluidinfo. The important thing to remember is that Fluidinfo makes it easy to mash up, share, annotate and create information in a sort of social-graph of data.
The important key concepts are:
Access to Fluidinfo is provided by a RESTful API which FOM abstracts away into a Pythonic object-oriented API.
The intention of django-fluidinfo is to add a thin layer and useful classes on top of FOM in order to make it as simple as possible to use Fluidinfo from within Django.
More information about Fluidinfo can be found at Fluidinfo’s website.
Footnotes
| [1] | NOT instantiations of classes as in Object Oriented Programming, but simply “objects” in the common-sense use of the term. |