Application Suggestion for willing Developer

Hi,

I'd like a simple, basic command line program or other solution that anyone can use to determine whether application named A is already installed in the main dock (or anywhere) of AmiDock.

Process:

1. Your program reads in the XML file associated with the current AmiDock.
2. Searches for the name given in the command line arguments.

If an instance is found either or both a warn is raised or a local environment variable is set containing the filename and path of the instance that we can perform a conditional check on.

I could properly do this myself in Hollywood in one afternoon, but surely SURELY someone can find time to write something in C/C++ or PortableE that can pull this off without me resorting to bloatware.

I might suggest something on OpenAmiga if feedback is poor here.

Quote:
I don't understand this part.

What I understood is that you want to run a "FindInAmidock" tool. This can be achieved very easily with a script. Something like:

Seems you know what you are talking about Elwood, I'll give it a whirl.

If that works which I suspect it will that script should be included as standard in C:!

You are a genius!

If you want to find the command from anywhere, not just in
the amidock then you can try the script below.
Open notepad and paste in what's between ==== lines.

;===================================
.KEY FILE/A
.BRA {
.KET }

if exists ${appdir/{FILE}}
echo ${appdir/{FILE}}
else
echo "*"{FILE}*" Not found in cache."
endif
;===================================

Now save it as "S:??" (thats S: plus two question marks)
and also set the +s script bit with; "protect S:?? +s"
(or choose your own name)

Now an example, if you have IBrowse installed, then
from a shell, just type; "?? ibrowse"
It will tell you where it is, (or not).

Arexx scripts go, naturally, in S:Arexx

Anywhere else might be found , but this is where system scipts go. Oh hang on, this isn't a system script, my bad! :)

Simn

Actually you're kinda right Simon, I have an added path
to S: on my setup, but the default install places shell
scripts in the S:Shell directory and there is also a
path there by default.
So "S:Shell" is the best place for it.

Quote:
Just be aware that this method is not foolproof. As an example, try looking for a program named "acemen".

To be absolutely robust, one should probably parse the XML file and find the correct elements in the relevant context. But it might be useful to have an easier API to things like this. Shouldn't application.library be able to provide this, e.g. to use from ARexx or Python?

Best regards,

Niels

@colinw

Or GetEnv appdir/ibrowse

(alternatively if your app is in the system path: Which command)

But I think that wasn't what was asked in the first post.

@djrikki
Quote:
Not at all, but I'm trying my best

Why not create a drawer specific for scripts in eg C:Scripts and keep all dos/python/Arexx/Lua scripts in there ?

Hmm maybe even all C: programs can use script equivelents especially DIR/List etc, so they can be easily updated.

I like this x86 command line program that has multiple features - Swiss File Knife :

http://stahlworks.com/dev/swiss-file-knife.html

@angelheart

Because there's already a drawer for this purpose, it's called S: (for Scripts). C: is for Commands. Why reinvent the wheel ?

Quote:
Yes, those kinds of "do-it-all-in-one-program"/"Jack-of-all-trades" solutions seem to be popular on those platforms. I've never understood why.

In AmigaOS we usually have separate commands or programs for each of those tasks. So instead of having to type e.g. "sfk list", "sfk delete" or "sfk find", we only have to type "list", "delete" or "search" (with appropriate arguments in both cases).

Of course some of sfk's subcommands can do things the corresponding Amiga commands can't - and vice versa. But if we need any of those features, we can usually create them with a simple script which again can be called (after being "S"-protected) with one word.

Just my humble opinion.

Best regards,

Niels

Quote:
And nowadays we even have the subdirectories S:Shell (for shell scripts) and S:ARexx (for ... you guessed it ).

Best regards,

Niels