SRL Archive - Help and Support

Quick question. I've been bored recently and am doing a little project. To make it a bit better it'd be handy if I could utilise the existing extensions in the script. For example, use srl.sex and/or Updater.sei to have the script update SRL.

Would anyone know how to go about this?

Thanks!

I think you should be capable of adding the extension as an include (.sex files really are just .simba files with a different extension) and then calling the update method from you script the same way you would call GetChat or whatever other method you would call from another include.

From: Kevin
I think you should be capable of adding the extension as an include (.sex files really are just .simba files with a different extension) and then calling the update method from you script the same way you would call GetChat or whatever other method you would call from another include.

I was hoping I wouldn't have to do that. Pretty much I want it so that someone can download the script and run it without having to download any other files.

From: Rich
I was hoping I wouldn't have to do that. Pretty much I want it so that someone can download the script and run it without having to download any other files.

Aren't all the extensions already downloaded upon the Simba install?

From: Kevin
Aren't all the extensions already downloaded upon the Simba install?

Yeh, but I'm not sure of any other way of using those extensions in their standard form/folders in a script.

From: Rich
Yeh, but I'm not sure of any other way of using those extensions in their standard form/folders in a script.

Instead of using

{$i sps/sps.simba}

I believe it should simply be:

{$i Extensions/security.sex}

(capitalization may matter)

Tried that, but I just get an error trying to run the functions in the extension.

Maybe @Wizzup? could help me out?

Not all functions in extensions will behave the same. Extensions were made to run into their own thread. From SRL 6+ this won't be possible anyway.

Bb is right but there is also an exception..

The code from the extension might be native or external and in order for it to even compile in Simba you might have to enable syscalls.
Try going to:

Tools->Settings(Expert->Settings->Interpreter->AllowSysCalls and set it to true. Must be done as admin

Can also be done by exiting your C:/Simba/Settings.xml and saving it. Then try the extension thing previous suggestions mentioned above. If it doesn't work then disable syscalls/put it back to normal.

Still a no go. Thanks anyway guys!

From: Rich
I was hoping I wouldn't have to do that. Pretty much I want it so that someone can download the script and run it without having to download any other files.

You could invest some time in the nearly-finished Script Manager in Simba. That may help?

From: Wizzup?
You could invest some time in the nearly-finished Script Manager in Simba. That may help?

Go for it. How do I get involved?

From: Rich
Go for it. How do I get involved?

IRC #Simba

From: Rich
Go for it. How do I get involved?

Ah, well… I think I'll quickly see if I can do a Simba 1.0 release candidate tonight and then we can pick it up from there. I prefer communication over mail (pm me for my mail) and irc, but the forum is good too. Just some dedicated thread… :)

CynicRus did quite a lot, I think I need to fix up my server-side of the script manager, and then we just need to test *heaps*. :)