Duplicating Fragments vs. Layouts
up vote
0
down vote
favorite
I am having trouble determining whether to use fragments or layouts (probably CardView) to populate one of my activities.
I am creating an activity with what I believe could have either multiple layouts or multiple fragments Intended Activity Layout Here, each of which must be duplicatable onClick of a button. Each fragment or layout will contain a single, "match parent" width AutoCompleteTextView, as well as three EditText views and one TextView arranged side by side in one row below the AutoCompleteTextView. The first trio of EditText and the TextView will be visible when the activity loads. I will then need two buttons--one which creates a nearly duplicate row of EditText and TextView boxes (the only difference being that the TextView should numerically count up with each addition), and another button which creates a new instance of the whole fragment/layout (AutoCompleteTextView and the base trio of EditText and single TextView).
I neither expect nor want the code written for me, but am just curious on everyone's thoughts of whether I should proceed with trying to nest these fields into separate layouts or separate fragments. I'm not yet advanced enough to know how each one may affect performance when it comes time for the app to recall the text entered into each box, or how much of a coding headache any of the options could create if I choose the less intuitive option.
Thank you for your help!
-Yago
android 
android-fragments asked Nov 12 at 3:34
Yago
1
add a comment |
up vote
0
down vote
favorite
I am having trouble determining whether to use fragments or layouts (probably CardView) to populate one of my activities.
I am creating an activity with what I believe could have either multiple layouts or multiple fragments Intended Activity Layout Here, each of which must be duplicatable onClick of a button. Each fragment or layout will contain a single, "match parent" width AutoCompleteTextView, as well as three EditText views and one TextView arranged side by side in one row below the AutoCompleteTextView. The first trio of EditText and the TextView will be visible when the activity loads. I will then need two buttons--one which creates a nearly duplicate row of EditText and TextView boxes (the only difference being that the TextView should numerically count up with each addition), and another button which creates a new instance of the whole fragment/layout (AutoCompleteTextView and the base trio of EditText and single TextView).
I neither expect nor want the code written for me, but am just curious on everyone's thoughts of whether I should proceed with trying to nest these fields into separate layouts or separate fragments. I'm not yet advanced enough to know how each one may affect performance when it comes time for the app to recall the text entered into each box, or how much of a coding headache any of the options could create if I choose the less intuitive option.
Thank you for your help!
-Yago
android android-fragments asked Nov 12 at 3:34
Yago
1
As opinion based, this question is off topic. But I will say you're thinking of multiple fragments vs layouts wrong. The key concept of a layout is that it contains the logic surrounding the views, not just the views themselves. Its not just about doing duplicate UI elements- a layout include tag or a custom compound view is sufficient for that.
– Gabe Sechan
Nov 12 at 3:39
Thank you Gabe. If it wasn't evident, I'm new to coding and to this site. I'll make sure I review the rules for what content gets posted where before I post next time. Thank you for the correction. I'm digging into include tags now. Thanks!
– Yago
Nov 12 at 3:41
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I am having trouble determining whether to use fragments or layouts (probably CardView) to populate one of my activities.
I am creating an activity with what I believe could have either multiple layouts or multiple fragments Intended Activity Layout Here, each of which must be duplicatable onClick of a button. Each fragment or layout will contain a single, "match parent" width AutoCompleteTextView, as well as three EditText views and one TextView arranged side by side in one row below the AutoCompleteTextView. The first trio of EditText and the TextView will be visible when the activity loads. I will then need two buttons--one which creates a nearly duplicate row of EditText and TextView boxes (the only difference being that the TextView should numerically count up with each addition), and another button which creates a new instance of the whole fragment/layout (AutoCompleteTextView and the base trio of EditText and single TextView).
I neither expect nor want the code written for me, but am just curious on everyone's thoughts of whether I should proceed with trying to nest these fields into separate layouts or separate fragments. I'm not yet advanced enough to know how each one may affect performance when it comes time for the app to recall the text entered into each box, or how much of a coding headache any of the options could create if I choose the less intuitive option.
Thank you for your help!
-Yago
android android-fragments asked Nov 12 at 3:34
Yago
1
I am having trouble determining whether to use fragments or layouts (probably CardView) to populate one of my activities.
I am creating an activity with what I believe could have either multiple layouts or multiple fragments Intended Activity Layout Here, each of which must be duplicatable onClick of a button. Each fragment or layout will contain a single, "match parent" width AutoCompleteTextView, as well as three EditText views and one TextView arranged side by side in one row below the AutoCompleteTextView. The first trio of EditText and the TextView will be visible when the activity loads. I will then need two buttons--one which creates a nearly duplicate row of EditText and TextView boxes (the only difference being that the TextView should numerically count up with each addition), and another button which creates a new instance of the whole fragment/layout (AutoCompleteTextView and the base trio of EditText and single TextView).
I neither expect nor want the code written for me, but am just curious on everyone's thoughts of whether I should proceed with trying to nest these fields into separate layouts or separate fragments. I'm not yet advanced enough to know how each one may affect performance when it comes time for the app to recall the text entered into each box, or how much of a coding headache any of the options could create if I choose the less intuitive option.
Thank you for your help!
-Yago
android android-fragments android android-fragments asked Nov 12 at 3:34
Yago
1
asked Nov 12 at 3:34
Yago
1
asked Nov 12 at 3:34
Yago
1
asked Nov 12 at 3:34
Yago
1
asked Nov 12 at 3:34
Yago
1
1
As opinion based, this question is off topic. But I will say you're thinking of multiple fragments vs layouts wrong. The key concept of a layout is that it contains the logic surrounding the views, not just the views themselves. Its not just about doing duplicate UI elements- a layout include tag or a custom compound view is sufficient for that.
– Gabe Sechan
Nov 12 at 3:39
Thank you Gabe. If it wasn't evident, I'm new to coding and to this site. I'll make sure I review the rules for what content gets posted where before I post next time. Thank you for the correction. I'm digging into include tags now. Thanks!
– Yago
Nov 12 at 3:41
add a comment |
As opinion based, this question is off topic. But I will say you're thinking of multiple fragments vs layouts wrong. The key concept of a layout is that it contains the logic surrounding the views, not just the views themselves. Its not just about doing duplicate UI elements- a layout include tag or a custom compound view is sufficient for that.
– Gabe Sechan
Nov 12 at 3:39
Thank you Gabe. If it wasn't evident, I'm new to coding and to this site. I'll make sure I review the rules for what content gets posted where before I post next time. Thank you for the correction. I'm digging into include tags now. Thanks!
– Yago
Nov 12 at 3:41
As opinion based, this question is off topic. But I will say you're thinking of multiple fragments vs layouts wrong. The key concept of a layout is that it contains the logic surrounding the views, not just the views themselves. Its not just about doing duplicate UI elements- a layout include tag or a custom compound view is sufficient for that.
– Gabe Sechan
Nov 12 at 3:39
As opinion based, this question is off topic. But I will say you're thinking of multiple fragments vs layouts wrong. The key concept of a layout is that it contains the logic surrounding the views, not just the views themselves. Its not just about doing duplicate UI elements- a layout include tag or a custom compound view is sufficient for that.
– Gabe Sechan
Nov 12 at 3:39
Thank you Gabe. If it wasn't evident, I'm new to coding and to this site. I'll make sure I review the rules for what content gets posted where before I post next time. Thank you for the correction. I'm digging into include tags now. Thanks!
– Yago
Nov 12 at 3:41
Thank you Gabe. If it wasn't evident, I'm new to coding and to this site. I'll make sure I review the rules for what content gets posted where before I post next time. Thank you for the correction. I'm digging into include tags now. Thanks!
– Yago
Nov 12 at 3:41
add a comment |
active
oldest
votes
active
oldest
votes
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f53255634%2fduplicating-fragments-vs-layouts%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
As opinion based, this question is off topic. But I will say you're thinking of multiple fragments vs layouts wrong. The key concept of a layout is that it contains the logic surrounding the views, not just the views themselves. Its not just about doing duplicate UI elements- a layout include tag or a custom compound view is sufficient for that.
– Gabe Sechan
Nov 12 at 3:39
Thank you Gabe. If it wasn't evident, I'm new to coding and to this site. I'll make sure I review the rules for what content gets posted where before I post next time. Thank you for the correction. I'm digging into include tags now. Thanks!
– Yago
Nov 12 at 3:41