tsheetx-developers Mailing List for Timesheet Next Gen (Page 2)

Brought to you by: ibrow, slmi113r, tommo4242

tsheetx-developers — Timesheet Next Gen - Developer's mailing list

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)

Flat | Threaded

<< < 1 2 3 4 .. 16 > >> (Page 2 of 16)

Re: [Tsheetx-developers] Excel Export Mode

From: Mark W. <ma...@rw...> - 2011-10-07 22:30:34

I have done a bit of googling, and I have come across a library called 
PHPExcel.  It looks awesome.

The project page is here: http://phpexcel.codeplex.com/

download here:  
http://phpexcel.codeplex.com/releases/view/45412#DownloadId=212184

Extract it to a folder in your html directory and then run some of the 
test files.  The API looks like it is really easy to use,
and it produces proper xls /xlsx files even pdf's!

Please let me know your thoughts!

Mark


_____________________________________________

Mob:  07725 695178
Email: ma...@rw...


On 07/10/2011 18:23, paul cooper wrote:
> heres how i do it in perl
>
> it reads the data  from ts-times and then puts them in  hash of a hash 
> with the main key , the starttime ( in seconds)
> the data can then be sorted on time by sorting the key
>
> it then loops through the array of sorted times  (%dh)
> and makes a string of the  values of the hash and writes it to a file
> the  file can then be  then imported into  spreadsheet and the the 
> data parsed using text to columns function in the spreadsheet
> As i only have to do this 1-2 times /yr  I do it manually each time.
> there are a few random variables  and functions from extracting data 
> for other things
>
> someone who knows more perl could probably tidy it up  by passing 
> hashes by reference
>
> its a bit of kludge but it does what i need it to .
>
>
> #!/usr/bin/perl -w
> use strict;
> use Date::Manip;
> use warnings;
>
> use Data::Dumper;
> use DBI;
> use CGI;
>
> my $dbh;my $sth;
>
>  my @holidays 
> =('20110103','20110422','20110425','20110429','20110502','20110530','20110829','20111226','20111227');
> my ($DAY, $MONTH, $YEAR) = (localtime)[3,4,5];#my $m = sprintf("%02d", 
> $MONTH-1);#print "month $m";
> my $m='01';
> my $y=2011;
> my $start="$y-$m-01";my $first="$y-$m-01";
>
> my %dh;
> $dbh = DBI->connect("dbi:mysql:ts_testing","root","dfrethbyh") or die 
> "Error: can connect ";
> $sth=$dbh->prepare("SELECT * FROM `timesheet_times` WHERE  
> YEAR(start_time) =2011 AND MONTH ( start_time) BETWEEN 1 and 6 ORDER 
> BY start_time");
> $sth->execute() or die "Cannot execute : $DBI::errstr\n";
> while ( my $ref=$sth->fetchrow_hashref() )
>     {my $s=$ref->{start_time};my $k=tosecs($s);my %h=%{$ref};
> $dh{$k}=\%h;
>     }
>
> open (F, '>/tmp/export.txt');
>
> for my $t (sort keys %dh)
> {
>     my $a=$dh{$t};my @s;
>     foreach my $k ( keys %$a )
>     {
>     if (exists ($$a{$k}))
>         {
>         push @s,$$a{$k};
>         }
>     else
>         {
>         push @s," ";
>         }
>     }
>     my $string = join (": ",  @s);
>     print F "$string\n";
>
> }
> close F;
> exit;
>
> sub isHoliday
> {
> my $r;
>  my $d =shift;
>  my $a =extractdate($d);# print "a is  $a";
>  foreach ( @holidays)
>  {
>    # print "foreach ".$_;print " a is $a \n";
>   if ($a eq $_){ $r=1;last}
>   }
>   return $r;
>
>  }
>
>

Re: [Tsheetx-developers] Excel Export Mode

From: Scott M. <sco...@gm...> - 2011-10-07 15:25:35

The existing XML export code was a serendipitous event; someone many years
ago contributed a single report (I believe it was the "grid" report) that
included a working export to Excel function.  I then attempted to copy that
working functionality and put it in the rest of the reports.  While I
understand what it takes to get that functionality to work in a new report,
I would say the underlying "how it works" details were never understood by
me.

-Scott

On Fri, Oct 7, 2011 at 10:07 AM, Mark Wrightson <ma...@rw...>wrote:

> Hi
>
> Does anyone have a working excel export mode? / Could explain how it is
> meant to work?
>
> To be more precise, the v1.5.2 excel export mode currently just writes
> html code into a .xls file.
> Opening it in Excel gives an error saying the format within the file is
> incorrect and then proceeds
> to make a best guess at how the data should be displayed.
>
> What is the ideal operation?
>
> I'm going through the reports and clearing up the code, and I have
> stumbled on this problem and I thought
> someone will know how it is meant to work.
>
> N.B. v1.5.3 export doesn't work atall (yet)
>
> Mark
>
> --
> _____________________________________________
>
> Mob:  07725 695178
> Email: ma...@rw...
>
>
>
> ------------------------------------------------------------------------------
> All of the data generated in your IT infrastructure is seriously valuable.
> Why? It contains a definitive record of application performance, security
> threats, fraudulent activity, and more. Splunk takes this data and makes
> sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-d2dcopy2
> _______________________________________________
> Tsheetx-developers mailing list
> Tsh...@li...
> https://lists.sourceforge.net/lists/listinfo/tsheetx-developers
>

[Tsheetx-developers] Excel Export Mode

From: Mark W. <ma...@rw...> - 2011-10-07 15:07:24

Hi

Does anyone have a working excel export mode? / Could explain how it is 
meant to work?

To be more precise, the v1.5.2 excel export mode currently just writes 
html code into a .xls file.
Opening it in Excel gives an error saying the format within the file is 
incorrect and then proceeds
to make a best guess at how the data should be displayed.

What is the ideal operation?

I'm going through the reports and clearing up the code, and I have 
stumbled on this problem and I thought
someone will know how it is meant to work.

N.B. v1.5.3 export doesn't work atall (yet)

Mark

-- 
_____________________________________________

Mob:  07725 695178
Email: ma...@rw...

[Tsheetx-developers] Translation (Italian) and invoices

From: Alberto F. T. <alb...@gm...> - 2011-10-06 10:00:25

Hi!
I started using Timesheet.php from version 1.2.1 for my small company, then
I suggested it to a customer who asked me to translate it and to add the
invoice functionality.
I added some tables (bank accounts, time billed) and, after selecting a
customer and checking which of the unbilled time (records of timesheet_times
table) should be billed, a .sxc file was generated with the invoice data.
Then, the selected timesheet_times records were inserted into the
time_billed table.
The project has been deployed in late 2006, and now another customer is
asking me for a more-or-less identical function.
I plan to port the 2006 patches to TimesheetNG 1.5.2, would it be
interesting to have the functionality added to the development trunk?

Alberto

Re: [Tsheetx-developers] Monthly updated to OO format

From: David T. <tom...@us...> - 2011-09-26 08:27:10

I would recommend not creating a branch for timezone handling changes, for exactly this reason, you're spliting your efforts and merging is much harder than simple synchronisation with commit and update cycles. Yes, things will get broken, but fixing them early is easier than later.

Mark, the class choices seem fine, go for it.
Cheers

Date: Sat, 24 Sep 2011 17:58:37 +0100
From: ma...@rw...
To: tsh...@li...
Subject: [Tsheetx-developers] Monthly updated to OO format

Hi All, 

I have made some extensive changes to Monthly.php to object orientate the data selection from the db.  This should reduce the level of repeated code across the various pages significantly once fully propagated. It also forms a good starting point to build the timezone stuff into.

The two new classes are: 

TsxTime -a single time entity (i.e. one row from the db)
TsxTimeList - a set of times that have been retrieved from the db. (basically an array of TsxTime objects) with supporting functionsThese updates have been made to the 2.0-branch.  The timezone work still needs consideration but this code should help make things slightly easier.

Please let me know your opinions.

Thanks

Mark

[Tsheetx-developers] Monthly updated to OO format

From: Mark W. <ma...@rw...> - 2011-09-24 16:58:49

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Hi All, <br>
    <br>
    I have made some extensive changes to Monthly.php to object
    orientate the data selection from the db.&nbsp; This should reduce the
    level of repeated code across the various pages significantly once
    fully propagated. It also forms a good starting point to build the
    timezone stuff into.<br>
    <br>
    The two new classes are: <br>
    <br>
    <ul>
      <li>TsxTime -a single time entity (i.e. one row from the db)</li>
      <li>TsxTimeList - a set of times that have been retrieved from the
        db. (basically an array of TsxTime objects) with supporting
        functions</li>
    </ul>
    These updates have been made to the 2.0-branch.&nbsp; The timezone work
    still needs consideration but this code should help make things
    slightly easier.<br>
    <br>
    Please let me know your opinions.<br>
    <br>
    Thanks<br>
    <br>
    Mark<br>
    <br>
    <pre class="moz-signature" cols="72">-- 
_____________________________________________
 
Mob:  07725 695178
Email: <a class="moz-txt-link-abbreviated" href="mailto:ma...@rw...">ma...@rw...</a></pre>
  </body>
</html>

[Tsheetx-developers] Timezone branch missing sql tables

From: Mark W. <ma...@rw...> - 2011-09-24 10:23:32

Hi Peter,

Please can you add the new tables that you have created to the sql 
upgrade file?

Mark

-- 
_____________________________________________

Mob:  07725 695178
Email: ma...@rw...

Re: [Tsheetx-developers] New branch required for timezone experiments?

From: Peter L. <pal...@gm...> - 2011-09-23 20:50:15

Thanks guys. I didn;t think it would  be that easy, mainly I though I would
not have permission to create branches. It will also be easy to copy the
changes I;ve made locally into the new branch as Scott has suggested.

On 24 September 2011 04:05, Mark Wrightson <ma...@rw...> wrote:

>  Hi Peter,
>
> Scott was about right in his instructions.  To make it one step easier, I
> have created the branch for the timezone work.
> Please check out
> https://tsheetx.svn.sourceforge.net/svnroot/tsheetx/branches/txsheet-2.0-timezone
>
> :)
>
> Mark
>
> _____________________________________________
>
> Mob:  07725 695178
> Email: ma...@rw...
>
>
> On 23/09/2011 15:22, Scott Miller wrote:
>
> >From memory, to correctly create a new branch, you first create a copy of
> what your working on *within the repository*, something like:
>    svn copy http://source-directory http://destination-directory
>
>  Then check the new branch out. Make changes, and check in; changes will
> get saved on the destination branch.
>
>  If you just copy it on your local machine as you've done so far, if you
> 'accidentally' ever check that in, it will be checked into the original
> source directory in the repository - not what you want.  To "fix" the
> situation you have, do the repository copy, check things out to a new
> directory on your local box, and then copy the changed files from your new
> working directory into the newly checked out directory.  Then make your new
> working directory the newly checked out directory, and delete the 'local
> copy' directory to keep accidents from happening.
>
>  -Scott
>
> On Thu, Sep 22, 2011 at 11:51 PM, Peter Lazarus <pal...@gm...>wrote:
>
>> Dave,
>> I think it would be useful to create a new branch for timezone
>> experiments. Then the experiments we do can be shared and criticised and
>> improved.
>>
>> I copied the latest branch txsheet-2.0-demo on my machine to a new
>> directory to do some experimenting. So far I can define a timezone for
>> each person, and in one report, display the stored timezone for each
>> time record. There are quite a number of mods to be made to the clock
>> popup to enable timezone entry to carry this further and allow data
>> entry. But it's not too difficult a change to make.
>>
>> The changes so far bring up another issue. If a user does work in New
>> York, his home base, and then flies to LA for two weeks, he would need
>> some temporary timezone change, or the ability to select an alternative
>> timezone at clockon/off time.
>>
>> Now I'm not exactly clear on how svn branches work, so that might be the
>> wrong terminology. But if the timezone stuff can use txsheet-2.0-demo as
>> a base, with a later probability that the changes could be merged back
>> into txsheet-2.0-demo is what I seek.
>>
>> Thanks
>> Peter
>>
>>
>> ------------------------------------------------------------------------------
>> All of the data generated in your IT infrastructure is seriously valuable.
>> Why? It contains a definitive record of application performance, security
>> threats, fraudulent activity, and more. Splunk takes this data and makes
>> sense of it. IT sense. And common sense.
>> http://p.sf.net/sfu/splunk-d2dcopy2
>> _______________________________________________
>> Tsheetx-developers mailing list
>> Tsh...@li...
>> https://lists.sourceforge.net/lists/listinfo/tsheetx-developers
>>
>
>
>
> ------------------------------------------------------------------------------
> All of the data generated in your IT infrastructure is seriously valuable.
> Why? It contains a definitive record of application performance, security
> threats, fraudulent activity, and more. Splunk takes this data and makes
> sense of it. IT sense. And common sense.http://p.sf.net/sfu/splunk-d2dcopy2
>
>
>
> _______________________________________________
> Tsheetx-developers mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/tsheetx-developers
>
>
>
> ------------------------------------------------------------------------------
> All of the data generated in your IT infrastructure is seriously valuable.
> Why? It contains a definitive record of application performance, security
> threats, fraudulent activity, and more. Splunk takes this data and makes
> sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-d2dcopy2
> _______________________________________________
> Tsheetx-developers mailing list
> Tsh...@li...
> https://lists.sourceforge.net/lists/listinfo/tsheetx-developers
>
>

