dmaax/ladybird
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
ladybird/UI/AppKit/Application/Application.h

51 lines
2.1 KiB
C
Raw Normal View History

Ladybird: Implement an AppKit chrome for macOS :^) This adds an alternative Ladybird chrome for macOS using the AppKit framework. Just about everything needed for normal web browsing has been implemented. This includes: * Tabbed, scrollable navigation * History navigation (back, forward, reload) * Keyboard / mouse events * Favicons * Context menus * Cookies * Dialogs (alert, confirm, prompt) * WebDriver support This does not include debugging tools like the JavaScript console and inspector, nor theme support. The Qt chrome is still used by default. To use the AppKit chrome, set the ENABLE_QT CMake option to OFF.
2023-08-20 17:14:31 -03:00
/*
LibWebView+UI: Always ask the user where to save screenshots We currently always save screenshots to the Downloads folder. We will now always ask for a save location. This will just let an upcoming feature to save images from web pages behave the same way. We will want the user to be able to choose a file name, since the file name from the URL might be nonsense or already exist.
2026-02-02 20:54:59 -03:00
* Copyright (c) 2023-2026, Tim Flynn <trflynn89@ladybird.org>
Ladybird: Implement an AppKit chrome for macOS :^) This adds an alternative Ladybird chrome for macOS using the AppKit framework. Just about everything needed for normal web browsing has been implemented. This includes: * Tabbed, scrollable navigation * History navigation (back, forward, reload) * Keyboard / mouse events * Favicons * Context menus * Cookies * Dialogs (alert, confirm, prompt) * WebDriver support This does not include debugging tools like the JavaScript console and inspector, nor theme support. The Qt chrome is still used by default. To use the AppKit chrome, set the ENABLE_QT CMake option to OFF.
2023-08-20 17:14:31 -03:00
*
* SPDX-License-Identifier: BSD-2-Clause
*/
#pragma once
LibWebView+WebDriver+UI: Migrate headless browsing to main Ladybird exe We currently create a separate headless-browser application to serve two purposes: 1. Allow headless browsing to take a screenshot of a page or print its layout tree / internal text. 2. Run the LibWeb test framework. This patch migrates (1) to the main Ladybird executable. The --headless flag enables this mode. This matches the behavior of other browsers, and means we have one less executable to ship at distribution time. We want to avoid creating too many AppKit / Qt facilities in headless mode. So this involves some shuffling of application init to ensure we don't create them until after we've parsed the command line arguments. Namely, we avoid creating the NSApp in AppKit and QCoreApplication in Qt. Doing so also requires that we don't create the application event loop until we've parsed the command line as well, because the loop we create depends on whether we're creating those UI facilities.
2025-06-06 16:42:12 -03:00
#include <LibWebView/Application.h>
Ladybird+headless-browser: Make RequestServer single instance on Lagom Co-Authored-By: Timothy Flynn <trflynn89@pm.me>
2024-04-15 20:39:48 -03:00
Ladybird/AppKit: Remove system header workarounds for global names
2024-07-17 02:54:53 -03:00
#import <Cocoa/Cocoa.h>
Ladybird: Implement an AppKit chrome for macOS :^) This adds an alternative Ladybird chrome for macOS using the AppKit framework. Just about everything needed for normal web browsing has been implemented. This includes: * Tabbed, scrollable navigation * History navigation (back, forward, reload) * Keyboard / mouse events * Favicons * Context menus * Cookies * Dialogs (alert, confirm, prompt) * WebDriver support This does not include debugging tools like the JavaScript console and inspector, nor theme support. The Qt chrome is still used by default. To use the AppKit chrome, set the ENABLE_QT CMake option to OFF.
2023-08-20 17:14:31 -03:00
Ladybird+headless-browser: Make RequestServer single instance on Lagom Co-Authored-By: Timothy Flynn <trflynn89@pm.me>
2024-04-15 20:39:48 -03:00
namespace Ladybird {
Meta: Enforce newlines around namespaces This has come up several times during code review, so let's just enforce it using a new clang-format 20 option.
2025-05-13 08:06:33 -03:00
LibWebView+WebDriver+UI: Migrate headless browsing to main Ladybird exe We currently create a separate headless-browser application to serve two purposes: 1. Allow headless browsing to take a screenshot of a page or print its layout tree / internal text. 2. Run the LibWeb test framework. This patch migrates (1) to the main Ladybird executable. The --headless flag enables this mode. This matches the behavior of other browsers, and means we have one less executable to ship at distribution time. We want to avoid creating too many AppKit / Qt facilities in headless mode. So this involves some shuffling of application init to ensure we don't create them until after we've parsed the command line arguments. Namely, we avoid creating the NSApp in AppKit and QCoreApplication in Qt. Doing so also requires that we don't create the application event loop until we've parsed the command line as well, because the loop we create depends on whether we're creating those UI facilities.
2025-06-06 16:42:12 -03:00
class Application final : public WebView::Application {
WEB_VIEW_APPLICATION(Application)
private:
LibWebView+UI: Don't declare a magic ctor for Application subclasses You would have to just know that you need to define the constructor with this declaration. Let's allow subclasses to define constructors as they see fit.
2025-06-10 20:13:03 -03:00
explicit Application();
LibCore: Keep main event loops alive Add an explicit initializer for process-lifetime event loops and use it for browser, helper service, and utility main loops. This preserves weak event loop references for cross-thread users while making main thread loop lifetime independent of normal program teardown.
2026-06-04 14:51:47 -03:00
virtual Core::EventLoop& create_platform_event_loop() override;
LibWebView+UI: Extract some UI-specific displays to Application helpers This is preparation for moving application menus to LibWebView. We will need a way to display these dialogs from outside of the UI layer.
2025-09-04 09:53:57 -03:00
virtual Optional<WebView::ViewImplementation&> active_web_view() const override;
LibWebView+UI: Add an Application method to open a URL in a new tab This lets us avoid each UI needing to handle link clicks directly, and lets actions stored in LibWebView avoid awkwardly going through the link click callbacks to open URLs.
2025-09-13 10:08:24 -03:00
virtual Optional<WebView::ViewImplementation&> open_blank_new_tab(Web::HTML::ActivateTab) const override;
UI+LibWebView: Implement "Open Link in New Window"
2026-02-17 16:23:45 -03:00
virtual void open_url_in_new_window(URL::URL const& url) override;
LibWebView+UI: Extract some UI-specific displays to Application helpers This is preparation for moving application menus to LibWebView. We will need a way to display these dialogs from outside of the UI layer.
2025-09-04 09:53:57 -03:00
LibWebView+UI: Always ask the user where to save screenshots We currently always save screenshots to the Downloads folder. We will now always ask for a save location. This will just let an upcoming feature to save images from web pages behave the same way. We will want the user to be able to choose a file name, since the file name from the URL might be nonsense or already exist.
2026-02-02 20:54:59 -03:00
virtual Optional<ByteString> ask_user_for_download_path(StringView file) const override;
LibWebView+UI: Extract some UI-specific displays to Application helpers This is preparation for moving application menus to LibWebView. We will need a way to display these dialogs from outside of the UI layer.
2025-09-04 09:53:57 -03:00
virtual void display_download_confirmation_dialog(StringView download_name, LexicalPath const& path) const override;
virtual void display_error_dialog(StringView error_message) const override;
LibWebView+UI: Generate action to enable/disable DevTools
2025-09-17 11:03:01 -03:00
LibWeb+LibWebView+UI: Use the system selection text for primary pasting Commit 218d82cb65c636d1a56d6cb921ad1a4afe4f7202 added support for pasting text with the middle mouse button. But primary pasting is actually meant to interact with the "selection" clipboard, not the text clipboard.
2026-05-18 08:18:50 -03:00
virtual Utf16String clipboard_text(ClipboardType) const override;
LibWebView+UI: Move clipboard handling from the WebView to the App Clipboard handling largely has nothing to do with the individual web views. Rather, we interact with the system clipboard at the application level. So let's move these implementations to the Application.
2025-09-18 09:16:36 -03:00
virtual Vector<Web::Clipboard::SystemClipboardRepresentation> clipboard_entries() const override;
virtual void insert_clipboard_entry(Web::Clipboard::SystemClipboardRepresentation) override;
UI/AppKit: Create a bookmarks application menu and toolbar
2026-03-22 12:47:39 -03:00
virtual void rebuild_bookmarks_menu() const override;
LibWebView+UI: Add an about:bookmarks page to manage bookmarks This page renders the bookmarks as a tree and hook context menu events up to the UI's bookmarks bar context menus to allow editing bookmarks. Users can also drag-and-drop bookmark items around.
2026-04-06 20:08:00 -03:00
virtual void show_bookmark_context_menu(Gfx::IntPoint, Optional<WebView::BookmarkItem const&>, Optional<String const&> target_folder_id) override;
UI/AppKit: Integrate bookmark context menus into the bookmarks bar
2026-03-31 08:56:12 -03:00
virtual Optional<BookmarkID> bookmark_item_id_for_context_menu() const override;
virtual NonnullRefPtr<BookmarkPromise> display_add_bookmark_dialog() const override;
virtual NonnullRefPtr<BookmarkPromise> display_edit_bookmark_dialog(WebView::BookmarkItem::Bookmark const& current_bookmark) const override;
virtual NonnullRefPtr<BookmarkFolderPromise> display_add_bookmark_folder_dialog() const override;
virtual NonnullRefPtr<BookmarkFolderPromise> display_edit_bookmark_folder_dialog(WebView::BookmarkItem::Folder const& current_folder) const override;
UI/AppKit: Create a bookmarks application menu and toolbar
2026-03-22 12:47:39 -03:00
LibWebView+UI: Generate action to enable/disable DevTools
2025-09-17 11:03:01 -03:00
virtual void on_devtools_enabled() const override;
virtual void on_devtools_disabled() const override;
LibWebView+WebDriver+UI: Migrate headless browsing to main Ladybird exe We currently create a separate headless-browser application to serve two purposes: 1. Allow headless browsing to take a screenshot of a page or print its layout tree / internal text. 2. Run the LibWeb test framework. This patch migrates (1) to the main Ladybird executable. The --headless flag enables this mode. This matches the behavior of other browsers, and means we have one less executable to ship at distribution time. We want to avoid creating too many AppKit / Qt facilities in headless mode. So this involves some shuffling of application init to ensure we don't create them until after we've parsed the command line arguments. Namely, we avoid creating the NSApp in AppKit and QCoreApplication in Qt. Doing so also requires that we don't create the application event loop until we've parsed the command line as well, because the loop we create depends on whether we're creating those UI facilities.
2025-06-06 16:42:12 -03:00
};
Meta: Enforce newlines around namespaces This has come up several times during code review, so let's just enforce it using a new clang-format 20 option.
2025-05-13 08:06:33 -03:00
Ladybird+headless-browser: Make RequestServer single instance on Lagom Co-Authored-By: Timothy Flynn <trflynn89@pm.me>
2024-04-15 20:39:48 -03:00
}
Ladybird: Implement an AppKit chrome for macOS :^) This adds an alternative Ladybird chrome for macOS using the AppKit framework. Just about everything needed for normal web browsing has been implemented. This includes: * Tabbed, scrollable navigation * History navigation (back, forward, reload) * Keyboard / mouse events * Favicons * Context menus * Cookies * Dialogs (alert, confirm, prompt) * WebDriver support This does not include debugging tools like the JavaScript console and inspector, nor theme support. The Qt chrome is still used by default. To use the AppKit chrome, set the ENABLE_QT CMake option to OFF.
2023-08-20 17:14:31 -03:00
@interface Application : NSApplication
@end
Reference in a new issue Copy permalink