MORPH
SIGN IN SIGN UP
cefsharp / CefSharp UNCLAIMED

.NET (WPF and Windows Forms) bindings for the Chromium Embedded Framework

0 0 0 C#
Normal View History Raw
Maintenance - Fixed formatting, file encoding, and copyright year (#2504) * Applied formatting * Fixed file encoding + Updated copyright year * Updated License * Fixed more file encoding * Copyright notice now shows the year the file was created
2018-09-10 02:41:13 +02:00
// Copyright © 2016 The CefSharp Authors. All rights reserved.
Remove CefSubProcess.cpp - having such trivial cpp files seems silly Convert CefRenderProcess into a cpp class - this should theoretically allow users to add CefSharp.BrowserSubprocess.Core as a reference then use their own process to spawn it Move CefRenderProcess and CefSubProcess into CefSharp.BrowserSubprocess namespace - otherclasses should really be moved as well Only use our custom subProcess when type is render, for gpu and plugin processes the standard implementation is just fine Remove CefSubProcess Rename CefAppWrapper to CefSubProcess
2016-05-16 18:52:35 +10:00
//
// Use of this source code is governed by a BSD-style license that can be found in the LICENSE file.
#pragma once
#include "Stdafx.h"
#include "include/cef_app.h"
Network Service - Register custom scheme in all process types The network services requires that custom schemes be registered, previously we only registered them in render processes. Add SubProcessApp to handle scheme registration CefAppUnmanagedWrapper inherits SubProcessApp now #2743
2019-07-04 20:47:21 +10:00
#include "SubProcessApp.h"
Remove CefSubProcess.cpp - having such trivial cpp files seems silly Convert CefRenderProcess into a cpp class - this should theoretically allow users to add CefSharp.BrowserSubprocess.Core as a reference then use their own process to spawn it Move CefRenderProcess and CefSubProcess into CefSharp.BrowserSubprocess namespace - otherclasses should really be moved as well Only use our custom subProcess when type is render, for gpu and plugin processes the standard implementation is just fine Remove CefSubProcess Rename CefAppWrapper to CefSubProcess
2016-05-16 18:52:35 +10:00
#include "CefBrowserWrapper.h"
#include "CefAppUnmanagedWrapper.h"
Upgrade to CEF 85.3.6+gacfac2f+chromium-85.0.4183.102 / Chromium 85.0.4183.102 - Remove CefSettings.RegisterExtension (#3184) - Add IRenderProcessHandler.OnWebKitInitialized - Add Cef.RegisterExtension (Browser SubProcess specific implementation) Resolves #3184
2020-09-16 13:38:20 +10:00
#include "Cef.h"
Remove CefSubProcess.cpp - having such trivial cpp files seems silly Convert CefRenderProcess into a cpp class - this should theoretically allow users to add CefSharp.BrowserSubprocess.Core as a reference then use their own process to spawn it Move CefRenderProcess and CefSubProcess into CefSharp.BrowserSubprocess namespace - otherclasses should really be moved as well Only use our custom subProcess when type is render, for gpu and plugin processes the standard implementation is just fine Remove CefSubProcess Rename CefAppWrapper to CefSubProcess
2016-05-16 18:52:35 +10:00
using namespace System::Collections::Generic;
using namespace System::Linq;
using namespace CefSharp::Internals;
Add Initial IRenderProcessHandler.OnContextCreated/Released implementation (#2697) * WinForms/WPF - Dispose of IFrame after calling LoadUrl * BrowserProcess - Add initial implementation of IRenderProcessHandler.OnContextCreated/OnContextReleased - IV8Context.Execute is the only method to be implemented so far (execute script without returning a result) - Wrappers for CefFrame and CefBrowser have yet to be imported yet, still need to determine if they should be included individually or reference to CefSharp.Core added * BrowserProcess - Add wrappers for Browser and Frame Ultimately we should probably remove the CefSharp.BrowserSubprocess.Core project and move all the code into a folder/namespace within CefSharp.Core This would allow us to share the a lot of existing code, major refactor required * CefSharp.Common.props - Add CefSharpBrowserProcessCore32/64 properties Make creating your own custom browser process easier * BrowserProcess - Remove example and add comments about creating your own custom version
2019-03-20 20:33:10 +10:00
using namespace CefSharp::RenderProcess;
Remove CefSubProcess.cpp - having such trivial cpp files seems silly Convert CefRenderProcess into a cpp class - this should theoretically allow users to add CefSharp.BrowserSubprocess.Core as a reference then use their own process to spawn it Move CefRenderProcess and CefSubProcess into CefSharp.BrowserSubprocess namespace - otherclasses should really be moved as well Only use our custom subProcess when type is render, for gpu and plugin processes the standard implementation is just fine Remove CefSubProcess Rename CefAppWrapper to CefSubProcess
2016-05-16 18:52:35 +10:00
namespace CefSharp
{
Untabify
2016-05-31 08:27:58 +10:00
namespace BrowserSubprocess
{
// Wrap CefAppUnmangedWrapper in a nice managed wrapper
public ref class SubProcess
{
private:
MCefRefPtr<CefAppUnmanagedWrapper> _cefApp;
Remove CefSubProcess.cpp - having such trivial cpp files seems silly Convert CefRenderProcess into a cpp class - this should theoretically allow users to add CefSharp.BrowserSubprocess.Core as a reference then use their own process to spawn it Move CefRenderProcess and CefSubProcess into CefSharp.BrowserSubprocess namespace - otherclasses should really be moved as well Only use our custom subProcess when type is render, for gpu and plugin processes the standard implementation is just fine Remove CefSubProcess Rename CefAppWrapper to CefSubProcess
2016-05-16 18:52:35 +10:00
Untabify
2016-05-31 08:27:58 +10:00
public:
Add Initial IRenderProcessHandler.OnContextCreated/Released implementation (#2697) * WinForms/WPF - Dispose of IFrame after calling LoadUrl * BrowserProcess - Add initial implementation of IRenderProcessHandler.OnContextCreated/OnContextReleased - IV8Context.Execute is the only method to be implemented so far (execute script without returning a result) - Wrappers for CefFrame and CefBrowser have yet to be imported yet, still need to determine if they should be included individually or reference to CefSharp.Core added * BrowserProcess - Add wrappers for Browser and Frame Ultimately we should probably remove the CefSharp.BrowserSubprocess.Core project and move all the code into a folder/namespace within CefSharp.Core This would allow us to share the a lot of existing code, major refactor required * CefSharp.Common.props - Add CefSharpBrowserProcessCore32/64 properties Make creating your own custom browser process easier * BrowserProcess - Remove example and add comments about creating your own custom version
2019-03-20 20:33:10 +10:00
SubProcess(IRenderProcessHandler^ handler, IEnumerable<String^>^ args)
Untabify
2016-05-31 08:27:58 +10:00
{
auto onBrowserCreated = gcnew Action<CefBrowserWrapper^>(this, &SubProcess::OnBrowserCreated);
auto onBrowserDestroyed = gcnew Action<CefBrowserWrapper^>(this, &SubProcess::OnBrowserDestroyed);
auto schemes = CefCustomScheme::ParseCommandLineArguments(args);
auto enableFocusedNodeChanged = CommandLineArgsParser::HasArgument(args, CefSharpArguments::FocusedNodeChangedEnabledArgument);
Remove CefSubProcess.cpp - having such trivial cpp files seems silly Convert CefRenderProcess into a cpp class - this should theoretically allow users to add CefSharp.BrowserSubprocess.Core as a reference then use their own process to spawn it Move CefRenderProcess and CefSubProcess into CefSharp.BrowserSubprocess namespace - otherclasses should really be moved as well Only use our custom subProcess when type is render, for gpu and plugin processes the standard implementation is just fine Remove CefSubProcess Rename CefAppWrapper to CefSubProcess
2016-05-16 18:52:35 +10:00
Add Initial IRenderProcessHandler.OnContextCreated/Released implementation (#2697) * WinForms/WPF - Dispose of IFrame after calling LoadUrl * BrowserProcess - Add initial implementation of IRenderProcessHandler.OnContextCreated/OnContextReleased - IV8Context.Execute is the only method to be implemented so far (execute script without returning a result) - Wrappers for CefFrame and CefBrowser have yet to be imported yet, still need to determine if they should be included individually or reference to CefSharp.Core added * BrowserProcess - Add wrappers for Browser and Frame Ultimately we should probably remove the CefSharp.BrowserSubprocess.Core project and move all the code into a folder/namespace within CefSharp.Core This would allow us to share the a lot of existing code, major refactor required * CefSharp.Common.props - Add CefSharpBrowserProcessCore32/64 properties Make creating your own custom browser process easier * BrowserProcess - Remove example and add comments about creating your own custom version
2019-03-20 20:33:10 +10:00
_cefApp = new CefAppUnmanagedWrapper(handler, schemes, enableFocusedNodeChanged, onBrowserCreated, onBrowserDestroyed);
Untabify
2016-05-31 08:27:58 +10:00
}
Remove CefSubProcess.cpp - having such trivial cpp files seems silly Convert CefRenderProcess into a cpp class - this should theoretically allow users to add CefSharp.BrowserSubprocess.Core as a reference then use their own process to spawn it Move CefRenderProcess and CefSubProcess into CefSharp.BrowserSubprocess namespace - otherclasses should really be moved as well Only use our custom subProcess when type is render, for gpu and plugin processes the standard implementation is just fine Remove CefSubProcess Rename CefAppWrapper to CefSubProcess
2016-05-16 18:52:35 +10:00
Untabify
2016-05-31 08:27:58 +10:00
!SubProcess()
{
_cefApp = nullptr;
}
Remove CefSubProcess.cpp - having such trivial cpp files seems silly Convert CefRenderProcess into a cpp class - this should theoretically allow users to add CefSharp.BrowserSubprocess.Core as a reference then use their own process to spawn it Move CefRenderProcess and CefSubProcess into CefSharp.BrowserSubprocess namespace - otherclasses should really be moved as well Only use our custom subProcess when type is render, for gpu and plugin processes the standard implementation is just fine Remove CefSubProcess Rename CefAppWrapper to CefSubProcess
2016-05-16 18:52:35 +10:00
Untabify
2016-05-31 08:27:58 +10:00
~SubProcess()
{
this->!SubProcess();
}
Remove CefSubProcess.cpp - having such trivial cpp files seems silly Convert CefRenderProcess into a cpp class - this should theoretically allow users to add CefSharp.BrowserSubprocess.Core as a reference then use their own process to spawn it Move CefRenderProcess and CefSubProcess into CefSharp.BrowserSubprocess namespace - otherclasses should really be moved as well Only use our custom subProcess when type is render, for gpu and plugin processes the standard implementation is just fine Remove CefSubProcess Rename CefAppWrapper to CefSubProcess
2016-05-16 18:52:35 +10:00
Untabify
2016-05-31 08:27:58 +10:00
int Run()
{
auto hInstance = Process::GetCurrentProcess()->Handle;
Remove CefSubProcess.cpp - having such trivial cpp files seems silly Convert CefRenderProcess into a cpp class - this should theoretically allow users to add CefSharp.BrowserSubprocess.Core as a reference then use their own process to spawn it Move CefRenderProcess and CefSubProcess into CefSharp.BrowserSubprocess namespace - otherclasses should really be moved as well Only use our custom subProcess when type is render, for gpu and plugin processes the standard implementation is just fine Remove CefSubProcess Rename CefAppWrapper to CefSubProcess
2016-05-16 18:52:35 +10:00
Untabify
2016-05-31 08:27:58 +10:00
CefMainArgs cefMainArgs((HINSTANCE)hInstance.ToPointer());
Remove CefSubProcess.cpp - having such trivial cpp files seems silly Convert CefRenderProcess into a cpp class - this should theoretically allow users to add CefSharp.BrowserSubprocess.Core as a reference then use their own process to spawn it Move CefRenderProcess and CefSubProcess into CefSharp.BrowserSubprocess namespace - otherclasses should really be moved as well Only use our custom subProcess when type is render, for gpu and plugin processes the standard implementation is just fine Remove CefSubProcess Rename CefAppWrapper to CefSubProcess
2016-05-16 18:52:35 +10:00
C++/CLI - Replace NULL with nullptr Issue #3636
2021-07-31 15:35:38 +10:00
return CefExecuteProcess(cefMainArgs, (CefApp*)_cefApp.get(), nullptr);
Untabify
2016-05-31 08:27:58 +10:00
}
Remove CefSubProcess.cpp - having such trivial cpp files seems silly Convert CefRenderProcess into a cpp class - this should theoretically allow users to add CefSharp.BrowserSubprocess.Core as a reference then use their own process to spawn it Move CefRenderProcess and CefSubProcess into CefSharp.BrowserSubprocess namespace - otherclasses should really be moved as well Only use our custom subProcess when type is render, for gpu and plugin processes the standard implementation is just fine Remove CefSubProcess Rename CefAppWrapper to CefSubProcess
2016-05-16 18:52:35 +10:00
Untabify
2016-05-31 08:27:58 +10:00
virtual void OnBrowserCreated(CefBrowserWrapper^ cefBrowserWrapper)
{
Remove CefSubProcess.cpp - having such trivial cpp files seems silly Convert CefRenderProcess into a cpp class - this should theoretically allow users to add CefSharp.BrowserSubprocess.Core as a reference then use their own process to spawn it Move CefRenderProcess and CefSubProcess into CefSharp.BrowserSubprocess namespace - otherclasses should really be moved as well Only use our custom subProcess when type is render, for gpu and plugin processes the standard implementation is just fine Remove CefSubProcess Rename CefAppWrapper to CefSubProcess
2016-05-16 18:52:35 +10:00
Untabify
2016-05-31 08:27:58 +10:00
}
Remove CefSubProcess.cpp - having such trivial cpp files seems silly Convert CefRenderProcess into a cpp class - this should theoretically allow users to add CefSharp.BrowserSubprocess.Core as a reference then use their own process to spawn it Move CefRenderProcess and CefSubProcess into CefSharp.BrowserSubprocess namespace - otherclasses should really be moved as well Only use our custom subProcess when type is render, for gpu and plugin processes the standard implementation is just fine Remove CefSubProcess Rename CefAppWrapper to CefSubProcess
2016-05-16 18:52:35 +10:00
Untabify
2016-05-31 08:27:58 +10:00
virtual void OnBrowserDestroyed(CefBrowserWrapper^ cefBrowserWrapper)
{
Remove CefSubProcess.cpp - having such trivial cpp files seems silly Convert CefRenderProcess into a cpp class - this should theoretically allow users to add CefSharp.BrowserSubprocess.Core as a reference then use their own process to spawn it Move CefRenderProcess and CefSubProcess into CefSharp.BrowserSubprocess namespace - otherclasses should really be moved as well Only use our custom subProcess when type is render, for gpu and plugin processes the standard implementation is just fine Remove CefSubProcess Rename CefAppWrapper to CefSubProcess
2016-05-16 18:52:35 +10:00
Untabify
2016-05-31 08:27:58 +10:00
}
Remove CefSubProcess.cpp - having such trivial cpp files seems silly Convert CefRenderProcess into a cpp class - this should theoretically allow users to add CefSharp.BrowserSubprocess.Core as a reference then use their own process to spawn it Move CefRenderProcess and CefSubProcess into CefSharp.BrowserSubprocess namespace - otherclasses should really be moved as well Only use our custom subProcess when type is render, for gpu and plugin processes the standard implementation is just fine Remove CefSubProcess Rename CefAppWrapper to CefSubProcess
2016-05-16 18:52:35 +10:00
Network Service - Register custom scheme in all process types The network services requires that custom schemes be registered, previously we only registered them in render processes. Add SubProcessApp to handle scheme registration CefAppUnmanagedWrapper inherits SubProcessApp now #2743
2019-07-04 20:47:21 +10:00
static int ExecuteProcess(IEnumerable<String^>^ args)
Untabify
2016-05-31 08:27:58 +10:00
{
auto hInstance = Process::GetCurrentProcess()->Handle;
Remove CefSubProcess.cpp - having such trivial cpp files seems silly Convert CefRenderProcess into a cpp class - this should theoretically allow users to add CefSharp.BrowserSubprocess.Core as a reference then use their own process to spawn it Move CefRenderProcess and CefSubProcess into CefSharp.BrowserSubprocess namespace - otherclasses should really be moved as well Only use our custom subProcess when type is render, for gpu and plugin processes the standard implementation is just fine Remove CefSubProcess Rename CefAppWrapper to CefSubProcess
2016-05-16 18:52:35 +10:00
Untabify
2016-05-31 08:27:58 +10:00
CefMainArgs cefMainArgs((HINSTANCE)hInstance.ToPointer());
Remove CefSubProcess.cpp - having such trivial cpp files seems silly Convert CefRenderProcess into a cpp class - this should theoretically allow users to add CefSharp.BrowserSubprocess.Core as a reference then use their own process to spawn it Move CefRenderProcess and CefSubProcess into CefSharp.BrowserSubprocess namespace - otherclasses should really be moved as well Only use our custom subProcess when type is render, for gpu and plugin processes the standard implementation is just fine Remove CefSubProcess Rename CefAppWrapper to CefSubProcess
2016-05-16 18:52:35 +10:00
Network Service - Register custom scheme in all process types The network services requires that custom schemes be registered, previously we only registered them in render processes. Add SubProcessApp to handle scheme registration CefAppUnmanagedWrapper inherits SubProcessApp now #2743
2019-07-04 20:47:21 +10:00
auto schemes = CefCustomScheme::ParseCommandLineArguments(args);
CefRefPtr<CefApp> app = new SubProcessApp(schemes);
C++/CLI - Replace NULL with nullptr Issue #3636
2021-07-31 15:35:38 +10:00
return CefExecuteProcess(cefMainArgs, app, nullptr);
Untabify
2016-05-31 08:27:58 +10:00
}
};
}
Remove CefSubProcess.cpp - having such trivial cpp files seems silly Convert CefRenderProcess into a cpp class - this should theoretically allow users to add CefSharp.BrowserSubprocess.Core as a reference then use their own process to spawn it Move CefRenderProcess and CefSubProcess into CefSharp.BrowserSubprocess namespace - otherclasses should really be moved as well Only use our custom subProcess when type is render, for gpu and plugin processes the standard implementation is just fine Remove CefSubProcess Rename CefAppWrapper to CefSubProcess
2016-05-16 18:52:35 +10:00
}
Reference in New Issue Copy Permalink