Hi, I'm working on a ticket management system (a la Trac) for in-house applications for my company. I have simple models: Application, Component, Milestone, Ticket.
One can open a ticket on an application, for a specific Component (belonging to the application selected), and attach it to a milestone (again belonging to that application). Because of this, my django-app is getting more and more complex: - I can't use generic views or the admin interface because the default Ticket model allows to link any application with any component with any milestone. - I have lots of custom manipulators / views for allowing only a subset of Milestones and Components per application. - etc... I feel like hacking PHP, and I lose the "Django rapid development" point :( So I came up with the idea that I should refine my django-app to match only one in-house application, and duplicate my django-app in my project for each inhouse application we manage. This would make my models dependencies a refreshing breeze (no more Application model required), but I would have to duplicate models, views, code and so on. Not very sexy... Did anyone end up with anything similar? Thanks for any feedback. Accédez au courrier électronique de La Poste : www.laposte.net ; 3615 LAPOSTENET (0,34 /mn) ; tél : 08 92 68 13 50 (0,34/mn) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
