Issue 64

Order of Operation (March 26, 2016)

1. Generate Execution Trace from example code (Han)

2. Searchbox will be used to match user input in executiontrace (Dana)

3. Collect search resuts in an array. (Dana)

4. Present the results in a static table (actual UI) for the user. (Dana)

5. Make the table dynamic with the Combo box different number of columns (jQuery) (Dana and Han)

6. Refine the combo box options (Han)

7. Import jlinq and jQuery for Aurelia (David)

8. Integrate with Ace Editor (Dana and Han)

9. Integrate with Aurelia (Working with David)

Sprint #4 Work Collaboration (March 22nd - April 6th)

1) (David) Issue #60 - Change onEventChange() names to more meaningful terms (David)
2) (Dana) Issue #64 - Add an interactive UI with a search and combo box for filtering execution trace
3) (Venkat) Issue #65 - Build visualization to execute program history
4) (Han) Issue #63 - Trace Service API example. And trying to get it working inside Aurelia.

Sprint #3 Work Collaboration (March 1st - March 22nd)

Based on our meeting after sprint 2 wrap-up on March 1st, we will create a stateless trace service being the 
execution trace feature team and provide code values and other pieces of the trace to the pastebin team
through a service class. We have a few items to be completed for sprint 3 and to make everyone's job easier
and team collaboration more organized for our feature team, here is my proposal for the task assignment

1) traceService.js class - David, since you have been working on integrating this class into Aurelia towards the end
   of spring 2, I think it would be a good idea for you to continue defining the interface to make it all work for 
   the visualization team. 
2) traceHelper.js class - (Han) Since I have been working on the getLineValues(lineNumber) and getValues(rangeValues)
   functions in the sample ExecutionTraceInterface.js, I will work on defining them traceHelper.js as we've discussed
   so we can use them in traceService.js
3) traceSearch.js Class - Dana, as you have been assigned the work for creating a trace table and query through the
   values for sprint 3, you should continue look into this area of the design. Since I have mostly implemented the 
   two methods we currently need for traceHelepr.js I (Han) will also help you look into it and we can hold a pair
   programming session as needed.
4) infinite loop solution - Venkat, as you have been working on infinite loop and implementing timeout functions for
   each loop in the code I would like you to discuss this with David as he has implemented a different way of solving
   this issue with global timeout.

Everyone should try to focus on the piece they have been assigned to before getting involved into another member's task so we can ensure there's no duplication work and all work gets completed before spring #3 is due. Please let me know if have any concerns regarding this assignment.

#Team Management

Team Meeting Notes with Professor LaToza (02-24-16)

1. Discussion about trace table format

2. How to divide up the work among the team for collaboration

3. What is expected for the upcoming sprint?

Get from other's branch

git branch "your own branch" git pull origin "someone's branch"

Workflow

 issue 11 Find loops (AST) -->
      issue 16 Stack trace (Instrumentation)--> End Sprint 1.
         issue 20 Type trace --> 
            issue 17 Location trace -->
                 issue 18 Trace search. End Sprint 2.

Communication Policy

We must acknowledge every Slack message.

##Development Policies ###Nightly commits for personal branches.

###Weekly commits (Mondays 9PM) for team branch.

###Closing Issues Stage 1: Peer review (your partner test cases passed)

Stage 2: Team review (pull request on ExecutionTrace)

Stage 3: Professor Review (pull request on master)

#Delegation Sprint 2:

Integration (David in charge of Execution Trace branch).

Team Scheduling(Slack meetups Dana, commits Han).

Code Reviews (David and Dana, Han and Venkat).

Repository WorkFlow

##Initial Setup Clone the project's repository in your Cloud9 workspace. [How To](dana's wiki).

List of GitHub Commands Create your branch.

   git branch branch_name

##Pull Before Pushing

Get up to date with the team branch.

   git pull origin ExecutionTrace
   git push origin your_branch

Pull a request to push your work

Do some work.

###Commit your work.

   git add --all
   git commit --all (git commit -m "my commit message")
   git push --all origin your_branch	

###Using the repository's Github page.

  Add a pull request from your branch to the team branch. 
  Explain your changes.
  Commit to team branch by merge the pull request.

#Sprint 2 To-do list

    traverse tree [done]
	find types [done]
	instrument code [done]
	add data to stack trace [done]
	
    collect stack trace
	search by type, identifier, line