a portable version would be great

[HahnloserR]

our company restricts the installation of apps.

so more or less the only way to use apps is the portable usage of them.

Hence that, it would be great to have a portable version.

[0xeb]

Essentially, Salamander has always been portable. Just install it once, and ZIP the contents / distribute

[ags1234]

@0xeb
This is good news.
I know that some work is being done on Salamander and I wonder if a more recent build exists...

[KRtekTM]

Essentially, Salamander has always been portable. Just install it once, and ZIP the contents / distribute

Salamander still requires Registry for storing configuration and plugins data, so the real portability needs the code changes.
Below analysis from Codex, I will take some time to think about it and I'll probably start implementing it, just for study purposes :D

[janrysavy]

See also https://github.com/copilot/share/c2441080-41a0-84a1-a952-304b405d614a

[KRtekTM]

See also https://github.com/copilot/share/c2441080-41a0-84a1-a952-304b405d614a

Thanks, this explains enough and I like the approach (option B) - in combination with abstraction layer (to keep the registry method side by side with the file storage method) it should ensure seamless migration between one configuration storage method and the other, even for already running installations (so users can switch back and forth on the fly or choose the method preferred).

[WaldemarH]

Hi guys,

just to let you know that I have a plan to move all settings to a settings class where the class will be be loaded at start and stored on the request or at the end (however the flags are set).

With this we'll have the option to do all kinds of stuff.. store it to a json5 file, store it to registry, store it to server/cloud location,... do a portable version,... whatever.

As with all things it will take so me time as registry is read from everywhere in salamander.

Currently I'm waiting for Jan to finish with the comments translations and then I'll start porting all my existing changes. I would continue the work but merging 50 big files manually is not fun, so I've stopped working on it for last few months.

BrW

[ags1234]

@WaldemarH
Excellent news!

As a side note, it would be great if the settings for Salamander would not be ever stored as binary, as Far Manager does, for example. Configuration is easier when users can edit a text file directly. Why json, why not the old and gold .ini file?

I would continue the work but merging 50 big files manually is not fun

Is there something others could do? Something repetitive maybe that does not require programming knowledge?

[WaldemarH]

@ags1234 At least for me I'm a text storring settings guy. :)

json can be used as the structure/hierarcy can also be stored, where ini is more or less just a key-value pair system. You can store everything in there, but the hierarcy is not visible.

Now as soon as we'll have all settings stored in a settings class we can read/write any format we'll want.
So adding ini would mean writing a loader and writter functions and that is it.

What is important to me is that location of this file could be defined.

BrW