yum3lo / oop_labs

Lab2 for OOP course TUM

oop_labs

Lab2 for OOP course TUM

Laboratory 2

Task

Create an object-oriented program that monitors and detects changes in documents within a designated folder.

In this laboratory, the task is to develop a simplified version of git functionality that detects changes within a specific folder. Here’s an example of an expected output of the program:

Created Snapshot ar: 2023-10-10T10:10:10.000000
test.txt - No Change
image.png - Changed
pyhton_script.py - Changed

As one can notice each file has a different extension .txt, .png and .py. The user is informed of the files changed status since the last snapshot time. From this output one can gather:

test.txt has experienced no change since the snapshot time of 2023-10-11, 09:01:28, while image.png and python_script.py did change since the snapshot.

Laboratory restrictions

1. No third party libraries are allowed, you can use only the ones available in your programming language.
2. You are free to create as many classes as you need to achieve a well structured working system.
3. Limitation of concepts: You are required to structure you’re program using the concepts of Inheritance and Polymorphism (Runtime and Compile time Polymorphism is a must)
4. USING GIT: You have to commit each significant change in your program. Failing doing so results in a 2 point deduction, plus writing a 2 page report on "Git usefulness". If there’s no report provided, laboratory isn’t accepted.

Base Laboratory (8 Grade)

Build a program loop, an interactive command line for the user to monitor changes in a folder. The folder location is hardcoded, meaning it’s constant, and up to the implementer to specify it’s location. The 3 mandatory actions a user can perform are:

Actions:

1. commit - Simply update the snapshot time (can be a variable) to the current time. Its functionality is to emulate change detection since the previous snapshot. When commit is invoked, the snapshot is updated and the state is again clean (no changes).

2. info - prints general information about the file. filename can be treated as an unique identifier, since even the OS doesn’t allow same filename + extension in the same folder.

• all files- file name, pretty print of the file extension, created and updated date and time.
• image files (png, jpg) - image size (ex. 1024x860).
• text files (txt) - line count, word count and character count.
• program files (.py, .java) - line count, class count, method count (files from previous laboratory can be used).

3. status - shows the output presented in 1.1. When calling status an iteration occurs through all the files stored in program memory and prints if they were changed during snapshot time and current time.

(Action naming isn’t mandatory to follow. The choice is yours.)