Allow launch prefixes

[PZeide]

It would be great if we could configure a prefix to use when launching an app (i.e: 'uwsm app -- '). It's needed for anyone who use uwsm for example.

[System64fumo]

I uhh don't quite get it?
Do you mean having an argument to launch programs?

Like: sysmenu someprog?

[PZeide]

For example, when using uwsm, you need to prefix every commands like 'codium' or 'obs' with 'uwsm app --' (i.e: uwsm app -- obs). It allows uwsm to launch your app in the systemd 'app-graphical.slice'. Hyprland has a great docs about that.
So it would be great if I could configure sysmenu so that any app launch is prefixed with a configurable string.

[System64fumo]

I'm sorry i still don't get it?

[PZeide]

Well, English is not my native language so maybe my explanations are hard to understand.
Here's a little example snippet of code maybe it will be easier to understand (I dont really know a lot of cpp so my code is probably wrong but the idea is here)

Currently, for the dock, this is the function to launch the clicked item (I think):

void dock::on_child_activated(Gtk::FlowBoxChild* child) {
    dock_item *button = dynamic_cast<dock_item*>(child);
    button->app_info->launch(std::vector<Glib::RefPtr<Gio::File>>());
}

What I want to explain is this:

void dock::on_child_activated(Gtk::FlowBoxChild* child) {
    dock_item *button = dynamic_cast<dock_item*>(child);

    // Somehow get the config
    if (config_main["main"]["launch-prefix"] == "") {
        button->app_info->launch(std::vector<Glib::RefPtr<Gio::File>>());
    } else {
        // If there is a launch-prefix configured, construct a new AppInfo with the prefix
        const char *commandline = button->app_info->get_commandline();
        // Concatenate the prefix and the commandline of the app_info
        const char* prefixed_command_line = main_config["main"]["launch-prefix"] + command_line;
        // Construct the prefixed AppInfo
        AppInfo *prefixed_app_info = AppInfo.create_from_commandline(prefixed_command_line, NULL);
        // Then launch the prefixed app info
        prefixed_app_info->launch(std::vector<Glib::RefPtr<Gio::File>>());
    }
}

( I tried to follow Gio docs at best but Im probably wrong).

Then, if I set config_main["main"]["launch-prefix"] to uwsm app -- and I run an app like OBS, the commandline executed by Gio.AppInfo.launch will be uwsm app -- obs instead of only obs for example.
I don't know if it's feasible or not but it would be great if I could configure something like that.

[System64fumo]

I'm still confused, From what i understand you're trying to add a method to launch a program via sysmenu?
Like
sysmenu obs and it would execute that?

[logrusx]

UWSM (Universal Wayland Session Manager) manages your Wayland session which includes running applications for you. For example I modified syspower to execute uwsm stop because I'm using uwsm to run my Hyprland instance and if I call terminate session it terminates it all including the login manager. Instead by calling uwsm it can stop everything it started gracefully and exit the user session without killing the login manager.

What OP's asking is for a way to add uwsm app -- in front, so that the application can be launched through uwsm.

[System64fumo]

Ohh i see now, Since i don't use uwsm i don't know what the exact issue but i'm assuming uwsm app -- sysmenu should work no?

[logrusx]

Ohh i see now, Since i don't use uwsm i don't know what the exact issue but i'm assuming uwsm app -- sysmenu should work no?

It's actually how I did it with walker, I'm not sure if that's the correct way though. I have no knowledge in that area.

[System64fumo]

@PZeide Do you mind providing more details?
Sorry for all of this by the way 😅

[logrusx]

Ohh i see now, Since i don't use uwsm i don't know what the exact issue but i'm assuming uwsm app -- sysmenu should work no?

It's actually how I did it with walker, I'm not sure if that's the correct way though. I have no knowledge in that area.

Actually if sysmenu never exits, that's not the way to use it with uwsm. To use if with uwsm, the commands run by sysmenu should be uwsm app -- <actual command here>
Otherwise if sysmenu is run through uwsm with uwsm app -- sysmenu it'll all go into one slice which is not the intended behavior, exactly the opposite.

[System64fumo]

Ah i see now.
I don't think i can do that since programs are launched like so:
item->app_info->launch(std::vector<Glib::RefPtr<Gio::File>>());

Not exactly the same way as launching a program via a terminal more like launching the .desktop file for the program.

[PZeide]

Ohh i see now, Since i don't use uwsm i don't know what the exact issue but i'm assuming uwsm app -- sysmenu should work no?

It's actually how I did it with walker, I'm not sure if that's the correct way though. I have no knowledge in that area.

Walker has a setting named: "AppLaunchPrefix" which mitigate this issue. Launching sysmenu using uwsm is only a part of the solution, every apps launched through sysmenu should also be launched through "uwsm app --" (in their own slice). It's why walker has this setting implemented.

[logrusx]

It's actually how I did it with walker, I'm not sure if that's the correct way though. I have no knowledge in that area.

Walker has a setting named: "AppLaunchPrefix" which mitigate this issue.

Ah, thanks for pointing that out. I hadn't yet gone through the configuration, it was next thing in the list.

[PZeide]

Ah i see now. I don't think i can do that since programs are launched like so: item->app_info->launch(std::vector<Glib::RefPtr<Gio::File>>());

Not exactly the same way as launching a program via a terminal more like launching the .desktop file for the program.

I think a .desktop file is just a file that contains some metadata and a commandline to start the app (maybe I'm incorrect). it's why you could maybe build a new app_info using AppInfo.create_from_commandline (docs) to add uwsm app -- before.

[System64fumo]

I think a .desktop file is just a file that contains some metadata and a commandline to start the app

Correct.

It's why you could maybe build a new app_info using AppInfo.create_from_commandline

True..
Eh i'll see if i can do this later, Sounds like boring work.

But thanks for the guidance 👍