Ui implementation solution of the wince application-Part 1: comparison of several UI Implementation Solutions

I. MFC hard Injury

Before taking over the current project, I was still an idiot for UI development on Windows platform. Apart from MFC, I only knew about GDI. In addition, MFC can only draw gray dialog boxes and buttons. However, in any case, I will not use MFC for Embedded projects that are extremely cost-sensitive. In extreme cases, the customized system is 31.8 M. I put an MFC DLL on armv4i, which is about 500 K, so there are only two options, either change the 32 M Flash to 64 m-my boss will cut me down, or the application layer UICodeRewrite all -- my subordinates will give me a token. On the other hand, I have seen a lot of applications on wince.Source codeAnd some outsourced software. I have never seen anyone using MFC. When MFC is used on the InternetProgramLow portability on different platforms, because you cannot expect other platforms to prepare luxury MFC for you. On the other hand, most experts are not willing to use it. I am not a master, but I can learn how to set the spectrum, so "Don't use" becomes "disdain to use" ^_^

Ii. Difficulties of GDI

Writing the entire UI from createwindow is really tiring. I wrote more than 500 lines to barely implement the button class. Another colleague also used about 500 lines to implement the track bar class. Moreover, there was no formal code review before testing. If multiple patterns are added to the industrial design center, we need to add several basic classes and then compensate the code review time, test time, and Bug fix time. It's not painful ~.

3. Exploring the path of GWES, I am not a pioneer

The wisdom of the masses is infinite. When my colleagues in this group were constrained by my GDI solution, the software engineer from the communication department helped complete the project to capture the dialogbox function from an application sample code of wince500. In my opinion, one thing that fails in the UI implementation solution is to habitually create a dialog resource from EVC, and then click Class Wizard immediately, and then associate the MFC class. After the dialogbox and button are drawn, the UI is created from the dialogbox function with the resouce ID. I also habitually think that dialogbox is not in standard SDK 500, but he does use dialogbox and button without referencing other lib and DLL from standardsdk_500, then, let's talk to me about how to overlay the image on the dialog and button. One hundred miles ~ I should try to find a piece of tofu and hit it to death ~

Iv. Final Research: Can gwes api be a solid foundation we need?
Can GWES APIs implement all the UI functions we need? No one knows. You need to evaluate it. I wrote all these in the same article when I started the draft.Article. I think it is better to separate the articles. After all, the topics are different. Please refer to the previous article: how to solve the technical difficulties in the GWES Solution