tylernakamura / calendar-java-objects Goto Github PK

Many of the methods are lacking explanations as to what they do. This is really not needed, but they could probably use some documentation.

For a class assignment:

5 Minute Video Demonstration of the project showing the following features:
- Version(section 3.7.4 of RFC 5545)
- Classification(3.8.1.3)
- Comment (3.8.1.4) Your system will compute the great circle distance between events and store it in the comment fields
- DTSTART (3.8.2.4)
- DTEND (3.8.2.2)
- Time Zone Identifier (3.8.3.1)

The document should be in a pdf that can be committed to the repository. The document needs to explain why the system is correct. The document also needs to explain how the system is tested and what the respective results were.

The validation methods in the Vevent.java file are currently stubs. All they do is make sure that the information added is correct. Some of the don't need a whole lot, I suppose we can just check length or anything for the strings.

currently, exporting a .ics file from the program and then importing into Google Calendar does not work. I suspect it has something to do with the format of the GEO.

When typing in:

commands

There are only a handful options. After the Calendar.printgreatcircledistance() method is finished. The interface should allow the user to type in:

printgcd

to call the print great circle distance method in Calendar.java

This implementation should be pretty easy as there are numerous examples for other commands. All work for this issue should be done in Interface.java

many things have changed since, most of the stuff just needs to be deleted so people aren't led astray 😉

When typing in:

commands

There are only a handful options. After the Calendar.sort() method is finished. The interface should allow the user to type in:

sort

to call the sort method in Calendar.java

This implementation should be pretty easy as there are numerous examples for other commands. All work for this issue should be done in Interface.java

Currently there are way too many files in the repo. Many of the classes are only used for a single function. At some point I will take the not needed classes and make them inner classes where they are needed. Examples of classes that don't need their own files:

• MD5CheckSum
• RandomStrings
• Geo
• Coordinate

It could also be possible to make Vevent an inner class of Calendar, but that could be too drastic

Probably won't tackle this until after the next deliverable

Here are the requirements:
Your system can read- in an arbitrary number of event files for a single date,
sort of the events by start time, then compute the great circle distance ( https://en.wikipedia.or/wiki/Great-circle_distance), based on the geographic position of successive events. You shall record the great circle distance in the comment field of the first-occurring event (see section 3.8.1.4
about comments). Here’s an example: EventN occurs from 11am-1pm EventNplusOne occurs from 130pm-3pm EventNplusTwo occurs from 4pm-5pm
Your system will compute the great circle distance, in statue miles and kilometers,
from the location of EventN to EventNplusOne, and record that in the comment field
of EventN.
Similarly, your system will compute the great circle distance, in statue miles and
kilometers, from the location of EventNplusOne to EventNplusTwo, and record that
in the comment field of EventNplusOne.
The idea is to give the user an idea how far apart their events are (can they walk? Bus? Drive? Fly?)
But I said that location was optional for events. What if there is only one event?
What do you do with the last event of the day? What are you going to do then?
You’ll have to think about it and come up with something reasonable

this is totally a bell and a whistle. Travis CI is a testing platform that makes it easier to test. I might dabble with it a bit, but if anyone wants to give it a go, here is the URL:

https://travis-ci.org/

Comments are required by project requirements. See RFC for more information. Modifications should be in Vevent.java file

Currently the addsample command is used to add a fixed vevent to the calendar.

For later testing it may be useful to add a random event instead of a fixed event.

Add a setRandom() method in Vevent.java that will set all of the values to something random yet valid

In order to compute the 'great circle distance,' the events that are taken in first have to be sorted. Note that this will break one of the tests. DO NOT SORT UNLESS ASKED TO 😃