dont force start/end

[GoogleCodeExporter]

Seems odd that Survey.opens and .closes are required.

I know it is easy enough to stuff bogus date/times into the fields....

Original issue reported on code.google.com by cfkars...@gmail.com on 17 Jul 2008 at 12:55

[GoogleCodeExporter]

Could you please elaborate around your use case ?
So far my opinion is different, adding a date is simple since you have some JS 
helper
on the right of the textfield.
The problem I see with this request is that these dates are used in several 
places to
control the behavior of the application.
--yml

Original comment by yann.ma...@gmail.com on 17 Jul 2008 at 9:46

[GoogleCodeExporter]

use case: Ongoing, indefinite collection of info.  In my current task, a 
"request a
quote" page which is really an elaborate "Contact us: name/phone#".

The JS helper only helps for open.  there is no "end of time" button for 
closes. 
Also, I am adding surveys programatically, and so the extra code (even 10 
bytes) is
distracting clutter.

:ooks like the only place that would need adjustment is
def open(self): - but I have a question about that as it is.

Anywhere else that would need adjustment?

Original comment by cfkars...@gmail.com on 17 Jul 2008 at 3:48

[GoogleCodeExporter]

cfkarsten,

I do not understand what you mean by "only helps for open". As you can see in 
the
screen capture attached the JS helper are there for "opens" and "closes". This 
page
is visible if you point your browser to : http://localhost:8000/survey/add/

If you want to remove this 2 dates you will also need to change the logic in 
many
places in the code we are checking if the date is between "opens" and "closes".

As of now I am against a modification in the logic. This report will be closed 
has
"wontfix"

--yml

Original comment by yann.ma...@gmail.com on 18 Jul 2008 at 7:30

• Changed state: WontFix

Attachments:

• ScreenShot022.png

[GoogleCodeExporter]

Wait the end of the discussion thread before deciding on this ticket : 
http://groups.google.com/group/django-survey/browse_thread/thread/a614f3c64f32e7
7c#

Original comment by yann.ma...@gmail.com on 18 Jul 2008 at 8:06

• Changed state: New

[GoogleCodeExporter]

juser@pycon08a:~/dj/lib/django-survey$ python examples/manage.py test survey 
Creating test database...
Creating table auth_permission
Creating table auth_group
Creating table auth_user
Creating table auth_message
Creating table django_site
Creating table django_content_type
Creating table django_session
Creating table django_admin_log
Creating table survey_survey
Creating table survey_question
Creating table survey_choice
Creating table survey_answer
Installing index for auth.Permission model
Installing index for auth.Message model
Installing index for admin.LogEntry model
Installing index for survey.Survey model
Installing index for survey.Question model
Installing index for survey.Choice model
Installing index for survey.Answer model
...
----------------------------------------------------------------------
Ran 3 tests in 1.088s

OK
Destroying test database...

Original comment by cfkars...@gmail.com on 18 Jul 2008 at 4:00

Attachments:

• django-survey.diff

[GoogleCodeExporter]

> I do not understand what you mean by "only helps for open". 

For open I can click today/now - that means when I save the survey, current 
date/time
will be after what got plugged in for .open, so the survey is usable until 
.close,
which is the problem:

There isn't a quick way to fill in .close with something that will let me use 
the
survey: If I click today/now, that basically means "it's closed before it was 
even
created"    so I have do drill into the calendar and click 'tomorrow',  which 
is OK
for testing, but no good for something I want open forever.

Original comment by cfkars...@gmail.com on 18 Jul 2008 at 4:07