Week 12: Fourth Sprint

Going into this demo we had Kerry with us, the CEO of the company, he has some good suggestions for high level functionality of the page, some design changes which old mate Pat was to take care of and a drill-down feature wherein if you click in the element of a graph it will flick you over to the main page and display a list of the jobs used to determine the statistic that they clicked on. I volunteered to take this on as it was quite apparent that old mate Pat was becoming a bit swamped with front-end tasks.

After I have finished the drill-down functionality I intend to move on to resolving some outstanding front-end bugs before our presentation on the 14th. During my work on the drill-down I found a couple bugs, one on my end and another on old mate Pat's end. Luckily they were quite easy to resolve so we fixed these up and continued ahead.

The process of implementing the drill-down involved a bit of learning to start with whilst working on my first goal of getting it working for the allocated vs unallocated pie chart.

To implement drill-down I had to add onto old mate Pat's existing code, I added a listener to the chart which executes a method of my choosing upon a user clicking on one of the graph elements. Said method takes the data required by the scheduler page and navigates over there using the data as parameters. From there the scheduler page filters itself as required to show the jobs related to the element the user clicked on. A use case example for this would be if they wanted to click on the 'allocated' portion of the pie chart to see which jobs are allocated, it would then flick them over to the scheduler page and show them the jobs, like so:

After getting over this initial learning hump I moved onto incorporating the global filters into the drill-down, so that if there are global filters set they also come over to the scheduler page and reflect in the jobs shown.

.
above is a snippet of code wherein I am receiving the parameters into a local object then following that I execute a switch statement that discerns the element clicked on from the dashboard page then calls the setFilters() method with appropriate parameters.

Next weeks blog will be the final one, not because we are done at fieldGo but because the blogs are due. Oh well, I'll try to give it a nice ending haha.

We finished off the week with both of us making good progress into drill-down and filtering. Hopefully next week we can polish these two features off and spend the rest of our time ironing out the kinks before presenting the demo on the 14th.