KConfig
Ansley, Michael
Michael.Ansley at intec.co.za
Tue Sep 14 08:19:08 BST 1999
You are going to have to store them with the document, because if you ever
reopen a document, then you need to know what the standard of measurement
was when you created the document. However, if you are storing the
information in a database (PostgreSQL springs to mind ;-) then you just dump
the current values (not the data readings) into a config file, because they
will also be stored with each set of values put into the database. You see,
it all depends on state. The state information (including the measurement
standards) have to be stored. The fact that you remember them in the
application for the next reading is purely incidental as far as the
application is concerned, a convenience for the user. However, if you go
back to a previous reading, or load a set of readings into another
application (such as a spreadsheet) you have to know what the measurement
parameters were, so you have to have this information stored with (or linked
to, in the case of a database) the primary data.
This is getting out of hand. Are you with me so far...
MikeA
>> -----Original Message-----
>> From: Hauke Hildebrandt [mailto:hhildebr at iup.uni-heidelberg.de]
>> Sent: Monday, September 13, 1999 7:23 PM
>> To: kdevelop at barney.cs.uni-potsdam.de
>> Subject: KConfig
>>
>>
>> Hi, Mike!
>>
>> Well, it probably is. However, I want to store data on the disk that
>> either rarely change between the documents, or some values
>> from the last
>> document are taken as default values forv the current one.
>> To give you an
>> example: The application is for controlling a measuring device. The
>> calibration is done using a standard identified by its number. The
>> standard is exchanged after half a year, so for that period
>> the number is
>> fixed. Another one: The value of the magnetic field during
>> the last scan
>> is used if the next scan does not give a reasonable value.
>> So these config
>> data are rather different from the "horizontal/vertical
>> menubar" stuff and
>> I would like to keep them in a separate file. Any ideas?
>>
>> Hauke
>>
More information about the KDevelop
mailing list