MaeBlok

You assemble *blocks* in your django template, with each block wired to a tastypie resource, which in turn is mapped to a django model. Each *block* will reside in a dijit ContentPane which you must define in your template. You have a choice of 2 layouts for each *block*, Form or Grid based. Form displays a single record in either a 1, 2 or 3 column layout while Grid displays many rows in a spreadsheet like grid. You can perform edits in place on fields in both layouts.

You can define the master-detail relationship between the *blocks* and enblok will automatically display the related detail *block* rows as the user navigates the master *block*'s rows.

You get for free the default *CRUD* functionality for each block, together with Search. You are not limited
to just a 2 level master-detail relationship, in fact enblok can support n-th level relationships but we
do not advise you to go beyond 3.

Read the distribution's enblok/readme.txt for further instructions.