Reply to thread

Message

<blockquote data-quote="morpheus_xx" data-source="post: 1111457" data-attributes="member: 48495">Up to now, if you open the MP2 skin files (screens, styles) inside a design tool (VisualStudio, Blend), the used elements are not known. This leads to underlining the control names and the lack of autocomplete (intellisense) feature.Fortunately I found an solution for this issue: <a href="http://msdn.microsoft.com/en-us/library/ms747086%28v=vs.110%29.aspx" target="_blank">http://msdn.microsoft.com/en-us/library/ms747086(v=vs.110).aspx</a>.It is possible to make own class implementations known to the xaml world! MPF already uses an own namespace, but the control types etc. are not yet published correctly. First step is to map CLR namespace to our MPF XAML-namespace:[CODE=C#]// Register CLR namespaces for XAML[assembly: XmlnsDefinition(&quot;www.team-mediaportal.com/2008/mpf/directx&quot;, &quot;MediaPortal.UI.SkinEngine&quot;)][assembly: XmlnsDefinition(&quot;www.team-mediaportal.com/2008/mpf/directx&quot;, &quot;MediaPortal.UI.SkinEngine.ScreenManagement&quot;)][assembly: XmlnsDefinition(&quot;www.team-mediaportal.com/2008/mpf/directx&quot;, &quot;MediaPortal.UI.SkinEngine.Commands&quot;)][assembly: XmlnsDefinition(&quot;www.team-mediaportal.com/2008/mpf/directx&quot;, &quot;MediaPortal.UI.SkinEngine.Controls.Animations&quot;)][assembly: XmlnsDefinition(&quot;www.team-mediaportal.com/2008/mpf/directx&quot;, &quot;MediaPortal.UI.SkinEngine.Controls.Panels&quot;)][assembly: XmlnsDefinition(&quot;www.team-mediaportal.com/2008/mpf/directx&quot;, &quot;MediaPortal.UI.SkinEngine.Controls.Transforms&quot;)][assembly: XmlnsDefinition(&quot;www.team-mediaportal.com/2008/mpf/directx&quot;, &quot;MediaPortal.UI.SkinEngine.Controls.Brushes&quot;)][assembly: XmlnsDefinition(&quot;www.team-mediaportal.com/2008/mpf/directx&quot;, &quot;MediaPortal.UI.SkinEngine.Controls.Brushes.Animation&quot;)][assembly: XmlnsDefinition(&quot;www.team-mediaportal.com/2008/mpf/directx&quot;, &quot;MediaPortal.UI.SkinEngine.Controls.Visuals&quot;)][assembly: XmlnsDefinition(&quot;www.team-mediaportal.com/2008/mpf/directx&quot;, &quot;MediaPortal.UI.SkinEngine.Controls.Visuals.Styles&quot;)][assembly: XmlnsDefinition(&quot;www.team-mediaportal.com/2008/mpf/directx&quot;, &quot;MediaPortal.UI.SkinEngine.Controls.Visuals.Templates&quot;)][assembly: XmlnsDefinition(&quot;www.team-mediaportal.com/2008/mpf/directx&quot;, &quot;MediaPortal.UI.SkinEngine.Controls.Visuals.Triggers&quot;)][assembly: XmlnsDefinition(&quot;www.team-mediaportal.com/2008/mpf/directx&quot;, &quot;MediaPortal.UI.SkinEngine.MpfElements.Resources&quot;)][assembly: XmlnsDefinition(&quot;www.team-mediaportal.com/2008/mpf/directx&quot;, &quot;MediaPortal.UI.SkinEngine.MarkupExtensions&quot;)][/CODE]This makes already all attributes visible to VS:[ATTACH=full]157925[/ATTACH] Next is to declare some properties as default for adding content via XAML:[CODE=C#]&nbsp; /// &lt;summary&gt;&nbsp; /// Screen class respresenting a logical screen represented by a particular skin.&nbsp; /// &lt;/summary&gt;&nbsp; [ContentProperty(&quot;Root&quot;)]&nbsp; public class Screen : UIElement, INameScope, IAddChild&lt;FrameworkElement&gt;, IUnmodifiableResource&nbsp; {&nbsp; &nbsp; #region Consts[/CODE]I currently add more attributes to MPF classes, so that in the end we will have (nearly complete?) designer support for MPF!!! Yeah, finally!This is useful for both [USERGROUP=39]@Developers[/USERGROUP]&nbsp; and [USERGROUP=38]@Designers[/USERGROUP]</blockquote>

