Static Table vs Dynamic Prototype for a Table with many (100+ items)
I'm relatively new to iOS and Xcode, so please forgive if the question seems stupid. I just couldn't get an answer through extensive searching.
I'm building an app that requires a tableView with 100+ items split into 6 or 7 sections, each list item with a checkbox accessory. As I understand, for my needs, a static table is adequate. However, with such a large list, would it be expensive in terms of resources compared to a dynamic prototype, where the program recycles the table slots?
ios xcode dynamic static tableview
asked Nov 13 '18 at 21:36
Jeremy Hao-Yang ChoiJeremy Hao-Yang Choi
174
add a comment |
I'm relatively new to iOS and Xcode, so please forgive if the question seems stupid. I just couldn't get an answer through extensive searching.
I'm building an app that requires a tableView with 100+ items split into 6 or 7 sections, each list item with a checkbox accessory. As I understand, for my needs, a static table is adequate. However, with such a large list, would it be expensive in terms of resources compared to a dynamic prototype, where the program recycles the table slots?
ios xcode dynamic static tableview
asked Nov 13 '18 at 21:36
Jeremy Hao-Yang ChoiJeremy Hao-Yang Choi
174
add a comment |
I'm relatively new to iOS and Xcode, so please forgive if the question seems stupid. I just couldn't get an answer through extensive searching.
I'm building an app that requires a tableView with 100+ items split into 6 or 7 sections, each list item with a checkbox accessory. As I understand, for my needs, a static table is adequate. However, with such a large list, would it be expensive in terms of resources compared to a dynamic prototype, where the program recycles the table slots?
ios xcode dynamic static tableview
asked Nov 13 '18 at 21:36
Jeremy Hao-Yang ChoiJeremy Hao-Yang Choi
174
I'm relatively new to iOS and Xcode, so please forgive if the question seems stupid. I just couldn't get an answer through extensive searching.
I'm building an app that requires a tableView with 100+ items split into 6 or 7 sections, each list item with a checkbox accessory. As I understand, for my needs, a static table is adequate. However, with such a large list, would it be expensive in terms of resources compared to a dynamic prototype, where the program recycles the table slots?
ios xcode dynamic static tableview
ios xcode dynamic static tableview
asked Nov 13 '18 at 21:36
Jeremy Hao-Yang ChoiJeremy Hao-Yang Choi
174
asked Nov 13 '18 at 21:36
Jeremy Hao-Yang ChoiJeremy Hao-Yang Choi
174
asked Nov 13 '18 at 21:36
Jeremy Hao-Yang ChoiJeremy Hao-Yang Choi
174
asked Nov 13 '18 at 21:36
Jeremy Hao-Yang ChoiJeremy Hao-Yang Choi
174
asked Nov 13 '18 at 21:36
Jeremy Hao-Yang ChoiJeremy Hao-Yang Choi
174
174
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
No stupid questions.
You should definitely use dequeued cells “recycled” as you say instead of static.
It’s best practice.
It’s trivially easy to do, with registering a nib for reuse.
Good article on this https://www.hackingwithswift.com/example-code/uikit/how-to-register-a-cell-for-uitableviewcell-reuse.
answered Nov 13 '18 at 21:53
WoodstockWoodstock
12.7k1261100
1
Great, thanks! and thanks for the website too, going to read up a lot.
– Jeremy Hao-Yang Choi
Nov 13 '18 at 22:40
My pleasure. Also check this out bro natashatherobot.com/…
– Woodstock
Nov 13 '18 at 23:05
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%2f53289864%2fstatic-table-vs-dynamic-prototype-for-a-table-with-many-100-items%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
No stupid questions.
You should definitely use dequeued cells “recycled” as you say instead of static.
It’s best practice.
It’s trivially easy to do, with registering a nib for reuse.
Good article on this https://www.hackingwithswift.com/example-code/uikit/how-to-register-a-cell-for-uitableviewcell-reuse.
answered Nov 13 '18 at 21:53
WoodstockWoodstock
12.7k1261100
1
Great, thanks! and thanks for the website too, going to read up a lot.
– Jeremy Hao-Yang Choi
Nov 13 '18 at 22:40
My pleasure. Also check this out bro natashatherobot.com/…
– Woodstock
Nov 13 '18 at 23:05
add a comment |
No stupid questions.
You should definitely use dequeued cells “recycled” as you say instead of static.
It’s best practice.
It’s trivially easy to do, with registering a nib for reuse.
Good article on this https://www.hackingwithswift.com/example-code/uikit/how-to-register-a-cell-for-uitableviewcell-reuse.
answered Nov 13 '18 at 21:53
WoodstockWoodstock
12.7k1261100
1
Great, thanks! and thanks for the website too, going to read up a lot.
– Jeremy Hao-Yang Choi
Nov 13 '18 at 22:40
My pleasure. Also check this out bro natashatherobot.com/…
– Woodstock
Nov 13 '18 at 23:05
add a comment |
No stupid questions.
You should definitely use dequeued cells “recycled” as you say instead of static.
It’s best practice.
It’s trivially easy to do, with registering a nib for reuse.
Good article on this https://www.hackingwithswift.com/example-code/uikit/how-to-register-a-cell-for-uitableviewcell-reuse.
answered Nov 13 '18 at 21:53
WoodstockWoodstock
12.7k1261100
No stupid questions.
You should definitely use dequeued cells “recycled” as you say instead of static.
It’s best practice.
It’s trivially easy to do, with registering a nib for reuse.
Good article on this https://www.hackingwithswift.com/example-code/uikit/how-to-register-a-cell-for-uitableviewcell-reuse.
answered Nov 13 '18 at 21:53
WoodstockWoodstock
12.7k1261100
edited Nov 13 '18 at 21:58
answered Nov 13 '18 at 21:53
WoodstockWoodstock
12.7k1261100
answered Nov 13 '18 at 21:53
WoodstockWoodstock
12.7k1261100
answered Nov 13 '18 at 21:53
WoodstockWoodstock
12.7k1261100
12.7k1261100
1
Great, thanks! and thanks for the website too, going to read up a lot.
– Jeremy Hao-Yang Choi
Nov 13 '18 at 22:40
My pleasure. Also check this out bro natashatherobot.com/…
– Woodstock
Nov 13 '18 at 23:05
add a comment |
1
Great, thanks! and thanks for the website too, going to read up a lot.
– Jeremy Hao-Yang Choi
Nov 13 '18 at 22:40
My pleasure. Also check this out bro natashatherobot.com/…
– Woodstock
Nov 13 '18 at 23:05
1
1
Great, thanks! and thanks for the website too, going to read up a lot.
– Jeremy Hao-Yang Choi
Nov 13 '18 at 22:40
Great, thanks! and thanks for the website too, going to read up a lot.
– Jeremy Hao-Yang Choi
Nov 13 '18 at 22:40
My pleasure. Also check this out bro natashatherobot.com/…
– Woodstock
Nov 13 '18 at 23:05
My pleasure. Also check this out bro natashatherobot.com/…
– Woodstock
Nov 13 '18 at 23:05
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%2f53289864%2fstatic-table-vs-dynamic-prototype-for-a-table-with-many-100-items%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