Re: [Tsheetx-developers] New branch required for timezone experiments?

From: Mark W. <ma...@rw...> - 2011-09-23 18:05:24

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Hi Peter, <br>
    <br>
    Scott was about right in his instructions.&nbsp; To make it one step
    easier, I have created the branch for the timezone work.<br>
    Please check out <a
href="https://tsheetx.svn.sourceforge.net/svnroot/tsheetx/branches/txsheet-2.0-timezone">https://tsheetx.svn.sourceforge.net/svnroot/tsheetx/branches/txsheet-2.0-timezone</a><br>
    <br>
    :)<br>
    <br>
    Mark<br>
    <pre class="moz-signature" cols="72">_____________________________________________
 
Mob:  07725 695178
Email: <a class="moz-txt-link-abbreviated" href="mailto:ma...@rw...">ma...@rw...</a></pre>
    <br>
    On 23/09/2011 15:22, Scott Miller wrote:
    <blockquote
cite="mid:CALMOH3eH-ztOpU=4NxmmLR3sOmwpdKY-6MYZEZbhQe=BT...@ma..."
      type="cite">&gt;From memory, to correctly create a new branch, you
      first create a copy of what your working on <b>within the
        repository</b>, something like:
      <div>&nbsp; &nbsp;svn copy <a moz-do-not-send="true"
          href="http://source-directory">http://source-directory</a> <a
          moz-do-not-send="true" href="http://destination-directory">http://destination-directory</a></div>
      <div><br>
      </div>
      <div>Then check the new branch out. Make changes, and check in;
        changes will get saved on the destination branch.</div>
      <div><br>
      </div>
      <div>If you just copy it on your local machine as you've done so
        far, if you 'accidentally' ever check that in, it will be
        checked into the original source directory in the repository -
        not what you want. &nbsp;To "fix" the situation you have, do the
        repository copy, check things out to a new directory on your
        local box, and then copy the changed files from your new working
        directory into the newly checked out directory. &nbsp;Then make your
        new working directory the newly checked out directory, and
        delete the 'local copy' directory to keep accidents from
        happening.</div>
      <div><br>
      </div>
      <div>-Scott</div>
      <div><br>
        <div class="gmail_quote">On Thu, Sep 22, 2011 at 11:51 PM, Peter
          Lazarus <span dir="ltr">&lt;<a moz-do-not-send="true"
              href="mailto:pal...@gm...">pal...@gm...</a>&gt;</span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex;">
            Dave,<br>
            I think it would be useful to create a new branch for
            timezone<br>
            experiments. Then the experiments we do can be shared and
            criticised and<br>
            improved.<br>
            <br>
            I copied the latest branch txsheet-2.0-demo on my machine to
            a new<br>
            directory to do some experimenting. So far I can define a
            timezone for<br>
            each person, and in one report, display the stored timezone
            for each<br>
            time record. There are quite a number of mods to be made to
            the clock<br>
            popup to enable timezone entry to carry this further and
            allow data<br>
            entry. But it's not too difficult a change to make.<br>
            <br>
            The changes so far bring up another issue. If a user does
            work in New<br>
            York, his home base, and then flies to LA for two weeks, he
            would need<br>
            some temporary timezone change, or the ability to select an
            alternative<br>
            timezone at clockon/off time.<br>
            <br>
            Now I'm not exactly clear on how svn branches work, so that
            might be the<br>
            wrong terminology. But if the timezone stuff can use
            txsheet-2.0-demo as<br>
            a base, with a later probability that the changes could be
            merged back<br>
            into txsheet-2.0-demo is what I seek.<br>
            <br>
            Thanks<br>
            Peter<br>
            <br>
