New UI framework with WinCE6.0 R3 -- Silverlight for Embedded FAQs

It is rare to write articles related to work. With the release of WinCE6.0 R3 (please refer to the Windows Embedded 6.0 R3 initial development experience that Jack Ma has provided for us, I have been trying to say that the embedded UI framework can finally be casually talked about. As an early user, I am here to contribute some basic knowledge and send a FAQ to impress everyone:

Q1: What is Silverlight for Embedded?

A1: Silverlight for Embedded is an application UI framework available on WinCE6.0 R3 and later versions. It provides a programming model separated by logic and UI, it can greatly reduce the workload of developer UI development. At the same time, the Xaml syntax similar to Silverlight/WPF also gives programmers/visual designers more knowledge intersections in different fields, reduces learning costs. Compared with Win32 GDI, Silverlight for Embedded makes it easier to create high-quality application interfaces and to modify and support multiple skins.

Q2: What is the relationship between Silverlight for Embedded and Silverlight?

A2: Silverlight for Embedded uses the same rendering core as Silverlight. You can think that Silverlight is a shell written for it using C, silverlight for Embedded is another shell written for it using C ++. The goal of Silverlight is a browser, while that of Silverlight for Embedded is an Embedded application (later, the WinCE browser may also support the Silverlight plug-in ).

Q3: Where can I find the Silverlight for Embedded document?

A3: Unfortunately, the Silverlight for Embedded document is not completed yet, But Silverlight for Embedded has a very similar architecture with Silverlight. You can use the Silverlight document on MSDN as a reference, all the differences are just the differences between C ++ and C # languages (in fact, we have always done this in the past year's Development ), you can also obtain technical information from Microsoft's Technical Support Department or JDP project.

Q4: In what environments does Silverlight for Embedded need to be developed?

A4: we need a full set of Running Environments for WinCE6.0 R3. Note that Silverlight for Embedded can only be developed using unmanaged C ++, we need to make some settings for our own project to reference Silverlight for Embedded (this is complicated, let's send a blog separately after the details). In addition, Expression Blend can help us generate the Xaml that describes the UI.

Q5: Is there any Silverlight for Embedded Application in WinCE6.0 R3?

A5: Please refer to our new Browser. In addition, some small sample programs are released along with WinCE6.0 R3.

Q6: What are the major changes in Silverlight for Embedded compared to Silverlight?

A6: Apart from changing the language from C # To C ++, there are two major changes:

1. You cannot inherit any controls except UserControl. That is, programmers outside of Microsoft cannot write native Control (Silverlight is acceptable), but you can still use UserControl to organize your interface.

2. The Event Callback Function Directly written in Xaml will be ignored. You need to find the element name in the C ++ code and bind the event with the C ++ code.

 

 

If you are interested, you can write down your questions. I will try to answer ^