package com.oner.test;

import android.app.Activity;
import android.content.Context;
import android.os.Bundle;
import android.util.Log;
import android.view.LayoutInflater;
import android.view.View;
import android.view.ViewGroup;
import android.widget.BaseAdapter;
import android.widget.ListView;
import android.widget.TextView;

public class Adapter_testActivity extends Activity {
	private ListView mListView;

	/** Called when the activity is first created. */
	@Override
	public void onCreate(Bundle savedInstanceState) {
		super.onCreate(savedInstanceState);
		setContentView(R.layout.main);

		mListView = (ListView) findViewById(android.R.id.list);
		mListView.setAdapter(new AdapterTest((Context) this));
	}

	private class AdapterTest extends BaseAdapter {
		String[] items = { "a", "b", "c", "d", "e", "a", "b", "c", "d", "e",
				"a", "b", "c", "d", "e", "a", "b", "c", "d", "e", "a", "b",
				"c", "d", "e", "a", "b", "c", "d", "e", "a", "b", "c", "d", "e" };
		private Context mContext;
		private LayoutInflater inflater;

		public AdapterTest(final Context context) {
			mContext = context;
			inflater = LayoutInflater.from(mContext);
		}

		@Override
		public int getCount() {
			return items.length;
		}

		@Override
		public Object getItem(int position) {
			return items[position];
		}

		@Override
		public long getItemId(int position) {
			return position;
		}

		@Override
		public View getView(int position, View convertView, ViewGroup parent) {
			View v = convertView;
			ViewHolder holder;

			int type = getItemViewType(position);
			Log.d("Adapter test","setting type:"+type);
			if (v == null) {

				holder = new ViewHolder();
				if (type == 0) {
					v = inflater.inflate(R.layout.item_type_one, null);
					holder.txtOne = (TextView) v.findViewById(R.id.txt_one);
				}else if(type ==1){
					v = inflater.inflate(R.layout.item_type_two, null);
					holder.txtTwo = (TextView) v.findViewById(R.id.txt_two);
				}
				else {
					v = inflater.inflate(R.layout.item_type_three, null);
					holder.txtThree = (TextView) v.findViewById(R.id.txt_three);
				}
				holder.type = type;
				v.setTag(holder);
			} else {
				holder = (ViewHolder) v.getTag();
				Log.d("Adapter test", " holder ::" + holder);
			}
                        String item = (String) getItem(position);
			if (item != null) {
				if (type == 0) {
					holder.txtOne.setText(item);

				} else if(type ==1 ) {
					holder.txtTwo.setText(item);
				}else{
					holder.txtThree.setText(item);
				}

			}
			return v;

		}

		@Override
		public int getItemViewType(int position) {
                        String item = (String) getItem(position);
                        if(item.equals("a"))return =0;
			else if(item.equals("b"))return=1;
			else   (item.equals("c"))return=2;
		}

		@Override
		public int getViewTypeCount() {
			return 3;
		}

	}

	static class ViewHolder {
		public int type;
		TextView txtOne;
		TextView txtTwo;
		TextView txtThree;
		@Override
		public String toString() {
			return "ViewHolder [type=" + type + ", txtOne=" + txtOne
					+ ", txtTwo=" + txtTwo + ", txtThree=" + txtThree + "]";
		}

	}
}

For the purposes of this example the list items being inflated all contain the same TextView with just a different id. I'm sure you get the idea.
Here's what the layout for the items looks like in case you're feeling lazy.

The listView will keep a cache of every view type you give it. The trick to avoid problems is to make sure that you properly implement getViewItemType().

                @Override
		public int getItemViewType(int position) {
                        String item = (String) getItem(position);
                        if(item.equals("a"))return =0;
			else if(item.equals("b"))return=1;
			else   (item.equals("c"))return=2;
		}

A common mistake (my first mistake) was to implement that logic inside of getView instead of getItemViewType. Prior to getting one of the view types out of it's cache the listView will call getItemViewType for its cache lookup, so you need to make sure it knows how to do so. Also make sure that your getItemId return something other than just 0. This will also make sure things work smoothly.

In my example I determine the item type by looking at the data.
After that it's a simply matter of looking at the type to re-populate the viewHolder.

I hope this helps. Thanks to Simon and Noah for helping me work through the problems.

The way to fix it is to go to:
Window -> Preferences -> Java -> Editor -> Content Assist -> Advanced

And check the boxes labeled "Java Proposals" and hit Apply.

Thanks to dchimento for the answer.

Link to the question / answer here:

eclipse - autocomplete has stopped working with android sdk - Stack Overflow.

The Gmail Public Labels API | Android Developers Blog.

Check it out!
android-unused-resources - Android Unused Resource Detector - Google Project Hosting

android-unused-resources - Android Unused Resource Detector - Google Project Hosting.

