SRL Archive - Development

For Simba 0.99 we've been working on a portable Simba (Or rather, Dgby714 has) - as well as a real system wide install. Upon, the Simba versions you have will be replaced with a portable one - leaving your current install intact. If you remove (or manually update) the settings.xml yourself, your Simba folder will be completely portable., but this is not recommended.

In a portable Simba, all (Script|Include|etc) paths are relative. They should reside inside the Simba directory. You can put it on a USB stick and run it from anywhere; the base path won't matter.

On a system wide install, Simba will store scripts in My Documents/Simba/Scripts and all the other data, includes, plugins, fonts will be stored in the user Application Data.

Hopefully we will also incorporate some privilege raising for the system wide install so it can temporarily become admin to update Simba and such.

And maybe we will also be able to make a nice settings form as well as export more settings such as font size, highlight colours, etc.

There won't be any changes in the core finding functions, I think most of the work for Simba 0.99 and 1.00 will happen in the GUI, other areas like integration into the system and usability. What I would personally like to add is a code completion for Lape, but I'm not sure this is do-able yet.

I suspect a first release candidate for Simba 0.99 will come in a few days.

Why is the Lape Intellisense not do-able? Isn't it the matter of just exporting stuff or creating objects? I've also tried the simba => Interpreter => Lape.. ={ it's definitely not ready yet because nothing I put in, ran.. Also why not just embed the settings.xml or whatever stops it from being portable inside of simba itself and when it has to update, you just update resources no?

From: ggzz
Why is the Lape Intellisense not do-able? Isn't it the matter of just exporting stuff or creating objects? I've also tried the simba => Interpreter => Lape.. ={ it's definitely not ready yet because nothing I put in, ran.. Also why not just embed the settings.xml or whatever stops it from being portable inside of simba itself and when it has to update, you just update resources no?

I haven't fully investigated, but I assumed not all the functionality was yet in place. I'll take a proper look later. As it for not functioning, it seems to run quite well for me…