Matthew Podwysocki's Blog

So far in this series, I’ve covered a bit about what first class events are in F# and how you might use them.  In the first post, we looked at what a first class events mean and some basic combinators in order to compose events together.  In the second post, we looked at how we might create events and publish them to the world through classes.  And in the third post I talked about how to manage the lifetime of a subscription.  Last time, I corrected my usage of the old create function and instead to use the Event class to create, trigger and publish events.  This time, we’ll look at how we can use first class events inside Async Workflows in order to do such items as tracking state.

So far in this series, I’ve covered a bit about what first class events are in F# and how you might use them.  In the first post, we looked at what a first class events mean and some basic combinators in order to compose events together.  In the second post, we looked at how we might create events and publish them to the world through classes.  And in the previous post, I talked about how to manage the lifetime of a subscription.  This time, I want to go over creating events again to show how it will be going forward in Visual Studio 2010 and beyond.

So far in this series, I’ve covered a bit about what first class events are in F# and how you might use them.  In the first post, we looked at what a first class events mean and some basic combinators in order to compose events together.  In the second post, we looked at how we might create events and publish them to the world through classes.  This time, let’s look at how we might manage the lifetime of a given event subscription.  Before we begin, let’s get caught up to where we are today:

In the previous post on first class composable events in F#, we talked mostly about the underlying types and the basic composition that you can achieve through the Event module.  By using the basic combinators of map, filter, partition, etc, we are able to create some rather rich scenarios for first class events.  We’ve already shown what we can do with existing events off of such things as Windows Forms applications, but how about we create our own?

Following last month’s great presentation by Chris Williams on Naked JavaScript, we’re continuing our dive into JavaScript, and we continue this time with a look into jQuery UI.  This month, we have Richard Worth, the Release Manager for jQuery UI, to talk with us about both jQuery UI and the jQuery UI CSS Framework.  Below are the details:

If you’ve been following me on Twitter lately, I’ve been playing a lot lately with event based programming in both F# events as well as the Reactive Framework (RX).  Today, I’m going to start a series in event processing, starting from the elementary concept of first class events in F#.

You may have noticed that in the past that I’ve talked extensively about Spec#, an object-oriented .NET language based upon C# with contract-first features as well as a non-null type system.  This project has not only been covered by myself, but also my CodeBetter compatriot, Greg Young, and by the illustrious Tony Hoare at QCon London during his “Null References: The Billion Dollar Mistake” presentation.  This project, after gaining momentum in the .NET world, has now been made part of .NET 4.0 as Code Contracts for .NET.

There has been a lot of talk going around involving the Microsoft Worldwide Partner Conference 2009, but another event, largely overshadowed, was the 10th annual Microsoft Research Faculty Summit.  During this summit, Tony Hey, the Microsoft External Research Vice President, announced the release of two tools to help transform research in the academic world, Project Trident and Dryad with DryadLINQ, which you can watch here.  These tools are available freely to academic researchers and scientists and can be downloaded here.  So, what are they and why should we care?