OnDemand menu item action - Are the programs suppose to run?

[bigpcman]

I noticed after installing via appbrowser "nano" that the program is not activated when the menu item is clicked. The .wmx nano entry is as follows:

Code: [Select]

tc@box:~/.wmx/OnDemand$ cat nano
#!/bin/sh
SAVE_ARGS=$*
2>/dev/null read TCEDIR < /opt/.tce_dir || exit 1
if [ ! -e /usr/local/tce.installed/nano ]; then
  tce-load -is $TCEDIR/optional/nano.tcz
fi

VIM appears to do the same thing:

Code: [Select]

tc@box:~/.wmx/OnDemand$ cat vim
#!/bin/sh
SAVE_ARGS=$*
2>/dev/null read TCEDIR < /opt/.tce_dir || exit 1
if [ ! -e /usr/local/tce.installed/vim ]; then
  tce-load -is $TCEDIR/optional/vim.tcz
fi
I thought the menu entry would actually activate the program.

In the case of vim, it would be great to have a gvim entry as well, since the extension installs it, that would get activated when the menu item is clicked.

Running tc 3.8.4

[roberts]

We recently has this discussion regarding command line programs.
If you load either onboot you notice that there is no menu to launch them either.

This is because the extension maker has chosen to set them up this way.
If the maker had an included a freedesktop item for at least a menu then there would be a menu item (onboot) and
ondemand would work as it does for extensions with such.

The recent discussion conclued with support of cliorx, e.g., Exec=cliorx nano
That way ondemand programs could be launched with or without X.

The most recent release even supports freedesktop item without the X-FullPathIcon as well as using base generic icons!

The infrastructure is there to support it. It requires extension makers to deploy it.

Without a freedesktop menu item, ondemand works exactly the same way as onboot, i.e., only loads the extension.
One is then required to open an xterm to launch.