A Little Strip of Progress

One of my personal goals for the next release of Mono is to fix many of the issues in MenuStrip, ToolStrip, and StatusStrip that manifest themselves in our port of Paint.Net 2.72. Paint.Net has been a godsend for the Winforms team, as it's over 100,000 lines of open-source C# Winforms code. It has helped us find countless bugs in our implementation, as well as some affirmation that we must have plenty of things right if we can run it decently well.

The main menu and tool bar were already in pretty good condition, as they exercise common use cases that I had worked on before. The only noticeable issue was that we were not querying Windows for the a couple of system colors, resulting in an ugly gray color scheme instead of the nicer, uh, beige?

(Click on images to enlarge.)

The tool box took a little bit more work. For ToolStrips, there are five different layouts you can choose. The only one I had implemented was HorizontalStackWithOverflow. The tool box needed Flow, so I had to modify the FlowLayout engine to layout ToolStrips as well. The result is pretty good. I think the two missing buttons are due to something missing in the port.


Finally, the StatusStrip has it's own layout type: SpringTableLayout. That had to be implemented as well as making sure that ToolStripControlHosts properly hid their hosted controls when they weren't visible. (The rectangle in Mono 1.2.3 is a hidden ProgressBar.)


Obviously, there are still several remaining issues that need to be cleaned up, but I'm quite proud of the progress so far.

Comments

Stuart said…
Congrats - great work!
March 6, 2007 at 3:39 PM
Kenneth Rohde Christiansen said…
Where can we get hold of the port?
March 6, 2007 at 3:41 PM
Jonathan Pobst said…
The port is available in Mono's SVN at svn+ssh://mono-cvs.ximian.com/extras/trunk/pdn272/trunk. However, I don't think it gets mirrored to the anonymous SVN.

It's still in bad enough shape that it's not very reliable, and I think it's been abandoned in favor of porting 3.0, but no one has started it. In my local copy, I have all the functionality turned off as I'm really only interested in getting the menus and toolbars to work. :/
March 6, 2007 at 5:01 PM
jacksonh said…
How come we are missing two of the tools in the toolwindow example?
March 6, 2007 at 10:13 PM
Anonymous said…
These comments have been invaluable to me as is this whole site. I thank you for your comment.
June 20, 2007 at 10:07 AM
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