This project is read-only.

Architecture

Within the framework folder there are three main components, as well as a CAB file to package them up and provide the required registry settings to make the Operating System aware of the new today screen item.

The three main components are as follows
  • ManagedTodayScreenItem.dll - This is a C++ dll that implements the Windows Mobile Today Screen Item API, It's sole purpose is to hook into the today screen API so we can get allocated a portion of the screen and have the ability to draw the today screen watermark/background image on our form's background.
  • ManagedTodayScreenItemHost.exe - This is a C# application that is launched by ManagedTodayScreenItem.dll to host the .NET Compact Framework CLR. It creates a single form (that it then hands back to the native dll). On start up it enumerates the available *.dlls within the \Program Files\Managed Today Screen Framework\ directory and creates an instance of any class marked with the TodayScreenItem attribute, placing them on the form in a sequential order.
  • ChrisTec.WindowsMobile.TodayScreen.dll - This contains the TodayScreenItem attribute class.

Samples

Within the sample folder is a couple of early examples of custom today screen items written in C#. The first class library project SampleTodayScreenItem demonstrates how a class library can contain more than one custom today screen item. The only thing that is important is that each class is public, marked with the TodayScreenItem attribute and derives from System.Windows.Forms.Control or one of it's subclasses.

Last edited Feb 21, 2008 at 11:22 AM by cfairbairn, version 2

Comments

pradip35 Dec 23, 2008 at 8:03 PM 
Great.....you are done a 'I M Possible' for me... I am a C# and Vb.net developer and don't know about CPP.
Thanx ones again for solve this problem.
I am using your christec.windowsmobile Solution to create a Cell Broadcast in Today screen.