I got the solution in another forum:
http://iphonedevbook.com/forum/viewtopic.php?f=25&t=3192&sid=9cf79468b81a8fd6c9d9020958d33388

Basically, just add the glView outlet to the MainViewController instead of the AppDelegate.

What I do: I create an OpenGL ES application template and a Utility Application template. I copy the files EAGLView.m and h, and the five ES*renderer.* files from the Opengl project to the utility project.

I copy these lines from the OpenGl project to the Utility project: (in utilityAppDelegate.m)

- (void)applicationDidFinishLaunching:(UIApplication *)application {
…
[glView startAnimation];
}

- (void) applicationWillResignActive:(UIApplication *)application
{
[glView stopAnimation];
}

- (void) applicationDidBecomeActive:(UIApplication *)application
{
[glView startAnimation];
}

- (void)applicationWillTerminate:(UIApplication *)application
{
[glView stopAnimation];
}

- (void)dealloc {
…
[glView release];
…
}
And in the utilityAppDelegate.h I add:

@class EAGLView;
EAGLView *glView;
@property (nonatomic, retain) IBOutlet EAGLView *glView;
I go to the view’s identity inspector, and change the class identity to EAGLview.

I open the mainview.xib and mainwindow.xib and drag the app_delegate from the mainwindow.xib, to be able to connect the glView outlet to the view. (Don’t know if this is the way to do it, but that’s the only way I could connect the glView variable to the view)

When I build and run, the multi colored square show up on the screen, but it does not animate!

When I debug, the glView variable is 0 in applicationDidFinishLaunching, and the startAnimation is not called. I suspect this has something to to with the way the outlet is connected to the view? Probably not connected.

What is missing? What have I done wrong?

Thank you!

The view needs the handles for the color and depth buffers. The FrameBuffer structure is just a convenient way of packing those two handles. So yes, you have the right idea and they’re all contained in the view, so they’re not passed around anywhere.

Why have a returned index for the respective frame buffers. Aren’t the frame buffers just properties of the view object? That way, each view should “know” it’s own frame buffer. Why pass it up and down the hierarchy?

Thanks a lot Noel!

Stuart

If anyone is interested, the app is “Lulav Wizard”, a simulator and educational tool for “shaking the lulav” for the Jewish holiday of Sukkot.

itms://itunes.apple.com/WebObjects/MZStore.woa/wa/viewSoftware?id=331224871&mt=8&s=143441

Noel, if you’re interested, I can probably get you a “free” code.

Thanks for posting anyway.

You can post example source plzz ??

Thnx.

That’s just a performance recommendation or best practice from Apple, not a violation of the expected user interface for example. So go for it!

Since this violates Apple’s published “best practices” (mixing OpenGLES and UIKit), do you think it may get rejected from the Application Store?

Anyway you can post a template or example?

Thanks again!

I would love if you could put up a very basic demo project , I think it would be awesome for me, since I do learn better with examples.

Again, thank you very much!

_NG