Menu
▾
▴
Re: [Tsheetx-developers] Simple timesheet editing
|
From: Mark W. <ma...@rw...> - 2011-05-16 15:10:17
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Scott, <br>
<br>
I acknowledge that you have spent some time making simple.php work
once again in the 2.x version however I think you have misunderstood
what Peter is saying. I think Peter is proposing to rewrite
sections of simple.php as there are many flaws in how simple
currently operates.<br>
<br>
I agree with Peter that the client / project / task is too easy to
change and I think his proposal is a much better one. Peter is also
discussing how the current method of deleting everything out of the
db before adding it back is a poor way of manipulating data. Just
consider if the server crashes between sql transactions - you could
end up with all the data being deleted and not being added back in.<br>
<br>
I also believe that simple.php needs to more closely relate to the
other methods of time entry as there are lots of compatibility
problems between the two methods. I realise this is a much
discussed point but we really can't use the reason "We must give
users the option" as validation for having two parts of a system
that simply don't work together properly. You wouldn't find it in a
commercial app, so why find it in this one? I'm sure there is a way
(i haven't looked yet) in making the two systems compatible. <br>
<br>
Regards<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 16/05/2011 15:51, Scott Miller wrote:
<blockquote
cite="mid:BAN...@ma..."
type="cite">forgot to "reply all"...<br>
<br>
<div class="gmail_quote">On Mon, May 16, 2011 at 9:51 AM, Scott
Miller <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:sco...@gm...">sco...@gm...</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">Peter,
<div><br>
</div>
<div>I have already gotten all this to work in the new (2.x
demo) version. Please reveiw the simple_action.php and
simple.php files to review and test this functionality.</div>
<div><br>
</div>
<div>-Scott<br>
<br>
<div class="gmail_quote">
<div>
<div class="h5">On Mon, May 16, 2011 at 6:47 AM, Peter
Lazarus <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:pal...@gm..." target="_blank">pal...@gm...</a>></span>
wrote:<br>
</div>
</div>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
<div>
<div class="h5">
I have been looking at the simple.php form. I have
mostly devised a way of dealing with updates and
insertions and deletions, and will soon be coding it
up.<br>
<br>
The way the current code works though is to accept
any change and apply it. So if in a previous use of
this simple weekly form the user entered some time
for client 1/project 1/task 1, and then in a
subsequent update, decided that he should have
selected client 1/project 2/task 3, he can just go
and re-select the new project and task, and the time
will now appear under the new project. The current
simple weekly timesheet does allow that change to
take place. <br>
<br>
I would like to propose a different way of making
such a change. I think that once a user selects a
specific client/project/task and enters time against
it, then that relationship should be locked down,
and not be able to be changed in the future. Hence,
the user could change client/project/task on first
entering the data, but once he saves his changes,
the client/project/task dropdowns should be locked
and be unchangeable. <br>
<br>
Why? Well, with this current design, it is of no
importance because all the times records are deleted
at start of processing anyway. I no longer want to
delete times records enn-mass, but decide to do
update, insert or delete times records based on the
user editing. From this point of view, the
relationship between client/project/task and the
entered time is important to manage. And from a
database design the relationship should not be
changed at will. In future, when the database has
some design changes, and perhaps referential
integrity is introduced, such a change would not be
allowed. Hence I would like to tighten up the user
interface now.<br>
<br>
My suggestion will then require the user to delete
the line containing the entered times for client
1/project 1/task 1, and re-enter them on a new line
for client 1/project 2/task 3.<br>
<br>
The alternative approach is to allow the user
interface to work as it currently does, allowing the
user to change client 1/project 1/task 1 to client
1/project 2/task 3, at any time. Under the covers
the change would be implemented by deleting the
current times records and inserting new ones with
the new client/project/task.<br>
<br>
What do you think about both approaches? Do you
think I am making things more complex?<br>
<font color="#888888"><br>
Peter<br>
<br>
<br>
</font><br>
</div>
</div>
------------------------------------------------------------------------------<br>
Achieve unprecedented app performance and reliability<br>
What every C/C++ and Fortran developer should know.<br>
Learn how Intel has extended the reach of its
next-generation tools<br>
to help boost performance applications - inlcuding
clusters.<br>
<a moz-do-not-send="true"
href="http://p.sf.net/sfu/intel-dev2devmay"
target="_blank">http://p.sf.net/sfu/intel-dev2devmay</a><br>
_______________________________________________<br>
Tsheetx-developers mailing list<br>
<a moz-do-not-send="true"
href="mailto:Tsh...@li..."
target="_blank">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>
<br>
</blockquote>
</div>
<br>
</div>
</blockquote>
</div>
<br>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
<a class="moz-txt-link-freetext" href="http://p.sf.net/sfu/intel-dev2devmay">http://p.sf.net/sfu/intel-dev2devmay</a></pre>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
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>
|
