Code from branch experimentValidation (commits 7349eb4 to fe074a3) (7 commits) already merged into newCreationFlow via develop.

Now, restructure this validation to be dynamic (where possible, done as the user passes through the field).

Includes from before: experiment title, input variable names, start date must not be after end date, list inputs must have at least one list option, email address field validation (admins and published).

New: validation of likert steps (should be a valid nonnegative number)

EDIT: New: validation of timeout (should be a valid nonnegative number)

Master Issue: #63

The slider is not a right way.

1. Should support all non-negative integers, including 0.
2. About negative numbers, since our conditional parser doesn't support negative numbers, we do not allow user to input a negative number.
3. Should not have minimum or maximum numbers.

Android Screenshot:

When the user clicks "submit" or "verify," perhaps they could get a page that contains all the errored widgets, so they can fix all their errors on one page.

Master issue: #63

Master Ticket:
#51

1. We need a radio like button instead of a button with a number
2. We need a left label and also a right label

Android design:

Crash reason:

1. one response in an experiment named 'bugs' where the experimentName field is null because it was submitted on the web form along time ago when we were just starting to do web based responses.
2. Also, it looks like the NSDate objects on many of those events are funky with years like 1969 and 45167
3. experimentId is null too
4. And the server doesn't return the experimentId on the events that are retrieved

Both in menu bar and in normal flow.

And another issue is that the textfield text is not set until user clicks on return button on the keyboard.

An input group is a list of schedules and a list of inputs. Each experiment will have a list of input groups.

Involves:

• Updating model to use input groups
• Migrating Android database
• Migrating server data store to use json objects

Assumptions:

• Sane schedulers who won't overlap input group schedules
• Android-side notifications are by input group, not by experiment (so, no problem with one triggered and one scheduled notification from each experiment being active).

This will allow us to quit sending -1 for the inputId on join and stop events.

1. user should be able to modify schedule right before they join if userEditable is set to YES. If userEditable is set to NO, then user should be disabled to modify the schedule.
2. user should be able to modify schedule via running experiment panel
3. for different scheduleTypes, user's ability to modify the schedule should be different
4. schedule modified should be stored
5. local notification should be modified accordingly
6. userEditable should be set to YES by default, especially
7. if the user modified the schedule before he/she joined, the modified schedule should be piggybacked inside the join event.

blah blah blah

As of the new light loading scheme implementation, Find experiments does not update Running Experiment definitions. It should.

In the meantime, user should use the Refresh button on the Running Experiments screen.

This way, the user knows what is wrong immediately.

Master issue: #63

Also add testing for "previous" and "next" logic buttons.

1. should not allow user to edit the schedule right before they join an experiment if the schedule's userEditable is set to NO
2. if the user modified the schedule before he/she joined, the modified schedule should be piggybacked inside the join event.

Add "verify" vs. "submit" options, or perhaps verify each panel as it is passed through in the flow.
Allow user to continue anyway even if there are errors.

Difficulty: some of the dynamic validation of fields will now need to be done at the beginning, as the user may re-enter the experiment creation view with invalid fields.

Master issue: #63

EDIT: This feature is two-pronged:

1. Verify button -- indicate error to users.
2. Save button -- if errors, alert user. However, allow them to continue if they would like.

Currently default timeout values aren't stuffed into the JSON generated by the server.

Use case:

• Surf to https://quantifiedself.appspot.com/experiments
  //EXP: JSON that includes timeout key's for each experiment
  //ACT: timeout key only appears for experiments that explicitly set the value

Take the user through the input group flow in experiment creation and make sure the underlying data model gets updated.

Schedule field is for backward compatibility usage, which doesn't apply to iOS.

#54

If user types in a conditional logic expression, make sure it is logical (fits our grammar and uses variable names that exist).

Master issue: #63

Add validation to experiment creation flow.

Master Ticket:
#51

• Need a better parser to support all conditions: ==, !=, >, <, >=, <=

&& || ()

No negative number support for now

q2 contains 1

• Need re-design to avoid N^2 computation for parsing and deciding part.

Give user the ability to reorder input tiles by dragging.

1. When joinEvent=1, Android payload has the schedule, but iOS doesn't, see the attachment.
2. For same timeZone:
   Android: timezone = "-07:00";
   iOS: timezone = UTC;

The payload is different means we may not post the correct event payload to server.

Payload Sample:
{
appId = Android;
emptyResponse = 0;
experimentName = Compliment;
experimentVersion = 1;
idFromTimes = 1373679703000;
joinEvent = 1;
missedSignal = 0;
pacoVersion = "2.0.79";
responseTime = 1373679703000;
shared = 0;
timezone = "-07:00";
what = {
joined = true;
schedule = "type = esm,frequency = 1,esmPeriod = day,startHour = 11:00,endHour = 21:00,weekends = true,times = [16:00],repeatRate = 1,daysOfWeek = ,nthOfMonth = 1,byDayOfMonth = true,dayOfMonth = 1";
};
whatString = "schedule=type = esm,frequency = 1,esmPeriod = day,startHour = 11:00,endHour = 21:00,weekends = true,times = [16:00],repeatRate = 1,daysOfWeek = ,nthOfMonth = 1,byDayOfMonth = true,dayOfMonth = 1, joined=true";
when = 1373690451535;
who = "[email protected]";
},
{
appId = "ios_paco";
emptyResponse = 0;
experimentName = "Compliment_1372870251.119019";
idFromTimes = 1372870251000;
joinEvent = 1;
missedSignal = 0;
pacoVersion = 1;
responseTime = 1372870251000;
shared = 0;
timezone = UTC;
what = {
joined = true;
};
whatString = "joined=true";
when = 1372870251386;
who = "[email protected]";
},

Master Ticket:
#51

After user clicks on submit, and the answer is submitted successfully, we should show a success alert.

1. expired experiments handling
2. deleted experiments handling

See if adding Paco-Server/war/pacoserver to .gitignore affects the server build.

User can:

• Choose an option to add conditional logic.
• Draw an arrow.
• Use pulldown menus on the input to define conditional logic.
• Click on a particular arrow to view the conditional it represents.

Statement should be reflected in panel on the input as well as by the arrows

Challenges/things to watch out for:

• Parenthesization
• Multiple meanings of dragging
• Hiding the arrows
• Error-checking the variable names

1. Be able to know if the user has participated the experiment or not
2. If he/she did participate, show an alert to notify the user
3. Code cleaning of old design of allowing participating multiple times

This is best done after the data model is updated.

Validation for:

• Unique variable names across signal groups.
• Required signal group names.

Master issue: #63

Currently, each text box and check box in experiment creation has its own anonymous value change handler. This could become a performance issue once there are multiple input groups. So, for classes with multiple ValueChangeHandlers (e.g. InputsPanel), let the containing class be the ValueChangeHandler.

#137

Minor bug.

1. User should be able to submit a photo
2. When user upload a picture, we need to validate it and maybe re-size it to the right size.
3. The photo should also be stored locally

Requirement: 1M

Android Code:
InputLayout.java : getPhotoValue()

When the user clicks on Participate and the survey page is shown, we shouldn't set default answers for them, especially considering that the questions may be conditional.

1. Administer experiments view -- hide the experiment list (or make it draggable/clickable) when a user clicks on an experiment

2. Experiment content panel should be scrollable and fixed size so its buttons don't keep moving.

3. Better positioning for the Create Experiment and Cancel buttons, which are now just fixed at the bottom.

4. Change wording/constants where necessary.

EDIT:

5. Format mouse-over text for error fields.

EDIT (2):

6. Format conditional logic panel to be clearer.

Currently, the json generator for /events does not add the experimentId.