Good opportunity to learn and explore.

Given these parameters: length, width, height, and maybe category generate a building. Instead of manually coding the building structure, use an algorithm to generate the structure.

This is an excellent opportunity to use browserify for a fairly large project. It's a setup for testing code using mocha.

These methods are relatively simple and provide a lot of convenience for the interface.

• isFilled()
• isEmpty()
• clear()

This will be a fun algorithm. The road should be be dynamic and curve based on its neighbors. Think about how sim city roads work when you lay them down. You do a search on its neighbors.

For the renderer, I will use a Three.js CDN and the playground.js library.

Remove the properties layer and position from CityCell. Thus far, I don't really see a usecase for them. Close this issue a need for them pops up in the future.

Create a road outline around the perimeter of the map. Then render it.

perimeter -> (layer, startPosition, endPosition)

By default replace=false

If true, replace will override the existing cell content with a street.

So far I have two layers, the street layer and the building layer. There should be a built-in layer called the merged layer.

Related to #25. Right now, I'm using a series of if/else statements. Refactor with a more elegant solution.

The content module should be elements that go inside cells.

This module defines the core TyrianCity logic and city generation algorithm. I'm going to keep this backend completely modular from the frontend and rendering process. That means Playground will be used in the renderer module.

Citygen: An Interactive System for Procedural City Generation
http://www.citygen.net/files/citygen_gdtw07.pdf

Procedural Modeling of Cities
https://graphics.ethz.ch/Downloads/Publications/Papers/2001/p_Par01.pdf

Part of the subversion city demo uses a path searching algorithm to generate roads between city centers.

The gulp task runner should support:

• ES6 compilation
• Standard pipeline

Investigate whether the closure compiler might be useful.

Since the 3D renderer module will be completely separated from the data abstraction, you can create a minimap as the 2D renderer. It will be fun.

The goal is to use mocha with babel.

Continuation of #32.
Create a watch for the stylesheets, js lib and source files. Use gulp-watch to handle errors.

At the moment, I'm keeping Layer fairly simple. These are some properties that I might want to add.

• z index
• opacity
• visibile

Given a center position (x, y) and a radius generate a circular road.

Write tests using pubtest to make sure everything works properly before passing the module into the rendering engine.

This grid should contain a n x m matrix of null values.

Units in the core module does not make a ton of sense. There's no real gain by including units here, so remove it and move it into the future Renderer module.

Create a package.json. The goal is to move front-end tests to the backend.

Here's what I brainstormed:

• Unit: used for easy scaling.
• Cell: used for groundwork.
• Layer: 2D array of cells.
• Zone: Abstract class for zoning such as streets or buildings.

Use a CDN to load three.js. Use playground.js for the underlying framework.

The interface for CityMap should encapsulate CityLayer. That way a programmer only needs to work with the CityMap. Create an object property on CityMap called layers. The keys will be the layer name and the value will be the layer.

Write tests for these simple methods as well.

Ideally each city object should be N cell units. Create a class representation of this unit.

This project has been on hiatus for the past two weeks. Please find more time to work on this project.

Here are some suggestions:

Avoid using the computer while eating. I usually end up watching like 2-3 episodes of whatever and feel like napping afterwards. If I can finish eating in 10 minutes by being away from a computer, I could potentially gain 5-10 hours every week.

Uberman programming. Try to sleep at 10PM and wake up at 2AM (4 hours). Then program for a few hours and go back to sleep, say around 5PM. You get double the amount of new neural connections made from biphasic sleep. Plus it's uninterrupted time during peak programming efficiency.

I'm currently working on the street generator and street direction is something that popped up. For this instance of the street generator, I'm going to ignore street direction. Nonetheless, I'm keeping this issue open for the future.

Streets should be generated in the x1, y1, x2, y2 positions that were defined.

Proposal:
Add an optional parameter for road thickness. By default it is 1.

Test the simple things.

Land is split between infrastructure and zone. Zones determine the type of land that occupies a cell.

These are the zones that should be available.

• commercial
• residential
• industrial

These are the infrastructure.

• park
• street

Create the following classes

CityZone
  - type
  - cell

Create a straight path.

straight -> (x1, y1, x2, y2)

Fills the layer with all street zones. Find a way to make to make this work regardless of direction. That means x1 can be greater or less than x2.