Good point, and a good suggestion. This sounds like a winner. What does everyone else think?
Respectfully, Adam Phillip Churvis Member of Team Macromedia Advanced Intensive Training: * C# & ASP.NET for ColdFusion Developers * ColdFusion MX Master Class * Advanced Development with CFMX and SQL Server 2000 http://www.ColdFusionTraining.com Download CommerceBlocks V2.1 and LoRCAT from http://www.ProductivityEnhancement.com The ColdFusion MX Bible is in bookstores now! ----- Original Message ----- From: "Jeff Fleitz" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Monday, August 16, 2004 11:16 AM Subject: Re: [plum] DisplaySearchDateTimeControl not working > Well, if you are going to make everything pull downs, why not make the > year one as well? Maybe you could add yearStart and yearEnd attributes > that would populate the year pulldown with that range of values? My > concern is the flow. Some of these systems are going to be high volumn > data entry, and going from a pulldown, pulldown, text entry and back to > pulldown, means that some people are going to be going from mouse to > keyboard and back to mouse to enter a datetime value. Seems like a lot > of work. > > Jeff > > Adam Churvis wrote: > > >What do you think of the other suggestion I had responding to Angel's input? > > > >Respectfully, > > > >Adam Phillip Churvis > >Member of Team Macromedia > > > >Advanced Intensive Training: > >* C# & ASP.NET for ColdFusion Developers > >* ColdFusion MX Master Class > >* Advanced Development with CFMX and SQL Server 2000 > >http://www.ColdFusionTraining.com > > > >Download CommerceBlocks V2.1 and LoRCAT from > >http://www.ProductivityEnhancement.com > > > >The ColdFusion MX Bible is in bookstores now! > >----- Original Message ----- > >From: "Jeff Fleitz" <[EMAIL PROTECTED]> > >To: <[email protected]> > >Sent: Monday, August 16, 2004 10:57 AM > >Subject: Re: [plum] DisplaySearchDateTimeControl not working > > > > > > > > > >>I like your suggestions. One concern I still have is with the time > >>field. If you use 'time' as a default value for a time field, the user > >>will still not know that a colon is required in the mask. If you can > >>change the validation message for that field to indicate that a colon in > >>required in the mask, then that would help, I think. A lot of systems > >>out there use 24 hour/military times and a lot of users are used to > >>entering data that way. If you don't tell them somehow what the time > >>format should look like, I think we can expect phone calls ;) > >> > >>Jeff > >> > >>Adam Churvis wrote: > >> > >> > >> > >>>We've entered the suppressTime and validation display items as bugs to be > >>>fixed in the next release. > >>> > >>>I'd like to get everyone's input on the date control masking issue that > >>> > >>> > >Jeff > > > > > >>>brought up. How does this sound for a solution: > >>> > >>>1) We pre-populate the day field with the word "day", the year field with > >>>the word "year", and the time field with the word "time". > >>> > >>>2) If the date control (cf_DisplaySearchDateTimeControl) is on a search > >>> > >>> > >form > > > > > >>>and the user doesn't touch the control before he performs a search, then > >>> > >>> > >it > > > > > >>>won't matter that there are values in those fields because the value of > >>> > >>> > >that > > > > > >>>control isn't added to the search criteria unless the user chooses a > >>> > >>> > >month > > > > > >>>from the month select menu. > >> > >> > >>>3) If the user does choose a month from the search date control but > >>> > >>> > >leaves > > > > > >>>the default values in the fields when he clicks Display Search, > >>> > >>> > >client-side > > > > > >>>validation will prompt the user to enter proper values for those fields. > >>> > >>>4) If the date control (cf_DisplayDateTimeControl) is for a required > >>> > >>> > >field > > > > > >>>on an add or edit form and the user doesn't edit the default values for > >>>those fields, client-side validation will prompt the user to enter proper > >>>values for those fields. > >>> > >>>5) If the date control is for an optional field on an add or edit form > >>> > >>> > >and > > > > > >>>the user doesn't edit the default values for those fields, then it won't > >>>matter that there are values in those fields because the value of that > >>>control isn't added to the insert or update clause unless the user > >>> > >>> > >chooses a > > > > > >>>month from the month select menu. > >>> > >>>6) We add JavaScript to the date controls such that if those default > >>> > >>> > >"day", > > > > > >>>"year", or "time" values are present, they will disappear as soon as the > >>>user clicks in that field. > >>> > >>>Let me hear your feedback, and we'll make it happen. > >>> > >>>Respectfully, > >>> > >>>Adam Phillip Churvis > >>>Member of Team Macromedia > >>> > >>>Advanced Intensive Training: > >>>* C# & ASP.NET for ColdFusion Developers > >>>* ColdFusion MX Master Class > >>>* Advanced Development with CFMX and SQL Server 2000 > >>>http://www.ColdFusionTraining.com > >>> > >>>Download CommerceBlocks V2.1 and LoRCAT from > >>>http://www.ProductivityEnhancement.com > >>> > >>>The ColdFusion MX Bible is in bookstores now! > >>>----- Original Message ----- > >>>From: "Jeff Fleitz" <[EMAIL PROTECTED]> > >>>To: "[email protected]" > >>><[email protected]> > >>>Sent: Monday, August 16, 2004 10:19 AM > >>>Subject: [plum] DisplaySearchDateTimeControl not working > >>> > >>> > >>> > >>> > >>> > >>> > >>>>I have a list with a nested search form that includes a datetime column > >>>>named LogCreated. I would like the user to be able to filter the list > >>>> > >>>> > > > > > > > >>>>against that column. > >>>> > >>>><cf_DisplaySearchDateTimeControl column="LogCreated" label="Log Entry > >>>>Date Filter" type="datetime" default="" searchByRange="No" > >>>>suppresstime="Yes"> > >>>> > >>>>I am getting back 'You did not enter any search criteria' in the list > >>>>display, even though there is valid data. I am using the latest new > >>>> > >>>> > >tags. > > > > > >>>>The tag works if the suppressTime attribute is 'No'. If it is > >>>>suppressed, it doesn't work. > >>>> > >>>>Also, the control layout is very confusing, i.e., there are no visual > >>>>masking clues to tell a user what they are supposed to enter. I get the > >>>>month pulldown, but the day and month columns will be confusing. If I > >>>>enter a time of 1000 AM (should be '10:00:00') I get a cryptic qForms > >>>>error message saying 'Please specify a valid 'LogCreated_criteriatime' > >>>>That is definately going to confuse users. The validation message > >>>>should match the column label. > >>>> > >>>>Suggest you place a formatting mask example at the end of the column, or > >>>>some visual cue. Cool control, but will cause headaches with users > >>>>unless they know how to use it properly. > >>>> > >>>>Jeff > >>>> > >>>>-- > >>>>_______________________________ > >>>> > >>>>Jeff Fleitz > >>>>Tekquest, Ltd > >>>>Integrated Digital Solutions > >>>>http://www.tekquest.com > >>>>866.472.5868 > >>>>_______________________________ > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>> > >>> > >>> > >>> > >>> > >>-- > >>_______________________________ > >> > >>Jeff Fleitz > >>Tekquest, Ltd > >>Integrated Digital Solutions > >>http://www.tekquest.com > >>866.472.5868 > >>_______________________________ > >> > >> > >> > >> > >> > > > > > > > > > > > > -- > _______________________________ > > Jeff Fleitz > Tekquest, Ltd > Integrated Digital Solutions > http://www.tekquest.com > 866.472.5868 > _______________________________ > > >
