学习日记 » ui https://www.softwareace.cn 时刻想着为自己的产品多做一些对他好的事情 Fri, 20 Mar 2026 06:58:28 +0000 zh-CN hourly 1 分享Duilib中基于wke的浏览器控件 https://www.softwareace.cn/?p=1615 https://www.softwareace.cn/?p=1615#comments Fri, 31 Mar 2017 02:38:28 +0000 http://www.softwareace.cn/?p=1615 概述
wke是基于谷歌chrome浏览器源代码的裁剪版本，大小仅仅只有10M左右，无需依赖其他的扩展库（跟CEF的一大堆大约40M的DLL来比简直爽呆了），就可以在本地使用谷歌内核快速加载网页。网上也有基于wke在Duilib 上扩展的控件代码，其实wke头文件挺清楚的了，接口一目了然，特别是JS与C++交互的函数更是容易看懂，也没什么难的，你也可以做到的。

代码
毕竟是裁剪库，有的功能还是没有接口来处理的（比如网页加载前、页面跳转、菜单消息……），头文件代码：

#ifndef __UIWKEWEBKIT_H_
#define __UIWKEWEBKIT_H_
#pragma once
#include "wke.h"
#include <string>
using std::wstring;
 
namespace DuiLib
{
    ///////////////////////////////////////////
    //网页加载状态改变的回调
    class CWkeWebkitLoadCallback
    {
    public:
        virtual void    OnLoadFailed()=0;
        virtual void    OnLoadComplete()=0;
        virtual void    OnDocumentReady()=0;
    };
    ///////////////////////////////////////////
    //网页标题、地址改变的回调
    class CWkeWebkitClientCallback
    {
    public:
        virtual void    OnTitleChange(const CDuiString& strTitle)=0;
        virtual void    OnUrlChange(const CDuiString& strUrl)=0;
    };
 
    class CWkeWebkitUI :
        public CControlUI,
        public wkeBufHandler
    {
    public:
        CWkeWebkitUI(void);
        ~CWkeWebkitUI(void);
        virtual void    onBufUpdated (const HDC hdc,int x, int y, int cx, int cy);
        virtual LPCTSTR    GetClass()const;
        virtual LPVOID    GetInterface(LPCTSTR pstrName);
        virtual void    DoEvent(TEventUI& event);
        virtual void    DoPaint(HDC hDC, const RECT& rcPaint);
        virtual void    SetPos(RECT rc);
        virtual void    DoInit();
        virtual void    SetAttribute(LPCTSTR pstrName, LPCTSTR pstrValue);
        //////////////////////////////////////
        const    wstring& GetUrl()const ;
        bool    CanGoBack() const;
        bool    GoBack();
        bool    CanGoForward() const;
        bool    GoForward();
        void    StopLoad();
        void    Refresh();
        wkeWebView    GetWebView();
        void    SetLoadCallback(CWkeWebkitLoadCallback* pCallback);
        CWkeWebkitLoadCallback* GetLoadCallback();
        void    Navigate(LPCTSTR lpUrl);
        void    LoadFile(LPCTSTR lpFile);
        void    LoadHtml(LPCTSTR lpHtml);
    protected:
        void    StartCheckThread();
        void    StopCheckThread();
        static    void OnTitleChange(const struct _wkeClientHandler* clientHandler, const wkeString title);
        static  void OnUrlChange(const struct _wkeClientHandler* clientHandler, const wkeString url);
    private:
        static int    m_bWebkitCount;
        HANDLE        m_hCheckThread;
        wstring        m_strUrl;
        wkeWebView    m_pWebView;
        wkeClientHandler    m_ClientHandler;
        CWkeWebkitLoadCallback*        m_pLoadCallback;
        CWkeWebkitClientCallback*    m_pClientCallback;
    };
}
 
#endif//__UIWKEWEBKIT_H_

实现部分代码：

#include "StdAfx.h"
#include "UIWkeWebkit.h"
#pragma comment(lib, "DuiEx/wke/wke")
 