------------------------------------------------------------------------------<br>
            All of the data generated in your IT infrastructure is
            seriously valuable.<br>
            Why? It contains a definitive record of application
            performance, security<br>
            threats, fraudulent activity, and more. Splunk takes this
            data and makes<br>
            sense of it. IT sense. And common sense.<br>
            <a moz-do-not-send="true"
              href="http://p.sf.net/sfu/splunk-d2dcopy2" target="_blank">http://p.sf.net/sfu/splunk-d2dcopy2</a><br>
            _______________________________________________<br>
            Tsheetx-developers mailing list<br>
            <a moz-do-not-send="true"
              href="mailto:Tsh...@li...">Tsh...@li...</a><br>
            <a moz-do-not-send="true"
              href="https://lists.sourceforge.net/lists/listinfo/tsheetx-developers"
              target="_blank">https://lists.sourceforge.net/lists/listinfo/tsheetx-developers</a><br>
          </blockquote>
        </div>
        <br>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
<a class="moz-txt-link-freetext" href="http://p.sf.net/sfu/splunk-d2dcopy2">http://p.sf.net/sfu/splunk-d2dcopy2</a></pre>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
Tsheetx-developers mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Tsh...@li...">Tsh...@li...</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/tsheetx-developers">https://lists.sourceforge.net/lists/listinfo/tsheetx-developers</a>
</pre>
    </blockquote>
  </body>
