From 31c00df89b52f152be290ccc601077912d77e5b3 Mon Sep 17 00:00:00 2001 From: nfoy Date: Mon, 10 Mar 2014 20:33:52 -0400 Subject: Sprint1-Retro: Tournament view task. --- doc/Sprint1-Retrospective.md | 8 ++++++++ 1 file changed, 8 insertions(+) (limited to 'doc') diff --git a/doc/Sprint1-Retrospective.md b/doc/Sprint1-Retrospective.md index 3da3669..f299d58 100644 --- a/doc/Sprint1-Retrospective.md +++ b/doc/Sprint1-Retrospective.md @@ -108,11 +108,19 @@ f ## Tournament view {#tourney-view} +The tournament view lists the tournaments on one page as a table of rows. Each +row lists sample tournament information (game name, players per team, etc) +along with buttons for different tasks, such as joining or viewing a tourny. +You can also create a new tournament here. The functionality we want is +here. + ## Homepage {#homepage} + # Implemented but not working well ## Match score models {#match-score} + This only functioned properly for noting which team would win a match. We want more information to be included, such as individual player scores. We also only had it working where the tournament host would decide who won. -- cgit v1.2.3 From 1f00553cbc5d281efe3ac1b434d16537a17bc969 Mon Sep 17 00:00:00 2001 From: webb39 Date: Mon, 10 Mar 2014 20:36:31 -0400 Subject: added match controller information --- doc/Sprint1-Retrospective.md | 15 +++++++++++++-- 1 file changed, 13 insertions(+), 2 deletions(-) (limited to 'doc') diff --git a/doc/Sprint1-Retrospective.md b/doc/Sprint1-Retrospective.md index 3da3669..ae1b07a 100644 --- a/doc/Sprint1-Retrospective.md +++ b/doc/Sprint1-Retrospective.md @@ -97,13 +97,24 @@ f f ## Login (UI) {#login-ui} - + ## Tournament settings {#tourney-settings} - + ## Tournament registration {#tourney-registration} ## Match controller {#match-controller} +The Match Controller creates the separate matches for a specific tournament. +When a tournament is started, it begins with an initial match that contains +no players. Currently, a player must join a match by entering the specific +tournament (by clicking the 'show' button on the tournament), +then they must enter the match (again by clicking the 'show' button but this +time on the match they desire to participate in) and then finally clicking +the 'join' button. This updates the match with the user as a participant in +the matc and then finally clicking the 'join' button. This updates the match +with the user as a participant in the match. A match can also be destroyed +by clicking the 'delete' button on the no longer desired match on the page. + ## Permissions system {#permissions} ## Tournament view {#tourney-view} -- cgit v1.2.3 From 6282225c0b3335e0a3c57a62973d3e8aa14f0909 Mon Sep 17 00:00:00 2001 From: guntasgrewal Date: Mon, 10 Mar 2014 20:50:07 -0400 Subject: Homepage and Tournament --- doc/Sprint1-Retrospective.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) (limited to 'doc') diff --git a/doc/Sprint1-Retrospective.md b/doc/Sprint1-Retrospective.md index 3da3669..2297051 100644 --- a/doc/Sprint1-Retrospective.md +++ b/doc/Sprint1-Retrospective.md @@ -107,8 +107,23 @@ f ## Permissions system {#permissions} ## Tournament view {#tourney-view} +The view page for tournaments contains a table that lists all on going +tournaments for all types of games. It also lists other game attribute like +Players per team, Teams per match, whether or not teams were randomized +and also has links to Show, Edit, Destroy, Join a particular tournament. +A link to create a tournament is also provided. Each of the links correspond +to view pages which are html.erb pages that provide styles and functionality +of each of the tournament setting features. Show, Edit, Destroy, all have +views of their own to perform each of the above actions. ## Homepage {#homepage} +The homepage is mainly controlled by the views that are associated with each +model and controller. The main view for the homepage is the one found in the +layouts called application.html.erb, this view is responsible for display of +all the headings, navigation bars, forms and containers. This view page +contains mostly links to other view pages and yields whatever the other view +pages have to offer. The Homepage redirects to Login, Signup, See Ongoing +Tournaments and shows the view for those models. # Implemented but not working well -- cgit v1.2.3 From f9af1121aa8b56967ad7d25ae41261ec263b5d22 Mon Sep 17 00:00:00 2001 From: AndrewMurrell Date: Mon, 10 Mar 2014 20:50:51 -0400 Subject: Finished those 2 other areas. --- doc/Sprint1-Retrospective.md | 19 ++++++++++++------- 1 file changed, 12 insertions(+), 7 deletions(-) (limited to 'doc') diff --git a/doc/Sprint1-Retrospective.md b/doc/Sprint1-Retrospective.md index c568917..eb5403e 100644 --- a/doc/Sprint1-Retrospective.md +++ b/doc/Sprint1-Retrospective.md @@ -94,7 +94,7 @@ has been an impressive journey. The entire team became familiar with deploying Rails in our rather diverse working environments and successfully deployed a server -instance located at demo.projectleaguer.net. +instance located at demo.projectleaguer.net as well as on our local boxes. ## Login (back-end) {#login-backend} @@ -110,8 +110,18 @@ place, this has been fixed). ## Tournament settings {#tourney-settings} +Tournament settings were implemented at a basic level, instituting those +items which are similar to all tournaments, regardless of type, orginating +from the game model. + ## Tournament registration {#tourney-registration} +Tournament registration and the tournament contoller were completed which +allowed users to join and participate in basic tournaments of several types. +The tournament controller handled a variety of tournament related tasks, +including creating and updating tournaments and validating tournament related +operations. + ## Match controller {#match-controller} ## Permissions system {#permissions} @@ -129,12 +139,7 @@ only had it working where the tournament host would decide who won. ## Server management {#srv-man} -The server management software interface is implemented, and working -fine. The other modules use it. However, what we didn't implement is -an actual *page* to edit these settings. We had this task in the -iteration because other items depended on it. Though we did not -implement the full story, we implemented the core reason that we -wanted it. + # Not implemented -- cgit v1.2.3