project created

.gitignore

-.idea
\ No newline at end of file
+.idea
+.out
+sae2.01-developpement-application.iml
\ No newline at end of file

README.md

-# SAE2.01 - Developpement application
+# saeshukan
 
+SAe project about Shukan planner for BUT INFO students
 
+A documentation of Shukan and Shukan scripts (shukan.html) is available in doc directory.
 
-## Getting started
-
-To make it easy for you to get started with GitLab, here's a list of recommended next steps.
-
-Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
-
-## Add your files
-
-- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
-- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
-
-```
-cd existing_repo
-git remote add origin https://gitlab.univ-lorraine.fr/piquerez/sae2.01-developpement-application.git
-git branch -M main
-git push -uf origin main
-```
-
-## Integrate with your tools
-
-- [ ] [Set up project integrations](https://gitlab.univ-lorraine.fr/piquerez/sae2.01-developpement-application/-/settings/integrations)
-
-## Collaborate with your team
-
-- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
-- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
-- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
-- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
-- [ ] [Automatically merge when pipeline succeeds](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
-
-## Test and Deploy
-
-Use the built-in continuous integration in GitLab.
-
-- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
-- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing(SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
-- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
-- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
-- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
-
-***
-
-# Editing this README
-
-When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thank you to [makeareadme.com](https://www.makeareadme.com/) for this template.
-
-## Suggestions for a good README
-Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
-
-## Name
-Choose a self-explaining name for your project.
-
-## Description
-Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
-
-## Badges
-On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
-
-## Visuals
-Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
-
-## Installation
-Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
-
-## Usage
-Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
-
-## Support
-Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
-
-## Roadmap
-If you have ideas for releases in the future, it is a good idea to list them in the README.
-
-## Contributing
-State if you are open to contributions and what your requirements are for accepting them.
-
-For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
-
-You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
-
-## Authors and acknowledgment
-Show your appreciation to those who have contributed to the project.
-
-## License
-For open source projects, say how it is licensed.
-
-## Project status
-If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
+A documentation of Shukan architecture (archiShukan.pdf) is also available in doc directory.

saeshukan-main/README.md

-# saeshukan
-
-SAe project about Shukan planner for BUT INFO students
-
-A documentation of Shukan and Shukan scripts (shukan.html) is available in doc directory.
-
-A documentation of Shukan architecture (archiShukan.pdf) is also available in doc directory.

saeshukan-main/data/2122_S1/V001_210626/S1/ANG1.txt

-TD
-TP2
-TD
-TP2
-TD
-TP2
-TD
-TP2
-TD
-TP2
-TD
-TP2
-TD
-SP
-TD
-Params
-Subtitle AC
-AffectTD 2 ACas ACas
-AffectTP 4 ACas ACas ACas ACas
-Sched 37 38 39 40 41 42 45 46 47 48 49 50 1 2 3

saeshukan-main/data/2122_S1/V001_210626/S1/ARC1.txt

-CM
-CM
-TD
-TD
-TD
-TD
-TP4
-TP4
-SD
-SD
-Params
-Subtitle SD
-AffectCM SDie
-AffectTD 2 SDie SDie
-AffectTP 4 SDie SDie SDie SDie
-Sched 35 36 36 36 36 36 37 38 38 45

saeshukan-main/data/2122_S1/V001_210626/S1/BDD1.txt

-CM
-CM
-TD
-TD
-TD
-TD
-TD
-TD
-TD
-TD
-TP4
-TP4
-TP4
-TP4
-TP4
-TP4
-SD
-SP
-EV2
-Params
-Subtitle SD
-AffectCM SDie
-AffectTD 2 DFin SDie
-AffectTP 4 DFin SDie SDie DFin
-Sched 39 39 40 40 41 41 42 42 44 44 45 46 47 48 49 50 1 2 3

saeshukan-main/data/2122_S1/V001_210626/S1/DEV1.txt

-CM
-CM
-CM
-TD
-TD
-TD
-TD
-TP4
-TP4
-TD
-TD
-TP4
-TP4
-TD
-TD
-TP4
-EV1
-TP4
-TP4
-TP4
-TP4
-EV1
-TP2
-CM
-CM
-TD
-TD
-TP2
-TP2
-CM
-TD
-TD
-TP2
-TD
-TD
-TP2
-TP2
-TD
-TD
-TP2
-TP2
-EV2
-Params
-Subtitle K-B-MD
-AffectCM ABou
-AffectTD 2 ABou ABou
-AffectTP 4 ABou ABou ABou ABou
-AffectSpec 5 2 EKer EKer
-AffectSpec 6 2 EKer EKer
-AffectSpec 7 4 EMic EMic EMic EMic
-AffectSpec 8 4 DJam DJam DJam DJam
-AffectSpec 11 4 DJam DJam DJam DJam
-AffectSpec 12 4 SDie SDie SDie SDie
-AffectSpec 13 2 EKer EKer
-AffectSpec 14 2 EKer EKer
-AffectSpec 15 4 SDie SDie SDie SDie
-AffectSpec 17 4 DJam DJam DJam DJam
-AffectSpec 22 4 EKer EKer EKer EKer
-AffectSpec 23 1 EKer
-AffectSpec 24 1 EKer
-AffectSpec 25 2 EKer EKer
-AffectSpec 26 2 EKer EKer
-AffectSpec 27 4 EKer EKer EKer EKer
-AffectSpec 28 4 EKer EKer EKer EKer
-AffectSpec 29 1 EKer
-AffectSpec 30 2 EKer EKer
-AffectSpec 31 2 EKer EKer
-AffectSpec 35 4 EKer EKer EKer EKer
-AffectSpec 36 4 EKer EKer EKer EKer
-AffectSpec 41 1 EKer
-OnLeft 5
-OnLeft 6
-OnLeft 8
-OnLeft 11
-OnLeft 13
-OnLeft 14
-OnLeft 17
-OnLeft 22
-OnLeft 23
-OnLeft 24
-OnLeft 25
-OnLeft 26
-OnLeft 27
-OnLeft 28
-OnLeft 29
-OnLeft 30
-OnLeft 31
-OnLeft 35
-OnLeft 36
-OnLeft 41
-OnRight 7
-OnRight 12
-OnRight 15
-Sched 37 37 38 38 38 39 39 39 40 41 41 41 42 44 44 44 44 44 45 46 47 47 48 49 49 49 49 49 49 50 50 50 50 1 1 1 1 1 1 2 2 3

saeshukan-main/data/2122_S1/V001_210626/S1/EC1.txt

-TD
-TQ2
-TD
-TQ2
-TD
-TQ2
-TD
-TD
-SP
-SP
-Params
-Subtitle AR
-AffectCM ARic
-AffectTD 2 ARic ARic
-AffectTP 4 ARic ARic ARic ARic
-AffectSpec 8 4 CMag CMag CMag CMag
-AffectSpec 9 4 CMag CMag CMag CMag
-OnRight 8
-OnRight 9
-Sched 37 38 39 40 41 45 46 47 50 1

saeshukan-main/data/2122_S1/V001_210626/S1/EGO1.txt

-CM
-TD
-TD
-TD
-TQ2
-TD
-TQ2
-TD
-TD
-TQ2
-SD
-TD
-TD
-TQ2
-TQ2
-TD
-SD
-EV2
-Params
-Hollyweek 44
-Subtitle BD
-AffectCM BDav
-AffectTD 2 BDav BDav
-AffectTP 4 BDav BDav BDav BDav
-Sched 37 37 39 40 41 42 45 46 46 47 47 48 48 49 50 1 2 3

saeshukan-main/data/2122_S1/V001_210626/S1/EGO2.txt

-CM
-TD
-TD
-TD
-TQ2
-TQ2
-TD
-TD
-TD
-SD
-TD
-EV2
-Params
-Hollyweek 44
-Subtitle BD
-AffectCM BDav
-AffectTD 2 BDav BDav
-AffectTP 4 BDav BDav BDav BDav
-Sched 35 36 36 37 38 39 40 41 45 46 47 48

saeshukan-main/data/2122_S1/V001_210626/S1/M1.txt

-CM
-CM
-TD
-CM
-TD
-TD
-TP2
-TD
-TD
-TP2
-TD
-TD
-TD
-TP2
-TD
-TD
-TD
-TQ2
-TP2
-EV2
-Params
-EndsOn 49
-Subtitle PA
-AffectCM PAde
-AffectTD 2 PAde PAde
-AffectTP 4 PAde PAde PAde PAde
-Sched 35 36 36 36 36 37 37 37 38 38 39 39 40 40 41 42 42 45 46 47

saeshukan-main/data/2122_S1/V001_210626/S1/M2.txt

-CM
-CM
-TD
-TD
-TD
-TD
-TP2
-TQ2
-TQ2
-TQ2
-TP2
-EV2
-Params
-StartsOn 45
-Subtitle PA
-AffectCM PAde
-AffectTD 2 PAde PAde
-AffectTP 4 PAde PAde PAde PAde
-Sched 45 45 46 47 48 48 49 50 1 1 2 3

saeshukan-main/data/2122_S1/V001_210626/S1/PPP1.txt

-TD
-TP2
-SP
-SP
-Params
-AffectTD 2 ARic ARic
-AffectTP 4 ARic ARic ARic ARic
-Sched 40 44 3 3

saeshukan-main/data/2122_S1/V001_210626/S1/SYS1.txt

-TM
-TM
-TP2
-TP2
-TP2
-TP2
-TP2
-TP2
-TP2
-TP2
-TP2
-TP2
-SD
-Params
-Hollyweek 48
-Subtitle AB
-AffectCM ABou
-AffectTD 2 ABou ABou
-AffectTP 4 SDie ABou ABou DJam
-Sched 38 38 39 39 40 40 41 41 42 42 44 44 45

saeshukan-main/data/2122_S1/V001_210626/S1/WEB1.txt

-TM
-TM
-TP2
-TP2
-TP2
-TP2
-SP
-EV1
-TP2
-TP2
-TP2
-SP
-EV1
-Params
-Subtitle PV
-AffectCM PVil
-AffectTD 2 PVil PVil
-AffectTP 4 PVil PVil PVil PVil
-AffectSpec 8 4 BDev BDev BDev BDev
-AffectSpec 9 4 BDev BDev BDev BDev
-AffectSpec 10 4 BDev BDev BDev BDev
-AffectSpec 11 4 BDev BDev BDev BDev
-AffectSpec 12 1 BDev
-OnRight 8
-OnRight 9
-OnRight 10
-OnRight 11
-OnRight 12
-Sched 36 36 37 38 39 40 41 42 46 47 48 49 50

saeshukan-main/data/2122_S1/V001_210626/S1/modules.txt

-DEV1
-WEB1
-ARC1
-SYS1
-BDD1
-M1
-M2
-EGO1
-EGO2
-EC1
-ANG1
-PPP1

saeshukan-main/data/2122_S1/V001_210626/S3/ACD4.txt

-CM
-TD
-CM
-TP4
-CM
-TD
-CM
-TD
-TP4
-CM
-TD
-TP4
-CM
-TM
-TM
-TP4
-TM
-EV2
-Params
-Subtitle x-DB-PG
-AffectCM DBol
-AffectTD 2 DBol DBol
-AffectTP 3 DBol DBol DBol
-AffectSpec 13 2 PGue PGue
-AffectSpec 14 2 PGue PGue
-AffectSpec 16 2 PGue PGue
-OnRight 13
-OnRight 14
-OnRight 16
-Sched 35 36 37 37 38 38 39 39 40 41 41 42 42 44 45 45 46 47

saeshukan-main/data/2122_S1/V001_210626/S3/ACD5.txt

-CM
-TD
-TD
-TQ2
-TD
-TP2
-CM
-TP2
-TD
-TP2
-EV2
-Params
-StartsOn 37
-Hollyweek 44
-Subtitle BD
-AffectCM BDav
-AffectTD 2 BDav BDav
-AffectTP 3 BDav BDav BDav
-Sched 37 37 38 38 39 40 40 41 42 42 45

saeshukan-main/data/2122_S1/V001_210626/S3/ANG3.txt

-TD
-TP2
-TD
-TP2
-TD
-TP2
-TD
-TP2
-TD
-TP2
-TD
-TP2
-TD
-TP2
-TD
-TP2
-TD
-TP2
-TD
-TP2
-TD
-TP2
-TD
-Params
-Subtitle AC
-AffectTD 2 ACas ACas
-AffectTP 3 ACas ACas ACas
-Sched 35 36 36 37 37 38 38 39 39 40 40 41 41 44 45 46 47 48 49 50 1 2 3