Identify.library

Find quick help here to get you started with Hollywood
Post Reply
SpawnPPC
Posts: 61
Joined: Fri Mar 15, 2024 11:51 pm

Identify.library

Post by SpawnPPC »

Hello everyone.

Is anyone an expert in ARexx integration with Hollywood?

And maybe together with the Identify.library library?

Or Documentation, Manuals or Explanatory Examples (not generic) on these topics?

There is really very little around or I searched badly.

It would be great to have help from someone who is experienced in the field.

All the advice is welcome.

Thanks everyone!

Emanuele
User avatar
jPV
Posts: 734
Joined: Sat Mar 26, 2016 10:44 am
Location: RNO
Contact:

Re: Identify.library

Post by jPV »

SpawnPPC wrote: Tue Oct 08, 2024 8:01 pm Is anyone an expert in ARexx integration with Hollywood?
It's quite simple when handling external things without prodviding an ARexx port on your program, just run ARexx code from a file or string with RunRexxScript() or send direct commands with SendRexxCommand(), and get results in a string variable.
And maybe together with the Identify.library library?
Identify library's developer package has some ARexx examples as scripts. I guess they should work from Hollywood with RunRexxScript() and you probably would want to change SAY lines to a return value to get results as a string in Hollywood. You'll have to learn a bit about ARexx for that.

Another option without using ARexx would be to use Identify library's ListExp shell command with Execute() and parse its output for what you need.

But are you planning to use this solution only for AmigaOS 3.x setups, or also for next generation etc.? I think Identify library is a bit too non-consistent solution, because the latest version is basically hitting the metal of 68k machines and doesn't work properly on non-68k architectures. There are separate older versions for MorphOS and OS4, but they are scattered who knows where in Internet.

Another option to get system information would be the ShowConfig shell command, but you'd still have to create several solutions for different cases, because it isn't in standard locations between the systems and I'd guess the output could differ too, which makes parsing a bit harder. For example, the command is located in the Tools dir in OS3.x (if it's installed at all from the Storage disk), in the Utilities dir in OS4, and in C: in MorphOS, and so on.. you'll have to research about all possible options.
plouf
Posts: 666
Joined: Sun Feb 04, 2018 11:51 pm
Location: Athens,Greece

Re: Identify.library

Post by plouf »

Its not that scatered
68k is in aminet
Morphos version is on morphos storage
And os4depot has os4 version so .. user can find it where it expect it

And as you confirm it is probably the best and suitable for all oses way:-)
Rather than creating a script for parsing diffirent commants for every hardware :-)
Christos
User avatar
jPV
Posts: 734
Joined: Sat Mar 26, 2016 10:44 am
Location: RNO
Contact:

Re: Identify.library

Post by jPV »

plouf wrote: Mon Oct 14, 2024 9:41 am Morphos version is on morphos storage
Is it? I didn't see it with a quick search...
plouf
Posts: 666
Joined: Sun Feb 04, 2018 11:51 pm
Location: Athens,Greece

Re: Identify.library

Post by plouf »

Christos
User avatar
jPV
Posts: 734
Joined: Sat Mar 26, 2016 10:44 am
Location: RNO
Contact:

Re: Identify.library

Post by jPV »

plouf wrote: Mon Oct 14, 2024 3:00 pm https://www.morphos-storage.net/?id=1533037
That's not the identify.library, but some shell command to identify file types, and not to identify system specs. Something completely different with a similar name.

But I have identify.library.elf in my C:, which is a MorphOS native version of the identify.library, but I have no idea where I've got that...
Post Reply