z4r/django-dymo — comment on commit 99250a1cb7ade63d1921d4f50e73c7512c234d2d
File:  line 0
By willhardy:

Sorry for the delayed response. Ultimately, this isn't exactly the direction I like to take frameworks: I prefer to let the end developer explicitly define their model and admin definitions. Agreed, that there are a lot of common steps currently involved in using dymo, and a number of gotchas that should be abstracted in a framework. I would rather work on reducing these steps and abstracting the irrelevant complexity, whilst leaving the end developers in control of their own models and admin definitions. This would however be fine as a separate project (but let me know if you do go in that direction, I'm currently not guaranteeing backwards compatibility).

I'll be checking in a number improvements in this direction, hopefully this would make an example project very succinct, but also obvious and explicit.

But thanks a lot for taking the time to get into the details! Please let me know what you think of the upcoming changes, I cannot really guess how useful they are for other developers and enjoy having my various decisions challenged.