Date	31/3/11
Away	Jernej
Agendas Raised	Ø  Buttons need to be fixed. People feel like the buttons could be better. Ø  Access to the labs Ø  Make minor changes to the program
Tasks Assigned	Tim Ø  Document and continue to test the program Jernej Ø  Create new buttons Ø  Diary Ø  Create some example knots Phil Ø  Continue to work on the GUI Allen Ø   Diary Ø  Help out where needed Jun Ø  Updating the kernel part of the program Ø  Fix any slight changes that may need to be made
Summary	Overall today was about showing Luke what had changed within the program since he had last seen it. Phil had implemented the some buttons of the GUI to the program but Luke and the rest of the group through like the buttons could be better and more suited to the example given above. Whilst Luke was fiddling with the program he also raised some functionality issues that could be changed around such as when trying to move a point it remembers where the initial positions of the point and once you wish to move to the left or right you need to go past this position to be able to change directions. Luke thought that it would be more user friendly is the user moved the mouse left the point moves left and same when the user moves the mouse right instead of having to move the point so far before the direction changes. Other discussion raised was with the snapshot functionality of the program. Luke suggested that it could be usefully to have this function run automatically in the background taking a snapshoot of what the user has done every X amount of time. Others agreed with this decisions however it the problem was then raised what if the user starts to create a knot then get side tracked. The program would continually be taking and saving snapshots of the knot slowly eating up the user’s hard drive space. The last point made was that if anyone doesn’t have a lot to do they could spend some time and create examples or demo pictures of proper knots. These examples could be used for the website and possibly on the poster that is due latter in this semester.

Date	24/3
Away	Jernej
Agendas Raise	Ø  Possible things that could be changes Ø  Bugs within the code
Task assigned	Continue from previous tasks
Summary	Today’s meeting was mainly a discussion amongst the group. Luke showed up for a bit to see if things are progressing which they are, He was happy and left. The main aim of today was a discussion between Phil and Jun. Phil , at the moment is implementing the GUI side of the program. He has found as he works and adds more to the code some errors arise in sections of the code. He felt like he needed to discuss this with Jun to see if he should change massive sections of the code before implementing and GUI aspects. Some changes are minor like making the code more Object Orientated then there are other changes which are more time consuming. These two discussed it with input from Allen and Tim as to which path was better to take. At the moment the main concern is to get the GUI in place and test the program. Once this is done, then section of the code can be rewritten to make it more understandable. As a group we realise that this is not a good practice but we would rather have something that function with some slightly messy code then have something that doesn’t function at all with neat code. As for the majority of the group everyone is continuing with the tasks they have been assigned. Most are moving to testing the program to find some bugs that may occur when certain scenarios are tried. Jernej is still working on the graphics for the buttons.

Date	17/3/11
Away	-
Agendas Raised	Testing methods GUI layout
Tasks Assigned	Tim Ø  Test the program Ø  Document Jernej Ø  Graphics for the buttons Ø  Test the program Ø  Diary Allen Ø  Work on the database aspect of the program Ø  Diary Phil and Jun Ø  Work in tandem on the GUI Ø  Contain to update the Kernel part of the program
Summary	Today everyone showed and it mainly about showing the progress that had been made with the GUI to Luke. There wasn’t a lot to show but there was deffinately a GUI slowing taking place. Phil demonstrated to the group what he had done and the direction he was thinking of taking to finish what he had started. This was good because the it raised a discussion in the group and some brainstorming was done as to whether we should move in one direction or another direction. Decisions made were: Ø  What style of buttons should be used Ø  The graphics of the buttons Ø  The layout of the GUI – this had been done previously but that was back when we thought we could use Win Form Ø  Seeing if we could get the program into certain states or modes. For example editing mode would only allow the user to add , remove, redo and undo knots. A discussion about testing was also made. Phil made the idea of creating a file which contains a list of all the limitations that have been tested on the program. This way everyone can see what has been tested on the program and if these tests cause any issues. Overall today was a good meeting and a lot was discussed as to where we will take the interface and ways to sort out possible bugs that are laying within the code.

Date	14/3/11
Away	Jun, Allen, Jernej
Agendas Rasied	Ø  Phil’s Progress on the GUI Ø  Peoples concerns
Tasks Assigned	People are still continuing with what they have been assigned during the meetings last week. At the moment more focus is being placed on the actual program itself and ways to improve it, this is good but it means that the documentation is kind of taking a back seat at the moment.
Summary	Today only Phil and I (Tim) showed up for this meeting which was OK. There is still progress being made however there is concern from other group members that this progress isn’t going along fast enough and people may be getting off track. Jun had expressed his concerns that to me that we needed to continue to remind Phil to get on track and get the GUI working and implemented as quick as possible. I told Phil this in the possible way that I could without trying to raise conflict within the group. Conflict is the last thing we want at this point of the project. Phil was quite understanding with this because he knew he did fiddle around to much last semester when he was assigned a task. He had told me that he has been making progress with the GUI and hopefully would be near done with it by Thursday if not the weekend at the latest. Hopefully this is early enough for other group members. This may sound like Phil hasn't done anything for the group but this is quite the opposite. Phil has worked hard over the break but was just over whelmed when he got back to uni that was the first time he had seen the code that Jun had written. Not being able to spend 24/7 towards the project he had taken Phil sometime to go through the code and throughly understand just what each function was trying to achieve. Phil was even rewritting the code to make it easier to understand and taking out the repetitiveness in the code and just adding simple functions