</html>

Re: [Tsheetx-developers] New branch required for timezone experiments?

From: Scott M. <sco...@gm...> - 2011-09-23 14:22:22

>From memory, to correctly create a new branch, you first create a copy of
what your working on *within the repository*, something like:
   svn copy http://source-directory http://destination-directory

Then check the new branch out. Make changes, and check in; changes will get
saved on the destination branch.

If you just copy it on your local machine as you've done so far, if you
'accidentally' ever check that in, it will be checked into the original
source directory in the repository - not what you want.  To "fix" the
situation you have, do the repository copy, check things out to a new
directory on your local box, and then copy the changed files from your new
working directory into the newly checked out directory.  Then make your new
working directory the newly checked out directory, and delete the 'local
copy' directory to keep accidents from happening.

-Scott

On Thu, Sep 22, 2011 at 11:51 PM, Peter Lazarus <pal...@gm...> wrote:

> Dave,
> I think it would be useful to create a new branch for timezone
> experiments. Then the experiments we do can be shared and criticised and
> improved.
>
> I copied the latest branch txsheet-2.0-demo on my machine to a new
> directory to do some experimenting. So far I can define a timezone for
> each person, and in one report, display the stored timezone for each
> time record. There are quite a number of mods to be made to the clock
> popup to enable timezone entry to carry this further and allow data
> entry. But it's not too difficult a change to make.
>
> The changes so far bring up another issue. If a user does work in New
> York, his home base, and then flies to LA for two weeks, he would need
> some temporary timezone change, or the ability to select an alternative
> timezone at clockon/off time.
>
> Now I'm not exactly clear on how svn branches work, so that might be the
> wrong terminology. But if the timezone stuff can use txsheet-2.0-demo as
> a base, with a later probability that the changes could be merged back
> into txsheet-2.0-demo is what I seek.
>
> Thanks
> Peter
>
>
> ------------------------------------------------------------------------------
> All of the data generated in your IT infrastructure is seriously valuable.
> Why? It contains a definitive record of application performance, security
> threats, fraudulent activity, and more. Splunk takes this data and makes
> sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-d2dcopy2
> _______________________________________________
> Tsheetx-developers mailing list
> Tsh...@li...
> https://lists.sourceforge.net/lists/listinfo/tsheetx-developers
>

[Tsheetx-developers] New branch required for timezone experiments?

From: Peter L. <pal...@gm...> - 2011-09-23 04:51:44

Dave,
I think it would be useful to create a new branch for timezone 
experiments. Then the experiments we do can be shared and criticised and 
improved.

I copied the latest branch txsheet-2.0-demo on my machine to a new 
directory to do some experimenting. So far I can define a timezone for 
each person, and in one report, display the stored timezone for each 
time record. There are quite a number of mods to be made to the clock 
popup to enable timezone entry to carry this further and allow data 
entry. But it's not too difficult a change to make.

The changes so far bring up another issue. If a user does work in New 
York, his home base, and then flies to LA for two weeks, he would need 
some temporary timezone change, or the ability to select an alternative 
timezone at clockon/off time.

Now I'm not exactly clear on how svn branches work, so that might be the 
wrong terminology. But if the timezone stuff can use txsheet-2.0-demo as 
a base, with a later probability that the changes could be merged back 
into txsheet-2.0-demo is what I seek.

Thanks
Peter