{"shas":[["5e00de5204ff2f0a18db91f710bf1888a6e45057","f80d0ca101e967b50b730ddf8e8aca0de85e8df6@exanimo.com","Admin thumbnails.","Matthew Tretter"],["4c78f2d24c4125b6df42a9f4a8a7fdede3f46bcd","f80d0ca101e967b50b730ddf8e8aca0de85e8df6@exanimo.com","_imgfield is now a property of ImageSpec\n\nMoved _imgfield from ImageModel to ImageSpec. Theoretically, this will allow you\nto have specs that use different image fields on the same model.","Matthew Tretter"],["57a28091c559c5a4f07140901a21b7b0904d124b","f80d0ca101e967b50b730ddf8e8aca0de85e8df6@exanimo.com","Added default_image_field\n\nThis works kind of like Django's models' _default_manager. If your specs don't\nspecify an image_field, and your IKOptions don't specify a default_image_field,\nthe first ImageField your model defines will be used.","Matthew Tretter"],["8cfe485a5a5a97c553096ed19b9a36e8c9bdd9a4","f80d0ca101e967b50b730ddf8e8aca0de85e8df6@exanimo.com","Storage can be specified on a per-spec basis.\n\nIf not defined on the spec, IKOptions.default_storage will be used. If that's\nnot defined, it will fall back to the image field's storage.","Matthew Tretter"]],"ref":"refs/heads/new_api","size":4,"head":"8cfe485a5a5a97c553096ed19b9a36e8c9bdd9a4","push_id":42265133}