----- "Curt Hagenlocher" <[EMAIL PROTECTED]> wrote: > The initialization code is so generic and predictable > that you don't have to do much more than lop the semicolons off the > ends of the lines.
Of course, you don't even have to do that as Python allows semicolons on the ends :) Another way to answer your question, Max, is that Mono supports WinForms too. We are working on a similar project, but I think IronPython + WinForms is where we will be for a few years. But, we aren't writing our base libraries in Python anymore, but C#. That way it still looks the same in Python, but the the other DLR languages can use them too. And you can use other alternate operating systems. I predict that there will be a huge number of DLR languages in the next few years, and your uses can switch languages while keeping the base libraries, if you write in C#. -Doug > Disclaimer: I am a Microsoft employee, but I have absolutely no inside > knowledge on any of the topics I've written on here other than those > related directly to IronPython. > > On Mon, Aug 4, 2008 at 7:06 PM, Max R. Yaffe < [EMAIL PROTECTED] > > wrote: > > > Note: I originally wrote this to Harry Pierson directly who asked that > I > post it publically. I hope it doesn't come off as too inflamatory. > > Harry - Thanks for the roadmap and the latest update. It clarifies a > particular issue that I'm having with deciding whether to adopt Iron > Python > and .Net for that matter. My particular application is a scientific > instrument control and data analysis package. It runs on Windows now > using > various older MS technologies (dating back to Windows 2.3!). It will > not > need to run from a web browser, mainly because of the requirements for > instrument control. The application is highly scripted using a dynamic > language of my own devising derived from Smalltalk and remarkably > similar to > Python. > > I had been looking at Qt 4.x+PyQt+Python 2.5 as an approach to > updating my > technology. However, I wanted to see what Microsoft had to offer. > WinForms > + Python seems to be the best fit for my technology because of the > need to > manipulate data tables and my desire to avoid the web. Silverlight > just > doesn't offer me any advantage and seems to be directed at pretty > pictures > and sounds. It also doesn't seem to handle the kinds of user/data > interaction I need. XAML also doesn't seem to offer any advantage for > my > code, or if it does, it certainly isn't clear what it might be other > than a > YAOUHD (yet another obese, unreadable HTML derivative). Your roadmap, > however, seems to deprecate WinForms. I'm worried that IronPython and > Microsoft are going to cut WinForms adrift just when I'm about to make > a > major investment in it. This might be the best approach for Microsoft > because it seems the "community" is mainly interested in pictures, > sounds, > and the web. But I need something more classical. > > I'd appreciate your comments and direction. > > Max Yaffe > Gamry Instruments, Inc. > > _______________________________________________ > Users mailing list > Users@lists.ironpython.com > http://lists.ironpython.com/listinfo.cgi/users-ironpython.com > > > _______________________________________________ > Users mailing list > Users@lists.ironpython.com > http://lists.ironpython.com/listinfo.cgi/users-ironpython.com _______________________________________________ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
