And practically, because open source is a model of collaboration, and there's no collaboration here -- django's a collaborative software project, and this is an engineering dead end where you pay (or not) for the code and then it gets thrown away afterwards. It's the wasted effort and duplication that bothers me, not the fact that money is involved.
Perhaps in some future release Django will incorporate one of these as standard. It's not much work to clean up the CSS each time, but it'd be one less thing to do in building great Django apps.
Kudos and credit to the authors of the original admin application – there's a hook for almost anything making it incredibly flexible. My major gripe has been template overriding (lot's of copy-pasting entire templates just to add a new block); but at least it's possible.
If that's your problem then take a look at: https://pypi.python.org/pypi/django-apptemplates
I think the price is reasonable and encourages people to use it in their commercial Django projects.
There is nothing that prevents people from deciding to pay him more if they feel like it.
That's a fallacious argument. That's not how the market works—consumers are very biased by prices. The more something costs, the more the perceived worth. That's why retailers offer sales. We've priced this at $1000 because it's worth $1000, but we'll give it to you for $800! If you price something too low, you're saying: this is worth $600, but please please pay me $800 because I worked really hard!
I agree with grandparent. $400 is at most 10 hours of designer/developer time—orders of magnitude cheaper than having this custom coded. The current Django admin desigin is a few years out of date; if I were developing a large-scale commercial application, I'd be more than happy to drop a few grand to significantly improve the backend UX.
I'm excited about this because if it actually makes money, supports the authors etc., then we can look forward to a well supported django admin interface.
Good luck to the authors.
Actually mptt tree package integration example is already added: http://djangosuit.com/admin/integrations/category/
It doesn't do some automatic sorting magic, but this is in our future plans.
> You must give any other recipients of the Work or Derivative Works a copy of this License; and
Is a simple mention, in the form of a link to the original Aoache License, enough?
http://exadmin.herokuapp.com/ User: admin Password: admin
People need to eat, and writing open source software to provide for themselves seems like a much better model than doing it for free in their spare time off from some proprietary coding job.
People who live and work outside of academia (and, lately, inside of it as well) for long enough eventually figure out that this perspective is naive. It just takes a while to lift your perspective far enough to see a larger part of the picture.
Personally, I'd love to see more of a marketplace for OSS projects. Open, collaborative projects that still make enough money to fund continued developement seems like a pretty good thing all round to me.
That said, a better question would be what's the problem with "paid for Django extensions"? If you don't like it, don't buy it.