namespace DuiLib{
///////////////////////////////////////////////////
//网页加载状态监测线程
DWORD WINAPI CheckThreadFun(LPVOID lpParam)
{
    CWkeWebkitUI* pWebkitUI=(CWkeWebkitUI*)lpParam;
    wkeWebView    pWebView=pWebkitUI->GetWebView();
    if ( NULL == pWebView )
        return 1;
    CWkeWebkitLoadCallback* pCallback=pWebkitUI->GetLoadCallback();
    if ( NULL == pCallback )
        return 1;
    bool bOver=false;
    while( !pWebView->isLoaded() )
    {
        if ( !bOver && pWebView->isDocumentReady() )
        {
            pCallback->OnDocumentReady();
            bOver=true;
        }
        if ( pWebView->isLoadFailed() )
        {
            pCallback->OnLoadFailed();
            return 1;
        }
        ::Sleep(30);
    }
    if ( pWebView->isLoadComplete() )
        pCallback->OnLoadComplete();
    return 0;
}
 
//////////////////////////////////////////////////////
int CWkeWebkitUI::m_bWebkitCount=0;
CWkeWebkitUI::CWkeWebkitUI(void)
:m_pWebView(NULL)
,m_hCheckThread(NULL)
,m_pLoadCallback(NULL)
,m_pClientCallback(NULL)
{
    if ( 0 == m_bWebkitCount )
        wkeInit();
    m_pWebView=wkeCreateWebView();
    m_pWebView->setBufHandler(this);
    m_ClientHandler.onTitleChanged    =&CWkeWebkitUI::OnTitleChange;
    m_ClientHandler.onURLChanged    =&CWkeWebkitUI::OnUrlChange;
    m_bWebkitCount++;
}
 
CWkeWebkitUI::~CWkeWebkitUI(void)
{
    StopCheckThread();
    m_pManager->KillTimer(this);
    wkeDestroyWebView(m_pWebView);
    m_bWebkitCount--;
    if ( 0 == m_bWebkitCount )
        wkeShutdown();
}
 
LPCTSTR CWkeWebkitUI::GetClass() const
{
    return L"WkeWebkitUI";
}
 
LPVOID CWkeWebkitUI::GetInterface( LPCTSTR pstrName )
{
    if( _tcscmp(pstrName, _T("WkeWebkit")) == 0 ) 
        return static_cast<CWkeWebkitUI*>(this);
    return CControlUI::GetInterface(pstrName);
}
 
void CWkeWebkitUI::DoEvent( TEventUI& event )
{
    switch( event.Type )
    {
    case UIEVENT_SETFOCUS:
        if ( m_pWebView ) m_pWebView->focus(); break;
    case UIEVENT_KILLFOCUS:
        if ( m_pWebView ) m_pWebView->unfocus(); break;
    case UIEVENT_WINDOWSIZE:
        if ( m_pWebView ) m_pWebView->resize(GET_X_LPARAM(event.lParam), GET_Y_LPARAM(event.lParam)); break;
    case UIEVENT_CHAR:
        {
            if ( NULL == m_pWebView ) break;
            unsigned int charCode = event.wParam;
            unsigned int flags = 0;
            if (HIWORD(event.lParam) & KF_REPEAT)
                flags |= WKE_REPEAT;
            if (HIWORD(event.lParam) & KF_EXTENDED)
                flags |= WKE_EXTENDED;
            bool bHandled=m_pWebView->keyPress(charCode, flags, false);
            if ( bHandled )
                return ;
            break;
        }
    case UIEVENT_KEYDOWN:
        {
            if ( NULL == m_pWebView ) break;
            unsigned int flags = 0;
            if (HIWORD(event.lParam) & KF_REPEAT)
                flags |= WKE_REPEAT;
            if (HIWORD(event.lParam) & KF_EXTENDED)
                flags |= WKE_EXTENDED;
            bool bHandled=m_pWebView->keyDown(event.wParam, flags, false);
            if ( event.wParam == VK_F5 )
                Refresh();
            if ( bHandled )
                return ;
            break;
        }
    case UIEVENT_KEYUP:
        {
            if ( NULL == m_pWebView ) break;
            unsigned int flags = 0;
            if (HIWORD(event.lParam) & KF_REPEAT)
                flags |= WKE_REPEAT;
            if (HIWORD(event.lParam) & KF_EXTENDED)
                flags |= WKE_EXTENDED;
            bool bHandled=m_pWebView->keyUp(event.wParam, flags, false);
            if ( bHandled )
                return ;
            break;
        }
    case UIEVENT_CONTEXTMENU:
        {
            if ( NULL == m_pWebView ) break;
            unsigned int flags = 0;
            if (event.wParam & MK_CONTROL)
                flags |= WKE_CONTROL;
            if (event.wParam & MK_SHIFT)
                flags |= WKE_SHIFT;
            if (event.wParam & MK_LBUTTON)
                flags |= WKE_LBUTTON;
            if (event.wParam & MK_MBUTTON)
                flags |= WKE_MBUTTON;
            if (event.wParam & MK_RBUTTON)
                flags |= WKE_RBUTTON;
            bool handled = m_pWebView->contextMenuEvent(event.ptMouse.x, event.ptMouse.y, flags);
            if ( handled )
                return ;
            break;
        }
    case UIEVENT_MOUSEMOVE:
    case UIEVENT_BUTTONDOWN:
    case UIEVENT_BUTTONUP:
    case UIEVENT_RBUTTONDOWN:
    case UIEVENT_DBLCLICK:
        {
            HWND hWnd=m_pManager->GetPaintWindow();
            if ( event.Type == UIEVENT_BUTTONDOWN )
            {
                ::SetFocus(hWnd);
                SetCapture(hWnd);
            }
            else if ( event.Type == UIEVENT_BUTTONUP )
                ReleaseCapture();
            unsigned int flags = 0;
            if (event.wParam & MK_CONTROL)
                flags |= WKE_CONTROL;
            if (event.wParam & MK_SHIFT)
                flags |= WKE_SHIFT;
 
            if (event.wParam & MK_LBUTTON)
                flags |= WKE_LBUTTON;
            if (event.wParam & MK_MBUTTON)
                flags |= WKE_MBUTTON;
            if (event.wParam & MK_RBUTTON)
                flags |= WKE_RBUTTON;
            UINT uMsg=0;
            switch ( event.Type )
            {
            case UIEVENT_BUTTONDOWN:    uMsg=WM_LBUTTONDOWN; break;
            case UIEVENT_BUTTONUP:        uMsg=WM_LBUTTONUP; break;
            case UIEVENT_RBUTTONDOWN:    uMsg=WM_RBUTTONDOWN; break;
            case UIEVENT_DBLCLICK:        uMsg=WM_LBUTTONDBLCLK; break;
            case UIEVENT_MOUSEMOVE:        uMsg=WM_MOUSEMOVE; break;
            }
            bool bHandled = m_pWebView->mouseEvent(uMsg, event.ptMouse.x-m_rcItem.left, \
                event.ptMouse.y-m_rcItem.top, flags);
            if ( bHandled )
                return ;
            break;
        }
    case UIEVENT_TIMER:
        if ( m_pWebView )
            m_pWebView->tick();
        break;
    case UIEVENT_SCROLLWHEEL:
        {
            POINT pt;
            pt.x = LOWORD(event.lParam);
            pt.y = HIWORD(event.lParam);
            int nFlag=GET_X_LPARAM(event.wParam);
            int delta = (nFlag==SB_LINEDOWN)?-120:120;
            unsigned int flags = 0;
            if (event.wParam & MK_CONTROL)
                flags |= WKE_CONTROL;
            if (event.wParam & MK_SHIFT)
                flags |= WKE_SHIFT;
            if (event.wParam & MK_LBUTTON)
                flags |= WKE_LBUTTON;
            if (event.wParam & MK_MBUTTON)
                flags |= WKE_MBUTTON;
            if (event.wParam & MK_RBUTTON)
                flags |= WKE_RBUTTON;
            bool handled = m_pWebView->mouseWheel(pt.x, pt.y, delta, flags);
            if ( handled )
                return ;
            break;
        }
    default:
        CControlUI::DoEvent(event); break;
    }
}
 
void CWkeWebkitUI::DoPaint( HDC hDC, const RECT& rcPaint )
{
    if ( m_pWebView )
    {
        RECT rcInsert;
        IntersectRect(&rcInsert, &m_rcItem, &rcPaint);
        m_pWebView->paint(hDC, rcInsert.left, rcInsert.top, \
            rcInsert.right-rcInsert.left, rcInsert.bottom-rcInsert.top, \
            rcInsert.left-m_rcItem.left, rcInsert.top-m_rcItem.top, true);
    }
}
 
void CWkeWebkitUI::onBufUpdated( const HDC hdc,int x, int y, int cx, int cy )
{
    RECT rcValide={ x, y, x+cx, y+cy };
    ::OffsetRect(&rcValide, m_rcItem.left, m_rcItem.top);
    HWND hWnd=m_pManager->GetPaintWindow();
    ::InvalidateRect(hWnd, &rcValide, TRUE);
}
 
void CWkeWebkitUI::Navigate( LPCTSTR lpUrl )
{
    if ( m_pWebView )
    {
        m_pWebView->loadURL(lpUrl);
        StartCheckThread();
    }
}
 
void CWkeWebkitUI::SetPos( RECT rc )
{
    CControlUI::SetPos(rc);
    if ( m_pWebView )
        m_pWebView->resize(rc.right-rc.left, rc.bottom-rc.top);
}
 
void CWkeWebkitUI::DoInit()
{
    if ( !m_strUrl.empty() )
        Navigate(m_strUrl.c_str());
    m_pManager->SetTimer(this, 100, 100);
}
 
void CWkeWebkitUI::StartCheckThread()
{
    StopCheckThread();
    m_hCheckThread=::CreateThread(NULL, 0, CheckThreadFun, this, 0, NULL);
}
 
void CWkeWebkitUI::StopCheckThread()
{
    if ( m_hCheckThread )
    {
        if ( ::WaitForSingleObject(m_hCheckThread, 10) != WAIT_OBJECT_0 )
            ::TerminateThread(m_hCheckThread, 0);
        ::CloseHandle(m_hCheckThread);
        m_hCheckThread = NULL;
    }
}
 
bool CWkeWebkitUI::CanGoBack() const
{
    return m_pWebView?m_pWebView->canGoBack():false;
}
 
bool CWkeWebkitUI::GoBack()
{
    return m_pWebView?m_pWebView->goBack():false;
}
 
bool CWkeWebkitUI::CanGoForward() const
{
    return m_pWebView?m_pWebView->canGoForward():false;
}
 
bool CWkeWebkitUI::GoForward()
{
    return m_pWebView?m_pWebView->goForward():false;
}
 
void CWkeWebkitUI::StopLoad()
{
    if ( m_pWebView )
        m_pWebView->stopLoading();
}
 
void CWkeWebkitUI::Refresh()
{
    if ( m_pWebView )
    {
        StopCheckThread();
        m_pWebView->reload();
        StartCheckThread();
    }
}
 
wkeWebView CWkeWebkitUI::GetWebView()
{
    return m_pWebView;
}
 
void CWkeWebkitUI::SetLoadCallback( CWkeWebkitLoadCallback* pCallback )
{
    m_pLoadCallback=pCallback;
}
 
CWkeWebkitLoadCallback* CWkeWebkitUI::GetLoadCallback()
{
    return m_pLoadCallback;
}
 
void CWkeWebkitUI::OnTitleChange( const struct _wkeClientHandler* clientHandler, const wkeString title )
{
 
}
 
void CWkeWebkitUI::OnUrlChange( const struct _wkeClientHandler* clientHandler, const wkeString url )
{
 
}
 
void CWkeWebkitUI::LoadFile( LPCTSTR lpFile )
{
    if ( m_pWebView )
        m_pWebView->loadFile(lpFile);
}
 
void CWkeWebkitUI::LoadHtml( LPCTSTR lpHtml )
{
    if ( m_pWebView )
        m_pWebView->loadHTML(lpHtml);
}
 
const wstring& CWkeWebkitUI::GetUrl() const
{
    return m_strUrl;
}
 
void CWkeWebkitUI::SetAttribute( LPCTSTR pstrName, LPCTSTR pstrValue )
{
    if ( _tcscmp(pstrName, _T("url")) == 0 )
        m_strUrl = pstrValue;
    else
        CControlUI::SetAttribute(pstrName, pstrValue);
}
 
}

 

