-
Notifications
You must be signed in to change notification settings - Fork 8.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Productize the WPF, UWP Terminal Controls #6999
Comments
This is something that I would like to see, especially if it was done in such a way that it could be ported to other frameworks such as avaloniaui. |
And maybe also in Uno Platform UI too! 😉 |
@zadjii-msft Any progress about those Tasks? |
Unfortunately nope. I think we originally slated this for late 2023, but alas, other internal priorities came in and bumped this. I think we fully intend to do this sometime SoonTM. |
Love it! 😆 Anyway, I'm thinking about moving (at least for Now ™️) to a web-based terminal emulator like |
End of 2024,any news about it?I am looking for a embedded terminal Control in WinUI3 |
I was able to get it fully working as a WPF control per my sample repo. |
What about WinUi3,my project is a fully WinUi3 project which can not embedde a WPF control in it. |
This scenario tracks the remaining work to productize the UWP and WPF versions of the Terminal Control. These will allow 3rd-party developers to embed terminal instances in their applications. That way, external developers won't need to write their own terminals, they can just re-use the one we build in this repo.
Currently, the Windows Terminal uses the UWP version of the control. Similarly, Visual Studio embeds the WPF version.
Pre-Requisites
These tasks aren't immediately related, but will need to get done first to unblock this work
TerminalCore
as well? Currently the Terminal Core only implements the VT sequences that ConPTY will emit. Hypothetically, someone might be using this in a scenario where conpty isn't on the other end.Tasks
Tasks
related
The text was updated successfully, but these errors were encountered: