Prerequisite: Introduction

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 convey that information with pretty screenshots, which is key. It's roughly akin to me trying to explain to my mom what I do for a living.

Another goal of mine is to reach out to Windows developers looking to get started with Mono. I've been developing on Windows since the early days of Visual Basic. I currently develop with Visual Studio 2005 on Windows XP. Hopefully, I can improve Mono's functionality and features for people developing on Windows, as well as help to lessen the learning curve for people with a Windows background. MoMA was my first effort at this, and I've been very happy with how well it has been received (over 17k page views and almost 1k submitted reports).

Or I'll post three times and then abandon my blog, like 95% of people who create a blog...

Comments

mdi said…
You did forget to post a screenshot on this first blog entry ;-)

Miguell
February 13, 2007 at 6:36 AM
Unknown said…
Yeah... where are the screenshots? :)
February 13, 2007 at 8:13 AM
Paco Martinez said…
A fine first entry :)

Paco
February 13, 2007 at 8:59 AM
purplepangolin said…
I hope you are in the 5 :-). I work in a very Microsoft centric workplace so all of the areas you mention are important if we ever decide to move to Mono.
February 13, 2007 at 9:55 AM
Jonathan Pobst said…
Haha, for an introduction post about myself, the only appropriate screenshot would have been a photo editor with a picture of me, which I wouldn't want to inflict on the world, at least not on the first post. :)
February 13, 2007 at 8:49 PM
Post a Comment

Popular posts from this blog

Introducing Pinta

Image
Over the holiday break, I stumbled upon this article from OSNews stating that there was a need for something like Paint.NET for Gtk. Having some experience with porting Paint.NET to Mono Winforms before, I knew that that was a massive task. But it still got me curious about Cairo and creating a layered canvas, since I had never played with Cairo or Gtk. After playing around for a few hours, I actually had a working paintbrush and canvas. Intrigued by my success, I played around with it for a few more days. By the end of the week I had a nifty little paint program with a few features. Now, a month later, it's time to open my little project up to the world: Pinta . Pinta is a clone of Paint.NET. It already has a small, but hopefully useful, set of features like multiple layers and infinite levels of Undo/Redo. I hope to implement the same feature set as Paint.NET. Currently there are several tools missing, as well as adjustments like brightness/contrast and levels and Pain
Read more

Mono in Visual Studio 2010

Image
One cool new feature in Visual Studio 2010 is enhanced Multi Targeting . Presumably, its all about allowing developers to target both the 2.0 and 4.0 runtimes from VS2010, but what it really means is you can easily target Mono from within Visual Studio 2010. Like this: To enable this, you need to unzip this file to: C:\Program Files\Reference Assemblies\Microsoft\Framework\.NETFramework\v3.5\Profile Once you do that, you can take your .NET project: Go to project properties and switch it to the Mono 2.4 Profile: Now it will compile using Mono's assemblies, and will flag methods that Mono does not contain, like thus: This also works for Intellisense: And Object Browser: We are very excited about this feature, which should make it easy for people to ensure they are staying compatible with the Mono subset of the .NET framework without leaving Visual Studio. Once VS2010 is released, we will hopefully release the profile packs as we release each Mono version!
Read more

I don't get KDE

Image
Last night while browsing the internets, I saw some screenshots of KDE 4.3 running on openSUSE 11.2. I've never tried KDE, so I installed the openSUSE 11.2 M8 build to briefly play with it. What got me interested was this element of the KDE desktop: I look at that and see hope. It is elegant and refined. It is glassy and tasteful. It says: "I can easily compete with Windows 7 and OSX." Simply put, it is beautiful. Yes, there are some problems with it. The buttons do not highlight in any way on hover. There are no tooltips, so I don't even know what the top two buttons do. From what I can tell, they do absolutely nothing. But it really lives up to KDE's reputation of eye candy. And then you open a window: It is.. gray. There is no glass. There are no gradients. There is no depth. There is no elegance. There is just gray. It says: "I am kicking Windows 95's ass! Barely!" I just don't get it. How can half of your desktop (let's
Read more