~doyle/blockbuster.git

author	Jordan <JordanDoyle@users.noreply.github.com>	2015-04-12 23:45:31.0 +00:00:00
committer	Jordan <JordanDoyle@users.noreply.github.com>	2015-04-12 23:45:31.0 +00:00:00
commit	af31be316bb3ffb6f58c2d2103ffe2a24618e1fd [patch]
tree	cd3e03109c2b563bafc42ab66ca433274cf9fe54
parent	a17e392240c09d1b161c0215be86a67215f90c21
download	af31be316bb3ffb6f58c2d2103ffe2a24618e1fd.tar.gz

Update README.md

Diff

 README.md | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/README.md b/README.md
new file mode 100644
index 0000000..6a7a17f
--- /dev/null
+++ b/README.md
@@ -0,0 +1,6 @@
# blockbuster
My interpretation of steps 1 to 6 of part 3 of [University of Salford's Java Project](https://drive.google.com/file/d/0B1SXk11s15KuQkRfa2NJcmxyN00/view?usp=sharing).

To aid with quick and easy expandability of this application in the upcoming parts, the application parses the `data is` line provided by the professor and uses [reflection](http://en.wikipedia.org/wiki/Reflection_%28computer_programming%29#Java) to set and get the values of each `LibraryItem` instance based on the values from the `data is` line which means there is no need the hardcode where each value is positioned in the data file, again, allowing easy portability.

Each part of this application has been documented to show what each part is doing for amateur developers.