Re: [dotnet-130] native .NET graphics performance issues
| From: | Chris J. |
| Sent on: | Thursday, September 10, 2009, 12:23 AM |
John,
I hate that we live in a world where this is necessary, but it just occurred to me that if some idiot attends the meetup, drinks too much and gets in a wreck on the way home, you and Andy, as hosts, and I, as organizer, could be held liable. I think we need to:
a) make sure anyone drinking is older than 21,
b) limit attendees' beer consumption
Any thoughts?
Chris Judge
I hate that we live in a world where this is necessary, but it just occurred to me that if some idiot attends the meetup, drinks too much and gets in a wreck on the way home, you and Andy, as hosts, and I, as organizer, could be held liable. I think we need to:
a) make sure anyone drinking is older than 21,
b) limit attendees' beer consumption
Any thoughts?
"The nationalist not only does not disapprove of atrocities committed by his own side, but he has a remarkable capacity for not even hearing about them." ��� George Orwell, From the essay "Notes on Nationalism" (1945)
From: John Nagle <[address removed]>
To: [address removed]
Sent: Tuesday, September 8,[masked]:52:14 PM
Subject: RE: [dotnet-130] native .NET graphics performance issues
From: [address removed] [mailto:[address removed]] On Behalf Of Chris Judge
Sent: Tuesday, September 08,[masked]:28 PM
To: [address removed]
Subject: [dotnet-130] native .NET graphics performance issues
If anyone is interested at the next meetup, I'll be talking about
limitations in .NET graphics (WPF and WinForms). To highlight these problems, I
have uploaded a few projects (all names begin with "Sierpinski").
In a nutshell, if you need to generate graphical output over time and that output is in the form of dots rather than lines, rectangles, ellipses, etc., WPF is absolutely not the way to go. Winforms will work, but you may have to use the Windows API depending on your need to zoom in and out.
These projects also use:
--
Please Note: If you hit "REPLY", your message will be sent to everyone on this mailing list ([address removed])
This message was sent by Chris Judge ([address removed]) from The Austin .NET Meetup.
To learn more about Chris Judge, visit his/her member profile
To unsubscribe or to update your mailing list settings, click here
Meetup Support: [address removed]
632 Broadway, New York, NY 10012 USA
--
Please Note: If you hit "REPLY", your message will be sent to everyone on this mailing list ([address removed])
This message was sent by John Nagle ([address removed]) from The Austin .NET Meetup.
To learn more about John Nagle, visit his/her member profile
To unsubscribe or to update your mailing list settings, click here
Meetup Support: [address removed]
632 Broadway, New York, NY 10012 USA
From: John Nagle <[address removed]>
To: [address removed]
Sent: Tuesday, September 8,[masked]:52:14 PM
Subject: RE: [dotnet-130] native .NET graphics performance issues
Chris...this will be very interesting for us...we're working
on a project that will be using, at various phases, WPF and GDI+ to
render 2048x1536 bitmaps.
On a related note, Andy will be showing our FastBitmap class
(which gives you a quicker getpixel/setpixel), along with our AppWrapper
(enforces single instance, catches unhandled exceptions, and some other nice
things), and possibly our TimeKeeper class, essentially nano-second precise
DateTime for doing high-precision timing.
I will be showing some fun stuff with Adobe Flex
interoperating with ASP.net web services. It's a really interesting way to
leverage the deployability of Flash with the ease of .Net
development.
This is shaping up to be a great meetup!
-John
From: [address removed] [mailto:[address removed]] On Behalf Of Chris Judge
Sent: Tuesday, September 08,[masked]:28 PM
To: [address removed]
Subject: [dotnet-130] native .NET graphics performance issues
In a nutshell, if you need to generate graphical output over time and that output is in the form of dots rather than lines, rectangles, ellipses, etc., WPF is absolutely not the way to go. Winforms will work, but you may have to use the Windows API depending on your need to zoom in and out.
These projects also use:
- thread synchronization
- calling unmanaged code (the Windows API)
- mathematical optimization
--
Please Note: If you hit "REPLY", your message will be sent to everyone on this mailing list ([address removed])
This message was sent by Chris Judge ([address removed]) from The Austin .NET Meetup.
To learn more about Chris Judge, visit his/her member profile
To unsubscribe or to update your mailing list settings, click here
Meetup Support: [address removed]
632 Broadway, New York, NY 10012 USA
--
Please Note: If you hit "REPLY", your message will be sent to everyone on this mailing list ([address removed])
This message was sent by John Nagle ([address removed]) from The Austin .NET Meetup.
To learn more about John Nagle, visit his/her member profile
To unsubscribe or to update your mailing list settings, click here
Meetup Support: [address removed]
632 Broadway, New York, NY 10012 USA
People in this
group are also in:
-
CocoaCoders
1,035 iOS, Mac, Swift & Cocoa Coders
-
AzureAustin: For Azure users in Austin, TX and World Wide!
1,387 Azurians
-
Refresh Austin (Web Design & Developer Meetup)
4,889 Refreshers
-
Bleeding Edge Web
4,155 Edgers
-
Austin Startup Meetup
5,877 Entrepreneurs
-
Austin PHP Meetup
2,231 PHP Developers