wez/wezterm
1
1
Fork 0
mirror of https://github.com/wez/wezterm.git synced 2024-12-18 10:52:16 +03:00
Code Issues Projects Releases Wiki Activity
7be824db62
wezterm/window/Cargo.toml

94 lines
2.6 KiB
TOML
Raw Normal View History

add very basic win32 window creation
2019-08-08 05:19:04 +03:00
[package]
name = "window"
version = "0.1.0"
authors = ["Wez Furlong"]
edition = "2018"
repository = "https://github.com/wez/wezterm"
description = "Cross platform window setup and render"
license = "MIT"
window: take a stabe at EGL for linux/windows This doesn't initialize it at all properly yet, but is groundwork for completing that work in a later commit
2019-10-25 01:54:41 +03:00
build = "build.rs"
window: enable egl support for wayland
2019-11-30 05:05:09 +03:00
[dev-dependencies]
window: add xsettings support on X11 systems This allows reading xsettings which contain information about both the active theme as well as the DPI. refs: #947
2021-07-18 22:52:20 +03:00
k9 = "0.11.0"
window: enable egl support for wayland
2019-11-30 05:05:09 +03:00
window: take a stabe at EGL for linux/windows This doesn't initialize it at all properly yet, but is groundwork for completing that work in a later commit
2019-10-25 01:54:41 +03:00
[build-dependencies]
window: make opengl always required
2020-12-29 23:13:23 +03:00
gl_generator = "0.14"
add very basic win32 window creation
2019-08-08 05:19:04 +03:00
Allow building without wayland support You can run `cargo build --release --no-default-features` to build without wayland support. This is useful for systems that do not have wayland (eg: the `slint` distro).
2021-06-27 03:05:22 +03:00
[features]
wayland: replace andrew with tiny_skia This has the consequence of removing the title bar text when client side decorations are in use.
2021-06-27 05:16:56 +03:00
wayland = ["wayland-client", "smithay-client-toolkit", "wayland-egl", "wayland-protocols"]
Allow building without wayland support You can run `cargo build --release --no-default-features` to build without wayland support. This is useful for systems that do not have wayland (eg: the `slint` distro).
2021-06-27 03:05:22 +03:00
add very basic win32 window creation
2019-08-08 05:19:04 +03:00
[dependencies]
window: separate gui window state from app state Removes the callbacks type and replaces event dispatch with an async capable channel. This makes it a bit simpler to model some of the window internals, and to prepare for a wgpu enabled future. This changes have been tested only on linux so far.
2021-05-04 18:38:43 +03:00
async-channel = "1.6"
wayland: fix key repeat The main culprit was the calloop feature that is used by default in the underlying SCTK crate. This commit: * Routes keyboard processing via the same keyboard mapping code that we use for X11 * Implements key repeats directly, and with awareness of elapsed time in case the repeat rate is quicker than the event dispatching quantum * Disables the calloop feature of SCTK and let us do our own polling of the wayland connection. Critically, key repeat is sticky and unpredictable while calloop is enabled. closes: #669
2021-06-28 00:24:41 +03:00
async-io = "1.1"
deps: misc updates
2020-12-29 20:21:50 +03:00
async-task = "4.0"
window: separate gui window state from app state Removes the callbacks type and replaces event dispatch with an async capable channel. This makes it a bit simpler to model some of the window internals, and to prepare for a wgpu enabled future. This changes have been tested only on linux so far.
2021-05-04 18:38:43 +03:00
async-trait = "0.1"
failure -> anyhow + thiserror
2019-12-15 08:43:05 +03:00
anyhow = "1.0"
window: add xsettings support on X11 systems This allows reading xsettings which contain information about both the active theme as well as the DPI. refs: #947
2021-07-18 22:52:20 +03:00
bytes = "1.0"
remove the config bridge and have window -> config directly
2021-03-24 07:56:57 +03:00
config = { path = "../config" }
failure -> anyhow + thiserror
2019-12-15 08:43:05 +03:00
thiserror = "1.0"
deps: update bitflags -> 1.3
2021-08-16 04:21:17 +03:00
bitflags = "1.3"
deps: upgrade euclid -> 0.22
2020-12-10 21:03:16 +03:00
euclid = "0.22"
wezterm: improve texture atlas allocation This commit uses the guillotine algorithm to assign rectangles, which is superior to the dumb algorithm previously in use. In addition, in the first pass of painting, if we get a texture space error, we clear the atlas and try again without increasing it size, which should serve as the ultimate defrag. Subsequent passes will cause the texture to grow if needed. refs: #306
2020-10-23 23:57:58 +03:00
guillotiere = "0.6"
deps: normalize the lazy-static version
2020-11-13 18:57:09 +03:00
lazy_static = "1.4"
window: make opengl always required
2020-12-29 23:13:23 +03:00
libloading = "0.6"
add arbitrary line drawing with anti-aliasing
2019-08-11 20:15:08 +03:00
line_drawing = "0.8"
window: allow wayland and x11 to co-exist This is a pretty gross and coarse "smash them together" commit. There is some redundancy between the two connection and window impls that I'd like to unify later, but this lets us build with support for both systems for now.
2019-11-28 19:51:54 +03:00
log = "0.4"
deps: cargo update, and a couple of dependabot suggestions
2021-07-19 05:10:46 +03:00
metrics = { version="0.17", features=["std"]}
add very basic win32 window creation
2019-08-08 05:19:04 +03:00
promise = { path = "../promise" }
add raw-window-handle impls
2021-05-06 08:59:52 +03:00
raw-window-handle = "0.3"
deps: misc updates
2020-12-29 20:21:50 +03:00
resize = "0.5"
wezterm: add raw_code concept to input layer This commit is a bit noisy because it also meant flipping the key map code from using the termwiz input types to the window input types, which I thought I'd done some time ago, but clearly didn't. This commit allows defining key assignments in terms of the underlying operating system raw codes, if provided by the relevant layer in the window crate (currently, only X11/Wayland). The raw codes are inherently OS/Machine/Hardware dependent; they are the rawest value that we have available and there is no meaningful understanding that we can perform in code to understand what that key is. One useful property of the raw code is that, because it hasn't gone through any OS level keymapping processing, its value reflects its physical position on the keyboard, allowing you to map keys by position rather than by value. That's useful if you use software to implement eg: DVORAK or COLEMAK but want your muscle memory to kick in for some of your key bindings. New config option: `debug_key_events = true` will cause wezterm to log an "error" to stderr each time you press a key and show the details in the key event: ``` 2020-12-06T21:23:10.313Z ERROR wezterm_gui::gui::termwindow > key_event KeyEvent { key: Char('@'), modifiers: SHIFT | CTRL, raw_key: None, raw_modifiers: SHIFT | CTRL, raw_code: Some(11), repeat_count: 1, key_is_down: true } ``` This is useful if you want to figure out the `raw_code` for a key in your setup. In your config, you can use this information to setup new key bindings. The motivating example for me is that because `raw_key` (the unmodified equivalent of `key`) is `None`, the built-in `CTRL-SHIFT-1` key assignment doesn't function for me on Linux, but I can now "fix" this in my local configuration, taking care to make it linux specific: ```lua local wezterm = require 'wezterm'; local keys = {} if wezterm.target_triple == "x86_64-unknown-linux-gnu" then local tab_no = 0 -- raw codes 10 through 19 correspond to the number key 1-9 positions -- on my keyboard on my linux system. They may be different on -- your system! for i = 10, 20 do table.insert(keys, { key="raw:"..tostring(i), mods="CTRL|SHIFT", action=wezterm.action{ActivateTab=tab_no}, }) tab_no = tab_no + 1 end end return { keys = keys, } ``` Notice that the key assignment accepts encoding a raw key code using a value like `key="raw:11"` to indicate that you want a `raw_code` of `11` to match your key assignment. The `raw_modifiers` portion of the `KeyEvent` is used together with the `raw_code` when deciding the key assignment. cc: @bew
2020-12-07 00:23:37 +03:00
serde = {version="1.0", features = ["rc", "derive"]}
deps: tiny-skia -> 0.7 closes: #2219
2022-07-04 16:30:34 +03:00
tiny-skia = "0.7"
deps: unpin glium from git, use latest release We were pinned on the revision where I had added dual source blending, because I wanted that feature ahead of the crate being published. Since then a couple of releases have been made so we can unpin. On Windows 11, we had a report of glium complaining about the opengl version. I can't find that error message string in the current version of the code so it's possible that that situation has been resolved. refs: https://github.com/wez/wezterm/issues/1813
2022-04-04 16:49:09 +03:00
glium = { version = "0.31", default-features = false }
support drag and drop files for wayland
2022-06-20 14:41:25 +03:00
url = "2"
fix build on linux refs: https://github.com/wez/wezterm/issues/784
2022-01-25 19:27:01 +03:00
wezterm-bidi = { path = "../bidi" }
refactor: move color parsing into wezerm-color-types crate Resolves a little bit of the awkward duplication of color types between some of the crates by factoring them a little bit better. This is prep for allowing specifying alpha for some colors in the config.
2022-02-05 23:59:54 +03:00
wezterm-color-types = { path = "../color-types" }
refactor deps so that window can depend on wezterm-font I want to use this to render the font in the title bar
2021-06-27 05:48:06 +03:00
wezterm-font = { path = "../wezterm-font" }
extract window::input to wezterm-input-types
2020-12-10 00:00:23 +03:00
wezterm-input-types = { path = "../wezterm-input-types" }
add very basic win32 window creation
2019-08-08 05:19:04 +03:00
[target."cfg(windows)".dependencies]
Improve RESIZE window_decoration on Windows
2022-03-24 17:20:26 +03:00
clipboard-win = "2.2"
shared_library = "0.1"
add very basic win32 window creation
2019-08-08 05:19:04 +03:00
winapi = { version = "0.3", features = [
use dark mode
2019-08-08 08:10:30 +03:00
"dwmapi",
add very basic win32 window creation
2019-08-08 05:19:04 +03:00
"handleapi",
Improve? IME on Windows This isn't perfect, but is sufficient to allow using the IME to enter eg: the heart emoji with cmd.exe. We have some issues locating and rendering chinese characters that make it difficult to prove/disprove that the IME is working 100% because we just can't see the glyphs. In addition, there appears to be something a bit wonky with conpty and emoji. If we use eg: `wezterm ssh HOST` to log in to a remote system, and use the IME to pick eg: the pig face emoji, this renders correctly. In that scenario we don't use conpty at all. The IME window is always placed in the top left corner of the window at the moment, which isn't great, but is better than the system default which is outside of the window. I need to introduce a way to set the IME position in the window layer so that the front end gui can set it to the current cursor position.
2019-11-02 19:35:19 +03:00
"imm",
window: tidy up crate deps
2019-08-08 19:13:22 +03:00
"libloaderapi",
add very basic win32 window creation
2019-08-08 05:19:04 +03:00
"synchapi",
Improve RESIZE window_decoration on Windows
2022-03-24 17:20:26 +03:00
"sysinfoapi",
window: tidy up crate deps
2019-08-08 19:13:22 +03:00
"winerror",
"winuser",
add very basic win32 window creation
2019-08-08 05:19:04 +03:00
]}
Improve RESIZE window_decoration on Windows
2022-03-24 17:20:26 +03:00
windows = { version="0.33.0", features = [
"UI_ViewManagement",
screens: improve naming on Windows, move resolve_geom to Connection On Windows, GDI returns unintuitive names like "\\.\DISPLAY6" that may not start numbered at either 0 or 1. This commit grubs through the various APIs so that we can produce more meaningful names like "DISPLAY6: Gigabyte M32u on NVIDIA 2080 TI" instead. This commit also makes the lua wezterm.window.screens() function consistent with the internal resolve_geom functions that each different implementation had, so that we can eliminate those functions in favor of this new one on the ConnectionOps trait. Still need to do macOS and verify that this commit doesn't break X11.
2022-07-06 22:54:18 +03:00
"Win32_Devices_Display",
Improve RESIZE window_decoration on Windows
2022-03-24 17:20:26 +03:00
]}
pty: pre-fill base env from registry env settings on Windows I think I'd like to make a config option for this, but for the moment, this first pass unconditionally updates the base environment with data from the registry. refs: https://github.com/wez/wezterm/issues/1848
2022-04-19 19:56:23 +03:00
winreg = "0.10"
add very basic win32 window creation
2019-08-08 05:19:04 +03:00
basic xcb windows too
2019-08-09 03:44:57 +03:00
[target.'cfg(all(unix, not(target_os = "macos")))'.dependencies]
x11: load XCursor.theme based cursors when available This requires `xcb-util-image-devel` on fedora, not sure about debian or other systems so far. refs: #524
2021-03-09 09:00:42 +03:00
dirs-next = "2.0"
filedescriptor: remove anyhow from public interface Use thiserror instead
2021-05-24 00:24:01 +03:00
filedescriptor = { version="0.8", path = "../filedescriptor" }
x11: make another run at weird resize related issue w/ nvidia This does two things: * Sets the event queue owner explicitly to xcb * Adopts a dri2 resize related workaround from the rust-xcb opengl example I think the latter is probably a NOP, but the former sounds like something important. refs: #1992
2022-06-18 07:17:51 +03:00
x11 = {version ="2.19", features = ["xlib_xcb", "xlib"]}
xcb = {version="1.1.1", features=["render", "randr", "dri2", "xkb", "xlib_xcb", "present"]}
window: point to re-integrated xkbcommon refs: https://github.com/rust-x-bindings/xkbcommon-rs/pull/30
2022-05-10 03:24:20 +03:00
xkbcommon = { version = "0.5.0-beta.0", features = ["x11", "wayland"], git="https://github.com/wez/xkbcommon-rs.git", branch="key-by-name"}
window: deps: upgrade to xcb 1.1 Was a bit fiddly. Eliminated the xcb_util crate refs: https://github.com/wez/wezterm/issues/1952
2022-05-08 00:18:26 +03:00
#xkbcommon = { version = "0.6", features = ["x11", "wayland"], path="../../xkbcommon-rs" }
deps: upgrade to mio 0.8
2022-05-05 05:19:14 +03:00
mio = {version="0.8", features=["os-ext"]}
hook up paint method for x11
2019-08-09 21:15:09 +03:00
libc = "0.2"
window: update smithay-client deps
2021-12-28 17:28:07 +03:00
smithay-client-toolkit = {version = "0.15", default-features=false, optional=true}
wayland-protocols = {version="0.29", optional=true}
wayland-client = {version="0.29", optional=true}
wayland-egl = {version="0.29", optional=true}
window: point to my xcb for for IME changes refs: https://github.com/rust-x-bindings/rust-xcb/pull/190 refs: https://github.com/H-M-H/xcb-imdkit-rs/pull/2
2022-05-08 23:59:24 +03:00
xcb-imdkit = { version="0.2", git="https://github.com/wez/xcb-imdkit-rs.git", rev="ede7c71b85fe2537efef6cf999a45690316211cf"}
x11/wayland: use xdg desktop portal settings interface to get dark mode There are some other settings in there that could also help with things like the cursor theme on Wayland. Note that we don't currently subscribe to the settings changed signal: that can be done in a follow up. refs: https://github.com/wez/wezterm/issues/2258 refs: https://github.com/wez/wezterm/issues/1742
2022-07-13 18:54:24 +03:00
serde = {version="1.0", features = ["derive"]}
deps: update zbus
2022-08-21 19:18:32 +03:00
zbus = "3.0"
zvariant = "3.6"
x11/wayland: use xdg desktop portal settings interface to get dark mode There are some other settings in there that could also help with things like the cursor theme on Wayland. Note that we don't currently subscribe to the settings changed signal: that can be done in a follow up. refs: https://github.com/wez/wezterm/issues/2258 refs: https://github.com/wez/wezterm/issues/1742
2022-07-13 18:54:24 +03:00
futures-util = "0.3"
really basic macos window
2019-08-09 06:53:16 +03:00
[target.'cfg(target_os="macos")'.dependencies]
remove local workaround for core-foundation UB issue My fixes landed upstream in https://github.com/servo/core-foundation-rs/commit/0a3ac83c1bb38d30a4d30530cd233385b7410b2c and are released already to crates.io
2019-11-13 11:05:55 +03:00
cocoa = "0.20"
really basic macos window
2019-08-09 06:53:16 +03:00
objc = "0.2"
switch macos clipboard crate This cleans up the `cargo audit` output on linux because the `clipboard` crate (which hasn't been updated in 3 years) depends on xcb=0.8.2 which is flagged by cargo audit. We don't use `clipboard` on any platform except macos This commit switches to the `clipboard_macos` crate; that appears to use a copy and paste of the macos specific code from the `clipboard` crate, so this shouldn't have any change in functionality. refs: https://github.com/wez/wezterm/issues/1952
2022-05-09 07:11:39 +03:00
clipboard_macos = "0.1"
remove local workaround for core-foundation UB issue My fixes landed upstream in https://github.com/servo/core-foundation-rs/commit/0a3ac83c1bb38d30a4d30530cd233385b7410b2c and are released already to crates.io
2019-11-13 11:05:55 +03:00
core-foundation = "0.7"
core-graphics = "0.19"
window: make opengl always required
2020-12-29 23:13:23 +03:00
cgl = "0.3"
Reference in New Issue Copy Permalink