Skip to content

Conversation

@vladaskorohodova
Copy link
Collaborator

No description provided.

Co-authored-by: dirkpieterse <dirk.pieterse@devexpress.com>
@vladaskorohodova vladaskorohodova merged commit afcc75b into DevExpress:24_2 May 13, 2025
5 checks passed
@vladaskorohodova vladaskorohodova deleted the date-box-overview24_2 branch May 13, 2025 11:45
vladaskorohodova added a commit to vladaskorohodova/devextreme-documentation that referenced this pull request May 13, 2025
vladaskorohodova added a commit to vladaskorohodova/devextreme-documentation that referenced this pull request May 13, 2025
vladaskorohodova added a commit that referenced this pull request May 13, 2025
vladaskorohodova added a commit that referenced this pull request May 13, 2025
@@ -0,0 +1,5 @@
- **Customization**

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should mention all important features as other vendors do
We have at least two component in one so we will have a long list here

  1. DateBox Types
    Describe the followings:
  • type prop
  • different types for value pickers
    'calendar' | 'list' | 'native' | 'rollers'
  1. Value Formating (Locale-dependent format, Built-in predefined formats, Custom Format String.

  2. Masked Input (from Sveta's doc)

You can use the displayFormat property to define a mask that controls user input if useMaskBehavior is true.

  1. Date/Time Ranges OR Accepted Date Range (min, max props)
    Example of the description from other landing:

By default, component has no limits and will accept any date the user provides. To limit the available dates users can select from, simply use min and max properties. They enable you to define the valid date ranges available within the component.

  1. Date disabling

  2. Calendar Options
    Please describe the followings in one section or in different
    firstDayOfWeek
    minZoomLevel /maxZoomLevel & zoomLevel
    selectionMode
    selectWeekOnClick
    showWeekNumbers & weekNumberRule

  3. Form Support and Value validation
    Example of such description:

Form support and date validation
Date values are validated within a minimum and maximum range to enforce entering only a valid date value. In a form component, integrate the form validation plugin to perform custom validation in the date text box.

We can mention invalidDateMessage & dateOutOfRangeMessage

  1. Adaptivity
    (see adaptivityEnabled)

  2. A11y, KBN, RTL

  3. Appearance settings
    I found the following list of properties that set basic UI. I think we should mention them with short descriptions (you can try to shorten the list without loosing info)

  1. Customization
    dropDownButtonTemplate
    calendar cell template

<img src="/images/DateBox/date-box-elements.png" alt="DateBox elements"/>

1. [Date display format](/Documentation/ApiReference/UI_Components/dxDateBox/Configuration/#displayFormat)
2. [Input buttons](/Documentation/ApiReference/UI_Components/dxDateBox/Configuration/buttons/)

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's be more specific
Input buttons: Clear and DropDownButton


1. [Date display format](/Documentation/ApiReference/UI_Components/dxDateBox/Configuration/#displayFormat)
2. [Input buttons](/Documentation/ApiReference/UI_Components/dxDateBox/Configuration/buttons/)
3. [Format and UI type](/Documentation/ApiReference/UI_Components/dxDateBox/Configuration/#type)

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should describe UI elements not API props on these pictures
So, it's better to remove 'Format and UI type' but add 'Calendar area OR Date picker: Calendar' and 'Time picker'

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants