From: Mark W. <ma...@rw...> - 2011-04-14 10:14:02
|
<!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"> Hi peter, <br> <br> Yes you are right about the mobile css type, however a large (wide) table will always need a large amount of screen space and no level of css will ever be able to change that.<br> <br> Cheers<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 14/04/2011 04:49, Peter Lazarus wrote: <blockquote cite="mid:4DA...@gm..." type="cite"> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> Mobile devices are handled by a separate css style sheet. The link to that style sheet contains: <big><big><code>media="handheld</code></big></big><br> Have a look here for an introduction. <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://perishablepress.com/press/2009/08/02/the-5-minute-css-mobile-makeover/">http://perishablepress.com/press/2009/08/02/the-5-minute-css-mobile-makeover/</a><br> <br> Just another good reason to clean up the html and drive the formatting via css. Sigh, I continue to pick away at the styles in tsng.<br> <br> On 04/13/2011 11:49 PM, Scott Miller wrote: <blockquote cite="mid:BANLkTik-2KGBRsGr=YuEjDXL179f+=DT...@ma..." type="cite"><br> <br> <div class="gmail_quote">---------- Forwarded message ----------<br> From: <b class="gmail_sendername">Scott Miller</b> <span dir="ltr"><<a moz-do-not-send="true" href="mailto:sco...@gm...">sco...@gm...</a>></span><br> Date: Wed, Apr 13, 2011 at 1:45 PM<br> Subject: Re: [Tsheetx-developers] txsheet-2.0-demo: new commit for internationalization<br> To: Mark Wrightson <<a moz-do-not-send="true" href="mailto:ma...@rw...">ma...@rw...</a>><br> <br> <br> Ah, I was not thinking about "mobile devices", so I saw no point in stretching things vertically.<br> <br> We could perhaps make two layouts, one for normal screens and another for mobile devices, is there an easy way to tell if a mobile device is viewing the page?<br> <br> The current version uses a 'text' field in the database which can hold up to 65535 characters, ie. 64kb. I'm fairly certain (but haven't verified) there is nothing in the code that cares how long a text message is, but it could be affected by the php max_post_size limitation.<br> <font color="#888888"> <br> -Scott</font> <div> <div class="h5"><br> <br> <div class="gmail_quote">On Tue, Apr 12, 2011 at 10:26 PM, Mark Wrightson <span dir="ltr"><<a moz-do-not-send="true" href="mailto:ma...@rw..." target="_blank">ma...@rw...</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;"> <div bgcolor="#ffffff" text="#000000"> The way the current clocking form is, it is suitable for use on small screens i.e. a smart phone which is a good feature.<br> The simple.php doesn't work well on a small screen due to width. Extended descriptions with carriage returns aren't possible either in simple.php whereas the other clocking methods allowed for carriage returns due to the use of textareas instead of single row fields.<br> <br> I feel there is no need to cramp stuff up when there is no real requirement. Simple.php needs to be all on single lines and that is fine, but for normal clocking I can't see a reason why it needs to be so slimline. If you take google calendars for example (see attached), everything is nicely spread out.<br> <br> Maybe the message box restriction was in an old version of tsheetx v1.2/v1.3<br> I suppose you could set a limit but if we do then it should be at least 1000chars, but then if there is no db limit then why bother?<br> <br> <br> <br> Regards <div><br> Mark<br> <pre cols="72">_____________________________________________ Mob: <a moz-do-not-send="true" href="tel:07725%20695178" value="+17725695178" target="_blank">07725 695178</a> Email: <a moz-do-not-send="true" href="mailto:ma...@rw..." target="_blank">ma...@rw...</a></pre> <br> </div> <div> <div> On 12/04/2011 18:42, Scott Miller wrote: <blockquote type="cite">That was just an example, the sizes were very rough and adjustable. Considering we now get 7 days of information on one line of the simple form, I don't think we're so tight on space that we need to move to 3-5 lines for each item on the daily page. I'd like to limit it to no more than two, the simple form does currently have this as an option (long description).<br> <br> I can see adding a date field is needed, and with the new form I would like to remove the clocking box altogether for this form. I am in agreement that the message box should be restricted, but I don't believe there is a limit of 255 characters in either the code or the database, so I'm curious as to why longer messages are currently truncated?<br> <br> As for editing, I'm proposing you can edit multiple items at a time with the form, so there would be no need for an "edit" link, but yes the 'x' would be to delete the item. With a test user/test install, maybe play with the simple form a bit to get a better idea of how the new daily form might work?<br> <br> -Scott<br> <br> <div class="gmail_quote">On Tue, Apr 12, 2011 at 5:18 PM, Mark Wrightson <span dir="ltr"><<a moz-do-not-send="true" href="mailto:ma...@rw..." target="_blank">ma...@rw...</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;"> <div bgcolor="#ffffff" text="#000000"> There are lots of inherent problems with using the simple timesheet in conjunction with other forms of time entry that I have always just disabled the simple view.<br> <br> I think for the daily view, more than one clock on/off isn't really required. The more elongated layout could cause issues as there won't be much room for the drop down menus if there is long strings, and the description being so small i don't think would work.<br> <br> A hybrid could work however? - Maybe:<br> <br> <table border="1" cellpadding="2" cellspacing="2" width="100%"> <tbody> <tr> <td valign="top">Client:<br> </td> <td valign="top">[drop down]<br> </td> <td colspan="1" rowspan="3" valign="top">Message:<br> </td> <td colspan="2" rowspan="3" valign="top">[Message Box]<br> </td> </tr> <tr> <td valign="top">Project:</td> <td valign="top">[drop down]<br> </td> </tr> <tr> <td valign="top">Task:</td> <td valign="top">[drop down]<br> </td> </tr> <tr> <td valign="top">Clock On:<br> </td> <td valign="top">[12-4-2011 ] [8.00 AM]<br> </td> <td valign="top">Clock off:<br> </td> <td rowspan="1" colspan="2" valign="top">[12-4-2011 ] [5.00 PM]</td> </tr> <tr> <td valign="top"><br> </td> <td valign="top">[Clock on and/or off]<br> </td> <td valign="top"><br> </td> <td valign="top"><br> </td> <td valign="top"><br> </td> </tr> </tbody> </table> <br> <br> Then rather than have the clocking box always visible at the top we could use a bit of javascript to make it appear - slide in from behind the menu for instance?<br> One of the most annoying things i found was it took much longer to enter times than spanned a day boundary. If the dates are already in this form but preset to today's date, that would give users the opportunity to clock over day boundaries. The other thing that I found is that there should be validation on the message box to restrict it to 255 chars or change the db so this limit is removed as I sometimes entered rather long messages only to find that it was truncated at a later date.<br> <br> If you wanted to add lots of times could you do it as follows:<br> Use my form as the entry method then have a button that you could click to add another clocking. The form above is then cleared and the data you previously entered is summarised as per Scott's image above it. the cross could be used to delete the time and another icon next to the cross could be added to edit the stored info. You would then need a final save btn:<br> <br> Maybe:<br> <br> <table border="1" cellpadding="2" cellspacing="2" width="100%"> <tbody> <tr> <td valign="top">Client1<br> </td> <td valign="top">Project1<br> </td> <td valign="top">Task 1<br> </td> <td valign="top">Description<br> </td> <td valign="top">Times<br> </td> <td valign="top">edit/delete<br> </td> </tr> <tr> <td valign="top">Client 2<br> </td> <td valign="top">Project2<br> </td> <td valign="top">Task 2<br> </td> <td valign="top">Description 2<br> </td> <td valign="top">Times<br> </td> <td valign="top">edit/delete<br> </td> </tr> <tr> <td valign="top"><br> </td> <td colspan="2" rowspan="1" valign="top"><br> </td> <td valign="top"><br> </td> <td valign="top"><br> </td> <td valign="top"><br> </td> </tr> <tr> <td valign="top">Client:<br> </td> <td colspan="2" rowspan="1" valign="top">[drop down]<br> </td> <td colspan="1" rowspan="4" valign="top">Message:<br> <br> </td> <td colspan="2" rowspan="4" valign="top">[Message Box]<br> </td> </tr> <tr> <td valign="top">Project:</td> <td colspan="2" rowspan="1" valign="top">[drop down]<br> </td> </tr> <tr> <td valign="top">Task:</td> <td colspan="2" rowspan="1" valign="top">[drop down]<br> </td> </tr> <tr> <td valign="top">Clock On:<br> </td> <td colspan="2" rowspan="1" valign="top">[12-4-2011 ] [8.00 AM]<br> </td> </tr> <tr> <td valign="top">Clock off: </td> <td colspan="2" rowspan="1" valign="top">[12-4-2011 ] [5.00 PM] </td> <td valign="top"><br> </td> <td valign="top">Add another clock <br> </td> <td valign="top">Submit All!<br> </td> </tr> </tbody> </table> <div> <br> <br> Cheers<br> <br> Mark<br> <br> <pre cols="72">_____________________________________________ Mob: <a moz-do-not-send="true" href="tel:07725%20695178" value="+17725695178" target="_blank">07725 695178</a> Email: <a moz-do-not-send="true" href="mailto:ma...@rw..." target="_blank">ma...@rw...</a></pre> <br> </div> </div> </blockquote> </div> </blockquote> </div> </div> </div> </blockquote> </div> </div> </div> </div> <pre wrap=""><fieldset class="mimeAttachmentHeader"></fieldset> ------------------------------------------------------------------------------ Forrester Wave Report - Recovery time is now measured in hours and minutes not days. Key insights are discussed in the 2010 Forrester Wave Report as part of an in-depth evaluation of disaster recovery service providers. Forrester found the best-in-class provider in terms of services and vision. Read this report now! <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://p.sf.net/sfu/ibm-webcastpromo">http://p.sf.net/sfu/ibm-webcastpromo</a></pre> <pre wrap=""><fieldset class="mimeAttachmentHeader"></fieldset> _______________________________________________ Tsheetx-developers mailing list <a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Tsh...@li...">Tsh...@li...</a> <a moz-do-not-send="true" 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> <pre wrap=""> <fieldset class="mimeAttachmentHeader"></fieldset> ------------------------------------------------------------------------------ Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. <a class="moz-txt-link-freetext" href="http://p.sf.net/sfu/vmware-sfdev2dev">http://p.sf.net/sfu/vmware-sfdev2dev</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> |