- The code must respect the [**good practices**](https://((DOMAIN))/root/public/src/branch/master/subjects/good-practices/README.md).
- The code must respect the [**good practices**](../good-practices/README.md).
- It is recommended that the code present a **test file**.
- Some [**banner**](https://((DOMAIN))/root/public/src/branch/master/subjects/ascii-art/README.md) files (.txt files) with a specific graphical template representation using ASCII will be given. The files are formatted in a way that is not necessary to change them.
- Some **banner** files with a specific graphical template representation using ASCII will be given. The files are formatted in a way that is not necessary to change them.
You must follow the same [instructions](https://((DOMAIN))/root/public/src/branch/master/subjects/ascii-art) as in the first subject but this time with colors.
You must follow the same [instructions](../README.md) as in the first subject but this time with colors.
The output should manipulate colors using the **flag**`--color=<color>`, in which `--color` is the flag and `<color>` is the color desired by the user. These colors can be achieved using different notations (color code systems, like `RGB`, `hsl`, `ANSI`...), it is up to you to choose which one you want to use.
@ -12,7 +12,7 @@ The output should manipulate colors using the **flag** `--color=<color>`, in whi
### Instructions
- Your project must be written in **Go**.
- The code must respect the [**good practices**](https://((DOMAIN))/root/public/src/branch/master/subjects/good-practices/README.md).
- The code must respect the [**good practices**](../../good-practices/README.md).
- It is recommended that the code should present a **test file**.
You must follow the same [instructions](https://((DOMAIN))/root/public/src/branch/master/subjects/ascii-art) as in the first subject but the second argument must be the name of the template. I know some templates may be hard to read, just do not obsess about it. Please...
You must follow the same [instructions](../README.md) as in the first subject but the second argument must be the name of the template. I know some templates may be hard to read, just do not obsess about it. Please...
### Instructions
- Your project must be written in **Go**.
- The code must respect the [**good practices**](https://((DOMAIN))/root/public/src/branch/master/subjects/good-practices/README.md).
- The code must respect the [**good practices**](../../good-practices/README.md).
- It is recommended that the code should present a **test file**.
- You can see all about the **banners** [here](https://((DOMAIN))/root/public/src/branch/master/subjects/ascii-art).
- You can see all about the **banners** [here](../).
You must follow the same [instructions](https://((DOMAIN))/root/public/src/branch/master/subjects/ascii-art) as in the first subject but the alignment can be changed.
You must follow the same [instructions](../README.md) as in the first subject but the alignment can be changed.
```console
We
@ -22,7 +22,7 @@ To change the alignment of the output it must be possible to use a **flag** `--a
### Instructions
- Your project must be written in **Go**.
- The code must respect the [**good practices**](https://((DOMAIN))/root/public/src/branch/master/subjects/good-practices/README.md).
- The code must respect the [**good practices**](../../good-practices/README.md).
- It is recommended that the code should present a **test file**.
- You must follow the same [instructions](https://((DOMAIN))/root/public/src/branch/master/subjects/ascii-art) as in the first subject **while** writing the result into a file. Yep, you will read from one file and write to another.
- You must follow the same [instructions](../README.md) as in the first subject **while** writing the result into a file. Yep, you will read from one file and write to another.
The file must be named by using the flag `--output=<fileName.txt>`, in which `--output` is the flag and `<fileName.txt>` is the file name which will contain the output.
### Instructions
- Your project must be written in **Go**.
- The code must respect the [**good practices**](https://((DOMAIN))/root/public/src/branch/master/subjects/good-practices/README.md).
- The code must respect the [**good practices**](../../good-practices/README.md).
- It is recommended that the code presents a **test file**.
You must follow the same [instructions](https://((DOMAIN))/root/public/src/branch/master/subjects/ascii-art) as in the first subject but this time the process will be reversed. desrever fo dnik siht toN.
You must follow the same [instructions](../README.md) as in the first subject but this time the process will be reversed. desrever fo dnik siht toN.
Ascii-reverse consists on reversing the process, converting the graphic representation into a text. You will have to create a text file containing a graphic representation of a random `string` given as an argument.
@ -11,7 +11,7 @@ The argument will be a **flag**, `--reverse=<fileName>`, in which `--reverse` is
### Instructions
- Your project must be written in **Go**.
- The code must respect the [**good practices**](https://((DOMAIN))/root/public/src/branch/master/subjects/good-practices/README.md).
- The code must respect the [**good practices**](../../good-practices/README.md).
- It is recommended that the code should present a **test file**.
###### Has the requirement for the allowed packages been respected? (Reminder for this project: (only [standard packages](https://golang.org/pkg/)
##### Try passing to the reverse flag `"--reverse=example00.txt"` the [example 00](https://((DOMAIN))/root/public/src/branch/master/subjects/ascii-art/reverse/example.md).
##### Try passing to the reverse flag `"--reverse=example00.txt"` the [example 00](example.md).
`Hello World`
###### Does it display the value above?
##### Try passing to the reverse flag `"--reverse=example01.txt"` the [example 01](https://((DOMAIN))/root/public/src/branch/master/subjects/ascii-art/reverse/example.md).
##### Try passing to the reverse flag `"--reverse=example01.txt"` the [example 01](example.md).
`123`
###### Does it display the value above?
##### Try passing to the reverse flag `"--reverse=example02.txt"` the [example 02](https://((DOMAIN))/root/public/src/branch/master/subjects/ascii-art/reverse/example.md).
##### Try passing to the reverse flag `"--reverse=example02.txt"` the [example 02](example.md).
`#=\[`
###### Does it display the value above?
##### Try passing to the reverse flag `"--reverse=example03.txt"` the [example 03](https://((DOMAIN))/root/public/src/branch/master/subjects/ascii-art/reverse/example.md).
##### Try passing to the reverse flag `"--reverse=example03.txt"` the [example 03](example.md).
`(somthing&234)`
###### Does it display the value above?
##### Try passing to the reverse flag `"--reverse=example04.txt"` the [example 04](https://((DOMAIN))/root/public/src/branch/master/subjects/ascii-art/reverse/example.md).
##### Try passing to the reverse flag `"--reverse=example04.txt"` the [example 04](example.md).
`abcdefghijklmnopqrstuvwxyz`
###### Does it display the value above?
##### Try passing to the reverse flag `"--reverse=example05.txt"` the [example 05](https://((DOMAIN))/root/public/src/branch/master/subjects/ascii-art/reverse/example.md).
##### Try passing to the reverse flag `"--reverse=example05.txt"` the [example 05](example.md).
`\!" #$%&'()*+,-./`
###### Does it display the value above?
##### Try passing to the reverse flag `"--reverse=example06.txt"` the [example 06](https://((DOMAIN))/root/public/src/branch/master/subjects/ascii-art/reverse/example.md).
##### Try passing to the reverse flag `"--reverse=example06.txt"` the [example 06](example.md).
`:;<=>?@`
###### Does it display the value above?
##### Try passing to the reverse flag `"--reverse=example07.txt"` the [example 07](https://((DOMAIN))/root/public/src/branch/master/subjects/ascii-art/reverse/example.md).
##### Try passing to the reverse flag `"--reverse=example07.txt"` the [example 07](example.md).
`ABCDEFGHIJKLMNOPQRSTUVWXYZ`
@ -72,7 +72,7 @@
###### +Does the project runs quickly and effectively? (Favoring recursive, no unnecessary data requests, etc)
###### +Does the code obey the [good practices](https://((DOMAIN))/root/public/src/branch/master/subjects/good-practices/README.md)?
###### +Does the code obey the [good practices](../../good-practices/README.md)?
###### Are the commands and the ants movements printed with the right format? One line per turn, `N` movements per turn, movements defined by `Lx-y``x` being the ant and `y` being the room, as it shows above?
##### Try running the program with [example00](https://((DOMAIN))/root/public/src/branch/master/subjects/lem-in/examples/README.md).
##### Try running the program with [example00](../examples/README.md).
```
$ go run . example00.txt
@ -50,7 +50,7 @@ $
###### Does it present the quickest path possible with the same number of turns as the result above?
##### Try running the program with [example01](https://((DOMAIN))/root/public/src/branch/master/subjects/lem-in/examples/README.md).
##### Try running the program with [example01](../examples/README.md).
```
$ go run . example01.txt
@ -102,7 +102,7 @@ $
###### Does it present the quickest path possible with the same number of turns as the result above?
##### Try running the program with [example02](https://((DOMAIN))/root/public/src/branch/master/subjects/lem-in/examples/README.md).
##### Try running the program with [example02](../examples/README.md).
```
$ go run . example02.txt
@ -124,7 +124,7 @@ $
###### Does it present the quickest path possible with the same number of turns as the result above?
##### Try running the program with [example03](https://((DOMAIN))/root/public/src/branch/master/subjects/lem-in/examples/README.md).
##### Try running the program with [example03](../examples/README.md).
```
$ go run . example03.txt
@ -156,7 +156,7 @@ $
###### Does it present the quickest path possible with the same number of turns as the result above?
##### Try running the program with [example04](https://((DOMAIN))/root/public/src/branch/master/subjects/lem-in/examples/README.md).
##### Try running the program with [example04](../examples/README.md).
```
$ go run . example04.txt
@ -189,7 +189,7 @@ $
###### Does it present the quickest path possible with the same number of turns as the result above?
##### Try running the program with [example05](https://((DOMAIN))/root/public/src/branch/master/subjects/lem-in/examples/README.md).
##### Try running the program with [example05](../examples/README.md).
```
$ go run . example05.txt
@ -273,7 +273,7 @@ $
###### Does it present the quickest path possible with the same number of turns as the result above?
##### Try running the program with [badexample00](https://((DOMAIN))/root/public/src/branch/master/subjects/lem-in/examples/README.md).
##### Try running the program with [badexample00](../examples/README.md).
```
$ go run . badexample00.txt
@ -283,7 +283,7 @@ $
###### Does it present the right result as above?
##### Try running the program with [badexample01](https://((DOMAIN))/root/public/src/branch/master/subjects/lem-in/examples/README.md).
##### Try running the program with [badexample01](../examples/README.md).
```
$ go run . badexample01.txt
@ -293,11 +293,11 @@ $
###### Does it present at least the result above?
##### Try running the program with [example06](https://((DOMAIN))/root/public/src/branch/master/subjects/lem-in/examples/README.md) and with 100 ants.
##### Try running the program with [example06](../examples/README.md) and with 100 ants.
###### Is the real time less than 1.5 minutes?
##### Try running the program with [example07](https://((DOMAIN))/root/public/src/branch/master/subjects/lem-in/examples/README.md) and with 1000 ants.
##### Try running the program with [example07](../examples/README.md) and with 1000 ants.
###### Is the real time less than 2.5 minutes?
@ -337,7 +337,7 @@ $
###### +Are the tests checking each possible case?
###### +Does the code obey the [good practices](https://((DOMAIN))/root/public/src/branch/master/subjects/good-practices/README.md)?
###### +Does the code obey the [good practices](../../good-practices/README.md)?
Christopher Fremond