Re : Re: ini file use

[tinnitus]

Hello,

i have a question concerning customs with ini file.

I would like to know what is the common use, for the moment i create a big cluster of cluster containing parameters of

program (using openg palette).

The values of this file normally don't change a lot but some times they have to and could be changed by user and some only by developper.

however if he knows he can makes canges directly with txt editor.

So have i to make two ini files or i am making confusion between ini file (ex path name, ports , devices) and parameter file ( number of point, Criteria of stability ...?

What is the common habit of programming ?

when it is needed do you make changes on ini file via txt editor or do you developp a vi to re-write it ?

Best regards

Tinnitus

[J.DECHET]

Not a really help with my response but all depend of needs and users.

Ask if your customers have a sufficient level in the environment of the software to change values by test editor or not?

You could write a configuration interface with several level of finishing... display, technics, limits, tests of compatibility... An opened word!!!

[PhillipBrooks]

This discussion on the LAVA forum may be of interest to you...

[Tom__Sedlack]

I use .ini files to run common code on multiple machines.  I keep a standard code base and it reads configuration and test information from the file.  Easy software maintenance as there is only one executable distributed to all locations.

[Wayne.C · Accepted solution]

Tinnitus,

I'm not sure that there is a 'standard' method for .ini files.  In some cases I think it is a good idea to split the information into multiple .ini files.  One to contain things that only the developer would need to change and one to contain things the user might need to change.

I always develop a vi to create the .ini file the first time.  That way if I need to provide an interface to change settings, I have it.  One advantage of this is that you can protect against silly typos that can happen in text editor.  You can build this into a Functional Global/Action Engine that takes care of the .ini in general.

I also suggest you take a look at the OpenG Variant Configuration File VIs  found here http://wiki.openg.org/Oglib_variantconfig. 

[Michael Ludwig]

I agree with Wayne.C though i go a bit further. The idea of two ini files is not bad per se as it does keep users from possibly editing "dangerous" information. I however usually prefer to create an actual UI to display and ini settings and allow the users to edit the settings from there because 1. that avoids mis-edits in the text file and 2. it does not encourage the user to "mess with the system". The OpenG Variant Config files are indeed a nice and easy way to write that "Settings UI". 

[tinnitus]

thank you all,

I were starting with openg config files, with section splitted on severals Tabs, but i reallized its a little bit borring...

each time you have a parameter to add, wires are broken.   

As i 'have no informatic background and i'm alone using labview

i would like to know if i were going on  good direction because i saw other config files based on xml or managed with use of classes .

Best regards Tinnitus

Message Edité par tinnitus le 01-16-2010 01:07 PM

Message Edité par tinnitus le 01-16-2010 01:12 PM