It does have some imperfections. You'll sometimes get false positives. For example:
If you're getting a dynamic reference to a resource, this tool won't catch that (not that I would expect it to). But that's just a minor thing.
Anyway thanks @google!

++dave;: Cucumber for Android!.

How to Install Ice Cream Sandwich ROM on Motorola Droid X.

The problem is that it's difficult to control configuration changes in a fragment activity with multiple fragments when you need fragments to behave differently.

Here is my scenario:
I have a fragment activity that displays different fragments one at a time. The first fragment displayed is not allowed to change orientation, it must be locked in portrait.
However the next fragment I show in the same activity needs to be able to change on both portrait and landscape orientations.

Sure I could have just rewritten my code to have the other fragment start in a different activity but that's besides the point.

Anyway, what you have to do is make sure you can get configuration changes

Manifest code:

Activity code:

//
//
	@Override
	public void onConfigurationChanged(Configuration newConfig) {

		if(fragment!=null && fragment.isResumed()){
			//do nothing here if we're showing the fragment
		}else{
			setRequestedOrientation(Configuration.ORIENTATION_PORTRAIT); // otherwise lock in portrait
		}
		super.onConfigurationChanged(newConfig);
	}

The code above doesn't work by itself. You would think so but there's a problem where you never receive more onConfigurationChanged callbacks after you call setRequestedOrientation.

Luckily we can take advantage of the lifecycle of our fragment to help our activity get out of it's funk.
When our fragment resumes we can do the following:

Fragment code:

//
//
@Override
	public void onResume() {
		getActivity().setRequestedOrientation(ActivityInfo.SCREEN_ORIENTATION_FULL_SENSOR);
..}

I also make sure that my activity goes back to portrait mode if I exit this fragment.

//
//
	@Override
	public void onPause() {
		getActivity().setRequestedOrientation(ActivityInfo.SCREEN_ORIENTATION_PORTRAIT); // set the activity back to //whatever it needs to be when going back.
		super.onPause();
	}

This ensures that the activity can go back to being stubborn about orientation changes while letting an individual fragment take over configuration changes while it's active.
I hope this is helpful! cheers!

I'm real proud of this one and I hope you all enjoy it :)

https://market.android.com/details?id=com.qtcstation&feature=search_result#?t=W251bGwsMSwyLDEsImNvbS5xdGNzdGF0aW9uIl0.

cheers!

How To Properly Set SVN svn:externals Property In SVN Command Line.

Wanted to shout out to this post now that it's the third or fourth time I end up using it as reference while messing around w/ svn externals.

Thanks Artem Russakovskii!

During my web days I became very attached to Charles as part of my development toolset. It was a sad day when I discovered it was difficult to get it to work with either the emulator, much less a phone.

My first attempt circa Android Froyo (2.2) yielded no success. It's still doable but you have to root your phone and download an app from the market. It was a bit frustrating given that the Charles documentation didn't provide a lot of insight.

A second attempt led me to try again on two Motorola phones running 2.3. It turns out that it is now possible to set a proxy when connecting to a wifi access point!!!
Oh happy day!

This means that we can have our phone point to the IP address of the computer running Charles. And just like magic Charles works!

First let's look at how to configure a phone, since it's easiest. Then we'll look at getting the emulator to work.

Configuring your android device to work with Charles.

Step 1:
Connect to your Wifi.

(note that your device and your machine running Charles need to be on the same network)

Proxy settings on a Motorola Droid 3!!

Set the port to the IP of your machine running Charles. Set the port to 8888.

To access the menu above on existing wifi networks simply long click the name. New networks will present the option when connecting.

That's it! Charles should work.

Now onto the second part.

Configuring the Android emulator to work with Charles.

When starting an emulator you can do one of two things:

Using the command line you can do something like:

emulator -http-proxy localhost.:8888 -port 5554 -debug-proxy @Nexus

Optionally you can set the same emulator  in the run configurations in Eclipse.

Watch out!!! this technique only works with revision 13 and above of the Android SDK. r12 was broken and had a bug logged against it but has since been fixed in 13. Make sure you're up to date!

Eclipse run configuration settings.

Remember that you have to make sure the emulator starts using these additional arguments. If you already have one running these extra arguments will have no effect as the proxy will not be created.

Charles gotchas:

If your apps use https you may run into some problems with the server rejecting your certificates (or lack thereof).

I think there is a way to get Charles to provide a certificate on behalf of your device but I haven't figured that part out yet.

In the mean time I've had luck using the FakeX509TrustManager when creating an https connection from within my app.

private static SSLContext createEasySSLContext() throws IOException {
		try {
			SSLContext context = SSLContext.getInstance("TLS");
			context.init(null, new TrustManager[] { new FakeX509TrustManager() }, null);
			return context;
		} catch (Exception e) {
			throw new IOException(e.getMessage());
		}
	}

I hope this is helpful!