Three methods of HTML integration in MFC

Three methods for integrating the HTML interface in MFC

Recently, I have considered replacing domolo seohelper with a new version of Seo assistant, all of which are presented in the form of HTML interfaces.

It is said that Gtalk is implemented in a similar way (?).
Inspiration-The Gtalk interface uses the IE control.

Snow Wolf nest: should the Gtalk chat interface be based on the IE kernel?

There are three feasible methods: the difference between them is:ProgramCodeDifferent from the HTML interaction mechanism;

1. If the dialog box is displayed and the user interaction items are relatively simple, we recommend that you use the showhtmldialogfn method and the windows. ARGs script method for communication;

2. If a large number of webpages are designed and need to be dynamically generated, we recommend that you refer to this article on msdn.Article; Using your chtmlctrl in my dialog-based app

3. For programs with complicated functions and strong user interaction, we have to send the trump card killer: cdhtmlview. For details, refer to this article: Integrating DHTML into MFC views.

Another: Today we have implemented a function blog that we wanted to do a long time ago to move the core code of the client, that is, posting a blog using a program, you can write a blog and send it to multiple BSP instances.

The original blog was migrated to the server. Now we are preparing to build a client version, so stay tuned.

I wrote it after work yesterday. As a result, it took nearly half an hour to start the machine today. After opening it, I saw that the memory was 1.2 GB. Dizzy.