Feature Request: ability to lauch command w/o terminal

[adam-kulagowski]

Hi,

I'm trying to launch web browser from X-pipe as some of my network devices have only HTTP/HTTPS management. Currently I'm using Terminal command with with the following command inside: /usr/bin/xdg-open http://X.X.X.X/ Although it works, in most of the cases the opened terminal provides no value as displays only Press [r] to restart or any other key to close this session ... (I've Firefox already running and above actions just creates another TAB inside FF).

I think it would be useful to allow hiding the terminal is some cases and just launch a command in background. Or maybe a new type of connection: Launch an application ?

Maybe I'm missing something but after reading the documentation that was the only way I came up with.

[crschnick]

Yeah I had to few a request for something like that. The problem is that it didn't result in a great plan on how to implement such a feature. I could just add a way to run a command in the background, but for something like opening a simple website that might be a bit overkill.

On that note, simply adding the ability to open a website hasn't made it yet into xpipe as I didn't see the additional value it provided compared to a simple browser bookmark. If you're not using the service tunnels via SSH, e.g. if your system does not support that, then adding an entry in xpipe to open a website it doesn't fit well into the UI. If the system is not added otherwise to XPipe, you will just have a top-level entry floating around that can only open a website and nothing more.

If you can share additional ideas on how to make this more than just a simple browser bookmark, I can look into it.

[adam-kulagowski]

Well, since XPipe advertises itself as a connection hub, request for web connections seems justified ;-)

Being more serious - I know I can use a bookmark but I would like to have all connections to my network devices in one place. Most of network devices supports SSH/telnet but few of them (such us based on Mikrotik SwOS) supports only http://

The current script approach with xdg-open works fine, there is just an unwanted side effect of empty tab in terminal. Adding checkbox to script: "Run in background" should solve everything.

As for the placement - I've moved the script from my Local Maching to the category where SSH connection are. So everything is nice & tidy :)

[crschnick]

I can think of how to implement this for v19. The terminal command entries in general need to be reworked as well