Hi Ball000,

thanks for your input :appreciated:

Quote:
Appearantly not :/

It seems doing it like you suggested, it still does not 'push' the name of the script to the tool. The tool will run, but the script isn't started.

I always wondered about why it isn't possible (at least that i know of) to have that CLI tooltype have something like e.g. CLI %F, and that it automatically replaces the %F with the (full) name of the actual project file that the icon belongs to.

I actually got something working, but it needs some cleanup.

Basically it is just like the normal iconx command but with a search replace for an additional tooltype (CLICOMMAND in my situation).

- the tool is set to wb2cli
- normal tooltypes as for iconX apply
- extra tooltype e.g. CLICOMMAND=lua:lua "%F"
- wb2cli reads CLICOMMAND tooltype
- wb2cli replaces %F with the original project-name.
- wb2cli systemtags() the lua:lua command with additional parameter

I am all for a system default solution, but i haven't come across it yet :/ (which is not a big wonder as normally a command like lua would _know_ about tooltypes and act accordingly. Alas, reality is that wb2cli seems to fill a gap.

Any other suggestions are welcome, as i am out of ideas myself.

Isn't it enough to put "CLI" (without the quotes) in the tooltypes of the default icon. It should be sufficient, considering how the OpenWorkbenchObject() function works.

@azvereth:
Exactly

You are on the right track. you might want to consider another tooltype called parameters (besides runwith).

Reason for this is for programs and/or scripts with spaces in their name, which could lead to problems. Ofcourse implementing quoting (and/or double-quoting) is also an option ofcourse. As long as it is handled ok, it should work.

Oh, and a word of warning: if you use your tool in a default icon, you also have to consider the fact that somneone could select 10 icons which have your tool in it's icon you would get all scripts as paramters in one go (in wbargs). At least that is how i understood it to work.

Thanks....

Think is it not so hard to implement that with FPC.... Perhaps it is possible to use AmiLUA as a "wrapper" (investigating as I have not written a single line of code in lua ever).

Think I am going to give it a try.

It is just as simple as take the WBMessage which contain two params the tool and the invoked projectname...
the tool must be the imaginary WBtoCLI but perhaps it is possibel (it should be) to provide a default tool to use in tooltypes tab as an argument, for example RUNWITH=lua:lua

Internally the WBtoCLI should be like start a shell FROM passed script with lua:lua <projectfile>

Hi azvareth,

More info required (so i can check).

- Wanderer or dopus magellan (and if the latter in which 'mode').
- Icaros desktop 1.5.2 regular or wip5, or perhaps even something else ?

In theory it should already work out of the box (if lua supports detecting started from wb), and if parameters are required then yes a solution like xicon (not iconx) can be used to parse (extra) parameters (could be a bit ackward on a default icon though).

red:
Here is an example of how to 'detect' started from wb/cli and act accordingly. More about implementation can be found here and to summarize here. (just try it with fpc, it's a piece of cake ).

Only when extra parameters are required then one would have to fallback to the arguments in the toollist and act accordingly.

red2: just checked (icaros WiP5) with for example Development/Lua/test-mui/Blancing.alua using doubleclick in Wanderer -> works like a charm.

red3: ah, got it. Indeed it would require some sort of 'frontend' like xicon that is capable of providing arguments through using tooltypes in the icon.

Reason for this is that programs like lua are not aware of amiga startup differences and tooltypes (hence why amilua exist).

The only way to be able to solve that is by either using a iconx script, but that would require you to provide the name of the script (and therefor iconx would defeat its own purpose) or something similar as xicon that can parse the tooltypes and 'push' them to the Tool given in the project icon. If something like textmacros can be used in the tooltype (e.g. %FILENAME% for the actual scriptname that was associated with the project's icon) then you could create a default icon for such (commandline) tools that doesn't have a clue about amiga.

Hello!

This might be a quite stupid question, however... I am trying to do something like this...

I have a show all icons selected in lua test directory (as the files have no .info file...

There I try to doubleclick one of the icons in hope that it should (according to the default icons tooltype lua:lua) launch lua and pass the script to the parser/interpreter but it does not...

It stops in some sort of interactive commandline version of lua.

I can however launch a CLI window and type lua:lua script.lua, and that works.

So to the question.

Could the default_lua icon be set up so that lua (or whatever default project tool) is invoked and the selected project file is passed as an argument to the tool itself...

Like an imaginary WBToCli that takes all WBParams and adjust them for CLI usage. for example something like this WBToCLI <"default command"> [$selectedfile]

note: I tried to use the Open command as well... but it did not work, I guess that tool check the default icon project tool and finds itself.