Week 5 (1): Break a leg.

--Originally published at tc3045 – Ce qui est chouette

This week’s end marked, as well, the ending of the second sprint of It’s not raining. As of now, our game has two levels, and a leaderboard. The main focus of this sprint was having a GUI, and more organized coding. We achieved both with the help of one of p5‘s recomended libraries called p5.SceneManager developed by Marian Veteanu.

factory theatre - kaykaybarrie
Factory Theatre by Kayla Jane Barrie on Flickr under a CC License.

The aim of this library is to modularize p5‘s sketch into multiple sketches called scenes, this is done in order to have a more organized structure for a p5 sketch, this helps a lot in game development. Before, we abstracted levels into JSONs to deal with multiple levels, but what if we wanted to just show the score, or have a menu, we would have had to forgo all gameplay aspects of our abstracted code to stop the time from ticking, and reset the setup of our sketch to show a whole nother screen. That’s the main issue scenes tackle, different screens that can’t be abstracted into the same blob, scenes proud themselves in being able to abstract these.

Using this library we were able to easily develop a leaderboard and a menu. Now, we’re just hoping Gerardo gets us pizza for behaving and not starting a mutiny. Yet.

– Another scallywag.

Week 5: Second milestone

--Originally published at TC3045 – "Site Title"

This week is the end of the first partial and with it came the second progress presentation in class. The presentation itself went smoothly. Everything worked as expected and no known bugs were present on the build that was showed.

The progress for the week was all that was expected, except for some errors present on this week’s plans. The previous blog entry lists a projectile and it’s interactions as work for this week, but it was really scheduled for next milestone. All other work expected for the week was successfully completed.

As of right now, I think the project is progressing constantly and has a bright future ahead. So far we haven’t found major roadblocks, so the biggest concern would be what to do in case we find one.

Week 6: Post mortem

--Originally published at TC3045 – Sagnelli's blog

This week we were able to read emojis in tweets, and separate user name from the tweet itself. By doing this, we avoid analyzing user names, and actually analyze the tweet itself. By reading emojis we can have a more accurate idea on what the person’s intention is. We can implement analysis in the text comparison to the emoji meaning. Henceforth, this week we could say that the preparations for the mining phase is over. We are now able to mine data of certain important people, of certain words, and to gather the complete data of these tweets.

For the upcoming partial, we are going to start mining data, and doing preparations for the analysis of this data. Moreover, we are going to eliminate stop words, and focus on what the tweet is actually trying to communicate. Henceforth, we are going to show a map of which words are most used, and who is actually winning this electoral campaign.

Postmortem week 6 – Slow slow week, onwards and upwards

--Originally published at TC3045 – Alejandro Güereca and College

Since I was out of town I sadly couldn’t get to work in the project as much as I wanted too but I had already taken that into account when the semester started. I did make the docker file so that the others could implement the web client with the other stuff that they have been working on. It was a slow week for me but I plan on putting more work into it starting monday.

Integrate first, develop later.

--Originally published at A project being made

So, we have had our second sprint review, and what we learned from this week is the importance of plan the framework of what are we are going to modify for future develop.

Each of us work on our respective functionalities, but it was difficult to merge the project so it could work in one single piece. Specifically on trying to merge the html templates to the angular app.

Solution?
Angular Components. Components are the main way we build and specify elements and logic on the page, through both custom elements and attributes that add functionality to our existing components.

Naturally this will be the main objective for next week, and to try to have all the structure of the front-end together.

End of Week 5: end of 2nd sprint

--Originally published at TC3045 – Quality and Software Testing

This is the end of week five and the end of the second sprint. Everything went really good because we finished everything we had planned for this week. Arturo and I added another library of p5 to manage scenes to make easier the implementation of different “views” of the videogame, such as a main menu, a leaderboard, etc. With that, I was able to implement with ease the main menu.

37014330542_ed06e5cccf_z
“Dark clouds & Sun rays.” flickr photo by Hefin Owen shared under a Creative Commons (BY) license

The clouds are getting darker, that is because the project is starting to take form, I cannot wait to enjoy the game but not as a developer but as a user.

Lo que hice en la semana 5

--Originally published at Andres Blog

Para esta semana seguimos investigando para poder hacer los test y en paralelo estuvimos pensando que tests hacer y los implementamos aunque nada mas alcanzamos a implementar dos porque solo teníamos una computadora en la que podíamos trabajar por problemas administrativos pero en parte estuvo bien ya que todo el equipo aprendió como implementar los tests en el proyecto.

 

Planning Week 5

--Originally published at A project being made

Week 5 (Febraury 13 – 18) is already starting, and the project seems to be going slower than we would like to. We hadnt used the trello table for a while, but our goal for this week is very clear: to have something to present this friday.

What are we going to present on friday?

Hopefully, a fully integrated empty project on Angular. Also the proper design of the home page and a fuctional login and register in firebase.