Icon for script on main Workbench window?

[Foebane]

I have been trying to take a script I wrote and stored in System:S and put it onto the main Workbench screen as an icon, so I can quickly and easily run it without having to open the relevant windows, "Execute Command" or DOpus.

How can I create an icon for a script, or indeed any file? It's been decades since I did it, and I've forgotten.

[Leffmann]

One way is to use IconEdit in Tools, save an icon of type "Project", and set its default tool to "C:IconX"

[Foebane]

Thank you, it worked great.

[AMIGASYSTEM]

You can also run a script as if it were an executable, to do this, just add the flag S (Script) to the file. From Workbench you can run this script by adding a "Tool" type icon

[daxb]

DOpus has an AddIcon funktion. Select your file and hit AddIcon button. Or copy an icon you like and rename it to the script name. You can also add a hotkey for the script start. Then no icon is needed.

[kolla]

Originally Posted by AMIGASYSTEM

You can also run a script as if it were an executable, to do this, just add the flag S (Script) to the file. From Workbench you can run this script by adding a "Tool" type icon

There's more to it. The regular WBInfo does not allow you to change icon type, but I presume you use RWBInfo which does.
You can also use ProcessIcon (http://aminet.net/package/util/wb/ProcessIcon)

ProcessIcon MyScript SIT Tool

The tooltype CLI must also be set (which is equivalent to "start from Shell" in WB45 WBInfo and RWBInfo) and most preferably also tooltype "DONOTPROMPT" (equivalent to "do not ask for input" in V45 WBInfo and RWBInfo).

[kolla]

Originally Posted by daxb

DOpus has an AddIcon funktion. Select your file and hit AddIcon button. Or copy an icon you like and rename it to the script name. You can also add a hotkey for the script start. Then no icon is needed.

Yeah, with Workbench, IIRC, an icon will be created once you stuff tooltypes etc into wbinfo window and hit "save". And you can of course use the OS commodity FKey to add hotkeys for launching scripts, instead of having icons on the Workbench.

[malko]

WB 1.3 is not really user-friendly when dealing with icon type.
If you want to change the type of an Icon to "Project" :
1- Load IconEdit
2- (slot 1) Open an already existing icon having the type "Project"
3- In a new slot (let's say slot 2), open the icon you want to change the type
4- Copy the icon opened in point 3- (slot 2) over the icon opened in point 2- (slot 1)
5- Save the icon (slot 1)
The icon has now the type "Project"

[AMIGASYSTEM]

Originally Posted by kolla

There's more to it. The regular WBInfo does not allow you to change icon type, but I presume you use RWBInfo which does..

Yes use RWBInfo (indispensable utility), in any case, you can change icon status with IconEdit or better with IconType

Originally Posted by kolla

The tooltype CLI must also be set (which is equivalent to "start from Shell" in WB45 WBInfo and RWBInfo) and most preferably also tooltype "DONOTPROMPT").

From the Shell the icon is not needed, the file script (S) runs as a normal executable

[ Show youtube player ]

[AMIGASYSTEM]

Originally Posted by malko

WB 1.3 is not really user-friendly when dealing with icon type.

With WB 1.3 you can also use the utility (from Shell) SetIcontype

[Foebane]

Thanks, all. Getting the script to run from an icon has been solved. I used IconEdit and dragging the script to it and setting the icon type, but haven't tried the DOpus Add Icon button yet.

[malko]

Originally Posted by AMIGASYSTEM

With WB 1.3 you can also use the utility (from Shell) SetIcontype

Humm, good to know Will give it a try.

[kolla]

Originally Posted by AMIGASYSTEM

From the Shell the icon is not needed, the file script (S) runs as a normal executable

No, that is not correct. The S flag tells the shell that it shall launch the file using the Execute command, not as a normal executable. In fact, the E (execute) flag should not even be set on such scripts.

With shell v45 from ThoR you can even "launch" other types of files the same way, as it supports datatypes. You just set the variable "VIEWER" to Multiview, and then you can just type "HELP:english/sys/amigaguide.guide" and it will open that file in Multiview. For this to work, the specified file must specifically _not_ have the E (executable) flag set.

[AMIGASYSTEM]

Originally Posted by kolla

No, that is not correct. The S flag tells the shell that it shall launch the file using the Execute command, not as a normal executable. In fact, the E (execute) flag should not even be set on such scripts.

No, just execute is in C, and then the script can be executed directly as an executable, see my video attached

[kolla]

You have a very simplified view of how this works
You should think of the S flag as a way to tell the shell that "Execute" is the default tool for a file - that is all.

Likewise - if you remove the E flag, and have no S flag, it tells the shell to attempt opening the file with the program specified with the $VIEWER variable, if that variable is present.

Likewise - if you set the H flag, and the P flag is present, it tells the shell to also make the program resident when running it.

[AMIGASYSTEM]

Normal that I need to give something to start (Windows does the same thing with the .bat files), even a normal executable needs a library, font or other to start.

[malko]

From "The Best Amiga Tricks & Tips ©1989 Data Becker, GmbH & ©1990 Abacus" :

PROTECT FILE/A,FLAGS,ADD/S,SUB/S
	Determines the protection bits a file should have.
	FILE	The name of the file to protect.
	FLAGS	Sets the protection status.
		R	The file can be read.
		W	The file can be written to.
		D	The file is deletable.
		E	The file is executable.
		In V1.3 the Hidden (H), Script (S), Pure (P) and
		Archive (A) bits can be set or reset.
		H	Hidden file.
		S	The file can be started without execute
			(script files only).
		P	The file can be placed in the Resident list
		A	The file is archived.
		The H and A bits function only with Kickstart 1.3.
	+, ADD	Sets the status of the given Status bit.
	-. SUB	Removes the status of the status bit.
	
V2.0 ALL/S,QUITE/S
	ALL	Multiple files may now be protected.
	QUIET	No messages are displayed.

[AMIGASYSTEM]

Originally Posted by malko

S The file can be started without execute
(script files only).

Yes because the command execute it automatically takes it from the system , if you try to rename the command execute script file does not work

[Daedalus]

It also talks about the H bit meaning "hidden" and the A bit only working under 1.3, so it's probably not the best source of information.

I did think that the E bit should also be set when the S bit is set (as in, it's an executable script), but I can't find any reference to it being either required or forbidden for scripts. It simply seems to be irrelevant when the S bit is present.

[AMIGASYSTEM]

The bit "E" it is not necessary to run a script or Icon, The bit "E" it is instead necessary on the real executables otherwise they do not start.