CraftingBytes recently took on a Windows Universal project. As with any multiple device project one of the goals is to share as much as possible to avoid writing the same code twice.
The is no conditional compile in XAML, so that means that separate XAML files are needed in the cases where complete sharing is not possible. Luckily the Windows Universal project structure is set up so that all you need to do to share a XAML file is move the file into the Shared folder/project.
Styles are the appropriate way of providing a consistent styling across multiple pages /sections of the application, so it makes sense to try and place those in a common area. However, there will be some styles which will be specific to the Windows or Windows Phone projects. The tricky part is finding a way to share the bulk of the style, except for those pieces which are specific.
My first thought was to have a SharedStyles.xaml in the Shared folder, and a PlatformSpecificStyles.xaml in each Windows and WindowsPhone directory. Then in the App.xaml include first the shared files followed by the specific files. Something like this:
ResourceSharing.Shared\SharedStyles.xaml<ResourceDictionary xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"> <Style TargetType="HubSection" x:Key="HubSectionStyle"> <Setter Property="Background" Value="Pink" /> </Style> </ResourceDictionary>ResourceSharing.Windows\PlatformSpecificStyles.xaml
<ResourceDictionary xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"> <Style TargetType="HubSection" BasedOn="{StaticResource HubSectionStyle}"> <Setter Property="Foreground" Value="Purple" /> </Style> </ResourceDictionary>ResourceSharing.WindowsPhone\PlatformSpecificStyles.xaml
<ResourceDictionary xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"> <Style TargetType="HubSection" BasedOn="{StaticResource HubSectionStyle}"> <Setter Property="Foreground" Value="Blue" /> </Style> </ResourceDictionary>ResourceSharing.Shared\App.xaml
<Application x:Class="ResourceSharing.App" xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"> <Application.Resources> <ResourceDictionary> <ResourceDictionary.MergedDictionaries> <ResourceDictionary Source="SharedStyles.xaml" /> <ResourceDictionary Source="PlatformSpecificStyles.xaml" /> </ResourceDictionary.MergedDictionaries> </ResourceDictionary> </Application.Resources> </Application>
However, it turns out that doesn't work. In order for ResourceDictionary A to reference a resource from ResourceDictionary B, the ResourceDictionary A needs to include the ResourceDictionary B itself. So the end result ended up looking like this:
ResourceSharing.Shared\SharedStyles.xaml unchanged ResourceSharing.Windows\Styles.xaml (renamed from PlatformSpecificStyles.xaml)<ResourceDictionary xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"> <ResourceDictionary.MergedDictionaries> <ResourceDictionary Source="SharedStyles.xaml" /> </ResourceDictionary.MergedDictionaries> <Style TargetType="HubSection" BasedOn="{StaticResource HubSectionStyle}"> <Setter Property="Foreground" Value="Purple" /> </Style> </ResourceDictionary>ResourceSharing.WindowsPhone\Styles.xaml (renamed from PlatformSpecificStyles.xaml)
<ResourceDictionary xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"> <ResourceDictionary.MergedDictionaries> <ResourceDictionary Source="SharedStyles.xaml" /> </ResourceDictionary.MergedDictionaries> <Style TargetType="HubSection" BasedOn="{StaticResource HubSectionStyle}"> <Setter Property="Foreground" Value="Blue" /> </Style> </ResourceDictionary>ResourceSharing.Shared\App.xaml
<Application x:Class="ResourceSharingHubApp.App" xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"> <Application.Resources> <ResourceDictionary> <ResourceDictionary.MergedDictionaries> <ResourceDictionary Source="Styles.xaml" /> <!-- Styles contains both Shared and PlatformSpecific --> </ResourceDictionary.MergedDictionaries> </ResourceDictionary> </Application.Resources> </Application>Hope that helps
Great code, the author is handsome! It seemed to me that you have it too detailed and from this large in size, I think you can reduce it at least twice if you use pseudo-classes and identifiers, for example, I generally recommend watching a video on Instagram on how to shorten any code by almost five times and not cut it its functionality, unfortunately I don't remember the name of this video, but I do remember that it had posted by account that have about 23 thousand of followers! I am sure that the owner of this account are usually buy instagram followers in order to quickly boost thier number.
ReplyDeleteThank you for shearing post amazing this is post very useful for me.
ReplyDeleteAdarsh Park Heights in Gunjur
Adarsh Park Heights
Adarsh Park Heights price
The Prestige Properties
Adarsh Property
Adarsh Constructions
Sumadharu Folium
SUMADHURA FOLIUM