That's the idea. Just waiting for Peter to be ready (and for you all to bug test it).
I deliberated on this a bit. I modeled PdBase on Peter's Java implementation and Java has the built in thread support. There's currently no easy way to include thread safety in a "native C++" wrapper, so I decided to leave it out. When C++11 comes around, I'd go ahead and use std::mutex and add a compile flag to disable it.
That's a good point. I hadn't thought of it. I figured the folder layout would add my wrapper in the "cpp" folder in the libpd repo. You would only include "cpp" if you wanted it. I can't imagine people using both the Obj-C and C++ wrapper simultaneously ...
Yes and, as I noted on the CreateDigitalNoise forum, I don't want to force a singleton on users. If you want a singleton, it's easy enough to add a PdBase object inside of it. Also, creation order is sometimes an issue with singletons and, last, I don't want to have to explain singletons to newbies.
The ofxPd wrapper does this ... it's easy enough using Poco::Files/ofxFiles in OF, but requires string handling in plain C++ that seems redundant so I didn't bother. I suppose it could be added, make a pull request.
Yeah I saw that. Originally it was "openFile" then I noticed it was "openPatch" in both Java PdBase and the Processing lib. I like openPatch better and it matches the name most users of the higher-level wrappers will be used to.
Ok thanks. I can fix this.