update the readme to correctly refer to github source rather than google repository (which is apparently abandoned) #4
Conversation
…r than the old one (on code.google.com)
…'arbitrary' responses for multiple choice and multi-choice survey questions
This avoids to copy the files in any new app, but they are autodiscovered by django.static.
…e questions. if present, make it show up only if it is needed (only if the user chooses the arbitrary answer option
…e survey interface to automatically redirect to login screen if there is an attempt to use a survey that requires login
Add option to hide mapping and flickr Collapse some fieldsets Change sizing on some boxes Combine rows in a few places Convert help text in to question mark and hover Make everything a lot more compact
Add option to hide mapping and flickr Collapse some fieldsets Change sizing on some boxes Combine rows in a few places Convert help text in to question mark and hover Make everything a lot more compact
…(simplify the admin interface)
This is done in support of the tagit jquery plugin which will be used to make it easier to add survey question fieldnames to a survey
…ort. This change is not yet finished and operational yet.
…or survey report field name input (so you don't have to remember the valid names of fields in surveys)
…names are really names of fields in surveys
…instead of refering directly to contrib.auth.user model
…title for this section
…me rendering a little easier
…ssion including checkboxes, multichoice, and regular question types too. make sure prepopulate works with 'arbitrary' type fields
… records go in the same pre-existing records. dont create more and more answer records
…and automatically use the survey complete page if report is not available
…r reports with axes from multiple surveys
|
Hey, there's a huge amount of work here! Awesom, this is amazong. Sorry for taking like ... two months to get back to you, especially considering my answer's gonna be "I need even more time to review your pull req." Gimmie a few days to look at this all.
|
|
Hi Adam. Thanks for taking the time to look it over. No sweat at all, take your time. There is a lot of work there and some of it was done with more consideration towards being mergeable and some of it was just done to try to get it done and useable for my project. I will probably be picking this up again and doing a lot more work in a project phase #2. In the meantime, please let me know if there are any little things that I can clean up for you to make it more worth your while to merge in. Future plans include: · Finishing my project to make it possible to have survey reports that combine results from multiple surveys. In my application, people have a login and they will do regular updates on various facts about their business. Their login includes some profile surveys that provide general facts about their business. Additionally, I survey them periodically for periodic information (e.g. what were your sales recently). In reports, I’m hoping to be able to combine this information to say: “people who said (in their profile) that they are doing X are earning on avg Y”. In other words, I guess some surveys are gathering independent variables and some are gathering dependent variables · I want to make it possible to update your survey responses at any time (again, the profile thing) · I want to provide the option to integrate with amCharts for your visualizations (for people who happen to have a license to amCharts) · At one point I set out to refactor the views.py a little to make it easier to do the multi-survey report thing. I might still do that but that will be harder for you to integrate so it’s probably not worth it. Perhaps when I get to that point if ever I will coordinate with you to see whether and how you would like it done. I apologize in advance for the myriad mistakes and shortcomings of the code you are about to read. J From: Adam DePrince [mailto:[email protected]] Hey, there's a huge amount of work here! Awesom, this is amazong. Sorry for taking like ... two months to get back to you, especially considering my answer's gonna be "I need even more time to review your pull req." Gimmie a few days to look at this all.
— |
Just added a line to the readme and modified the reference to google to indicate it is the old repo.
Did not update setup.py though maybe should...