Log in

View Full Version : .NET Compact Framework Date Time Picker

Andy Sjostrom
02-05-2003, 06:46 PM
<a href="http://www.businessanyplace.net/?p=datetimepicker">http://www.businessanyplace.net/?p=datetimepicker</a><br /><br />More developer content is heading your way! Chris Forsberg puts <a href="http://www.intelliprog.com/netcf/index.html">IntelliProg's .NET Compact Framework datetime-picker</a> to the test. The <a href="http://www.businessanyplace.net/?p=datetimepicker">article</a> includes lots of sample code and apparantly Chris likes what he sees!<br /><br />"When creating mobile application, the efficiency in data entry can be the difference between success and failure. Most mobile scenarios require data entry to be very fast and accurate and this DateTimePicker control is an excellent way of entering date and time values. For a .NET CF developer, it works just the way you expect it to."
Jimmy Dodd
02-05-2003, 08:37 PM
Not meaning to complain too much, but it really gripes me :evil: that MS left out a DateTimePicker control in the .NET CF. Every built in PIM app that ships with the PocketPC uses the DateTimePicker so it seems that it would be an obvious choice for inclusion. Any idea behind the reasoning not to do so? :?:
Jimmy Dodd
02-05-2003, 08:44 PM
BTW, any experience with their RTF control (another control woefully missing from my toolbox)? There doesn't seem to be a trial version of it.
Peter Foot
02-05-2003, 10:04 PM
BTW, any experience with their RTF control (another control woefully missing from my toolbox)? There doesn't seem to be a trial version of it.

Drop Alex an eMail, I'm sure there is either a Beta program or he can give you an idea of the release date. Theres a link at the bottom of the page
http://www.intelliprog.com/netcf/index.html

HTH
Peter
Peter Foot
02-05-2003, 10:08 PM
Not meaning to complain too much, but it really gripes me :evil: that MS left out a DateTimePicker control in the .NET CF. Every built in PIM app that ships with the PocketPC uses the DateTimePicker so it seems that it would be an obvious choice for inclusion. Any idea behind the reasoning not to do so? :?:

I think its a mixture of size constraints and time for development, I think getting the core of the cf implemented well was very important, they didn't want to spread the developers too thinly. However in the beta process a dtpicker and a grid control were both promised, the grid control made it into the final beta but the dt picker did not.