A Message from POCO Community

Hello,

I’ve heard you guys are in process of adopting POCO, so I wanted to drop a line, say hi and compliment your good taste :wink:

Seriously now, POCO is a breath of fresh air in the C++ world. I blogged about it when we switched to boost license http://pocoproject.org/poco/blog/?p=4.

At this point, I can not offer much, because we are overwhelmed keeping up with our own stuff. What I can do is give you some pointers. I’ve seen you are looking for documentation contribution and you’re not keen on doxygen/javadoc. Welcome to the club. By now, you must have seen what comments look like in POCO - we also have the generator that actually works and emits HTML documentation.

Code is available from SVN sandbox:

http://poco.svn.sourceforge.net/viewvc/poco/sandbox/PocoDoc/

PocoDoc depends on CppParser (also available from sandbox). Here’s what the result looks like:

http://pocoproject.org/poco/docs/

Recently, I have POCO-ified HARU PDF library (http://poco.svn.sourceforge.net/viewvc/poco/sandbox/PDF/) and we are hoping that someone may step in and contribute PocoDoc PDF generator.

Also, you guys may want to talk to Guenter - he’s a big time Mac fan. Since you appear to be Mac-oriented crowd, maybe it would make sense to have project files for XCode included in POCO. However, bear in mind that things like that do require a commitment - I currently maintain 3 versions of Visual Studio solution files and it’s a nightmare.

Anyway, I’ll hang around and try to stay in touch.

Best regards,

Alex

Hi Alex,

it’s great to hear from you -

yes, we’ve been considering POCO for a while now and are really excited by what we see. I’ve always felt there was a missing link in developing cross platform c++ applications and for us this seems like an ideal fit with what we are doing, which is cross platform audio visual environment for artistic tinkering. We’ve actually started to develop addons (udp, tcp, directory listing, etc) and when we saw what poco could do, we realized it would simplify things alot to have it integrated into the core.

It’s something we are actively pursuing for the next release (after we get the one we are working on out the door). I’m already using it in one project this month for networking and xml parsing, and various OF folks have started to use it for their research, like:

http://code.google.com/p/cppglue/

Whenever I show to people whose opinion I really trust they are all impressed - a very good sign.

Also thanks much for the info about pocoDoc, it looks really good! I am happy to give it a try. Theo and I are not really developers by background (we are artists who became programmers) so it’s good to learn about the things people do to manage projects, help people get into them, etc, and (we are starting to realize) the tools that help folks manage all the releases and builds.

Anyway, all of this is to say thanks! and we look forward to getting OF + POCO soon. I think it’s going to open alot of doors for creative hacking.

take care!
zach

Hi Alex!

xcode project files for POCO and/or a universal poco framwork would be awesome! I’ve gotten poco to work with xcode, but it’s a bit tedious and I’m sure it could be done much smoother. I understand that it would require some work to maintain it though… I’ll see if I can get hold of Guenter. I’d be happy to help out and test xcode releases…

Hi Alex!

Definitely the option to easily compile the library as a universal binary. That would be great - it took me quite a while to figure out how to change the files to build the library for PPC (ie non-native arch type)

I documented the process here:
http://forum.openframeworks.cc/t/event-handling-±merging-of-with-poco-c++/408/18

Some sort of OSX-Universal flag or even OSX-PPC and OSX-i386 would make things a lot easier. Once I had the two libs (i386 and ppc) it was pretty straightforward to combine them into a universal binary using lipo.

But these are small things :smiley: - it works great and we are very excited about integrating poco more tightly into openFrameworks as we work on the next release.

Thanks for making such a super library!
Theo

[quote author=“theo”]
Thanks for making such a super library!
Theo[/quote]

Well, Guenter is really the one responsible for it.

As far as ideas and contributions you guys have, we will be happy to have them in POCO. The best way to submit them is through sourceforge tracker (patches/feature requests).

Alex