DataGrid: Prefer DatePicker DataGridDateEditColumn and add public API

[David-Moreira]

No description provided.

[stsrki]

Looking good to me.

What do you think if we add API, like bool NativeMode, that will keep the DateEdit<> if enabled?

[David-Moreira]

Looking good to me.

What do you think if we add API, like bool NativeMode, that will keep the DateEdit<> if enabled?

Then I'd do the same thing for the numeric column. Would you agree? Also altough NativeMode is a clear name for us, it might not be for our users? Do they understand exactly what NativeMode means? Altough I'm not finding a better name.

[stsrki]

Then I'd do the same thing for the numeric column. Would you agree?

Since we are going with new options I think it makes sense to make it for numeric column also.

Also altough NativeMode is a clear name for us, it might not be for our users? Do they understand exactly what NativeMode means? Altough I'm not finding a better name.

Maybe NativeInputMode?

[David-Moreira]

Then I'd do the same thing for the numeric column. Would you agree?

Since we are going with new options I think it makes sense to make it for numeric column also.

Also altough NativeMode is a clear name for us, it might not be for our users? Do they understand exactly what NativeMode means? Altough I'm not finding a better name.

Maybe NativeInputMode?

So I was starting to work on this, but I noticed that there really isn't feature parity. The native one might have different parameters, features...
Do you think it makes sense to have Parameters that will only have effect when in a certain Mode? That might be a little bit confusing and might mislead users to try and use incompatible combinations?
i.e
NativeInputMode=true+ DisabledDays
NativeInputMode=false + Step, etc...

[stsrki]

Then I'd do the same thing for the numeric column. Would you agree?

Since we are going with new options I think it makes sense to make it for numeric column also.

Also altough NativeMode is a clear name for us, it might not be for our users? Do they understand exactly what NativeMode means? Altough I'm not finding a better name.

Maybe NativeInputMode?

So I was starting to work on this, but I noticed that there really isn't feature parity. The native one might have different parameters, features... Do you think it makes sense to have Parameters that will only have effect when in a certain Mode? That might be a little bit confusing and might mislead users to try and use incompatible combinations? i.e NativeInputMode=true+ DisabledDays NativeInputMode=false + Step, etc...

We just need to document it and say that in native mode those parameters will be ignored.

[David-Moreira]

Then I'd do the same thing for the numeric column. Would you agree?

Since we are going with new options I think it makes sense to make it for numeric column also.

Also altough NativeMode is a clear name for us, it might not be for our users? Do they understand exactly what NativeMode means? Altough I'm not finding a better name.

Maybe NativeInputMode?

So I was starting to work on this, but I noticed that there really isn't feature parity. The native one might have different parameters, features... Do you think it makes sense to have Parameters that will only have effect when in a certain Mode? That might be a little bit confusing and might mislead users to try and use incompatible combinations? i.e NativeInputMode=true+ DisabledDays NativeInputMode=false + Step, etc...

We just need to document it and say that in native mode those parameters will be ignored.

It's both modes. Both modes might have some parameter that's incompatible with the other.

[stsrki]

Yeah, that makes it more complicated.

If there are overlapping parameters in terms of features then prefer the higher ones. Introduce DisabledDays but don't introduce Step.

[stsrki]

It would be good to have an example in the docs that re-enables native mode.

[stsrki]

Can we reuse the DisplayFormat from BaseDataGridColumn? It is the same thing.

[David-Moreira]

Makes sense, although this would have the advantage that you could have a different display format (when viewing the table) and edit format (when editing the records)

[stsrki]

In the past this DisplayFormat was used on DateEdit. Back then, DateEdit was using some JS for formating. So it makes sense to make it used on DatePicker today.

[stsrki]

Just a small note. Make it uppercase so it matches the naming for numeric component, (NumericEditFragment).