<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; "><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Here are the slides from my presentation:</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><BR class="khtml-block-placeholder"></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><A href="http://brianray.chipy.org/pyincppchipy/">http://brianray.chipy.org/pyincppchipy/</A><FONT class="Apple-style-span" size="7"><SPAN class="Apple-style-span" style="font-size: 37.8px;"><B></B></SPAN></FONT></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><BR class="khtml-block-placeholder"></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">BTW, Gulp is going well. I am currently making project files for: Gnu configure/make, xcode 2.1, M$ VC7. (Maybe Eclipse CDT and Codewarrior) They build a dylib/dll which then can be used in the same environment instead of linking to Python directly. The advantage is Gulp handles things in a very OO C++ way with templates and what not. So, If a developer want to develop simultaneously in Python and C++, Gulp will help. And they do not need to spend as much time worrying about memory management or type juggling as if they were using the Python API. Plus I am trying some things regarding packaging. </DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><BR class="khtml-block-placeholder"></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Brian</DIV></BODY></HTML>