Matt Culbreth wrote: > Hello Friends, > > I'm beginning a new project for a client and I'm going to use either > Django or TurboGears. I'd like to get some feedback from this group on > the direction I should take.
Here's a point for point of my suggestions. Please note that my experience with Django is rather limited, so this information may be slightly biased towards my experience. > > The facts: > 1. The application is basically for a user to respond to surveys. Both should be sufficient here. ;) > 2. The survey questions are fixed and follow the standard 5 point > response types with radio buttons (strongly agree, agree, mix, > disagree, strongly disagree). Again, both will handle this well. I am assuming that you will want to be able to create/edit new surveys, which might be slightly easier with Django due to the admin interface. That said I doubt the relationships in a survey will be anything that TurboGears' Catwalk couldn't handle. > 3. There are a fixed number of survey pages. The user fills out a > survey and then is asked to select from a pre-defined list of possible > problems and their solutions. The application shows the pre-defined > list, which is filtered based on some of their answers to the survey > questions. Either platform should suit you well here. If the filtering gets really complicated you might get easier queries/better performance out of SQLAlchemy, which seems to have better support in TurboGears. > 4. There needs to be a very simple Admin interface to essentially > create a new survey instance, invite users (by emails), and then > monitor the progress of the survey (who has responded, etc.). With Django you would have a jumpstart on this, as the "create a new survey instance" is built in. Catwalk can do this well, but this kind of task isn't exactly what Catwalk was designed to do. Both should be relatively well suited for the rest of this. > 5. There will be 5-6 reports based on the surveys. These reports are > aggregate responses by manager, organization unit, etc. Nothing > overall difficult. If any of those reports would look good as graphs, TurboGears has you covered. You can easily download and install PlotKit already packaged as a ready-to-use TurboGears widget. > > So, based on this, my initial leaning had been to go to TurboGears. My > thoughts were that the application is not interested in content > management or display, and that I'd like to use a bit of AJAX goodies > here and there. AJAX is easier in TG as well. The widget system makes it pretty simple to write and package discrete bits of functionality so that it is easy to have them show up on the page. It can even take care of javascript/css includes for you, so you can get back to concentrating on something besides updating your templates. > > Any different take on this? Is Django a fit here and I'm not seeing > it? Django would work pretty well. I think out of the two TG is a better fit, but really either one seems capable enough. hth, Adam --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