Date	10/3/11
Away	Jernej
Agendas Raise	Ø  Possible ways to test the program Ø  User interface ideas / possibilities
Task assigned	Tim Ø  Update the documentation Ø  Try to attempt to Unit test the program Jernej Ø  Test the program graphically Phil Ø  Continue to develop the user interface Jun Ø  Implement changes to the program that people have mentions Allen Ø  Work on the database aspect of the program
Summary	Today’s meeting was short but simple. The main discussion was about possible ways to test the program so it can become more secure code. Tim had the idea that unit testing with XNA was easy to do however it is near impossible to be able to unit test when graphics are involved. So from here the discussion then moved onto how would you test the graphical aspect of the program. Jun said that the best way to do this would be to keep running what we have and fiddling with the program until bugs and any issues arise. The conversation then moved onto it if it was possible to still unit test the code but mainly unit test the sample functions such as the Key pressed functions. Some simple tests could be written to test all the possible solutions and methods for this. This task was assigned to Tim. After this discussion it was about how Phil is going with the user interface. He said that he hasn’t implemented anything permanent yet but is more toying with ideas and demos that he has found on the internet. Hopefully once he gains a better aspect of all of this the user interface will begin to take shape

Date	8/3/11
Away	-
Agendas Rasied	Ø  There is an issue with try to implement WinForm with XNA with the way we have written the Kernel or the main part of the program. This problem is that there is a clash within the libraries of System.Windows.Forms.Keys and Xna.Gamemaking.Keys . This creates a problem because if we wish to keep the keyboard shortcuts that are already in place we can’t add and Winform but there is a work around of just doing the interface in XNA Ø  For people such as Tim and Jernej that have trying to learn C# now trying to get their head around the XNA library is becoming pretty hard for them So Jun is willing to give them a crash course so they can understand it and also help to contribute 10% of the coding
Tasks Assigned	Same as the last meeting, everyone is continuing to work on what they have be assigned.
Summary	Overall this was a very brief meeting with everyone still working on what they were assigned from last meeting. There was some discussion from the finds of the library clashes which is fine because as a group we were leaning towards implementing the user interface within XNA as this will ease the computational resources slightly. At the moment we just need to keep things moving and moving at a fairly quick pace to get things done, sorted and move on. This means setting deadlines for things to be completed so at the end we have enough time to thoroughly test and debug the code to a higher standard.

Date	3/3/11
Away	-
Agendas Raise	Ø  Possible solutions to small bugs in the demo
Task assigned	Tim Ø  Update the documentation Ø  Construct knots that look graphically pleasing Jernej Ø  Test the program Phil & Jun Ø  Implement the user interface possibly with XNA Allen Ø  Work on the database aspect of the program
Summary	Today was about showing Luke what we had achieved as a group over the break. Luke seemed to be very impressed with the amount of work and functionality that had been achieved. Jun gave Luke a demo of all the functionality that was part of the demo such as the basic adding of points to a string, deleting point, undo and redo. Jun also demonstrate some more fancy aspects such as the use of the viewports which was done by Phil over the break, the animation of a completed string and the ability to take captures or “check points” of important stages of the construction of a knot. From here now its just a matter or deciding which way to implement the user interface. The two choices are with XNA and winforms or just simply in XNA. The idea of it just in XNA does make it computationally better and also simpler for programming purposes.

First meeting for this semester

Date	1/3/11
Away	-
Agendas Raised	Today the main agendas rose where what people thought of the work we had completed as a group over the break. Everyone was assigned individual tasks and today was a day people could share their thoughts on what others had done over the break. There was a discussion as to where we go from the simple near prototype of the main function of the program. This discussion was whether or not we should try and adapt it to winform or add buttons to it with XNA. No final idea was decided upon, however we thought we should run it past Luke first and hear the advice he has to give
Tasks Assigned	Tim Ø  Testing Ø  Trying to get some good results from running the program Jernej Ø  Testing Ø  Get use to the program to see if anything could be changes to give the user a better experience Allen Ø  Start to work on possible ways to store and load knots for the program Phil & Jun Ø  Both discussing possible ways to incorporate what we have into winform and add the possible four different view ports
Summary	Overall today was a catch up to make sure everyone is one the right page and motivated to finish this project and finish it strongly. Hopefully we can continue to work hard on what we have achieved so far and as a group we can strive to do our best. There still is a lot of work that needs to be done but once we meet with Luke on Thursday and listen to some ideas and advice he has to give we will make appropriate decisions and move on from there.