code monkey

I just got through watching Miguel's presentation as FOSDEM. If you've never seen Miguel give a presentation, you really should watch one. He has all the excitement and showmanship of Steve Jobs, only it's completely natural and spontaneous instead of super-polished. (As evidenced by the fact that things don't always go right.) I had suggested he appear on The Daily Show as "equal time" after Bill Gates pimped Vista on it. I don't really know what the target audience is at FOSDEM, but this is a great talk for Windows developers interested in porting their apps to Mono. There's some history and background for the first ten minutes, but then he moves into how to use MoMA on your applications, the types of things it detects, and what they mean. After that, it gets even more interesting (to me) as Miguel breaks down the data we have received from MoMA. He provides statistics about what types of apps people are running in the wild, how many we suppor

A few posts ago, I showed some images of what a Reversi project looked like running on .Net, Mono on Windows, and Mono on Linux. If you want to follow along at home, here's a walkthrough to running the game. First, you need to go to CodeProject and download the game . I just downloaded the executable. Extract it to somewhere. Mono on Windows Download the latest Mono setup package from the Mono project downloads page . Currently, the latest version is 1.2.3.1. Run the setup program. GTK# and XSP are optional. GTK# is for application using the GTK toolset. XSP is for running webforms. Since I'm only interested in Winforms, I generally do not install these. This should create a Mono 1.2.3.1 for Windows group in your start menu. In it, choose the "Mono-1.2.3.1 Command Prompt" program. Navigate to where you placed the executable. Run it using: "mono Reversi.exe" Now you're not only losing Reversi to the computer, you are losing to the computer runni

jackson had a good idea for today, and I thought I'd copy it. Since it's a holiday, I hacked on something other than Mono today. Before I worked on Mono, my open source community of choice was Jabber (fun fact: I did that webpage as well). Back then, I released a Jabber server written in VB.Net. One thing that I have laying around that I've never released is an XMPP client. Since it's written in VB.Net and uses the ToolStrip and MenuStrip controls, I figured I'd try to port it to Mono as another test case for the *Strip stuff. I initially thought our VB runtime was missing too much and started rewriting it in C#. As I realized how much code there was, I decided that wasn't going to work. All of my logic and custom control libraries worked in VB, so I ended up leaving them as is. The main form was where most of the VB compiler magic ("My" classes) was creating problems, so I rewrote it in C# and used the other libraries as is. After a day of

Recently we released Mono 1.2.3 (and Mono 1.2.3.1 yesterday). I am very proud of this release, for several reasons: It's the first release since I've become a full time Mono developer. It's the first release to incorporate MoMA feedback. It's a tremendous improvement over 1.2.2, with over 100 MWF bugs fixed, and over 800 missing methods reported through MoMA implemented. The biggest question of course, is "Is it ready to run your app?". The one thing I learned in school is that the answer to every computer question is "It depends". .Net 1.1 If your app is running on the .Net framework version 1.1 and is fully managed, the answer is yes. We consider our support for 1.1 to be feature complete, and encourage everyone to try out their .Net 1.1 apps on Mono. If something isn't working, or looks wrong, it's most likely a bug, and we want to know about it. The bugzilla database for Mono in general is here , and the bugzilla database for MWF is

Hi! I'm Jonathan Pobst. You may remember me from such Mono contributions as "ToolStrip: the one that looks like Microsoft Office" or " MoMA : that program just asking for a lawsuit from the Museum of Modern Art". Or you probably don't, but that's ok. Since those contributions, I've been fortunate enough to be hired as a full time open source developer. I work mainly on Managed.Windows.Form (MWF): Mono's implementation of the .Net framework's System.Windows.Forms. Things that are specifically my areas are ToolStrip, MenuStrip, StatusStrip, FlowLayoutPanel, and TableLayoutPanel. I also maintain MoMA, and spend some time implementing some of the most needed SWF 2.0 functionality as reported by the MoMA reports submitted. I decided I needed a blog because MWF is a really cool technology. But more importantly, it lends itself well to screenshots. I mean, I'm sure JIT optimizations and compilers are fascinating, but it's hard to con