Laputa

XamlBinding is a language binding that integrates .xaml files into SharpDevelop's code-completion infrastructure.
Here is an example of SharpDevelop showing a tool tip for a property in a .xaml file:

A window in .xaml is a partial class: one part is generated from the .xaml file, the other is the user code. If the xaml file specifies a name for an element, the compiler will generate a field that can be used by the user code. XamlBinding adds code-completion support for such fields:

As you can see in the "Search Results" window, "Find references" now searches for references in .xaml files. The "rename" refactoring will update both the XAML and C# code.

Finally, the WPF designer that I wrote earlier this year is now integrated in SharpDevelop. Here is a screen shot:

The designer replaces SharpDevelop's property grid with its own, WPF-based property grid. This property grid will provide support for editing attached properties and data binding in the future.

Unlike the Windows Forms designer, which is included in the .NET Framework and merely hosted by SharpDevelop (which isn't as easy as it sounds); the WPF designer is written from scratch. Thankfully WPF makes this a lot easier than writing a Windows Forms designer from scratch would be.

The WPF designer is still missing lots of features; I would welcome any help.

You can download preview builds of SharpDevelop 3.0 from our build server.

Categories: Daniel

Sunday, June 24, 2007 4:23:00 PM (W. Europe Standard Time, UTC+01:00)

Comments [5]

Monday, June 25, 2007 4:41:44 AM (W. Europe Standard Time, UTC+01:00)

Hi

I have been waiting for this particular release. I am referring to the WPF Designer, just updated the code. Btw what kinda help would you be looking for ?

Vikram Ramanathan

Monday, June 25, 2007 9:44:08 AM (W. Europe Standard Time, UTC+01:00)

I could need help implementing the missing features. This could be better editing support for specific controls (DockPanel, StackPanel: allow positioning child elements, TabControl: allow creating tab pages), support for editing properties in the PropertyGrid (properties of the following types are not editable but should be: Brush, ImageSource, ContextMenu, ResourceDictionary, etc.), or one of missing "main" features that are not related to specific controls/properties (e.g. Copy+Paste, data binding).

Daniel Grunwald

Tuesday, June 26, 2007 5:29:08 AM (W. Europe Standard Time, UTC+01:00)

Daniel

Can you mail me with the details. I will start with understanding the code for now. Btw whenever i open the Boo interpreter i get an unrecorable error. I am running the code of SVN. Let me know where to post this and if there any mailing lists or something like that..

Vikram Ramanathan

Friday, July 06, 2007 4:46:00 PM (W. Europe Standard Time, UTC+01:00)

Does the WPF designer is builtin in SharpDevelop_2.2.0.2595.msi?
I can't find it.

fabiopedrosa

Sunday, July 08, 2007 11:08:28 AM (W. Europe Standard Time, UTC+01:00)

Like the title of the post says, it's in SharpDevelop 3.0; not in any of the 2.x versions.

Daniel Grunwald

Comments are closed.