On Jun 21, 1:36 pm, [EMAIL PROTECTED] wrote: > Which tools would you use? I want the interface design to be as easy > and fast as possible, all ideology aside. I'm considering > eitherIronPython+Visual Studio or Python+Qt -- but I'm open for other > suggestions. > > Visual Studio seems to offer the easiest solution, but isIronPython > stable enough? How easy is theIronPython/Visual Studi integration? > What aboutIronPythonStudio?
IronPython 1 is very stable. IronPython 2 is still in beta. The IronPython 1 and Visual Studio 2005 integration (via the SDK) is pretty good. Personally I think IronPython Studio is a bit immature - and I don't like the way it generates Python code anyway. The Windows Forms designer in Visual Studio is pretty good. Unfortunately better than most GUI designers available for other Python compatible toolkits. I still don't like the designer for creating UIs with fluid layouts - I don't think it handles them very well. In my opinion, the best way to use the designer is to actually generate C# rather than IronPython code. You can then subclass from IronPython and implement the programmed behaviour - using the designer only for the UI layout. Windows Forms is very cross platform now with Mono. Mono now has full coverage of the .NET 2.0 winforms APIs. Michael Foord http://www.ironpythoninaction.com/ -- http://mail.python.org/mailman/listinfo/python-list
