--Originally published at Ce qui est chouette

This past week we worked on new levels, progressing through them, storing them locally and fixing some bugs. On Tuesday we had a small review with our professor, Ken, to see how we were going; both parties ended up agreeing we were doing fine, but should delegate a bit more of the responsibilities that pertain to the project.

Onto the deliverables

We generalized text elements to be included in the JSON representation of the map, to not include hardcoded text server-side. We fixed some problem we had with flags messing up the end-of-level and kept the player from progressing to the next level. Now we store the JSONed level in a global variable to reload the level browser-side whenever the player fails to complete the level and falls victim to a cruel trap put there by us, yes, us, the developers who inherently despise them. But hey, the server receives less requests now

– A reviewed dude.

--Originally published at Ce qui est chouette

This week we’ll be developing the web application’s integration with a database. What the database will contain is the design of the levels as a JSON—by storing the coordinates of each element by groups—and the leaderboard of scores associated to a named user—maybe with an arcade style 4-letter select-screen. Because inside It’s not raining we’re dealing directly with JSONs, our database will have the same format.

mLab

As of now we’re thinking of using MongoDB as our database, and we found mLab to be our best option for hosting a MongoDB instance, as it is hosted as-a-service and it has a pretty juicy free-tier offer.

And some more stuff . . .

There are some bugs that need fixing and in-game progress that needs to be reflected by advancing to another level after reaching the goal (yep, this still isn’t done, but it wasn’t really part of the core of the game).

– module.exports = { author: Arturo Fornés };

--Originally published at Ce qui est chouette

This past week was our first delivery, we reached the first milestone of the project, and with it, the first sprint came to an end. This milestone consisted of having a playable demo of the game, with basic physics, an enemy, a goal, structures—walls, floor— and a level loader. Most of these are self explanatory, except, maybe, for the level loader. The focus of this was to receive a JSON object specifying the location of the structures, the enemies, the goal and the player for a level loader method to receive and upon which build the level.

In regards to management, we’re getting used to using the issue tab in our Github repository to keep track of who’s doing what, and are trying to chip in the comments for suggestions and clarification. In the Gitflow front, we’ve secured the branch master so that it has the latest fully playable version of the project and no one can mess with it without having their mess approved by another member of the team.

Contrary to popular belief, we are not planning a mutiny, Gerardo.

– A scallywag.

--Originally published at Ce qui est chouette

This week flew by fast, and so did progress of the project. This week on code, I left the basic game movements ready, movement, jumping and gravity, collisions, and the hardest, wall jumps; now all that’s left is some enemies, level design and testing the API. This can be found in our public Github repository, in which we’re using the good’l Gitflow Workflow—at least I’m trying to get the team on board with the basic feature/develop/master. I’m also attempting to get them to write out descriptive commits, with a title and description, so that in case of a metaphorical fire, we’ve got a metaphorical little fire fighter.

There’s a live demo—and here’s where we’ll be hosting the game unless we need some processing power—hosted using Heroku. Now that I’m on the topic of platforms, let’s get into frameworks, I tested p5.js with p5.play; played—hehe—around with the physics, and we decided we’d be sticking with for the long run. For testing purposes I suggested Chai, but Miguel later discovered a more complete ensemble for testing in Javascript including Chai, Mocha, Nook.

The game’s name hasn’t changed, It’s not raining, and I haven’t got an umbrella, because I don’t need it, as it’s not raining. So I guess I’m fine.

– The guy who hasn’t the need for an umbrella.

--Originally published at Hermes's Blog

This week I worked in setting up the api server. As today (january 20) we have the server up and running with signup and login methods, hashing the passwords. We have mocha tests passing. We wrote the code first and then I started searching for the test framework, but from now on we will start doing test driven development. We will define all the routes we want, what they should they do and how do we expect them to behave (errors, validations, status codes, etc.).

This is the repo for the backend: https://github.com/Web-Moviles-Spring18/Web. I will change the main branch from master to develop (a new one) and tell my team to start using gitflow (maybe I’ll have to tell them to learn it first, I’ll give ’em this tutorial: https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow).

We still don’t have anything for the Android app, but I really, really want to experience using kotlin.

--Originally published at Ce qui est chouette

const assert = require(‘assert’);

Wow wow wow it’s here. First week. We have some things to do in this space of time. Let’s get to it. On the menu, as an aperitive I’ll be looking at frameworks for browser-based game development that hopefully include sprite rendering and a bit of physics, for the main dish, a smoked unit testing module for NodeJS with garlic.

As of now, I’m thinking of the following technologies and will be trying them out—will post more about that at the end of the week.

p5.js

p5.js is a Javascript library that aims at making drawing code accessible, with a wide range of functionality in the software sketchbook variety. I’m interested in p5 because of some additional libraries its community provides, mainly p5.play which, SURPRISE SURPRISE, has 2D Sprite management and 2D Physics. I’ll be making a very simple movement demo by the end of the week with some squares.

Unit Testing in NodeJS

I don’t really have any candidate for this aspect . . . by the end of the week I aim at having one. Looking for some mock HTTP Requests and Unit testing for the p5.play library, mock some collisions for the 2D Physics, this last one I could develop from scratch with a simple assert—I think NodeJS had an Assert method.

Anyway . . .

That’s what this week will be all about, catch you later.

– assert.equal( theAboutGuy( ), me( ) ) .