Menu
▾
▴
Re: [Tsheetx-developers] newdaily
|
From: Scott M. <sco...@gm...> - 2011-04-14 14:57:56
|
The all caps just mean that nothing has been put into the translation files yet. And the bizzare date format, I've seen that before, but I don't remember why or how I fixed it. I'm not really buying into the "oh, we need to protect the users from themselves" argument, but this could perhaps be a user configurable item (once we actually get a working user configuration area). I think you're over reacting to the amount of data being posted. I realize change is sometimes disconcerting, so, play with it as we develop it, and I think you'll see you're perhaps just trying to cling to something that is familiar to you now. -Scott On Thu, Apr 14, 2011 at 2:37 PM, Mark Wrightson <ma...@rw...>wrote: > > _____________________________________________ > > Mob: 07725 695178 > Email: ma...@rw... > > > On 14/04/2011 15:20, Scott Miller wrote: > > <grin> I thought it might make more sense once you saw what I had in mind. > > Yes, the ability to edit multiple entries was part of my plan. Considering > we should have potentially more data being passed in via the simple sheet, I > think as long as your max_post_size is set to something sane, 64K or more, I > don't think you'll run into any problems even with your habit of entering an > entire paragraph for each task :-). I would rather not have to keep the > edit screen around if we don't need it. Yes, I want to put a date field in > there somehow. > > I don't particularly like that you could accidentally edit something. i.e. > if you have 10 clocks on the newdaily page, you could quite easily type into > the wrong box or something (user error i know). This could be tidied up if > there was a button next to delete called edit that then enabled that row for > editting using javascript. Thus a user has to intentionally do something to > edit a clock. Also it would mean only the changed rows (the rows being > editted) would require submission, thus reducing the number of items being > transmitted back to the server. The button could be a check box? > > > Would it be better/simpler to have drop down selects for each date item > (day, month, year)? Or should we use the date picker? > > I think the date picker would be better. The date picker does need some > work doing it to improve it, but on the whole I think it is a better way of > doing things. > I think we should have separate fields for date and time as per google > calendars as it makes it easier to work with and is more clean. > > > Considering the layout is selectable, and you're the one that last made > changes to the "big description" layout (as copied from the simple.php > file), you should be able to tweak the vertical spaces as you'd like (at > least I'm assuming you're talking about vertical space when you mentioned > finding it hard to click on the correct drop down menu). > > Oh right, I see. Multiple different layouts are present. I think that the > "no description" view should be scrapped. Clock times have no meaning > unless something descriptive is written next to them when you are looking > back after even just one week. > > > A collaborative effort on this would be great Mark, Peter, others, so > change/fix things and check them in, but please notify us when you've > checked in your stuff. > > Can we do something about the english translations all in capital letters > / no spaces as it is quite annoying. i.e. > > " JDAILY: 14ThuAprilAprCEST_Apr+02004CEST00_ThuAM2011_2011EAMR"? > > Cheers > Mark > > -Scott > > On Thu, Apr 14, 2011 at 10:12 AM, Mark Wrightson <ma...@rw... > > wrote: > >> Hi Scott, >> >> I thought from your original description that the work you were doing was >> a replacement of just the clock on/off box. It makes more sense now! >> >> One problem I can foresee is that whenever you submit a new clock, it will >> also submit all other clocks on this page, and we may run into the post size >> limit. This could easily be avoided by only submitting individual clock >> times. Can we implement your idea in such a way that clock times that >> already have been entered do not appear in form fields? An edit button >> could be added and a bit of javascript used to enable editting of that >> particular clock time. This style of implementation would then lend itself >> to the scenario when times have already been 'submitted to a supervisor' and >> aren't available for editting. >> >> Do you intend to add a date field into this form, particularly in the end >> time so that clocking over a day boundary can be supported? The javascript >> date picker can be configured to add time entry on the bottom aswell just so >> you know. >> >> The clock on/off buttons could be in the same column to save space in >> width (one above the other)? >> I realise this is just a preliminary version, but i find it is very easy >> to click on the wrong drop down menu, I think that some more space between >> each one is required. >> Also rather than creating a new row when the task field has been selected, >> maybe there could be a add a new clock button instead? >> >> >> >> Cheers >> Mark >> >> _____________________________________________ >> >> Mob: 07725 695178 >> Email: ma...@rw... >> >> >> On 14/04/2011 04:42, Peter Lazarus wrote: >> >> Well I like it. It covers all that is in the daily sheet and removes the >> clockon/off thing above. That results in a neater looking entry form. The >> clock on now clock off now columns will become the green/red buttons I >> assume. >> Peter >> >> On 04/14/2011 08:14 AM, Scott Miller wrote: >> >> I've just submitted my updates, and I've added a very rough page called >> newdaily. The submission script doesn't exist, the grand total doesn't >> calculate the right thing, but the rough concept is there, take a look and >> see what you think. >> >> -Scott >> >> On Wed, Apr 13, 2011 at 9:08 PM, Mark Wrightson <ma...@rw... >> > wrote: >> >>> Hey Everyone, >>> >>> Please could you do a SVN Update, I have gone through and corrected all >>> of the db table references in every file. >>> >>> Cheers Mark >>> >>> -- >>> _____________________________________________ >>> >>> Mob: 07725 695178 >>> Email: ma...@rw... >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> 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. http://p.sf.net/sfu/vmware-sfdev2dev >>> _______________________________________________ >>> Tsheetx-developers mailing list >>> Tsh...@li... >>> https://lists.sourceforge.net/lists/listinfo/tsheetx-developers >>> >> >> >> ------------------------------------------------------------------------------ >> 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. http://p.sf.net/sfu/vmware-sfdev2dev >> >> >> _______________________________________________ >> Tsheetx-developers mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/tsheetx-developers >> >> > |
