Sean’s right, it does look a lot like C++. Still, it enabled Rick to build a Linux-native SHP to SDF conversion tool when the alternative (actual C++) would have been painful. Good to see it being used!
-J
Sean’s right, it does look a lot like C++. Still, it enabled Rick to build a Linux-native SHP to SDF conversion tool when the alternative (actual C++) would have been painful. Good to see it being used!
-J
This entry was posted on December 3, 2008, 9:42 am and is filed under FDO, Open Source. You can follow any responses to this entry through RSS 2.0. Both comments and pings are currently closed.
Comments are closed.
Fusion theme by digitalnature | powered by WordPress
Entries (RSS) and Comments (RSS) ^
#1 by rbranson on December 3, 2008 - 12:56 pm
I’m sure it would have helped if I was actually a Python developer :) It does get the job done though, and, much agreed that it’s a much more rapid approach than C++, especially for something that doesn’t require the same level of “bulletproofness.” I am implementing some stuff on the MapGuide API using JRuby (Ruby on Java VM), which has turned out to be decent with some help from a few wrapper classes. Ultimately I would like to have the time to dust off the old C++ chops and put together an FDO SWIG port for Ruby. The only problems I’ve had so far with Python/SWIG/FDO out of the box is that there’s no reasonable way to access the IoStream classes.