<snip> > plug and play. A manager/developer making the decisions on a platform > for their next project should be able to download django and just plug > in the functionality he/she needs. Dependencies will exist but that's > normal. <snip> > If all that would happen django would be an easy choice for anyone, > well absolutely for me. Without these I spent months swinging back > and forth on various decisions because the above situation does not > exist for django.
The market you talk about sounds like one where things like Pinax/ Satchmo/LFS are a substantial match for their requirements and who can then benefit from the power of Django in extending beyond the capabilities of what those apps provide. The drupal/joomla/plone/ wordpress type market, perhaps? The kinds of applications I build in Django aren't in the style of public-facing websites, they're web-based applications where few if any of the facilities from Pinax, Satchmo or LFS are of any interest to me. In fact for me one of the appeals of Django was that it didn't try to do too much for me (i.e. it didn't quickly start to get in the way like, say, drupal tends to once you get beyond a certain point). I quite like the skeleton proposal Russ sketches out in the mail you replied to - that sounds like it would have more of a general reach rather than trying to get into the drupal/joomla/plone/wordpress space. Regards, Matt -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
