Recommended approach for handling Android P dialogs
It seems that Fragments are deprecated in Android P. I am reading a book where they are used (which is not really strange after all) and I am trying to decide which is the best approach to deal with Dialogs. In the relevant guide in the documentations the recommended approach suggest using the DialogFragment from the support library and not from the Android P library since it's deprecated. I did not expect all the relevant guides to be updated to point to the today recommended approach but to me it's a bit confusing.
As I see it I have 2 options:
- I can use support library and make my code work as it was meant to work before Android P. This of course comes with a cost of using a support library element (for example in my application size).
- Use the recommended approach for handling Android P
Dialogs.
Well, my question is since I am in the step of learning (and I don't have an existing project to maintain for example) which is the recommended approach for Dialogs? The guide refers that:
Using DialogFragment to manage the dialog ensures that it correctly
handles lifecycle events ...
and I know that using DialogFragment guaranteed that my application would work flawlessly in every lifecycle event (if for example smart phone was rotated etc). So I probably shouldn't rely on Dialog class itself either. So, which is the recommended approach?
android asked Nov 13 '18 at 7:47
EyprosEypros
2,14811531
add a comment |
It seems that Fragments are deprecated in Android P. I am reading a book where they are used (which is not really strange after all) and I am trying to decide which is the best approach to deal with Dialogs. In the relevant guide in the documentations the recommended approach suggest using the DialogFragment from the support library and not from the Android P library since it's deprecated. I did not expect all the relevant guides to be updated to point to the today recommended approach but to me it's a bit confusing.
As I see it I have 2 options:
- I can use support library and make my code work as it was meant to work before Android P. This of course comes with a cost of using a support library element (for example in my application size).
- Use the recommended approach for handling Android P
Dialogs.
Well, my question is since I am in the step of learning (and I don't have an existing project to maintain for example) which is the recommended approach for Dialogs? The guide refers that:
Using DialogFragment to manage the dialog ensures that it correctly
handles lifecycle events ...
and I know that using DialogFragment guaranteed that my application would work flawlessly in every lifecycle event (if for example smart phone was rotated etc). So I probably shouldn't rely on Dialog class itself either. So, which is the recommended approach?
android asked Nov 13 '18 at 7:47
EyprosEypros
2,14811531
What would be the downside for you usingDialoginstead ofDialogFragment?
– Ezzy
Nov 13 '18 at 7:50
As I get it from the guide it provides the tools to handle every lifecycle events as I mentioned.
– Eypros
Nov 13 '18 at 7:57
add a comment |
It seems that Fragments are deprecated in Android P. I am reading a book where they are used (which is not really strange after all) and I am trying to decide which is the best approach to deal with Dialogs. In the relevant guide in the documentations the recommended approach suggest using the DialogFragment from the support library and not from the Android P library since it's deprecated. I did not expect all the relevant guides to be updated to point to the today recommended approach but to me it's a bit confusing.
As I see it I have 2 options:
- I can use support library and make my code work as it was meant to work before Android P. This of course comes with a cost of using a support library element (for example in my application size).
- Use the recommended approach for handling Android P
Dialogs.
Well, my question is since I am in the step of learning (and I don't have an existing project to maintain for example) which is the recommended approach for Dialogs? The guide refers that:
Using DialogFragment to manage the dialog ensures that it correctly
handles lifecycle events ...
and I know that using DialogFragment guaranteed that my application would work flawlessly in every lifecycle event (if for example smart phone was rotated etc). So I probably shouldn't rely on Dialog class itself either. So, which is the recommended approach?
android asked Nov 13 '18 at 7:47
EyprosEypros
2,14811531
It seems that Fragments are deprecated in Android P. I am reading a book where they are used (which is not really strange after all) and I am trying to decide which is the best approach to deal with Dialogs. In the relevant guide in the documentations the recommended approach suggest using the DialogFragment from the support library and not from the Android P library since it's deprecated. I did not expect all the relevant guides to be updated to point to the today recommended approach but to me it's a bit confusing.
As I see it I have 2 options:
- I can use support library and make my code work as it was meant to work before Android P. This of course comes with a cost of using a support library element (for example in my application size).
- Use the recommended approach for handling Android P
Dialogs.
Well, my question is since I am in the step of learning (and I don't have an existing project to maintain for example) which is the recommended approach for Dialogs? The guide refers that:
Using DialogFragment to manage the dialog ensures that it correctly
handles lifecycle events ...
and I know that using DialogFragment guaranteed that my application would work flawlessly in every lifecycle event (if for example smart phone was rotated etc). So I probably shouldn't rely on Dialog class itself either. So, which is the recommended approach?
android android asked Nov 13 '18 at 7:47
EyprosEypros
2,14811531
asked Nov 13 '18 at 7:47
EyprosEypros
2,14811531
asked Nov 13 '18 at 7:47
EyprosEypros
2,14811531
asked Nov 13 '18 at 7:47
EyprosEypros
2,14811531
asked Nov 13 '18 at 7:47
EyprosEypros
2,14811531
2,14811531
What would be the downside for you usingDialoginstead ofDialogFragment?
– Ezzy
Nov 13 '18 at 7:50
As I get it from the guide it provides the tools to handle every lifecycle events as I mentioned.
– Eypros
Nov 13 '18 at 7:57
add a comment |
What would be the downside for you usingDialoginstead ofDialogFragment?
– Ezzy
Nov 13 '18 at 7:50
As I get it from the guide it provides the tools to handle every lifecycle events as I mentioned.
– Eypros
Nov 13 '18 at 7:57
What would be the downside for you using
Dialog instead of DialogFragment?– Ezzy
Nov 13 '18 at 7:50
What would be the downside for you using
Dialog instead of DialogFragment?– Ezzy
Nov 13 '18 at 7:50
As I get it from the guide it provides the tools to handle every lifecycle events as I mentioned.
– Eypros
Nov 13 '18 at 7:57
As I get it from the guide it provides the tools to handle every lifecycle events as I mentioned.
– Eypros
Nov 13 '18 at 7:57
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53276158%2frecommended-approach-for-handling-android-p-dialogs%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53276158%2frecommended-approach-for-handling-android-p-dialogs%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
What would be the downside for you using
Dialoginstead ofDialogFragment?– Ezzy
Nov 13 '18 at 7:50
As I get it from the guide it provides the tools to handle every lifecycle events as I mentioned.
– Eypros
Nov 13 '18 at 7:57