Is it possible to extend the DatePicker control - xamarin.forms

I have a UWP app that has many Date entry fields and I currently use the DatePicker to provide the three spinners for day, month and year. In most cases this works well for my users, but where the field is a date of birth it's causing some issues for the users. They are complaining about having to scroll back through the years, in some cases many of them. Is there a way to extend or override the spinner for the year to change the behaviour of the arrow buttons to skip forward or backward ten at a time?
I've looked at using the CalendarView but I think this introduces UX issues when selecting the actual day, I feel it's more suited for mouse use rather than touch.
Any help or pointers much appreciated

Related

JavaFX DatePicker with multiple choice

I need to choose more than one date from calendar. Is there some useful component? I've tried to use https://kenai.com/projects/jfxcalendarpicker/pages/Home in multiple mode, but it has some critical bugs for me.

Tracking state in separate tabs in MVC 3 application

Basically what I need to be able to do, and I already know it is not a good idea, I have fought tooth and nail to not do it, but I need to have it so each individual tab in tabbed browsers is treated as a separate session; users will need to be able to have the same page open in separate tabs, but in a different context.
I have spent countless hours working on this and come down to the fact that in order for this to work, you are going to have to have a key that you embed into a hidden field, or on the route, or something like that.
So with that said, do you have any good ideas on how to accomplish this?

Creating a table dynamically, with multiple lines of text in each cell and each cell being clickable, in ASP.NET

I'm trying to design a calendar-type table that is built dynamically based on data from a separate database source.
This is an illustration of the basic design idea:
Here's an image:
If an object was added that was referenced to a Saturday, another column would be added and if the one on Monday was removed, the column would disappear and vice versa.
The weekdays are column headers and the squares represents cells with some lines of information. Each cell in its whole should be clickable.
The entire table should show a single month only.
I'm thinking this might be very time consuming to implement, and will quite quickly become impossible to re-read and understand later on if it isn't designed right. So if anyone has a more simple way to implement a month-view of a calendar, with some lines of information stored in each cell, and a possibility to call Server.Transfer() on the click event of a cell, it would be just as ideal.
As far as I know, the Calendar component doesn't support editing the contents of the cells in calendar, and other than that I don't really know which way would be the best way to go.
If I can improve the question in any way, please let me know.
I think what you want is not a Calendar, but rather a Scheduler control, which includes functionality to display a calendar view, add/edit "appointments" and provide events of what happens when you click them.
This thread lists a lot of such Scheduler control that you can use, some of them free.
Here are some additional links that implement similar functionality:
http://www.rekenwonder.com/aspnet/schedule.html
http://www.codeproject.com/Articles/7619/Databound-Schedule-Controls
http://www.codeproject.com/Articles/31766/DayPilot-Scheduler-Control-for-ASP-NET
I think reusing one of those components and spending some time to research them would be much less time consuming that implementing your own solution from scratch. If what you want falls into those common UI patterns supported by those controls, you'll be fine.
If, on the other hand what you want is not a common practice, you may rethink your approach.

Creating a scheduling / calendar grid in ASP.NET

I am working on the prototype for a scheduling application on an intranet system. The application is for scheduling and tracking promotional workers at various locations on various dates.
Currently, only for prototyping, I am generating a data table of location/date, and from this I iteratively build an HTML table (asp:Table control). On visiting each cell, I query for people working that location-date and populate the cell accordingly. This is very inefficient, and will at worst be improved by querying cached data for the whole location/date grid.
I'm looking around for established patterns and techniques for dealing with scenarios like this in HTML in general, maybe a visualization library for jQuery or something, and for ASP.NET in particular, maybe a library for implementation on a GridView etc.
Am I going in the right direction with this, and if so, what recommendations are there regarding the previous paragraph?
As regards the user interface, I would take a look at the Telerik scheduler control and see how that one is done. You don't want table cells stretching the layout, and even filtering may not help you unless you truncate the displayed text as a link to a modal pop-up, or some kind of master-details set up.
http://demos.telerik.com/aspnet-ajax/scheduler/examples/overview/defaultcs.aspx
Why don't you try placing the calender control on the left side and then select the current date by default. Thereafter user can select a date and you can list the data using a gridview based on the selected date-location. That should ease up the interface as well.
These controls are complex, and there are many third party vendors out there with components like these. Take a look around at some of the components available to you, as it is A LOT of work to develop a component like this yourself (we were going to attempt to do it, but realized to make it efficient and usable we needed to buy one, so we purchased Telerik).
HTH.

DatePicker for a Mobile Website?

What is best way to allow user to pick date from a mobile device from usability prospective?
I'd detest any form of drop-down, select-list when using a mobile app.
Unfortunately, three separate boxes (for day, month and year) would be equally painful on a MIDP-profile device.
I'd almost suggest using one text box, and do a DateTime.TryParse(String, out DateTime) to get the result. That allows them to type in any number of formats.. and the bulk of the time it'll work okay.
Also, if you gave them a hint on the form as to the correct formatting (e.g. 12 Mar 2009) then it'd probably be the format they use.
Are you building WAP page in asp.net? You have a DatePicker control in the mobile toolset. On devices that supports it this will render as a regular date picker (as in regular asp.net) while on more limited devices it will render as a series of selectors where you first select the year, then the month and finally the date. Unless you have a good reason to do otherwise you should use this I think.

Resources