Initializing a Fragment
I am new to Android and having an issue in initializing Fragment
I am looking at two lines of code and cannot figure out the actual difference between these two approaches and which one to opt. Kindly suggest
1) SignUpFragment fragment = new SignUpFragment();
2) SignUpFragment fragment = SignUpFragment.newInstance();
android-fragments
add a comment |
I am new to Android and having an issue in initializing Fragment
I am looking at two lines of code and cannot figure out the actual difference between these two approaches and which one to opt. Kindly suggest
1) SignUpFragment fragment = new SignUpFragment();
2) SignUpFragment fragment = SignUpFragment.newInstance();
android-fragments
add a comment |
I am new to Android and having an issue in initializing Fragment
I am looking at two lines of code and cannot figure out the actual difference between these two approaches and which one to opt. Kindly suggest
1) SignUpFragment fragment = new SignUpFragment();
2) SignUpFragment fragment = SignUpFragment.newInstance();
android-fragments
I am new to Android and having an issue in initializing Fragment
I am looking at two lines of code and cannot figure out the actual difference between these two approaches and which one to opt. Kindly suggest
1) SignUpFragment fragment = new SignUpFragment();
2) SignUpFragment fragment = SignUpFragment.newInstance();
android-fragments
android-fragments
edited Nov 13 '18 at 11:31
Samuel Robert
3,32052034
3,32052034
asked Nov 13 '18 at 11:05
Abhilash GuptaAbhilash Gupta
34
34
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
I personally use the first one as it will make a new object of signupFragment ,while the second option will make a new instance of that class.The difference between both is defined in the below link.
https://stackoverflow.com/questions/3323330/difference-between-object-and-instance
add a comment |
If you have no arguments to pass to fragment you can use first one.
SignUpFragment fragment = new SignUpFragment();
But if you have arguments you can use factory methods such as second one to hide creating bundle and putting the arguments' boilerplate codes.
ProfileFragment fragment = ProfileFragment.newInstance(userId);
public class ProfileFragment extends Fragment
public static ProfileFragment newInstance(int userId)
Bundle args = new Bundle();
args.putInt("userId", userId);
ProfileFragment fragment = new ProfileFragment();
fragment.setArguements(args);
return fragment;
add a comment |
1) SignUpFragment fragment = new SignUpFragment();
You should only use in case you do NOT need to create SignUpFragment instance more frequently.
2) SignUpFragment fragment = SignUpFragment.newInstance();
This is more recommended approach. In which, you would going to follow Singleton pattern for creating Instance of your class and more generic methods can be created in future if needed.
SignUpFragment.newInstance() is not a singleton pattern. It creates new object event time
– Samuel Robert
Nov 13 '18 at 11:39
add a comment |
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%2f53279639%2finitializing-a-fragment%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
I personally use the first one as it will make a new object of signupFragment ,while the second option will make a new instance of that class.The difference between both is defined in the below link.
https://stackoverflow.com/questions/3323330/difference-between-object-and-instance
add a comment |
I personally use the first one as it will make a new object of signupFragment ,while the second option will make a new instance of that class.The difference between both is defined in the below link.
https://stackoverflow.com/questions/3323330/difference-between-object-and-instance
add a comment |
I personally use the first one as it will make a new object of signupFragment ,while the second option will make a new instance of that class.The difference between both is defined in the below link.
https://stackoverflow.com/questions/3323330/difference-between-object-and-instance
I personally use the first one as it will make a new object of signupFragment ,while the second option will make a new instance of that class.The difference between both is defined in the below link.
https://stackoverflow.com/questions/3323330/difference-between-object-and-instance
answered Nov 13 '18 at 11:25
Saad MaqboolSaad Maqbool
1869
1869
add a comment |
add a comment |
If you have no arguments to pass to fragment you can use first one.
SignUpFragment fragment = new SignUpFragment();
But if you have arguments you can use factory methods such as second one to hide creating bundle and putting the arguments' boilerplate codes.
ProfileFragment fragment = ProfileFragment.newInstance(userId);
public class ProfileFragment extends Fragment
public static ProfileFragment newInstance(int userId)
Bundle args = new Bundle();
args.putInt("userId", userId);
ProfileFragment fragment = new ProfileFragment();
fragment.setArguements(args);
return fragment;
add a comment |
If you have no arguments to pass to fragment you can use first one.
SignUpFragment fragment = new SignUpFragment();
But if you have arguments you can use factory methods such as second one to hide creating bundle and putting the arguments' boilerplate codes.
ProfileFragment fragment = ProfileFragment.newInstance(userId);
public class ProfileFragment extends Fragment
public static ProfileFragment newInstance(int userId)
Bundle args = new Bundle();
args.putInt("userId", userId);
ProfileFragment fragment = new ProfileFragment();
fragment.setArguements(args);
return fragment;
add a comment |
If you have no arguments to pass to fragment you can use first one.
SignUpFragment fragment = new SignUpFragment();
But if you have arguments you can use factory methods such as second one to hide creating bundle and putting the arguments' boilerplate codes.
ProfileFragment fragment = ProfileFragment.newInstance(userId);
public class ProfileFragment extends Fragment
public static ProfileFragment newInstance(int userId)
Bundle args = new Bundle();
args.putInt("userId", userId);
ProfileFragment fragment = new ProfileFragment();
fragment.setArguements(args);
return fragment;
If you have no arguments to pass to fragment you can use first one.
SignUpFragment fragment = new SignUpFragment();
But if you have arguments you can use factory methods such as second one to hide creating bundle and putting the arguments' boilerplate codes.
ProfileFragment fragment = ProfileFragment.newInstance(userId);
public class ProfileFragment extends Fragment
public static ProfileFragment newInstance(int userId)
Bundle args = new Bundle();
args.putInt("userId", userId);
ProfileFragment fragment = new ProfileFragment();
fragment.setArguements(args);
return fragment;
edited Nov 13 '18 at 11:30
answered Nov 13 '18 at 11:25
Samuel RobertSamuel Robert
3,32052034
3,32052034
add a comment |
add a comment |
1) SignUpFragment fragment = new SignUpFragment();
You should only use in case you do NOT need to create SignUpFragment instance more frequently.
2) SignUpFragment fragment = SignUpFragment.newInstance();
This is more recommended approach. In which, you would going to follow Singleton pattern for creating Instance of your class and more generic methods can be created in future if needed.
SignUpFragment.newInstance() is not a singleton pattern. It creates new object event time
– Samuel Robert
Nov 13 '18 at 11:39
add a comment |
1) SignUpFragment fragment = new SignUpFragment();
You should only use in case you do NOT need to create SignUpFragment instance more frequently.
2) SignUpFragment fragment = SignUpFragment.newInstance();
This is more recommended approach. In which, you would going to follow Singleton pattern for creating Instance of your class and more generic methods can be created in future if needed.
SignUpFragment.newInstance() is not a singleton pattern. It creates new object event time
– Samuel Robert
Nov 13 '18 at 11:39
add a comment |
1) SignUpFragment fragment = new SignUpFragment();
You should only use in case you do NOT need to create SignUpFragment instance more frequently.
2) SignUpFragment fragment = SignUpFragment.newInstance();
This is more recommended approach. In which, you would going to follow Singleton pattern for creating Instance of your class and more generic methods can be created in future if needed.
1) SignUpFragment fragment = new SignUpFragment();
You should only use in case you do NOT need to create SignUpFragment instance more frequently.
2) SignUpFragment fragment = SignUpFragment.newInstance();
This is more recommended approach. In which, you would going to follow Singleton pattern for creating Instance of your class and more generic methods can be created in future if needed.
answered Nov 13 '18 at 11:35
Bhavesh PatadiyaBhavesh Patadiya
22.2k126899
22.2k126899
SignUpFragment.newInstance() is not a singleton pattern. It creates new object event time
– Samuel Robert
Nov 13 '18 at 11:39
add a comment |
SignUpFragment.newInstance() is not a singleton pattern. It creates new object event time
– Samuel Robert
Nov 13 '18 at 11:39
SignUpFragment.newInstance() is not a singleton pattern. It creates new object event time
– Samuel Robert
Nov 13 '18 at 11:39
SignUpFragment.newInstance() is not a singleton pattern. It creates new object event time
– Samuel Robert
Nov 13 '18 at 11:39
add a comment |
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%2f53279639%2finitializing-a-fragment%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