Process, those are provided by higher levels. The engine itself does not have a user interface, norĭoes it take input, nor does it know how to connect to an actual The iOS and UIKit code share a lot of the code, that code lives under the Apple directory.īoth of these rely on the terminal engine (implemented in class In the iOS sample that that connects the TerminalView for iOS to an SSH connection. But this git module references a module that pullsĪ precompiled SSH client ( Frugghi's SwiftSH), along with The core library currently does not provide a convenient way to connect to SSH, purely And the safest way ofĬonnecting to a remote system is with SSH. Not offer access to processes, the most common scenario will be to Unlike the NSView case running on a Mac, whereĪ common scenario will be to run local commands, given that iOS does

That can be connected to your application by implementing the same Which like its NSView companion is an embeddable and reusable view There is an equivalent UIKit UIVIew implementation for The TerminalView to a Unix pseudo-terminal and runs a command there. To host a local Unix command, so I have included I anticipate that a common scenario will be NSView control that can be connected to any source by implementing the The macOS AppKit NSView implemention TerminalView is a reusable This repository contains both the terminal emulator engine, as well as concrete implementation for iOS using UIKit, and macOS using AppKit. SwiftTerm is a VT100/Xterm terminal Emulator for Swift applications that can be embedded into macOS or iOS applications.

Terminal emulator for mac