You can subscribe to this list here.
2008 |
Jan
|
Feb
(1) |
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
(3) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2009 |
Jan
(1) |
Feb
|
Mar
|
Apr
(4) |
May
(3) |
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2010 |
Jan
|
Feb
|
Mar
|
Apr
(6) |
May
(10) |
Jun
(1) |
Jul
(3) |
Aug
(19) |
Sep
(52) |
Oct
(5) |
Nov
(15) |
Dec
|
2011 |
Jan
|
Feb
(65) |
Mar
(53) |
Apr
(55) |
May
(37) |
Jun
|
Jul
(1) |
Aug
(17) |
Sep
(28) |
Oct
(7) |
Nov
|
Dec
|
2012 |
Jan
(3) |
Feb
|
Mar
(2) |
Apr
|
May
(4) |
Jun
(3) |
Jul
(1) |
Aug
|
Sep
|
Oct
(1) |
Nov
(1) |
Dec
(1) |
2013 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(3) |
2014 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
From: Rob S. <ib...@us...> - 2009-04-06 07:31:34
|
Hi Guys, Just to let you know that I've started to hack up a new version of Timesheet NG. Just rought hackings so far, with zero functionality, but hopefully it is enough to show you my thoughts on this. Please find attached a tar.gz file of my hackings (not on SVN yet as might all be scrapped!) I'm trying to focus on 2 things with this effort: 1. cleanly structured MVC approach 2. whilst allowing the creation of additional modules to add functionality I've tried to combine the two thoughts by making everything into a module (even the core functionality such as database connection etc) and then having all additional functionality as modules. Each of these modules is then, in turn, broken down into the MVC approach. The initial modules I can imagine we'll have are: calendar, weekly, daily, clients, projects, tasks, users, account (for user's personal account management), reports; etc. Project/user rates will be handled by the project and user modues respectively. As you can probably see, I've been hacking apart the Kohana PHP framework to allow it to fit this structure - not sure how successful yet, but it's been quite fun (in a sunday night coding with beer sort of a way) the only functionality that really works at the moment is the URL to module/controller functionality, internationalisation, config keys/values and the mysql database connection. to test, install on your machine, and if you go to the root directory in your browser you should see a bunch of stuff, but there should be on there somewhere: "calendar index" you can then go to <host>/calendar/ in your browser and you should see the same page, where as <host>/calendar/add/ should have "add method" as the text. That's it so far. Please let me know what you think Cheers all, and have a good week Rob |
From: David T. <tom...@ho...> - 2009-01-05 06:35:38
|
Hi, happy new year everyone I have finished debugung the allowances calculations for absence management (holiday, glidetime). There are two reports, and I think they are now consistent with each other. I have checked this into the SVN trunk, and also updated the old /tag/timesheet.ng-1.3.1 branch and renamed it to /branches/timesheet.ng-1.3.x. We can make the /tag version when we are happy with the v1.3.1. I did check-out the /branches/exp_installer version but it didn't work for me for a clean install. Not sure if it is just a mySQL problem yet... Cheers From: tom...@ho...To: tsh...@li...Subject: Absence managementDate: Thu, 18 Dec 2008 09:41:29 +0100 Hi to anyone listening.. I checked everything in that I have been working on last night. Different types of absences/leave can be entered on the absences pages. This is only monthly and to half-day granularity, that's how we have been using it. Public holidays can be entered, and appear on the calendar, but there is no user interface yet to manage these. There is an example SQL script to add public holidays. The new table timesheet_absences holds this info, with the impicit rule that an entry with a null user id applies to all users. The holiday calculation is working according to the new timesheet_allowances table. Again there is no user interface yet to manage this table. I tried to put the rule in that every user gets an initial allowance entry (of zero). Normally holiday allowance is added yearly, and this works. I use the earliest entry in this table as the user's "start date" i.e. when he joined the company/system. Glide-time is held in a similar way but is much more complicated to calculate. You need to calculate the worked-time (from the times entered), the required working-time (attendance) - you need to exclude public holidays and other things, and in our system you could compensate the time, or have it paid out. Compensation is an absence to record, and paying out hours should be represented by a negative entry in the glide-time allowance table. The glide-time calculation is messy and not well implemented, and on the monthly report the calculation is wrong. And it needs to be more flexible/configurable. But the basics are there. At least no one has to use this who doesn't want too, because it can be switched off (set ACL to none) on the config page. Cheers Invite your mail contacts to join your friends list with Windows Live Spaces. It's easy! Try it! _________________________________________________________________ More than messages–check out the rest of the Windows Live™. http://www.microsoft.com/windows/windowslive/ |
From: David T. <tom...@ho...> - 2008-12-18 08:41:33
|
Hi to anyone listening.. I checked everything in that I have been working on last night. Different types of absences/leave can be entered on the absences pages. This is only monthly and to half-day granularity, that's how we have been using it. Public holidays can be entered, and appear on the calendar, but there is no user interface yet to manage these. There is an example SQL script to add public holidays. The new table timesheet_absences holds this info, with the impicit rule that an entry with a null user id applies to all users. The holiday calculation is working according to the new timesheet_allowances table. Again there is no user interface yet to manage this table. I tried to put the rule in that every user gets an initial allowance entry (of zero). Normally holiday allowance is added yearly, and this works. I use the earliest entry in this table as the user's "start date" i.e. when he joined the company/system. Glide-time is held in a similar way but is much more complicated to calculate. You need to calculate the worked-time (from the times entered), the required working-time (attendance) - you need to exclude public holidays and other things, and in our system you could compensate the time, or have it paid out. Compensation is an absence to record, and paying out hours should be represented by a negative entry in the glide-time allowance table. The glide-time calculation is messy and not well implemented, and on the monthly report the calculation is wrong. And it needs to be more flexible/configurable. But the basics are there. At least no one has to use this who doesn't want too, because it can be switched off (set ACL to none) on the config page. Cheers _________________________________________________________________ Invite your mail contacts to join your friends list with Windows Live Spaces. It's easy! http://spaces.live.com/spacesapi.aspx?wx_action=create&wx_url=/friends.aspx&mkt=en-us |
From: David T. <tom...@ho...> - 2008-07-25 12:06:39
|
Hi While I was looking over the old timesheet project (http://sourceforge.net/projects/tsheet) I saw that there were a few things checked into the CVS that are not in the 1.2.1 zip, there are also some patches contributed from people, and some bugs reported that might be relevant.Before we release 1.3.1 I will go through what I find and try to integrate it, _if_ I think it is generally relevant. For example, a fix to add the mobile phone number to the user fields is not ground breaking so I will leave it. More eyes checking this would help though... Cheers From: tom...@ho...To: tsh...@li...Date: Wed, 16 Apr 2008 08:36:34 +0200Subject: [Tsheetx-developers] Legacy support Hi Contrary to what I said before about not bothering to maintain the old timesheet.php, I have been working on the trunk branch (1.3.x).It was easier to integrate the contributions here. We can then merge in one go with the 1.5 branch (Rob - consistent coding rules are a Good Thing, but your reformatting makes merging harder). I put in the stuff I had about manager level access (Issue 15), but this is not finished because I would like to make it configurable. I have also put in issues 20 and 21, and will do 22 and 24. That will be all the known issues for "Legacy Support", has anyone got anything else burning to go in? This could then be released as 1.3.1 (subject to your tests first). I have left all copyrights and e-mail addresses so far, but we should consider changing these. Making a release will bring attention to us, there is a saying about this somewhere (little and often?). What do you think? Cheers _________________________________________________________________ News, entertainment and everything you care about at Live.com. Get it now! http://www.live.com/getstarted.aspx |
From: Rob S. <ib...@us...> - 2008-07-04 21:04:12
|
Cheers Tommo, Have updated my SVN so will have a play with it this weekend (still no internet at home!) Many thanks for this, if I get a chance I'll have a look at the print reports Cheers Rob > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 4 Jul 2008 14:42:29 +0200 > From: David Thompson <tom...@ho...> > Subject: [Tsheetx-developers] Version 1.3.1 testing > To: <tsh...@li...> > Message-ID: <BAY...@ph...l> > Content-Type: text/plain; charset="iso-8859-1" > > Hello to anyone listening... > > I have checked in the role-based ACL changes - tested in my usual way (hope method). This should be my last change to the 1.3.1 branch, I looked at print_report.php and decided it was not worth the effort to get it working. > > So testing is the order of the day in any case, in particular the fresh install and upgrade processes. On the way we should find if everything else is OK. > > Feedback through the usual channels... > > Cheers > _________________________________________________________________ > News, entertainment and everything you care about at Live.com. Get it now! > http://www.live.com/getstarted.aspx > -------------- next part -------------- > An HTML attachment was scrubbed... > > ------------------------------ > > ------------------------------------------------------------------------- > Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! > Studies have shown that voting for your favorite open source project, > along with a healthy diet, reduces your potential for chronic lameness > and boredom. Vote Now at http://www.sourceforge.net/community/cca08 > > ------------------------------ > > _______________________________________________ > Tsheetx-developers mailing list > Tsh...@li... > https://lists.sourceforge.net/lists/listinfo/tsheetx-developers > > > End of Tsheetx-developers Digest, Vol 3, Issue 1 > ************************************************ > -- Rob Searles ib...@us... http://timesheet.ibrow.com |
From: David T. <tom...@ho...> - 2008-07-04 12:42:26
|
Hello to anyone listening... I have checked in the role-based ACL changes - tested in my usual way (hope method). This should be my last change to the 1.3.1 branch, I looked at print_report.php and decided it was not worth the effort to get it working. So testing is the order of the day in any case, in particular the fresh install and upgrade processes. On the way we should find if everything else is OK. Feedback through the usual channels... Cheers _________________________________________________________________ News, entertainment and everything you care about at Live.com. Get it now! http://www.live.com/getstarted.aspx |
From: David T. <tom...@ho...> - 2008-04-16 06:36:34
|
Hi Contrary to what I said before about not bothering to maintain the old timesheet.php, I have been working on the trunk branch (1.3.x). It was easier to integrate the contributions here. We can then merge in one go with the 1.5 branch (Rob - consistent coding rules are a Good Thing, but your reformatting makes merging harder). I put in the stuff I had about manager level access (Issue 15), but this is not finished because I would like to make it configurable. I have also put in issues 20 and 21, and will do 22 and 24. That will be all the known issues for "Legacy Support", has anyone got anything else burning to go in? This could then be released as 1.3.1 (subject to your tests first). I have left all copyrights and e-mail addresses so far, but we should consider changing these. Making a release will bring attention to us, there is a saying about this somewhere (little and often?). What do you think? Cheers _________________________________________________________________ News, entertainment and everything you care about at Live.com. Get it now! http://www.live.com/getstarted.aspx |
From: Rob S. <ib...@us...> - 2008-02-09 02:03:11
|
Hi, There has been lots going on behind the scenes this week, mainly by Peter (thanks Peter!) I have written a Todo list for the key things we need to look at for February, which you can find here: http://timesheet.ibrow.com/s:todo A full index of the wiki can be found here: http://timesheet.ibrow.com/?do=index And a useful page about the structure of the wiki is here: http://timesheet.ibrow.com/wiki:structure The homepage is a bit rubbish and it would be good to get a template that could neatly list the top and 2nd level pages. I have tried the "sidebar" template again, but it is a bit rubbish that when you click on a namespace you expect it to go to that start page, but instead it goes to the index. If anyone can sort this out that would be great! Tomorrow I'm going to start working on the planing/development of 1.5 so feel free to email/skpye/msn me if you want to chat about it Many thanks, and have a great weekend Rob -- Rob Searles ib...@us... http://timesheet.ibrow.com msn: mes...@ib... skype: ibrow99 |