manter VS tauri

Link to the project: https://github.com/iondodon/manter

Link to project: https://github.com/iondodon/manter

How to add autocomplete suggestions support for your needed CLI: https://github.com/iondodon/manter/wiki

Link to project:

https://github.com/iondodon/manter

This project aims to create a terminal with functionalities that improve the experience of using terminals. Examples of useful functionalities would be autocomplete suggestion, showing the current branch of a project, prepared scripts that can be reused, and others. You can come up with your ideas. The project uses technologies such as Svelte on the front-end, which offers flexibility regarding the implementation of the interface. On the back-end side, the most important part is the PTY. All the back end is implemented in Rust. The basic framework of the project is Tauri.

At the moment the terminal has suggestions only for some commands (cd, ls). To support more commands it is needed to add them in the Manter's "library" located at src/cli/library/library.ts. It is possible to have custom script based suggestions. For example if we write in the terminal “git checkout” and after we press Space, a dropdown will appear with all available branches.

A good analogy to understand the purpose of this project is the following - traditional terminals are like simple code editors while this terminal is like an IDE.

Anyone is welcome to contribute to this project with and ideas. Imagine the terminal you would like to use. Feel free to open any issue with suggestions and bugs.

Terminal built with Tauri (Rust+Svelte).

I got this idea of creating a terminal that is more user friendly having autocomplete suggestions. I couldn’t create a suggestions engine that would work for all commands. But I defined a structure (a state machine in src/cli/library/library.ts) that can be used to determine the next suggestions. The good part with this approach is that it is possible to have custom script based suggestions. For example if we write in the terminal “git checkout” and after we press Space, a dropdown will appear with all available branches. The bad part is that it will take some time to add more supported commands in this “library”.

Another feature is that in the bottom bar of the terminal we can have custom script based information. In .manter.json we can define a script that will generate this information. The script will be executed each time the prompt appears.

On the front-end are used web technologies which offer a flexibility to add any feature and style that we want.

Repository: https://github.com/iondodon/manter

I'm working on my new open-source project Manter (cross-platform terminal). Learning Rust by building software.

Hi, dear Tauri! Long time no see. I published my first post, Developing a Desktop Application via Rust and NextJS. The Tauri Way almost a year ago. Since then, Tauri has become stronger. I'm happy about that! And now, I am very pleased to make a useful contribution to the Tauri community. As a full-stack developer, I frequently face situations where I need to start a DB-based UI project as fast as possible. It's stressful if I need to start the project from 100% scratch. I prefer to keep some boilerplates on hand, which will save me time and nerves and will be the subject of this article.

Hey Thanks!

Just electron & vite. I might actually migrate off electron, Tauri (https://tauri.app/) seems to be getting more stable and it's gotten great reviews.

I think this is the boilerplate I used though https://github.com/cawa-93/vite-electron-builder.

Well the great thing about WebAssembly is that you can port QT or anything else to be at a layer below -- thanks to WebAssembly Interface Types[0] and the Component Model specification that works underneath that.

To over-simplify, the Component Model manages language interop, and WIT constrains the boundaries with interfaces.

IMO the problem here is defining a 90% solution for most window, tab, button, etc management, then building embeddings in QT, Flutter/Skia, and other lower level engines. Getting a good cross-platform way of doing data passing, triggering re-renders, serializing window state is probably the meat of the interesting work.

On top of that, you really need great UX. This is normally where projects fall short -- why should I use this solution instead of something like Tauri[2] which is excellent or Electron?

[0]: https://github.com/WebAssembly/component-model/blob/main/des...

[1]: https://github.com/WebAssembly/component-model/blob/main/des...

[2]: https://tauri.app/

Welcome to the 2nd episode of our series “Building with Tauri”, where we chat with developers who build amazing projects and products using Tauri.

Tauri seemed like the "thing" I should switch to because everybody loves Rust (heh), and because it ships significantly smaller apps.

First of all, I will be using npm as my package manager but feel free to use whatever you prefer. Find more info here.

Today I'm talking about Tauri! Do you know all the various tools that allow you to develop native applications starting from web languages? They often need an intermediate compilation, in the middle of which you end up encountering various problems not always transparent and directly solvable with a language mostly detached from native development. On the other hand, there's still the ease of developing attractive and easily usable interfaces, which are more difficult to develop with low level languages.