Create dynamic tables in android. New view vs inflater

Question

I would like to create dynamic table in android (custom number of rows and columns). Minimum sdk is 3.0

I suppose to crate it via one of 2 ways:

1) via creating new TextView

TableRow tr = ....;

for ( i = 0; i < NumOfRows .... ) {
    TextView tv = new TextView(this);
    tv.setLayoutParams(...);
    tv.setText("Text I wanna to see");
    tr.add(tv);
}

2) via inflater

LayoutInflater inflater = (LayoutInflater) this.getSystemService(Context.LAYOUT_INFLATER_SERVICE);

for ( i = 0; i < NumOfRows .... ) {
    TextView tv = (TextView) mInflater.inflate(R.layout.my_cell_layout, null, false)
                    .findViewById(R.id.my_cell_item);
    tv.setText("Text I wanna to see");
    tr.add(tv);
}

3) Your way :)

What is faster? What should I select?enter code here

Answer 1

It's all as per your requirement that which is better.

from link http://www.aslingandastone.com/2010/dynamically-changing-android-views/

Because layouts can be created either in XML or in code, you could probably make do without ever having to do dynamic XML layout loading. That being said, there are some clear advantages as to why I think one may want to do so:

Code cleanliness. Doing anything more than basic layouts in code can get very messy, very fast. Code re-use. It’s extremely easy to inflate an XML layout into a specified view with one or two lines of code Performance. Creating the objects necessary for an in-code layout leads to unnecessary garbage collection. As per the Android Designing for Performance article, “avoid creating short-term temporary objects if you can.” Attribute availability. Defining Views in an XML layout exposes attributes that are not always available by object methods.

* Possible disadvantages:

It make take more time to do an XML layout versus defining the layout in code, especially if there are only one or two interface elements that need to be changed. *

Answer 2

To find out which is faster, implement both methods and use the method profiling utility, TraceView. That being said, its easier to maintain an XML file when making changes than it is to modify code. So, if I were you, I would prefer technique #2.