Make dialog more flexible. about pin_code_fields HOT 9 CLOSED

What the OP suggests is valid. The dialog widget seems not that flexible in ways such that I can't get full control of the dialog contents. For instance, I can't change the text style of the dialog content texts, or at least I can't find a way to do that. So to add more parameters to the existing dialogConfig interface or to leave that dialog part completely to the user seems like a better idea. And I prefer the second one.

from pin_code_fields.

I've consulted with a UX designer before making decision on UI. The pasted code should be asked from the user.
And there are these parameters which solve the localization problem
`/// title of the [AlertDialog] while pasting the code. Default to [Paste Code]
final String dialogTitle;

/// content of the [AlertDialog] while pasting the code. Default to ["Do you want to paste this code "]
final String dialogContent;

/// Affirmative action text for the [AlertDialog]. Default to "Paste"
final String affirmativeText;

/// Negative action text for the [AlertDialog]. Default to "Cancel"
final String negativeText;`

from pin_code_fields.

Did you mean the localization for the pasted value?

from pin_code_fields.

from pin_code_fields.

In that case, there must be a default one, as developers might not have the time to add their own dialog widget, they just want to use a default one. Or if someone wants to modify then they can their own, but there should be a default one always.

from pin_code_fields.

Thanks for your feedback, there should always be a default configuration which would automatically generate default dialogs and stuffs for user as many developers might not the need customization. And for the one who needs customization, how would you suggest it to be? Should they be able to able to change content only or they can build the whole widget with other buttons and stuffs?

from pin_code_fields.

It's all up to you. If you don't want to remove the current implementation of the dialog widget and API, because it seems like a good idea since many users might not need customization, then please don't as it's a good and valid reason. I just suggested to leave it completely to the user (maybe as an event listener as the OP implied) because that dialog part seems like not a part of the library. If you don't want to remove it, then leaving the whole building process of the dialog might not be a good idea. The two seem really diverse.

Whether you add more configurations to the dialogConfig or leaving the whole process as an event, either one should work.

from pin_code_fields.

No updates on this?

from pin_code_fields.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

from pin_code_fields.