Windows Scripting
  Home arrow Windows Scripting arrow Page 2 - Data Converstion and Task Addition with WP...
ASP Free Forums 
.NET  
ASP  
ASP Code  
ASP.NET  
ASP.NET Code  
BrainDump  
C#  
Code Examples  
Database  
Database Code  
IIS  
Microsoft Access  
MS SQL Server  
Visual Basic.NET  
Windows Scripting  
Windows Security  
XML  
ASP Web Hosting  
ASP.NET Web Hosting 
Mobile Linux 
App Generation ROI 
Windows Web Hosting
 
IBM® developerWorks 
Sun Developer Network 
Weekly Newsletter
 
Developer Updates  
Free Website Content 
 RSS  Articles
 RSS  Forums
 RSS  All Feeds
Write For Us Get Paid 
Request Media Kit
Contact Us 
Site Map 
Privacy Policy 
Support 
 USERNAME
 
 PASSWORD
 
 
  >>> SIGN UP!  
  Lost Password? 
WINDOWS SCRIPTING

Data Converstion and Task Addition with WPF
By: Peyton McCullough
  • Search For More Articles!
  • Disclaimer
  • Author Terms
  • Rating: 5 stars5 stars5 stars5 stars5 stars / 1
    2008-09-08

    Table of Contents:
  • Data Converstion and Task Addition with WPF
  • Converting Values, Continued
  • Adding Tasks
  • Adding Tasks, Continued

  • Rate this Article: Poor Best 
      ADD THIS ARTICLE TO:
      Del.ici.ous Digg
      Blink Simpy
      Google Spurl
      Y! MyWeb Furl
    Email Me Similar Content When Posted
    Add Developer Shed Article Feed To Your Site
    Email Article To Friend
    Print Version Of Article
    PDF Version Of Article
     
     
    ADVERTISEMENT


    Data Converstion and Task Addition with WPF - Converting Values, Continued


    (Page 2 of 4 )

    Now the converter for status is done, and it's time to move on to the converter for priority. The converter needs to convert the priority into an appropriate color name: red for high priority, orange for medium priority, and green for low priority. The process is exactly the same as before, only there's no need to be able to convert back (since there's no way to convert back from within the application-the color is static). Create a class named PriorityConverter:


    namespace WpfToDo

    {

     class PriorityConverter : System.Windows.Data.IValueConverter

    {

     public object Convert(object value, Type targetType, object parameter, System.Globalization.CultureInfo culture)

    {

     string rawPriority = ((string)value).ToLower();

     if (rawPriority == "high")

    {

     return "Red";

    }

     else if (rawPriority == "medium")

    {

     return "Orange";

    }

     else

    {

     return "Green";

    }

    }


     public object ConvertBack(object value, Type targetType, object parameter, System.Globalization.CultureInfo culture)

    {

     throw new NotImplementedException();

    }


    }

    }


    So, the application contains some two classes that were coded in, but that code now needs to be referenced in the XAML. Fortunately, however, the intermediate work involved in making this possible is very simple. First, the WpfToDo namespace, which contains the two classes, needs to be worked into the XAML. Place the following attribute in the Window tag:


    xmlns:local="clr-namespace:WpfToDo"


    You'll find several similar attributes already there. Place the new one right under them.

    Next, instances of each of the classes need to be placed in the Resources section, just like the XmlDataProvider:


    <Window.Resources>

     ...

     <local:StatusConverter x:Key="statusConverter" />

     <local:PriorityConverter x:Key="priorityConverter" />

     ...

    </Window.Resources>


    The final step is very simple. The binding needs to be set up, along with references to the two converters. Modify the existing tags, adding the appropriate attributes:


    <CheckBox Grid.Row="0" Grid.RowSpan="2" Grid.Column="0" HorizontalAlignment="Center" VerticalAlignment="Center" IsChecked="{Binding XPath=Done, Converter={StaticResource statusConverter}}" />

    <TextBlock Grid.Row="0" Grid.Column="1" FontWeight="Bold" Foreground="{Binding XPath=Priority, Converter={StaticResource priorityConverter}}" Text="{Binding XPath=Name}" />


    The application now represents the data fully:



    More Windows Scripting Articles
    More By Peyton McCullough


       · Hello,In this third article of my series on WPF, we implement some of the...
     

    WINDOWS SCRIPTING ARTICLES

    - Working With Arrays in VBScript
    - Compressed Folders in WSH
    - Using .NET Interops in VBScript
    - Nilpo`s Scripting Secrets, Vol I
    - Database operations using Silverlight 2.0 WC...
    - Modifying XML Files in WSH
    - Reading XML Files in WSH
    - Visual Basic 2005 XML Programming Using XML ...
    - Creating an XML Document in WSH
    - Introducing Two-Way Data Binding using Silve...
    - Silverlight 2.0 Application Development with...
    - Burning Multisession CDs with IMAPI2 in WSH
    - Creating a Silverlight 2.0 Application that ...
    - Burning CDs with the IMAPI2 Control
    - Burning CDs in Windows XP with WSH

     
    Best Practices for Windows Vista Migration Presentation
    Dell and Microsoft recently held a series of face-to-face seminars entitled, &qu....

     
    Creating a Culture for Code Reuse
    If you oversee development teams you know that like it or not proprietary and ex....

     
    Keys to Web Application Acceleration: Advances in Delivery Systems
    Accelerate Web apps by up to 5x. Ensure significantly faster access to the Web a....

     
    Optimizing Application Monitoring
    Tired of finding out from your customers that you're offline? This white paper e....

     
    Solaris to Solaris Migration -- Migrating applications from Sun SPARC to Dell PowerEdge R900
    This comprehensive Migration Guide reviews the approach that Principled Technolo....

     




    © 2003-2009 by Developer Shed. All rights reserved. DS Cluster 5 hosted by Hostway
    Stay green...Green IT