lsileoni / cub3d Goto Github PK

Immediate norming is required for rendering and possibly other stuff.

What needs to be done

Need to integrate the mlx library into the project in order to interact with the X server and render a framebuffer.

How

A good start would be to render a flat color on an image, that was created with mlx.

Libft is in a bad state, get next line is not up to date and there's no trusty hashtable implementation in sight.

There's a lack of error handling for many things and in general the whole project needs a deep look.

There should be a basic workflow for the project, which makes the project and checks whether it succeeded or not. Just as an additional check to see if there's anything wrong with the project.

What needs to be done

There is a need to write a map parser for the program. It takes in a file, which is a stream of bytes and you have to parse out the path to the textures, floor and ceiling RGB colors and the map data itself.

Example map

NO ./path_to_the_north_texture
SO ./path_to_the_south_texture
WE ./path_to_the_west_texture
EA ./path_to_the_east_texture

F 220,100,0 (Floor RGB color)
C 225,30,0 (Ceiling RGB color)

        1111111111111111111111111
        1000000000110000000000001
        1011000001110000000000001
        1001000000000000000000001
111111111011000001110000000000001
100000000011000001110111111111111
11110111111111011100000010001
11110111111111011101010010001
11000000110101011100000010001
10000000000000001100000010001
10000000000000001101010010001
11000001110101011111011110N0111
11110111 1110101 101111010001
11111111 1111111 111111111111

Conditions the map must fulfill

• The map must be closed/surrounded by walls, if not the program must return an error.
• Except for the map content, each type of element can be separated by one or more empty line(s).
• Except for the map content which always has to be the last, each type of element can be set in any order in the file.
• Except for the map, each type of information from an element can be separated by one or more space(s).
• The map must be parsed as it looks in the file. Spaces are a valid part of the map and are up to you to handle. You must be able to parse any kind of map, as long as it respects the rules of the map.