PROTECTED] On Behalf Of Max R. Yaffe
Sent: Monday, August 04, 2008 7:06 PM
To: users@lists.ironpython.com
Subject: [IronPython] Roadmap and updates
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
winforms controls.
Michael
Harry
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Max R. Yaffe
Sent: Monday, August 04, 2008 7:06 PM
To: users@lists.ironpython.com
Subject: [IronPython] Roadmap and updates
Note: I originally wrote this to Harry Pierson
be in the next release.
Thanks for the bug report and easy repro!
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sylvain
Hellegouarch
Sent: Tuesday, August 05, 2008 12:05 AM
To: [EMAIL PROTECTED]; Discussion of IronPython
Subject: Re: [IronPython] Roadmap
:) But if there was a strong
desire to see that we could consider it.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sylvain
Hellegouarch
Sent: Wednesday, August 06, 2008 1:53 PM
To: Discussion of IronPython
Subject: Re: [IronPython] Roadmap and updates
Hi,
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
I do not want to sound like I downplay the IP team work, not at all, but
the lack of visibility is not playing in their favor in my opinion.
Writing code is one thing, giving recurrent feedback is sometimes worth
more ;)
I wanted to reiterate that I don't downplay the IP team's work.
Giles Thomas wrote:
Curt Hagenlocher wrote:
Until then, you can always do what I understand Resolver Systems did:
save your forms as C# and manually copy the generated code into your
Python classes. The initialization code is so generic and
predictable that you don't have to do much more
Curt Hagenlocher wrote:
Until then, you can always do what I understand Resolver Systems
did: save your forms as C# and manually copy the generated code
into your Python classes. The initialization code is so generic and
predictable that you don't have to do much more than lop the
semicolons
On Tue, Aug 5, 2008 at 3:33 AM, Giles Thomas
[EMAIL PROTECTED] wrote:
Curt Hagenlocher wrote:
Until then, you can always do what I understand Resolver Systems did: save
your forms as C# and manually copy the generated code into your Python
classes. The initialization code is so generic and
to questions is always much easier :)
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sylvain
Hellegouarch
Sent: Tuesday, August 05, 2008 12:24 AM
To: Discussion of IronPython
Subject: Re: [IronPython] Roadmap and updates
I do not want to sound like I downplay
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
XAML is really just an XML-based object persistence format. It's not
directly tied to the display technology that it's mostly used for, which is
WPF or Windows Presentation Foundation. It's really WPF that should be
compared to Windows Forms -- you can use WPF without writing a single line
of
Max R. Yaffe 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
- 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
14 matches
Mail list logo
