 Ken Johnson
|
caf348f189
|
made some big changes here. The schedule had a has_one relationship with the PTO model. That is a problem since we only get one result back. meaning, a user cant have multiple scheduled events. This has been fixed with the use of has_many within the PTO model. Now, in relation to the PTO section, the next changes to happen are to be a fully functional create action that allows an event to be schedule, the form and controller has already been created. Umm, also, a calendar has been added and when we get the results back from a call to the create event action we will update that calendar. Think that is about it for now
|
2013-05-28 12:48:35 -04:00 |
|
|
Ken Johnson
|
a1712f78a3
|
added another chart for PTO and fixed badly named method
|
2013-05-28 10:41:04 -04:00 |
|
|
Ken Johnson
|
657db353c4
|
working on new chart for PTO
|
2013-05-28 10:12:31 -04:00 |
|
|
Ken Johnson
|
9feae35f5f
|
switching to a different graph
|
2013-05-28 09:44:17 -04:00 |
|
|
Ken Johnson
|
21752fab7e
|
I am setting this up, in this way, so that we have some extensibility. We may wish to have some sort of a polymorphic association where multiple models need to have a scheduling model available to them. That being said, as of right now, only the pto model needs it so I am doing a belong_to and has_one association between the two
|
2013-05-27 13:09:33 -04:00 |
|
|
Ken Johnson
|
daddb138a5
|
okay, I am tired, I am just gonna continue this effort sat night or sun. Anyways, some of the main things this app should do are running so not a bad day. I would say we are only a couple days from beta release.
|
2013-05-25 03:01:53 -04:00 |
|
|
Ken Johnson
|
af763d40bf
|
added the PTO section
|
2013-05-24 20:54:07 -04:00 |
|