解析：
主要处理的就是消息部分，把这个区域的那种消息分发给wke的接口去处理。另外就是加了个线程，检测网页加载状态，通过回调通知网页加载完成、失败、DOC完成（需要用户先初始化回调指针才会通知用户）。
控件定义完成后，我们需要来配置XML了：

放在一个布局里面，指定URL即可，你也可以加上其他属性然后在SetAttribute中对这些属性进行初始化。

运行程序，一个无窗口的chrome内核网页控件就展示出来了：

]]> https://www.softwareace.cn/?feed=rss2&p=1615 0 duilib tag https://www.softwareace.cn/?p=949 https://www.softwareace.cn/?p=949#comments Mon, 15 Sep 2014 02:07:28 +0000 http://www.softwareace.cn/?p=949 http://www.tuicool.com/topics/11300021

]]> https://www.softwareace.cn/?feed=rss2&p=949 0 Chromium Embedded Framework 中文文档（简介）（转） https://www.softwareace.cn/?p=745 https://www.softwareace.cn/?p=745#comments Wed, 26 Mar 2014 08:26:02 +0000 http://www.softwareace.cn/?p=745 简介

 

Chromium Embedded Framework (CEF)是由 Marshall Greenblatt 在2008年创办的开源项目，致力于基于Google Chromium项目开发一个Web控件。 CEF目前已支持多种编程语言和操作系统，能方便地集成到现有或者新的应用程序中，设计上，它追求高性能的同时，也追求易于使用，它的基本框架通过原生库提供C和C++的编程接口，这些接口将宿主程序与Chromium与WebKit的实现细节隔离，能让浏览器与应用程序无缝集成，并支持自定义插件、协议、Javascript对象与扩展。宿主程序还能根据需要控制资源加载、页面跳转、上下文菜单、打印等等。这些好处都是在支持Google Chrome同等效率与HTML5技术可用的基本上提供的。
大量的个人与组织为CEF的开发提供了时间与资源上的贡献，但是我们需要社区更多的投入，来支持CEF核心项目与扩展地对其它语言与框架提供支持的项目（参见扩展项目一节）。如果你有兴趣为CEF提供时间与金钱上的支持，请参见

CEF Donations 页面。

 

编译发行版本

编译发行版本，包涵所有构建基于CEF应用程序所需的文件，在下载章节提供下载，该版本是可以独立使用的，不依赖于CEF或者Chromium的源代码。

 

源代码发行版本

CEF项目是Chromium项目（http://chromium.org）的扩展项目，因此，要编译CEF源代码需要先下载Chromium源代码（下载方式见http://dev.chromium.org/developers/how-tos/get-the-code）并且根据你所选的系统与编译指示安装所有依赖的项目；然后，将CEF的文件放在Chromium的src目录顶层，跟base/chrome/thrid-party这些目录一起，比方说如果你的Chromium安装目录是C:\svn\Chromium\src那么CEF的文件应该在C:\svn\Chromium\src\cef。CHROMIUM_BUILD_COMPATIBILITY.txt 文件有CEF与Chromium版本兼容性的说明信息,如果要将Chromium升级某一版本，使用
gclient sync –revision src@#### –force，

此外，DEPS文件将确保其它目录以合适的形式下载。在大多数系统下，编译需要提供至少4GB内存。

 

在Windows下编译

跟随你的Visual Studio版本的 Windows build instructions ，运行CEF根目录下的cef_create_projects.bat脚本，根据GYP的配置生成Visual Stodio项目文件。如果你机器上同时安装了VS2005和VS2008，那么在运行cef_create_projects脚本前，可通过设置GYP_MSVS_VERSION 环境变量为”2005″ 或”2008″来指定版本。

通过将gclient工具集成到CEF，可以自动在Chromium源代码更新后下载CEF源代码更新和运行cef_create_projects。编辑位于Chromium src目录父目录(上例中是"C:\svn\Chromium") 的.gclient文件，在已有的solutions数组中添加如下的行:

