How to make a nice conclusion unknown number of TextView?

I'm writing an application that parses the website. The site has a clickable tags, which I also scab. I need to bring them to my app in anroid and that they were clickable, you need to bring them one by one in TextView. What layout to use to programmatically could bring him an unknown amount of Textviews and below when you reach the end of the row TextView postponed(as in LinerLayout they just go out of sight)
April 7th 20 at 15:50
5 answers
April 7th 20 at 15:52
wrap the LinearLayout in a ScrollView
although it is wise to use RecyclerView
April 7th 20 at 15:54
You can do everything in one TextView and put each URLSpan Daegu.
April 7th 20 at 15:56
All you need is a RecyclerView. Put it where you want to display your TextView., to scroll he will, to do nothing. Fill can be either a separate layout file with your TextView and you can use standard android simple_list_item1 - then id of your TextView будет@android:id/text1.
April 7th 20 at 15:58
Try Element Chips, they are created for it.

April 7th 20 at 16:00
and that they were clickable, you need to bring them one by one in TextView.

Don't do it! For this there is a Span if you output text in the form of a large number of TextView it will slow down, fail and fall, and if not, still not terribly rational.
You here:
Firstly it is not clear what will cause these brakes, glitches and drop? Secondly, what is not rational?
I don't remember any intelligent application on my phone where you would use the ClickableSpan, but RecyclerView - almost every. ViewHolder keeps as much item as you need, so no brakes, regardless of the number of lines is not expected. Plus with RecyclerView always remain extensive customization - you can then attach the image and make each element more visible. - Otho.Cormi commented on April 7th 20 at 16:03
@joseph_Cole, As I understand it, he doesn't need a list. Man, in fact, want to display text at the same time, some words should be clickable. What does the recycler?
Glitches and downs, theoretically, can be caused by lack of memory because of the huge number of TextView objects that are displayed simultaneously on the screen. - Joy.Adams commented on April 7th 20 at 16:06
@Fabiola_Langworth7, it's just ridiculous how many there are in your TextView? A million? Even if there a million is still slow and will not fly for reasons described above.
But it was requested by the author - "to programmatically could bring him an unknown number of TextView", and that's what he needs may be different of course, but then you need to formulate questions better. - Otho.Cormi commented on April 7th 20 at 16:09

Find more questions by tags Android