On Mon, Nov 21, 2005 at 05:03:37PM +0100, Pierre Vaudrey wrote: > Art, > > Le 21 nov. 05 ? 14:27, Art Haas a ?crit : > > >Would you be interested in trying to get things working again under > > PyObjC? > I accept to try, but I'm not an expert neither in python nor in cocoa ! > > I can describe some of what will be involve in getting the port > > to work again. > I wait for your information.
Great! The first thing that needs to be done is to adjust all the 'import' statements. They need to look something like one of the following formats ... import PythonCAD.Generic.foo or from PythonCAD.Generic import foo Replace 'foo' above with the appropriate module, i.e point, segment, etc. Part of the reason the PyObjC port broke was the PythonCAD files were moved into a 'PythonCAD' subdirectory. This move was done to make PythonCAD be a better neighbor with other Python software that a user could install, such as Zope. By moving the files into a 'PythonCAD' subdirectory, the likelyhood of accidentally bringing in a PythonCAD module went down to essentially zero. Once all the 'import' statements have been adjusted, the next step will be fixing up the connect() messages so the PyObjC front-end will be correctly tied into the interface neutral back end. Let me know when you can start trying that and I'll explain what needs to be done. Thanks for looking at the Cocoa/PyObjC front end! Art Haas -- Man once surrendering his reason, has no remaining guard against absurdities the most monstrous, and like a ship without rudder, is the sport of every wind. -Thomas Jefferson to James Smith, 1822 _______________________________________________ PythonCAD mailing list [email protected] http://mail.python.org/mailman/listinfo/pythoncad
