-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create dialog service and Select Project dialog #388
Comments
I believe this is necessary for opening the Resource Viewer or Text Collection with a specified set of projects for the tech demo. @GlennPruitt |
Good UX means dialog primary buttons should always convey an action to take ususally using a verb. A secondary button (if it exists) is almost always the verb "Cancel". That means we shouldn't have any Yes/No dialogs. Remember that users essentially hate confirmation dialogs, usually don't read them and just want to get rid of them as quickly as possible. So confirmation dialogs should only be used rarely when it is crucial. Rather than use a confirmation dialog it is better to allow the user to undo the action or easily recreate the data so they have confidence to discover what things do. |
Select Multiple Projects split off to #514 |
|
Created #551 for extensions creating custom webview dialogs |
Documentation: |
As an extension developer, I want to be able to ask the user for some information using existing dialogs in Platform.Bible so it is easy for me to get information from users.
We need to create a dialog service that allows extensions to asynchronously ask the user for a response to something. There are some things we need to put in this service:
papi.dialogs.getProject
or somethingIf the linked issues are done first, just connect them into this dialog service. If not, just make sure they are put in with the issue in which they are to be created.
The text was updated successfully, but these errors were encountered: