comradephilos / coyote Goto Github PK

Control Your OverTimes (easily) - a simple and fast tool for time tracking, which allows you to overiew all your overtimes you achieved at work over a certain period of time. In future there will be support for multiple employees etc.. Made with Lazarus/Object Pascal.

Home Page: http://coyote.lukas-franke.com/

Pascal 100.00%

coyote's Introduction

CoYOT(e)

Control Your OverTimes (easily)

This programme is a lightweight, open-source and userfriendly tool to keep an eye on overtimes at work. It calculates - based on attendance times the user entered - how many hours of working time the user accumulated and visualises the balance so that he always is up to date. If used consequently one can save precious free time and organize working time in a way that employees and bosses might profit from.

open source

CoYOT(e) is open source. That means you can use it freely and distribute it under the terms of GPLv3 and even change it to fit your demands. And of course you can also contribute to this project as a programmer, designer or as a user sending feedback. You can also take the source code to compile it on almost every computer and operating system you want - Thanks to Lazarus IDE and it's multi-platform components.

what can it do?

create and edit weeks in a grid view
edit single entries in the grid like you would e.g. in Excel
calculate your overall working time by entering begin and leave of a workday
get to know how many hours you can take off based on overtimes
manage and calculate the number of days you took off
load and save to/from a file or upload to a database server ( in future )
change the color theme

what is planned in future?

track time for a number of people and easily switch between them
releases for Windows, MacOS and Linux
language support for multiple languages ( currently english only )
statistics, bar charts or graph charts
export functions e.g. to various file formats
upload to and download from a firebird database

downloads

You will find any older version by clicking the link to the Download Page. Read the release notes carefully! Alternatively you can of course always download the newest commit of the programme on this main page ( click "download zip" on the right ), if you are fine with the fact that the version might look and feel like it is not yet finished and many functions/buttons etc. may have no effect or even may cause errors and crashes.

installation

1. download the current package
2. unzip it to any destination you want
3. open the /bin folder
4. double click on the binary that is for your OS

CoYOTe-darwin for MacOS
CoYOTe-linux for Linux
CoYOTe-win.exe for Windows

There is no installation tool needed and the programme won't create any files to another directory, so that the programme is always portable. That means, that you can easily copy the programme folder to another computer and use it there without installation needed. If there is no binary for your OS check out the last paragraph "compile or edit the project", where you can find information on how to compile the project. Note that the programme is still in development and so the programme folder may contain files that would not be needed in a normal release version.

compile or edit the project

via Lazarus IDE GUI

The programme is written in Object Pascal and created with Lazarus IDE and the Free Pascal Compiler. To open/edit the project you can open the "coyote.lpi"-file with the Lazarus IDE and start coding/compiling! If you compile CoYOT(e) on a system, that is supported by the Free Pascal Compiler, you will get a binary file matching your system in the "bin"-folder.

via command prompt

git clone https://github.com/ComradePhilos/coyote.git
cd coyote
lazbuild -B CoYOTe.lpi

coyote's People

Contributors

Stargazers

Watchers

coyote's Issues

Release Preview

I added a new Branch for the current preview version. This should contain all the executables etc. for a preview and wont get any other changes. So, be patient for the Version 0.0.2.7 Preview ;)

crash on exit

When closing the programme and you opened the "edit week window", there is an exception! Going to fix that.

Grid in main window

After I decided that a workweek should become a period, which can can have more than 7 days, the grid in the main window needs to be adapted in some way.

database connection

Recently I have worked on a database connection for CoYOT(e). So far the connection worked using a firebird component and a local firebird server. The database connection should be optional so that you could still use CoYOT(e) by saving to/loading from files (this would be what the "e" in CoYOT(e) stands for: easy/simple). But there are many things to think about and I'm not sure how to expand the database support AND how to keep this as simple as it was intended to be. Maybe it would be better to offer a different programme version for each, file- and database-support.
Until this is not clear, don't expect to see many changes/improvements to the database support.

Statistic Labels invisible after language change

I found a bug that I could not fix until now. The labels shown in the picture are invisible after changing the language. Maybe this is a Lazarus-Bug!?

Toolbar

The panel with buttons in it needs to be replaced with a real toolbar in future. This will improve the "look & feel".

programme crash considering the weeklist

Fixed some bugs and finally added event handling to support multiple window-transactions. But now if you do certain operations with the weeklist, the programme crashes. And also the StringGrid shows weird results... I will have to wear my lucky socks to search for the mistake...

Editing Days in Single-Week-Window

Programme needs a "ignore day in calculation"-flag to have a whole week like "mon - fri" and just ignore the wednesday. Otherwise you would have to create two 2-day-weeks.

Language support

Something new I would like to discuss: language support. I First tried the i18n-function of the Lazarus IDE, which automatically creates .po-files that contain all the resource strings. This was quite a nice idea, because you could easily edit these files with an editor for po-files. But actually I never found how to translate the resource strings with the newer file at the end and I also got the impression that there a lot of older ways that all won't work with the new IDE Version 1.2.2. So I'm thinking of making a self-made translation function that uses the same mechanics that the ini-file component does.
You put in the original word, which will be the key and the translation will be the translation. And the ini-component just searches for any entries that match.

Seems like it's actually a good idea, but I originally didn't want to make such out-of-the-box things by myself..... well,.. in fact they aren't out-of-the-box, as I just told you ;)
Maybe someone would like to throw his or her ideas straight into the comments (or just say some nice things to honour this great idea) ! =)