django-apps

I need an app for crop an image in the client side, I mean, using a cropping tool like Jcrop jquery plugin. I found this tools: django-image-cropper django-image-cropping django-imagehandler django-avatar-crop But the last two depends of admin and the two first seem very coupled to ther own ImageFields and models, any good solution? We are working over a big application with many features and is very difficult change the logic writed I think this is something that you will probably be best off writing yourself as it depends on how your data and models are layed out, whether (and where) you

I would like to bundle up css and javascript files. I also want to send far-future expire headers to clients, so I need file versioning. A quick search across the Internet has shown there are several asset managers developed for Django. Here is a list of those that I could reach: django-compress django-assets django-assetpackager django-media-bundler django-mediacat django-site-assets django-static-management django-compressor They seem to perform more or less the same job. django-compress, django-compressor and django-site-assets seem to be especially promising at the first glance. I will

so I have 2 apps running in the same project. My files are structured as follows: /project_codebase /project __init.py settings.py urls.py wsgi.py ... /app1 ... /app2 ... manage.py So, I for some weird reason have a different name for my base directory (that is, it ends with codebase). Hopefully, that is not an issue. In my settings.py , I have this: INSTALLED_APPS = [ ... 'app1', 'app2', ] Ok, so in my models.py (from app2) , I can easily import models from app1 with from app1.models import * , however, when I use from app2.models import * in my models.py (from app1) , I get an ImportError.

I'm really struggling with this whole app-idea. I read a lot of tutorials and style guides and I know I should try to create specialized apps, that do exactly one thing. This all makes sense when looking at some simple tutorial project but as soon as it gets to a complex real life project, I find myself unable to determine how I should draw the lines between different apps. One of the problems is, that I want to have one site (or multiple sites) where the user sees a lot of different stuff. Stuff that should be from different apps, when following the app design rules. How would I realize

I've found 3 row-level permission solutions for Django 1.2+ django-object-permissions django-guardian django-authority Could someone tell if there is any recommended more than the others, what are their main differences, etc.? I'll start this by saying we use none of these for object level permission - we use our own custom method and I really wish we hadn't. If you can avoid object level permissions at all, do so, they are a pain to organise. This is how I evaluate the 3 apps you've mentioned. Active Development: django-guardian (1 week ago) django-object-permissions (1 year ago) django

I will be brief: to work in the spirit and idea of a Django app, it is ok for an app to import models from inside another app ? Say, a User statistics app will import models from a User app something like: from users.models import users If you're building an internal app that has no chance of ever being released to the public, sure, do whatever you want. If you're building an internal app that has little chance of ever being released to the public, but will possibly be used by future/current developers, sure, but be sure to document what the app needs to work properly. If you're building an