Config parameters: where to store them?

[ErosOlmi]

We are discussing where to store thinAir parameters like colors, fonts, editor options, ...

What do you think?

[RobertoBianchi]

Normally in a well done application user should not be aware were data are stored (data means settings only not data itself) .
Of course ThinBASIC user are specials users, so they must know and choose if possible the 'rockin way', so please vote for USE WINDOWS REGISTRY! :lol:

Thank you very much and best regards,
Roberto

[ErosOlmi]

That's why this pool: Roberto and I have a different idea on this aspect so we would like to know other opinions.

In my idea this kind of programs (editors, interpreters, debuggers) should be very portable from one box to the other just using file copy. Imagine you have to install thinBasic in different machines (we hope many :wink: ) or run thinBasic from a network shared resource.

For this reason registry settings are not very confortable. In my opinion a INI file or better an XML file can do the same job of the registry but at the same time give high flexibility.

Please express your idea if you like.

Thanks a lot.

[Petr Schreiber]

Hi,

this is really interesting question.

I always used sort of cfg/ini file when I did some progs in PowerBASIC, because I did not believed to the mysterious registry :) ( there was no reason for disliking the registry, I wonder why I'm aware of it :) ).

But the dark side of disk file appeard, when various people tried to "play a tricks" on my 3D editor app, setting awful resolutions in config file :D.


Petr

[RobertoBianchi]

Petr,

Using a text file you discard the built in data type provided by Windows.
Also windows provides a secure per user context, even if for now we do not use it.
I prefer window's registry because it's a modern, robust and scalable way to quickly store and retrive data configuration.

Bye,
Roberto

[RobertoBianchi]

Ok, inasmuch as there is parity the things remain as they are, I close the voting. ;D
Cheers

Roberto