Class heirarchy question

Question

This beginning of this post sounds similar to another of my recent posts. The end question is different. I'm just providing the atmosphere for the situation
I am coming from a c++ world into objective-c++/cocoa. I work for a company that sells static libraries to be used by other developers. Distributed with these libraries are, of course, the header files.
Currently, I am tasked with adding cocoa support to out library. I am using a subclass of NSOpenGL (we'll call it myNSGL) to render to. For proof of concept, I placed the rendering code in the instance methods of myNSGL, and called them from my controller class. This all works fine, able to render, and so on...
Now, I need to move this rendering code from the myNSGL class to inside our static library, abstracting it from the end user. This is where I have some questions.
In the class myNSGL, I am overriding the initWithFrame method. It creates an NSOpenGLPixelFormat then calls [super initWithFrame: pixelFormat:]. Fine, no problem. Here is the problem. I want to move all custom code (setup, rendering, etc...) inside the static library and only provide client developer with the h and mm files (In IB, they'll need to set the View's class to myNSGL). My question is, How can I initialize myNSGL's super class from inside my lib code? This call is vital, but I don't want it exposed to the client developer. Maybe this will help to visualize:
// Client Application code:
// client.h:
#include "myNSGL.h"
@interface ......{
myLib *_mylib;
IBOutlet myNSGL *_mynsgl;
// client.mm:
#import "client.h"
@implementation .......
- (id)init{
// use instance of my static lib.
_mylib->initializeNSGL();
// more calls to _mylib...
@end
// Static lib, lib.cpp:
#include "myNSGL.h"
class myLib{
private:
myNSGL* _mynsgl;
NSOpenGLContext* _context;
public:
void initializeNSGL()
GLuint attribs[] =
NSOpenGLPFAWindow,
NSOpenGLPFADoubleBuffer,
0
NSOpenGLPixelFormat* fmt = [[NSOpenGLPixelFormat alloc] initWithAttributes: (NSOpenGLPixelFormatAttribute*) attribs];
// PROBLEM!!! can't call anything on myNSGL's super.
[_windowRef [super initWithFrame:[_windowRef frame] pixelFormat: [fmt autorelease]]];
//////////////////////////////////////////

Answer 1

Your client developers shouldn't need any .mm files. All you should distribute are the headers and the library.
What you need to do is separate the headers into a public interface and a private interface. The public interface should contain all a client should ever need to see, plus instance data. The private interface is implemented as an Objective-C category. Then, your .mm files will import both the public and the private interfaces.
If you want to hide your instance data, that will be more work. You would have to use protocols or maybe dummy header files. You could maybe have a build stage that strips the data out of the headers and exports them into your framework. I don't know if that would work or not - probably not.