Closed dyve closed 10 years ago
Generally, this looks great. @dyve, would you mind pulling the GeoDjango stuff into a separate PR? I'd really like to explore how we can add tests for that stuff. The rest of the changes are good to go as-is.
The naming suggestion is good - I'll make that change in a separate PR. We use this package all over the place internally, so I'll need to coordinate the changes.
OK, I'll wait for the name changes first and see if I can put in separate PR's then.
I am working my own version of this into a project with GeoDjango now. I'll contribute my changes. Best way to go forward:
Good news is, the GeoDjango stuff is working in my project :-)
South compatibility, GeoDjango versions, LiveModel, LiveGeoModel
Tests pass. I added an extra test run of aal the field tests to test a LiveModel against a hand coded Model with a LiveField.
I changed the file names to match the Django equivalents. Also, consider naming the app 'livefield' instead of 'django-livefield'. Keep the repo and the PyPI name to django-livefield of course.