solutions = [ { #Existing definitions here... }, # BEGIN NEW LINES { "name"        : "src/cef",     "url"         : "http://chromiumembedded.googlecode.com/svn/trunk", }, #END NEW LINES ]

Mac OS X下编译

目前仅支持Mac OS X 10.6 (Snow Leopard) 和10.7 (Lion) ，编译结果可运行于10.5, 10.6 and 10.7。根据Mac build instructions正确的配置系统，如果是10.7和Xcode 4，请遵循Xcode4Tips中额外的编译指示。

运行CEF根目录下的cef_create_projects.sh可根据GYP的配置生成XCode项目文件。

 

Linux下的编译

开发中。

扩展项目

CEF基础框架支持C和C++语言，感谢其它维护者的努力工作，CEF可以支持更多的编程语言与框架。这些扩展项目并非由CEF团队维护，所以如果你有任何问题，请直接联系各项目的维护者。

如果你维护着一个不在这个列表中的项目，请到CEF Forum发贴或者直接联系Marshall。

支持

General Usage Wiki page提供使用CEF的概览，CEF支持与相关讨论在CEF Forum中进行。

帮助

CEF仍有大量工作需要开展，如果你想为CEF做出贡献请查看Open状态的Issue，或者在CEF的源代码中搜索TODO，我们还需要人为所有支持的功能编写测试用例。

重大更改

此处并未列出所有的版本,完整版本列表请查看 Changes list。

9月 23, 2011: 编译版本293，添加对VS2010的支持，并包含以下改进与Bug修复:

 

August 9, 2011: Binary release 275 contains the following enhancements and bug fixes.

  • 关闭触摸屏的支持，以使Google Map API功能正常( issue #134 ).
  • 修复一个执行大量同步加载请求时死循环的bug ( issue #192 ).
  • 修复OnResourceResponse拼写错误( issue #270 ).
  • 修复一个在某些情况下关机时会造成Crash的线程问题( issue #277 ).
  • 增加accelerated_video_enabled, accelerated_drawing_enabled 和accelerated_plugins_enabled浏览器设置( issue #278 ).
  • 添加在某些windows机器上加速内容需要的d3dx9_43.dll和d3dcompiler_43.dll文件( issue #280 ).
  • 清理模态窗口回调实现 ( issue #281 ).
  • 关闭语音输入，避免在Google搜索页面点话筒图标会crash的问题。 ( issue #282 ).
  • 当将drag_drop_disabled 设为true时禁用HTML5 drag( issue #284 ).
  • 修复在取消popup窗口时crash的问题( issue #285 ).

 

June 14, 2011: Binary release 259 significantly revamps the CEF API and contains the following enhancements and bug fixes.

  • 使用angle库支持GL ( issue #136 ).
  • CefV8Value 添加Date类型支持( issue #190 ).
  • Add a workaround for the SyncRequestProxy deadlock problem ( issue #192 ).
  • Replace CefHandler with a new CefClient interface and separate handler interfaces ( issue #218 ).
  • Add support for virtual inheritance to allow multiple CefBase parented interfaces to be implemented in the same class ( issue #218 ).
  • Replace CefThreadSafeBase with IMPLEMENT macros to support virtual inheritance and to only provide locking implementations when needed ( issue #218 ).
  • Move the CefBrowserSettings parameter from CefInitialize to CreateBrowser ( issue #218 ).
  • Add a new cef_build.h header that provides platform-specific and OS defines ( issue #218 ).
  • Introduce the use of OVERRIDE to generate compiler errors on Windows if a child virtual method declaration doesn’t match the parent declaration ( issue #218 ).
  • Move CEF header files that should not be directly included by the client to the “include/internal” folder ( issue #218 ).
  • Add support for navigator.onLine and online/offline window events ( issue #234 ).
  • Use NDEBUG instead of _DEBUG because _DEBUG is not defined on Mac ( issue #240 ).
  • Add OnResourceReponse and CefContentFilter for viewing and filtering response content ( issue #241 ).
  • Add support for setting response header values ( issue #246 ).
  • Break CefRegisterScheme into separate CefRegisterCustomScheme and CefRegisterSchemeHandlerFactory functions ( issue #246 ).
  • Allow registration of handlers for built-in schemes ( issue #246 ).
  • Supply scheme and request information to CefSchemeHandlerFactory::Create ( issue #246 ).
  • Add CrossOriginWhitelist functions for bypassing the same-origin policy with both built-in and custom standard schemes ( issue #246 ).
  • Add support for modal dialogs ( issue #250 ).
  • Add support for IME-aware applications ( issue #254 ).
  • Restore keyboard focus on window activation ( issue #256 ).
  • Fix bug when dragging to a window before mouse events have been detected ( issue #262 ).

 

May 10, 2011: Binary release 231 contains the following enhancements and bug fixes.

  • Add cookie get/set support ( issue #88 ).
  • Allow custom schemes to cause redirects ( issue #98 ).
  • Set the libcef.dll version number to the build revision number ( issue #108 ).
  • Add support for returning an HTTP status code from HandleBeforeResourceLoad and custom scheme handlers via the CefResponse class ( issue #202 ).
  • Add support for V8 accessors and entering a V8 context asynchronously ( issue #203 ).
  • Don’t load URLs twice for popup windows ( issue #215 ).
  • Make modal popup windows behave the same as non-modal popup windows ( issue #216 ).
  • Force Flash and Silverlight plugins to use windowless mode when rendering off-screen ( issue #214 ).
  • Don’t download files that will be loaded by a plugin ( issue #227 ).
  • Add a CefDOMNode::IsSame() method for comparing CefDOMNode objects.

 

March 25, 2011: Binary release 212 contains the following enhancements and bug fixes.

  • Add off-screen rendering support ( issue #100 ).
  • Add persistent storage support for cookie data ( issue #193 ).
  • Allow registration of non-standard schemes ( issue #195 ).
  • Improve the behavior of HandleAddressChange, HandleTitleChange, HandleLoadStart and HandleLoadEnd notifications ( issue #200 ).
  • Respect the WS_VISIBLE flag when creating browser windows ( issue #201 ).
  • Fix a bug in CefWebURLRequest that could result in inappropriate calls to CefHandler methods ( issue #204 ).
  • Add a history entry when navigating to anchors within the same page ( issue #207 ).
  • Add a HandleNavStateChange notification for back/forward state changes ( issue #208 ).
  • Fix crash when using WebKit inspector break points ( issue #210 ).
  • Add support for retrieving values from DOM form elements using CefDOMNode::GetValue.
  • Add the CefRunMessageLoop() function for efficient message loop processing in single-threaded message loop mode.

 

February 28, 2011: Binary release 195 contains the following enhancements and bug fixes.

  • Add the CefWebURLRequest class that supports direct loading of URL resources from client applications ( issue #51 ).
  • Add CefDOM classes and the CefFrame::VisitDOM method that allow direct access to and modification of the DOM ( issue #60 ).
  • Add support for the HTML5 drag and drop API and support for dragging content to other applications or the desktop (issue #140).
  • Add a CefV8Context object and CefV8Value::ExecuteFunctionWithContext method to support asynchronous V8 callbacks ( issue #188 ).
  • CefRegisterPlugin now only supports a single mime type per registration.
  • Fix a bug where URL and title change notifications were not being sent for CefFrame::LoadString.

 

February 1, 2011: Binary release 181 will be the last binary release that includes libraries for VS2005. It contains the following enhancements and bug fixes.

  • Improve thread safety by making some methods only callable on the UI thread ( issue #175 ).
  • Add NewCefRunnableMethod and NewCefRunnableFunction templates (in cef_runnable.h) that simplify task posting ( issue #175 ).
  • Add a boolean argument to the HandleLoadStart and HandleLoadEnd events that will be true while the main content frame is loading ( issue #166 ,  issue #183 ).
  • Add an HTTP status code argument to the HandleLoadEnd event ( issue #177 ).
  • Only call the HandleAddressChange and HandleTitleChange events for the main content frame load ( issue #166 )
  • Pass the URL for new popup windows to the HandleBeforeCreated event (issue #5).
  • Add members to the CefSettings structure for specifying log file location and severity level ( issue #172 ).
  • Add single sign-on support ( issue #148 ).
  • Add zooming support ( issue #116 ).
  • Add developer tools support ( issue #127 ).
  • Add a HandleProtocolExecution event for handling unregistered protocols ( issue #155 ).
  • Add a HandleStatus event for status messages, mouse over URLs and keyboard focus URLs ( issue #61 ).
  • Add support for creating and parsing URLs via CefCreateURL and CefParseURL ( issue #181 ).
  • Fix the problem with frame activation when displaying SELECT list popups ( issue #169 ).
  • Accelerated compositing and HTML5 video now work together ( issue #143 ).

 

November 22, 2010: Revision 149 introduces a number of long-awaited features and a few important bug fixes.

  • The API now uses CefString and cef_string_t types instead of std::wstring and wchar_t. The new types support conversion between ASCII, UTF-8, UTF-16 and UTF-32 character formats and the default character type can be changed by recompiling CEF ( issue #146 ).
  • Allow customization of global and per-browser settings for everything from User-Agent and plugin search paths to specific WebKit features ( issue #145 ).
  • Add support for accelerated compositing and fast WebGL ( issue #136 ). You will need to disable accelerated compositing to watch HTML5 video with this release ( issue #143 ).
  • Expose popup window feature information via the CefPopupFeatures argument passed to CefHandler::HandleBeforeCreated ( issue #135 ).
  • Fix a crash caused by Flash-related JavaScript ( issue #115 ).

 

November 15, 2010: Revision 137 provides the first working build of CEF for the Mac OS X platform (issue #68). There’s still a lot of work required to bring it up to par with the Windows port. Missing features are indicated by “TODO(port)” comments in the source code. Help with fixing bugs and implementing missing features is welcome.

October 24, 2010: Revision 126 disables WebGL support due to performance problems with the default Chromium implementation. WebGL support will be re-enabled once a better-performing implementation is available ( issue #136 ).

  • Add a CefHandler::HandleDownloadResponse() method for handling Content-Disposition initiated file downloads ( issue #6 ).
  • Add XML parsing support with CefXmlReader and CefXmlObject classes ( issue #28 ).
  • Add Zip archive reading support with CefZipReader and CefZipArchive classes (issue #30).
  • Add a new cef_wrapper.h header file that exposes helpful utility classes provided as part of the libcef_dll_wrapper target.

 

October 15, 2010: Revision 116 causes CEF to ignore the “Automatically detect settings” option under LAN Settings in order to fix a problem with slow resource loading on Windows ( issue #81 ). Manual configuration under LAN Settings is still respected.

  • Add a CefBrowser::ReloadIgnoreCache() method and MENU_ID_NAV_RELOAD_NOCACHE menu support. ( issue #118 ).
  • Add support for audio playback with HTML5 video ( issue #121 ).
  • Fix back/forward navigation when the history contains pages that failed to load ( issue #125 ).
  • Change the CEF User-Agent product version to “Chrome/7.0.517.0″

 

August 31, 2010: Revision 100 re-introduces the CefHandler::HandleJSBinding method. The memory leaks that necessitated the elimination of this method have now been fixed ( issue #72 ).

  • The CefRequest argument to CefHandler::HandleBeforeResourceLoad can now be modified allowing the request to be changed on the fly ( issue #41 ).
  • A default tooltip implementation is now provided and tooltip text can be modified using CefHandler::HandleTooltip ( issue #61 ).
  • Printing paper size, orientation and margins can now be changed using CefHandler::HandlePrintOptions ( issue #112 ).
  • Find in page with result highlighting is now supported using CefBrowser::Find, CefBrowser::StopFinding and CefHandler::HandleFindResult.
  • The binary release of revision 100 provides libraries for both Visual Studio 2005 and Visual Studio 2008. It can be downloaded from the project Downloads page.

 

April 7, 2010: Revision 73 eliminates the CefHandler::HandleJSBinding method. This modification addresses memory leaks that many users have been reporting. For more information see  issue #72 .

October 2, 2009: Revision 50 adds GYP support for generating the CEF project files. This makes it easy to build CEF with both VS2005 and VS2008. See the “Source Distributions” section above for additional details.

August 21, 2009: Revision 37 adds support for custom scheme handlers. Use the new CefRegisterScheme() function in combination with the CefSchemeHandlerFactory and CefSchemeHandler classes to create handlers for requests using custom schemes such as myscheme://mydomain.

July 24, 2009: Revision 32 helps to speed up the addition of new features and bug fixes to CEF. It adds the CEF Patch Application Tool and the “patch” project which together support automatic application of patches to the Chromium and WebKit source trees as part of the build process. See the README.txt file in the new patch directory for additional information.

July 8, 2009: CEF now has a dedicated build bot thanks to Nicolas Sylvain and Darin Fisher over at Google. The build bot synchronizes to each Chromium revision and then builds CEF, reporting on any compile errors that occur. Having a build bot for CEF will help the Chromium developers avoid accidentally breaking API features required by CEF, and help the CEF developers keep up with the frequently changing Chromium HEAD revision. You can view the build bot output at http://build.chromium.org/buildbot/waterfall.fyi/waterfall?branch=&builder=Chromium+Embedded

June 20, 2009: Revision 30 adds the CEF Translator Tool which facilitates automatic generation of the C API header file (cef_capi.h) and CToCpp/CppToC wrapper classes. See the translator.README.txt file in the new tools directory for additional information. Introduction of this tool required minor changes to the CEF C++ and C APIs.

  • The C++ ‘arguments’ attribute of CefV8Handler::Execute() and CefV8Value::ExecuteFunction() now has the ‘const’ qualifier.
  • C API global function names that were previously in the cef_create_classname() format are now in the cef_classname_create() format.
  • The C API cef_frame_t::get_frame_names() member function now has return type ‘void’ instead of ‘size_t’.
  • The C API cef_frame_t::execute_javascript() member function has been renamed to cef_frame_t::execute_java_script().

 

May 27, 2009: Revision 26 introduces two major changes to the CEF framework.

  • Frame-dependent functions such as loading content and executing JavaScript have been moved to a new CefFrame class. Use the new CefBrowser::Get*Frame() methods to retrieve the appropriate CefFrame instance. A CefFrame instance will now also be passed to CefHandler callback methods as appropriate.
  • The CEF JavaScript API now uses the V8 framework directly instead of creating NPObjects. JavaScript object hierarchies can be written in native C++ code and exported to the JavaScript user-space, and user-space object hierarchies can be accessed from native C++ code. Furthermore, support for the V8 extension framework has been added via the new CefRegisterExtension() function. The CefJSHandler and CefVariant classes have been removed in favor of new CefV8Handler and CefV8Value classes. To attach values to the JavaScript ‘window’ object you must now implement the CefHandler::HandleJSBinding() callback method instead of calling the (now removed) CefBrowser::AddJSHandler() method.
]]> https://www.softwareace.cn/?feed=rss2&p=745 0 嵌入Chrome cef到MFC CView https://www.softwareace.cn/?p=744 https://www.softwareace.cn/?p=744#comments Wed, 26 Mar 2014 08:17:33 +0000 http://www.softwareace.cn/?p=744 公司项目中一直存在着一个CHtmlView模块来显示URL，但是随着web页面的更新（加入HTML5 and 其它一些比较新的技术）越来越发现使用CHtmlView已经无法满足目前的需求。开始还是试着去修改一些东西去满足当前需要，不过好景不长终于有一天CHtmlView连我们目前的web页面都打不开了，于是决定采用Chrome来作为浏览器引擎。

嵌入到MFC

使用CEF

首先，需要下载CEF框架。其中包含了一个使用CEF的例子。目前的CEF共有3个版本（详情见：http://code.google.com/p/chromiumembedded/downloads/list）：
CEF1：单线程的浏览器框架
CEF2：已放弃开发
CEF3：多线程浏览器框架
在这里使用的是CEF1来构建我们的程序。
下载好CEF框架后，打开CEF工程文件找到并编译libcef_dll_wrapper项目（cefclient是一个可运行的例子，有兴趣的朋友可以研究研究）就可以了。

创建我们的CWebView

创建好工程后我们需要连接下面这两个静态库：
\cef_binary\Debug\Lib\libcef_dll_wrapper.lib
\cef_binary\lib\Debug\libcef.lib
要与浏览器交互我们需要创建一个CefClient的子类，如下：
#pragma once
#include <cef_client.h>

class CWebClient 
	: public CefClient
	, public CefLifeSpanHandler
{
protected:
	CefRefPtr<CefBrowser> m_Browser;

public:
	CWebClient(void){};
	virtual ~CWebClient(void){};

	CefRefPtr<CefBrowser> GetBrowser() { return m_Browser; }

	virtual CefRefPtr<CefLifeSpanHandler> GetLifeSpanHandler() OVERRIDE
	{ return this; }

	virtual void OnAfterCreated(CefRefPtr<CefBrowser> browser) OVERRIDE;

	// 添加CEF的SP虚函数
	IMPLEMENT_REFCOUNTING(CWebClient);
	IMPLEMENT_LOCKING(CWebClient);
};

 

接下来就开始修改我们的视图类了：
创建：
// CWebView message handlers
int CWebView::OnCreate( LPCREATESTRUCT lpCreateStruct )
{
 	if ( CView::OnCreate(lpCreateStruct) == -1)
 		return -1;

	CefRefPtr<CWebClient> client(new CWebClient());
	m_cWebClient = client;

	CefSettings cSettings;
	CefSettingsTraits::init( &cSettings);
	cSettings.multi_threaded_message_loop = true;
	CefRefPtr<CefApp> spApp;
	CefInitialize( cSettings, spApp);

	CefWindowInfo info;
	info.SetAsChild( m_hWnd, CRect(0, 0, 800, 600));

	CefBrowserSettings browserSettings;
	CefBrowser::CreateBrowser( info, static_cast<CefRefPtr<CefClient> >(client), 
		"http://192.168.1.21:8080/dialysis/web/page/nav/content.jsp", browserSettings);

	return 0;
}

 

调整大小：
void CWebView::OnSize( UINT nType, int cx, int cy )
{
	CView::OnSize(nType, cx, cy);

	if(m_cWebClient.get())
	{
		CefRefPtr<CefBrowser> browser = m_cWebClient->GetBrowser();
		if(browser)
		{
			CefWindowHandle hwnd = browser->GetWindowHandle();
			RECT rect;
			this->GetClientRect(&rect);
			// ::SetWindowPos(hwnd, HWND_TOP, 0, 0, cx, cy, SWP_NOZORDER);
			::MoveWindow( hwnd, 0, 0, cx, cy, true);
		}
	}
}

 

如果在编译CWebView出现连接错误可以把libcef_dll_wrapper工程的Runtime Library修改为Multi-threaded Debug DLL (/MDd) 并将Treat warnings as errors修改为No (/WX-)试试。
]]> https://www.softwareace.cn/?feed=rss2&p=744 0 C++界面库 https://www.softwareace.cn/?p=742 https://www.softwareace.cn/?p=742#comments Mon, 24 Mar 2014 10:29:32 +0000 http://www.softwareace.cn/?p=742 刚开始用C++做界面的时候，根本不知道怎么用简陋的MFC控件做出比较美观的界面，后来就开始逐渐接触到BCG  Xtreme ToolkitPro v15.0.1，Skin++,等界面库，以及一些网友自己写的界面库，开始对于C++软件界面美化有了一点点的心得。不敢藏私，希望和一些新手朋友们分享交流。

 

一.  开源C++界面库

1.RingSdk

Ringsdk是CSDN上一个前辈自己写的界面库，这个界面库很轻而易举实现QQ2009的界面效果。链接见

http://blog.csdn.net/ringphone/article/details/2911244   貌似Ringsdk和MFC无法进行交互，但是 RingSdk其中有很多的图形处理的代码都非常有参考价值。

 

2.redui的官方网站http://www.redui.org 已经打不开了。官方QQ群是 40729296

CSDN地址是
http://blog.csdn.net/jameshooo/article/details/6677272

这是官方的说明

REDUI，又名REDirectUI，全称是Rendering Engine for DirectUI，是一款基于XML描述的 DirectUI 渲染引擎，能将“控件”的交互和渲染过程分解成多种独立的要素，包括布局、视觉效果、样式、UI自动化、滤镜、脚本、事件、3D场景、3D模型、通用动画等。通过这些要素的排列组合，可以呈现出各种不同效果的控件，甚至能在XML中直接自定义控件类型。支持2D/3D无缝融合。
• REDUI支持GDI/GDI+/DirectDraw/D3D等渲染方式，并有支持OPENGL/ES的愿望

 

3.Duilib 这个就比较大名鼎鼎了，不用多说了吧。包括华为网盘在内的很多业内企业都在用这个界面库。我用Duilib做了一个小型的界面。贴出来献丑一个。

 

4.WGI-1.0.7-Demo-Project-for-windows 。。额。。时间太长，忘记了这个代码是什么，姑且先忽略它。

 

5.cj60lib 这个玩过Gh0st3.6木马的人都熟悉，是一款对MFC进行拓展的界面库

6.金山界面库 这个就不赘述了，可以直接上金山的论坛找源代码和资料

7.skinTK_V0.20 一款类似于Skin++的开源界面库

8.FreeCL_Skin2.3 一款不错的控件库 扩展了常用的MFC控件 。  这个是FreeCL_Skin提供的一个效果实例。

 

9.GuiLib1.5 一个老外写的界面库 没有用过，没有调查，就没有发言权。大家自行百度。

 

10.基于3D的界面库 MangoGUI_V0.1.5

 

MangoGUI是猫仔在DXUT基础上修改得来的一个开源GUI系统。

目前来说基本上继承了DXUT里面绝大多数的功能和改进了使用方式，让DX学习爱好者更容易去使用GUI系统。

如果你也是一位对GUI有兴趣的同学，非常欢迎你一同来参与到MangoGUI的设计当中来！

作者博客

http://m9551.blog.sohu.com/

 

11.基于Skia的directui库metalbone

代码托管地址

http://code.google.com/p/metalbone/

官方说明

MetalBone是一个C++ DirectUI库。接口、命名等借鉴Qt，而并非使用Windows风格。

MetalBone的特点是，使用CSS来定制样式（如果没有CSS的话，则什么也不显示，lol）。目前可以使用Direct2D或Google Skia来绘制界面。MetalBone使用的是 WWM协议（基于LGPL）

 

12.SonicUI2011

效果比较不错的一款皮肤库

作者CSDN地址是

http://my.csdn.net/akof1314

 

13 基于OpenGl的界面库 beGUI-0.1.3-src

代码托管地址

http://code.google.com/p/begui/

 

二 未开源或商业界面库

 

1.Flash4UI

看命名就知道是将Flash嵌入到UI中。

官方网站是  http://www.flash4ui.com/

效果图片

 

2.bolt 迅雷7界面引擎

迅雷界面引擎，这个用过迅雷下载和迅雷看看的就有体会了，界面的确是做的非常的赞。而且流畅，CPU占用和内存各种都很棒。采用了脚本交互的方式，脚本语言采用了Lua.可惜的是迅雷只开放了接口SDK给个人使用。

官方网址 http://bolt.xunlei.com/

 

3.clayui

百度百科说明   clayui是一个采用纯C++编写的界面框架，可以很方便的移植到各种系统上。现在支持的系统包括android，windows，wince，linux。clayui的特点是能实现各种2D，3D动画，一些WPF，FLEX才能实现的界面效果，通过clayui可以很方便的实现。 clayui的底层渲染支持纯软件渲染，d3d，opengl es硬件加速渲染，您可以根据自身的需求选择合适的渲染方式，使您界面的用户体验达到最佳效果

效果

4.DSkinLite

官方网址  http://www.uieasy.cn/dskinlite/

官方Demo

 

5.libuiDK

官方说明:LibUIDK是国际上顶尖的专业开发Windows平台下图形用户界面的开发包，也是国内第一款商业的高级界面开发工具。该开发包基于Microsoft的MFC库。使用此开发工具包可轻易把美工制作的精美界面用Visual C++实现，由于LibUIDK采用所见即所得的方式创建产品界面，所以极大的提高了产品的开发速度，并大大增强图形用户界面(GUI)的亲和力。LibUIDK还可以使您的软件轻松具有当今流行的换肤功能，以提高产品的竞争力。

官方网站

http://www.iuishop.com/index.asp

实例

 

6. SiteUi   SkinSE  都有官方网站。就不继续搬砖的工作了。

 

7.（未开源）上海勇进UIPower

这个比较牛逼。一款界面库就是大几百万的。老总阙海忠还亲自录了20集的界面库相关的视频

官方网站 http://www.uipower.com/

这是老阙的视频。

 

8.炫彩界面库

炫彩界面库貌似是私人开发的一个界面库，可以用C++.c#易语言等来开发。炫彩库的作者貌似是湖北襄阳人哟。

官方网站 http://www.xcgui.com/
9.魔方界面库

官方网站 http://www.muilib.com/

MuiLib(Magic UI Library)Windows高级界面开发库是在国内首家免费开源的DuiLib界面开发库基础上经过针对性的扩展而发展起来的，他继承了DuiLib高度自由灵活的特点，并吸收了其他界面库的一些优点，针对Windows层窗口按像素透明技术而重点优化后形成的一个优秀界面开发库，是一个使用纯C++调用Windows API的开发库，无任何其他第三方依赖框架，您可以使用其提供的各种高级控件来创建更加炫酷的用户界面

 

10 XtremeToolkit

由Codejock 公司出品的一款界面库。应用也是比较广泛的。在2013版的大灰狼远程操控中就采用了这款界面库。

 

11.Sharpui

代码托管地址  https://github.com/china520/sharpui

Sharpui是居于现在流行的DUI思想的一套界面库，可以方便实现半透明和各种界面效果，采用纯c++实现，分为引擎和控件两个部分，这两个部分采用动态库的形式提供，引擎部分处理了事件、资源、渲染、控制逻辑，同时提供了各种应用层面控件的实现基类，包括：Visual、Element、FrameworkElement、Control、ContentControl、Window、Panel、Popup，这些类封装了基础控件的实现细则，所有用户实现的控件都必须继承自这些类，对于需要呈现的控件必须继承至FrameworkElement。
控件部分提供的所有控件均采用DUI方式实现、分层绘制，实现各种常用的布局控件，可灵活实现界面的自动布局；Sharpui本身所有数据结构采用原生实现，内存自动管理，不依赖于std的任何容器，使得库的使用更加独立、编译更加简单，使用VS任意一个版本编译都可以用在其它版本里，不需要担心由于std版本原因而产生编译问题。

 

 

以上都是我在工作和个人业余时间收集积累的开源或商业界面库，这些界面库各有各的特色和侧重点，也有不同的换肤思想，如果要用在项目中还是要进行适当的增删整改。

由于个人能力水平见识有限，也有些大神的作品没有被收录其中。表示遗憾。

]]> https://www.softwareace.cn/?feed=rss2&p=742 0 CControlUI Paint BkImage https://www.softwareace.cn/?p=673 https://www.softwareace.cn/?p=673#comments Tue, 31 Dec 2013 03:37:09 +0000 http://www.softwareace.cn/?p=673 

void CControlUI::PaintBkImage(HDC hDC)
{
	if (m_hIcon == NULL)
	{
		if( m_sBkImage.IsEmpty() ) return;
		if( !DrawImage(hDC, (LPCTSTR)m_sBkImage) ) m_sBkImage.Empty();
		}
	else
	{
		int iconSize = 0;
		// 因为icon宽和高都是一样的，所以取控件宽和高其中最小的值进行判断取多大的图标画出来。
		int minIcon = GetWidth() < GetHeight() ? GetWidth() : GetHeight();
		int m_iconSize[7] = {16, 24, 32, 48, 64, 128, 256};
		bool flag = false; 
		for (int i=0; i<6; ++i)
		{
			if (minIcon >= m_iconSize[i] && minIcon < m_iconSize[i+1])
			{
				iconSize = m_iconSize[i];
				flag = true;
				break;
			}
		}
		if (!flag)
		{
			if (minIcon<m_iconSize[0])
			iconSize = m_iconSize[0];
			else
			iconSize = m_iconSize[6];
		}

		int x = (GetWidth()-iconSize)/2;
		int y = (GetHeight()-iconSize)/2;
		::DrawIconEx(hDC, m_rcItem.left+x, m_rcItem.top+y, m_hIcon, iconSize, iconSize, 0, 0, DI_NORMAL);
	}

}

//m_hicon需要添加个方法设置，

 

]]> https://www.softwareace.cn/?feed=rss2&p=673 0 duilib中使用CWebBrowserUI去掉IWebBrowser2的边框 https://www.softwareace.cn/?p=547 https://www.softwareace.cn/?p=547#comments Mon, 26 Aug 2013 00:23:48 +0000 http://www.softwareace.cn/?p=547 

STDMETHODIMP DuiLib::CWebBrowserUI::GetHostInfo( DOCHOSTUIINFO* pInfo ) { pInfo->dwFlags |= DOCHOSTUIFLAG_NO3DBORDER;//去掉3D边框 if (m_pWebBrowserEventHandler) { return m_pWebBrowserEventHandler->GetHostInfo(pInfo); } return S_OK; }
1.修改CWebBrowserUI的STDMETHOD(GetHostInfo)(DOCHOSTUIINFO* pInfo)函数，如下：

STDMETHODIMP DuiLib::CWebBrowserUI::GetHostInfo( DOCHOSTUIINFO* pInfo )
{
pInfo->dwFlags |= DOCHOSTUIFLAG_NO3DBORDER;//去掉3D边框
if (m_pWebBrowserEventHandler)
{
return m_pWebBrowserEventHandler->GetHostInfo(pInfo);
}
return S_OK;
}
注意：此种方法直接修改了库的源码，不建议。

2.建一个新类继承自CWebBrowserEventHandler覆盖HRESULT STDMETHODCALLTYPE GetHostInfo(DOCHOSTUIINFO __RPC_FAR *pInfo)如下：

virtual HRESULT STDMETHODCALLTYPE GetHostInfo( DOCHOSTUIINFO __RPC_FAR *pInfo)
{
if (pInfo != NULL)
{
pInfo->dwFlags |= DOCHOSTUIFLAG_NO3DBORDER;
}
return S_OK;
}
使用的时候

pWeb->SetWebBrowserEventHandler(你的子类);
建议此方法，不修改源库，继承的方法。

 

]]> https://www.softwareace.cn/?feed=rss2&p=547 0 Duilib 使用IE https://www.softwareace.cn/?p=546 https://www.softwareace.cn/?p=546#comments Mon, 26 Aug 2013 00:22:25 +0000 http://www.softwareace.cn/?p=546 

1.xml中配置<ActiveX name="ie" clsid="{8856F961-340A-11D0-A96B-00C04FD705A2}" delaycreate="false"/>

2.代码中实现：

CActiveXUI* pActiveXUI = static_cast<CActiveXUI*>(m_pm.FindControl(_T("ie")));
if( pActiveXUI ) 
 {
    IWebBrowser2* pWebBrowser = NULL;
    pActiveXUI->GetControl(IID_IWebBrowser2, (void**)&pWebBrowser);
    if( pWebBrowser != NULL ) 
    {
     pWebBrowser->Navigate(L"http://www.duilib.com",NULL,NULL,NULL,NULL); 
     pWebBrowser->Release();
    }
  }

CWebBrowserUI 使用
1.XML配置<WebBrowser name="ie" clsid="{8856F961-340A-11D0-A96B-00C04FD705A2}" delaycreate="false"/>

2.创建CWebBrowserEventHandler* m_pWebBrowserEventHandler对象

3.如果不需要滚动条则需要在virtual HRESULT STDMETHODCALLTYPE GetHostInfo(/* [out][in] */ DOCHOSTUIINFO __RPC_FAR *pInfo)中设置pInfo->dwFlags |= DOCHOSTUIFLAG_SCROLL_NO | DOCHOSTUIFLAG_NO3DBORDER;
4.如果不想要菜单则在virtual HRESULT STDMETHODCALLTYPE ShowContextMenu(
/* [in] */ DWORD dwID,
/* [in] */ POINT __RPC_FAR *ppt,
/* [in] */ IUnknown __RPC_FAR *pcmdtReserved,
/* [in] */ IDispatch __RPC_FAR *pdispReserved)
返回S_OK，如果想要显示菜单则返回S_FALSE

5.打开页面

CWebBrowserUI  * pWebBrowserUI = static_cast<CWebBrowserUI *>(m_pm.FindControl(_T("ie")));
 pWebBrowserUI ->SetWebBrowserEventHandler(m_pWebBrowserEventHandler);
if(  pWebBrowserUI != NULL )  {
      pWebBrowserUI ->Navigate2(_T("http://www.duilib.com")); 
 }

 

]]> https://www.softwareace.cn/?feed=rss2&p=546 0 Duilib编译成静态库 https://www.softwareace.cn/?p=538 https://www.softwareace.cn/?p=538#comments Fri, 23 Aug 2013 01:33:07 +0000 http://www.softwareace.cn/?p=538 这套库做界面还是非常不错的，虽然官方团队开始了Lomox的研发，不再支持这套库了，但是它依然有它的价值。

感谢指正。

有很多人不知道如何编译成静态库，其实很简单的。

首先在vs中设置duilib项目。如图：配置类型改为静态库。

第二步修改UIlib.h头文件上面的宏。如图：

第三步在这个头文件下面添加内容：

#pragma comment(lib,”oledlg.lib”)
#pragma comment(lib,”winmm.lib”)
#pragma comment(lib,”comctl32.lib”)
#pragma comment(lib,”Riched20.lib”)

如图：

 

然后编译，看看它的生成目录是不是有个DuiLib.lib文件生成。注意不是bin目录。

修改第一个demo的链接项，编译后连同它需要的皮肤文件拷贝到任意一个地方，运行试试

from http://blog.csdn.net/tornodo/article/details/7660728

 

]]> https://www.softwareace.cn/?feed=rss2&p=538 0