Timesheet-Moose
---------------

Born out of two desires - one learn some Python and IronPython. Two, automatically fill in my timesheet for work.

A simple set of scripts for logging possible working hours (when a work machine is turned on and off) and format them for use in a timesheet spreadsheet.

The logger application - MooseLogger, simply notes the time that the program starts up and shuts down to a text file. Add MooseLogger to the start up programs to start it automatically.

The Moosepy script reads the text file and parses the start and end times. Then the times are rounded to the most suitable 15 minute interval (as per the requirements for filling in the timesheet). The most like estimate of working hours is printed out along with other options. Finally, the times can be automatically added to a spreadsheet.

TO DO
------

1. Build GUI front end - preferably a web app front end
	- User should be able to view their current month's timesheet from logger data
		- Display current month & current month estimated hours - DONE
		- Display table of working hours - DONE
	 	- Display log file used to generate estimated hours - DONE
		- Refactor configuration and display of tables - DONE
		- User can download an Excel spreadsheet version of their timesheet - DONE

2. Make web app standalone
	- User should be able to install GUI front end
		- Make web app standalone - DONE
		- Allow user to configure web app deployment
		- Create build and deployment infrastructure
			- Deploy as zip file - DONE
	- User should be able to run .exe and use browser to interact with Timesheet program
		- Standalone .exe hosting - DONE

2a. Refactor web page routes:
	- Initial page should redirect to a display timetable page. - DONE
	- Use specflow to drive the development of the page

2b. User can configure their application:
	- User can configure the location of their timesheet.log
	- User can configure the report writer

3. User should be able to edit the time data
	- User should be able to edit the times in the timesheet
	- User should be able to save the timesheet for later viewing
	- User should be able to create an excel version of the timesheet

4. Make front end user specific
	- User should be able to log on and view their timesheet
	- User should be able to log off

5. Automatically fill in public holidays
	- User should see public holidays already accounted for in timesheet
	- User's excel version should have public holidays accounted for

6. Automatically fill in holidays from online holiday tracker
	- User can use third party holiday tracker plugin
	- User can log in to third party holiday tracker
	- User can import holiday information into timesheet

License
-------

Copyright (c) 2013, Charles Armitage
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met: 

1. Redistributions of source code must retain the above copyright notice, this
   list of conditions and the following disclaimer. 
2. Redistributions in binary form must reproduce the above copyright notice,
   this list of conditions and the following disclaimer in the documentation
   and/or other materials provided with the distribution. 

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR
ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

The views and conclusions contained in the software and documentation are those
of the authors and should not be interpreted as representing official policies, 
either expressed or implied, of the FreeBSD Project.