mirror of
https://github.com/LadybirdBrowser/ladybird.git
synced 2025-10-09 09:39:13 +00:00
5f8d852dae
Currently, if we want to add a new e.g. WebContent command line option, we have to add it to all of Qt, AppKit, and headless-browser. (Or worse, we only add it to one of these, and we have feature disparity). To prevent this, this moves command line flags to WebView::Application. The flags are assigned to ChromeOptions and WebContentOptions structs. Each chrome can still add its platform-specific options; for example, the Qt chrome has a flag to enable Qt networking. There should be no behavior change here, other than that AppKit will now support command line flags that were previously only supported by Qt.
91 lines
2.9 KiB
C++
91 lines
2.9 KiB
C++
/*
|
|
* Copyright (c) 2024, Andrew Kaster <akaster@serenityos.org>
|
|
*
|
|
* SPDX-License-Identifier: BSD-2-Clause
|
|
*/
|
|
|
|
#pragma once
|
|
|
|
#include <AK/Badge.h>
|
|
#include <LibCore/EventLoop.h>
|
|
#include <LibMain/Main.h>
|
|
#include <LibURL/URL.h>
|
|
#include <LibWebView/Options.h>
|
|
#include <LibWebView/Process.h>
|
|
#include <LibWebView/ProcessManager.h>
|
|
|
|
#ifdef __swift__
|
|
# include <swift/bridging>
|
|
#else
|
|
# define SWIFT_IMMORTAL_REFERENCE
|
|
#endif
|
|
|
|
namespace WebView {
|
|
|
|
class Application {
|
|
AK_MAKE_NONCOPYABLE(Application);
|
|
|
|
public:
|
|
virtual ~Application();
|
|
|
|
int execute();
|
|
|
|
static Application& the() { return *s_the; }
|
|
|
|
static ChromeOptions const& chrome_options() { return the().m_chrome_options; }
|
|
static WebContentOptions const& web_content_options() { return the().m_web_content_options; }
|
|
|
|
Core::EventLoop& event_loop() { return m_event_loop; }
|
|
|
|
void add_child_process(Process&&);
|
|
|
|
// FIXME: Should these methods be part of Application, instead of deferring to ProcessManager?
|
|
#if defined(AK_OS_MACH)
|
|
void set_process_mach_port(pid_t, Core::MachPort&&);
|
|
#endif
|
|
Optional<Process&> find_process(pid_t);
|
|
|
|
// FIXME: Should we just expose the ProcessManager via a getter?
|
|
void update_process_statistics();
|
|
String generate_process_statistics_html();
|
|
|
|
protected:
|
|
template<DerivedFrom<Application> ApplicationType>
|
|
static NonnullOwnPtr<ApplicationType> create(Main::Arguments& arguments, URL::URL new_tab_page_url)
|
|
{
|
|
auto app = adopt_own(*new ApplicationType { {}, arguments });
|
|
app->initialize(arguments, move(new_tab_page_url));
|
|
|
|
return app;
|
|
}
|
|
|
|
Application();
|
|
|
|
virtual void process_did_exit(Process&&);
|
|
|
|
virtual void create_platform_arguments(Core::ArgsParser&) { }
|
|
virtual void create_platform_options(ChromeOptions&, WebContentOptions&) { }
|
|
|
|
private:
|
|
void initialize(Main::Arguments const& arguments, URL::URL new_tab_page_url);
|
|
|
|
static Application* s_the;
|
|
|
|
ChromeOptions m_chrome_options;
|
|
WebContentOptions m_web_content_options;
|
|
|
|
Core::EventLoop m_event_loop;
|
|
ProcessManager m_process_manager;
|
|
bool m_in_shutdown { false };
|
|
} SWIFT_IMMORTAL_REFERENCE;
|
|
|
|
}
|
|
|
|
#define WEB_VIEW_APPLICATION(ApplicationType) \
|
|
public: \
|
|
static NonnullOwnPtr<ApplicationType> create(Main::Arguments& arguments, URL::URL new_tab_page_url) \
|
|
{ \
|
|
return WebView::Application::create<ApplicationType>(arguments, move(new_tab_page_url)); \
|
|
} \
|
|
\
|
|
ApplicationType(Badge<WebView::Application>, Main::Arguments&);
|