Hi, thank you very much for your app, this is very efficient for what I am building. I have found a bug in the javascript code that bind fields between them. The thing is that the bindings are not actually stored in an array, but in a string (comma-separated), in a one-element array, in the array. I had to modify a bit the code to make it work correctly (line 105 in static/js/bindings.js):

var tmp = binding.true_field[0][0];
tmp = tmp.split(",");
$.each(tmp, function(index, selector){
    ...
}

(and the same for false fields)

I assume it would be a better way to correctly fill the array instead of splitting the string, but I can't understand where it is filled. There might be the same problem for true/false choices but I did not try to use them.

Once uploaded images do not validate if the form is submitted without changing them. PIL throws IOError (truncated file).

Changing file's opening mode should help:

https://github.com/django-dataforms/django-dataforms/blob/master/dataforms/forms.py#L565 - there is 'r' mode, 'rb' should be used probably.

Hi,

Eric Liu and I worked on some cool features that we'd like to see merged into the original branch of the project. The features are:

1 - Support for specifying an "initial" parameter to create_collection and create_form, this can be thought as the same behavior of specifying initial data for a django form. 2 - Enable form fields to have a "placeholder" attribute defined; you know, the HTML5 placeholder attribute :) 3 - Support for a "virtual" (in the sense that it isn't going to be send as a parameter to the field itself, instead it is just used by dataforms itself) field attribute "blank_choice_label", which is used to change the default option "--------" on select fields (a use case is when you have a "State" dropdown and you want the default option to be "[Select State]").

Please, let me know what you think.

Thanks!