How to make iconx script file minimize

[powrslave]

I made a script into an executable which works but the window cannot be button or minimized.

[fishy_fiz]

Is NIL what you're asking about? (ie. Not wanting CLI window to display the script contents when run)

[powrslave]

i'd like to see the contents.

Similar to if I open cli and then wirelessmanager prism2.device so I make sure it connects then I can click on the little square and it turns into a script icon on desktop.
Just tired of typing it when I want to connect. (don't want it in startup)

[Pat the Cat]

Seem to recall these two as offering some utlity, but I think neither is 100% compatible with everything, and may be very ancient.

http://aminet.net/package/util/wb/CLITool

Good for running program that you normally have to use a CLI for, by double clicking an icon instead.

http://aminet.net/search?query=IconJ

Funkier version of IconX with reconfigurable output. IconX just displays an "Out of Order notice - noob hack going on in background, look away" blank display.

I do seem to recall IconJ being OK with later AmigaDOS releases up to 3.1 at least, but like I say, they are both pretty creaky.

[Brian]

I made a script into an executable which works but the window cannot be button or minimized.

Have you set the WINDOW tooltypes for IconX?

WINDOWS=CON:0/50//80/IconX/AUTO/WAIT/CLOSE

Install KingCON and you will have a minimize option.

[guest11527]

I made a script into an executable which works but the window cannot be button or minimized.

That is only a matter of the WINDOW specification. Add to the end of the window path a "/AUTO/CLOSE/WAIT", and the window will only pop open if the command has something to print, will stay on the screen, and will have a close button.

I.e., something like

Code: [Select]

WINDOW=CON:0/0/640/100/My Title/AUTO/CLOSE/WAIT
will do the job.

[guest11527]

Install KingCON and you will have a minimize option.

Install ViNCEd and you will have much more. Comes with 3.9 anyhow. Also understands AUTO/CLOSE/WAIT, and will have an iconify button that works.

[kolla]

What is the advantage of using project icon type with IconX as default tool vs. using tool icon type, setting S flag and set CLI as tooltype (or "Start from Shell" in 3.9 info window)?

[kolla]

I think the main reason people prefer KingCON over ViNCEd is the complexity of ViNCEd, it is rather daunting, heck, even spelling it right is TRicKy It has so many features that one can really wonder what kind of situations one would have need for it all. And yet, it does not have tabs (which everyone wants), and it struggles if used as terminal emulator.

[Thomas]

What is the advantage of using project icon type with IconX as default tool vs. using tool icon type, setting S flag and set CLI as tooltype (or "Start from Shell" in 3.9 info window)?

The S flag can easily be lost when you copy the file to another location using the wrong options. For example the Copy CLI command will remove the flag if you forget to say CLONE.

[guest11527]

I think the main reason people prefer KingCON over ViNCEd is the complexity of ViNCEd, it is rather daunting, heck, even spelling it right is TRicKy

I wonder what the problem with the default configuration is. Just keep it, you're fine.

It has so many features that one can really wonder what kind of situations one would have need for it all. And yet, it does not have tabs (which everyone wants)

Does Kingkong have Tabs? I guess not. Adding Tabs would be another project, but not right now please. It has virtual consoles and screens, though.

and it struggles if used as terminal emulator.

Huh, what? Unlike all the other terminals, ViNCEd includes a VT100 and VT220 emulation, and not only CBMs own interpretation of the CSI sequences (which is really quite a bit off). Actually, I used ViNCEd quite a while as ssh terminal to run emacs over a dial-in connection at our university.

[kolla]

The S flag can easily be lost when you copy the file to another location using the wrong options. For example the Copy CLI command will remove the flag if you forget to say CLONE.

Yeah, but that is really a "meta problem", and in my eyes a flaw with the copy command, I always use clone and cannot fathom why that is not default. :hammer:

I was more curious in direct benefits/caveats with using one or the other.

[kolla]

I wonder what the problem with the default configuration is. Just keep it, you're fine.

Sure - but it is a rather intrusive and... in lack of better word, "bloated" option when all you want is iconify and tab completion.

Does Kingkong have Tabs? I guess not. Adding Tabs would be another project, but not right now please. It has virtual consoles and screens, though.

Yes, and I suspect most people do not know it is there and certainly not how to set it up and use it, as I said, the configuration of ViNCEd is quite daunting. KingCON also does not have tabs, but the handler is half the size of vnc.library, and can even be put in kickstart and work when booting without startup-sequence (Yes, I know... copied to RAM before execution, still useful though.)

Huh, what? Unlike all the other terminals, ViNCEd includes a VT100 and VT220 emulation, and not only CBMs own interpretation of the CSI sequences (which is really quite a bit off).

Well, the world has moved on, vt220 is not exactly the benchmark for a good terminal anymore. ViNCEd has ANSI terminal with colours, which is nice, but 16 colours ANSI terminal is also kinda "old school" in these days of true colour xterm and consoles. There is option for tmux to deal with 256-colour terminal, but not for only 16 colours, for example. In my experience, both Term and AmTelnet (that is, the terminal MUI class) are better choices for simple terminal emulation, and it always helps to use GNU screen in the other end, less need for ctrl+L frenzy. And, then there is the question of charset handling.

Actually, I used ViNCEd quite a while as ssh terminal to run emacs over a dial-in connection at our university.

That may be why. emacs lives in its own "retro reality" and (like vt220), should not be the benchmark for whether a terminal emulation works or not. But we are touching the main topic here - why should the console handler on the Amiga even have terminal emulation at all?

Anyways, I do think ViNCEd is awesome, but I also see why people rather use KingCON (Kingkong is something else). It would be nice with a new console handler that implements the basics like KingCON does, but in a more system friendly way. If someone with the know-how could make a video tutorial for all the stuff one can accomplish with ViNCEd, I would love watching and learning

[Thomas]

Yeah, but that is really a "meta problem", and in my eyes a flaw with the copy command, I always use clone and cannot fathom why that is not default. :hammer:

It's not only copy. If you use ZIP or TAR or any other non-Amiga archiver to transport the files to somewhere else, those non-standard flags get lost. Even with LhA flags are lost if you don't set the right options.

The same happens if you copy the file to a non-Amiga file system like FAT. CF0 comes to mind.

I was more curious in direct benefits/caveats with using one or the other.

The IconX thing also works on Kick 1.3.

[kolla]

OK, since I only get answers that for me are irrelevant and not really what I am asking about, I assume then that there is no difference between using IconX and setting S bit and tooltype CLI

I could imagine that IconX for example could read more tooltypes, there are IconX "clones" that can do a lot more.