Hi Andrew, just to give you an idea about the Suneido/wxWidgets binding generation.
class wxStringMap
{
public:
wxStringMap();
virtual ~wxStringMap();
bool HasValueFor(const wxString& key) const;
const wxString& ValueFor(const wxString& key) const;
};
The generated wrapper wxsuneido.dll
extern “C” __declspec(dllexport) wxStringMap* wxStringMap_CTor() // CONSTRUCTOR
{
return new wxStringMap();
}
extern “C” __declspec(dllexport) void wxStringMap_DTor(wxStringMap* self) // DESTUCTOR
{
delete self;
}
extern “C” __declspec(dllexport) bool wxStringMap_HasValueFor(wxStringMap* self, const char* key)
{
return self->HasValueFor(key);
}
extern “C” __declspec(dllexport) const wxString* ValueFor(wxStringMap* self, const char* key)
{
return &(self->ValueFor(key));
}
And finally the GENERATED suneido class (a fraction)
wxStringMap = class
{
New()
{
,classptr = dll int* wxsuneido:wxStringMapCTor()
}
HasValueFor(key)
{
return dll bool wxsuneido:wxStringMap_HasValueFor(classptr, key)
}
ValueFor(key)
{
}
}
A few question and suggestions.
What about the Destructor ?
We should start with wxWiodgets 2.93 to avoid UNICODE / NON UNICODE problems. Does Suneido support Unicode strings ?
I think it would make sense to have a generic IntPtr 32/64 bit agnostic!
So I was wrong. We will have a DLL (wxSuneido.DLL) and wrapped classes)
Keep in mind that the gemeration of wxsuneido.dll as well as the suneido wrapper classes are generated. So probably so Suneido for wxWidgets is close than one mifgt think !
Next message will contain some thoughts about event-handling etc.
Would be nice to get some feedback .
Bjoern