[QUOTE="morpheus_xx, post: 1111457, member: 48495"] Up to now, if you open the MP2 skin files (screens, styles) inside a design tool (VisualStudio, Blend), the used elements are not known. This leads to underlining the control names and the lack of autocomplete (intellisense) feature. Fortunately I found an solution for this issue: [url]http://msdn.microsoft.com/en-us/library/ms747086%28v=vs.110%29.aspx[/url]. It is possible to make own class implementations known to the xaml world! MPF already uses an own namespace, but the control types etc. are not yet published correctly. First step is to map CLR namespace to our MPF XAML-namespace: [CODE=C#]// Register CLR namespaces for XAML [assembly: XmlnsDefinition("www.team-mediaportal.com/2008/mpf/directx", "MediaPortal.UI.SkinEngine")] [assembly: XmlnsDefinition("www.team-mediaportal.com/2008/mpf/directx", "MediaPortal.UI.SkinEngine.ScreenManagement")] [assembly: XmlnsDefinition("www.team-mediaportal.com/2008/mpf/directx", "MediaPortal.UI.SkinEngine.Commands")] [assembly: XmlnsDefinition("www.team-mediaportal.com/2008/mpf/directx", "MediaPortal.UI.SkinEngine.Controls.Animations")] [assembly: XmlnsDefinition("www.team-mediaportal.com/2008/mpf/directx", "MediaPortal.UI.SkinEngine.Controls.Panels")] [assembly: XmlnsDefinition("www.team-mediaportal.com/2008/mpf/directx", "MediaPortal.UI.SkinEngine.Controls.Transforms")] [assembly: XmlnsDefinition("www.team-mediaportal.com/2008/mpf/directx", "MediaPortal.UI.SkinEngine.Controls.Brushes")] [assembly: XmlnsDefinition("www.team-mediaportal.com/2008/mpf/directx", "MediaPortal.UI.SkinEngine.Controls.Brushes.Animation")] [assembly: XmlnsDefinition("www.team-mediaportal.com/2008/mpf/directx", "MediaPortal.UI.SkinEngine.Controls.Visuals")] [assembly: XmlnsDefinition("www.team-mediaportal.com/2008/mpf/directx", "MediaPortal.UI.SkinEngine.Controls.Visuals.Styles")] [assembly: XmlnsDefinition("www.team-mediaportal.com/2008/mpf/directx", "MediaPortal.UI.SkinEngine.Controls.Visuals.Templates")] [assembly: XmlnsDefinition("www.team-mediaportal.com/2008/mpf/directx", "MediaPortal.UI.SkinEngine.Controls.Visuals.Triggers")] [assembly: XmlnsDefinition("www.team-mediaportal.com/2008/mpf/directx", "MediaPortal.UI.SkinEngine.MpfElements.Resources")] [assembly: XmlnsDefinition("www.team-mediaportal.com/2008/mpf/directx", "MediaPortal.UI.SkinEngine.MarkupExtensions")] [/CODE] This makes already all attributes visible to VS: [ATTACH=full]157925[/ATTACH] Next is to declare some properties as default for adding content via XAML: [CODE=C#] /// <summary> /// Screen class respresenting a logical screen represented by a particular skin. /// </summary> [ContentProperty("Root")] public class Screen : UIElement, INameScope, IAddChild<FrameworkElement>, IUnmodifiableResource { #region Consts[/CODE] I currently add more attributes to MPF classes, so that in the end we will have (nearly complete?) designer support for MPF!!! Yeah, finally! This is useful for both [USERGROUP=39]@Developers[/USERGROUP] and [USERGROUP=38]@Designers[/USERGROUP] [/QUOTE]

Verification