MasDennis/Rajawali — pull request #162 by ToxicBakery (2012-09-21 21:57:08+00:00)
Title: Adding Fragment support round two

- Added v4 support lib
- Deprecated RajawaliActivity, new projects should now use RajawaliFragmentActivity for compliance purposes.
- Fixed project configuration so that parent projects do not require the v4 support library. Should they need it, no conflicts arise from having library in parent project.

This should not have the issues of the previous fragment support commit as I have resolved the base issue that the libs folder was improperly configured. Surprisingly it just needed to be at the bottom in the XML and presto parent projects no longer require the support library.

Should anyone have issue with this, before posting it as an issue, try updating to the latest ADK and updating your eclipse plugins. I believe duplicate libs in library project is an issue they recently added more fixes for.

New example usage:
```Java
import rajawali.RajawaliFragmentActivity;
import rajawali.renderer.RajawaliRenderer;
import android.content.Context;
import android.os.Bundle;

public class MainActivity extends RajawaliFragmentActivity {

@Override
public void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
final MyRenderer renderer = new MyRenderer(getApplicationContext());
renderer.setSurfaceView(mSurfaceView);
super.setRenderer(renderer);
}

class MyRenderer extends RajawaliRenderer {

public MyRenderer(Context context) {
super(context);
}

}
}
```