[EMAIL PROTECTED] wrote: > Hi all, > > Departing from the recent thrilling discussion, I pose a geogeek question: To > SWIG or not to SWIG? > > I contribute to the Virtual Terrain Project (VTP, www.vterrain.org). The > applications are built on GDAL, PROJ.4, wxWidgets, and OSG. Each of these > has SWIG python bindings or similar, with wxPython being key. The ultimate > goal: script data processing, build python GUIs to interact with the VTP API, > and embed an interactive interpreter (pyshell/pycrust?) to control the scene > graph of the 3d visualization tool. > > My initial experiments with swig to wrap a few of the VTP objects was pretty > painless... so I wonder, was this a honeymoon? Hopefully, y'all with > experience writing or using swig bindings or other c/py framework can weigh > in. Rants, gotchas, resources, whatever great or token wisdom will be > sincerely appreciated. > > Thanks! > > Nino
SWIG's bindings got a lot faster recently -- just as fast as anything you could write yourself -- but it's a cumbersome abstraction unless you really need to support many different languages. I'm interested in idiomatic Python programming, so I'm ignoring SWIG and just using Python's C API or Cython. Sean _______________________________________________ Geowanking mailing list [email protected] http://lists.burri.to/mailman/listinfo/geowanking
