gEDA Project Wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
Pre-existing systems:
Presently there are a couple. GTK has one, there’s the one that loads command line arguments, and there’s also the menu system, which could be considered a preferences system.

I’d like to centralize this system so that other parts of the code can take advantage of it.

=== Requirements ===
  * The system should be able to interact with specified preferences files. \\ This allows subsystems to create their own if they want. It will also allow the user to specify such a file at startup.
  * The system should manage the reading and writing of the files transparently. \\ We don’t want developers to have to think too hard about how this works.
  * The system should not put constraints on what can be contained by the preference. \\ It should be allowed to be anything. Ultimately it’s a string when it’s stored and read, but it should be convertible into any data type.
  * The system should be partitionable such that a subsystem may keep track of their own preferences without having to interact with the preferences of any other subsystem.

Secondarily:
  * The files should be human readable. \\ There’s an interesting question here about locales…

=== Architecture ===
The general assumption is that subsystems are going to have their own structures to store their preferences, for example the Settings structure in global.h. So, we're building this system around storing and loading data from other structure that already exist, as opposed to being a database for storing the actual preference data itself. This has some advantage over a database in that individual structures have unique memory locations and don't require lookups when trying to find a particular preference value. I imagine that we could work that out if we really needed to. But for now, I assume that this central preference structure exists.

That means that our work here is essentially going to be to define framework the describes the preference metadata so that we can save and load it in a programmatic fashion. To that end, we're going to define data structures that don't hold the preference data itself, but describe it and have a pointer to the actual data so that we can retrieve and store it. Preference metadata consists of things like name, help text, and data type. 

There are a number of standard data types, including int, double, and string, and we'll also include a forth data type "pointer" as essentially an "other". This will allow the preference objects to be more complex structures.

Ideally, we'll just be able to create a structure of metadata objects and say "save all of these to a file", or "load all of the data from that file according to these specs". To that end, we'll need a structure that we can iterate over. 

=== Process ===
One of the considerations here is separating the storage and application so that the methods can change. If we decide we'd rather store preferences in an SQL database, we can do that without having to rewrite the whole system. We only have to write functions to load and save the key values pairs in the database.

I'm not too worried about the speed of these routines, so, it doesn't matter much if the lists are sorted. Reading, and writing preferences doesn't happen very often.

We're going to go with a two step process. The read and write functions will take a pointer to a list of PreferenceItems. The readers and writers can interact explicitly with the data they are reading/writing and there's no need to build an intermediate list. This better supports the option for alternate storage formats.

  * load_preferences(file, preflist)
   - open the preference store
   - for each item in the store
   - Look up the preference in the preflist
   - get a reader: check for a reader in the structure and use it if it's there. Otherwise lookup the default reader for the preference type.
   - apply the reader to set the preference
  * save_preferences(preflist, file)

I'd also like this process to work for command line arguments so that any preference stored in a file can also be specified on the command line.

=== Data Structures ===
We're going to draw heavily on the work that's already been done with the preferences (HIDAttributes) in designing the data structures for this system. 
== PreferenceDefinition ==
The primary data structure describes a preference item. 

<code c>
/*! 
 * \brief PreferenceDefinition data structure
 */
typedef struct
{
  /*! key that identifies the preference */
  char * key; 
  /*! Human readable name of the preference */
  char * name;
  /*! preference type identifier (enum) */
  int type;
  /*! Text that describes what the preference influences */
  char * help_text;
  /*! Reader function that converts the value string into useful data */
  void (*reader)(char * index_str, char * input_str, void * ptr);
  /*! Writer function that converts the value back into a string */
  void (*writer)(char * index_str, void * ptr);
  /*! data pointer passed to reader and writer */
  PreferenceValue * ptr;
  /*! a value that can be used to initialize the preference; type defined as per above. */
  PreferenceValue default_val;
} PreferenceDefinition;
</code>

There will be a number of "reader"/"writer" functions implemented by default to handle common data types like floats, ints, coords, etc. The data pointer will be passed to the reader and writer functions, and could contain anything. But it probably is a pointer to the variable to be set by the converted value from the PreferenceItem. Using function pointers like this allows for a lot of flexibility in how subsystems can use this code. The reader functions, for example, may also be responsible for notifying a GUI that the preference has been updated.

Note: the default_val should initialize the value to something that is SAFE, i.e. something that will never, ever cause PCB to crash.

== Preference Values ==
My initial thought was to make this a void pointer so that it could be anything. The current PCB pref stuff uses a union structure for this instead, and I'm wondering if that would be easier to work with. The union structure could have a "pointer" item in it that would allow for more complicated items to be allocated. This would keep the val with the structure in memory, which would be nice.

The realization that I'm having comes out of writing an object list copy function for a preference definition. If the data payload is a custom user defined object, then the copy function won't know how to make a copy of it. Normally the way it works is that when an object is added to a list, the list makes it's own copy. That way it doesn't have to worry about the user changing, or unallocating, the data. I've been thinking for a while that I need a version of the list that assumes ownership of the data when it's added.

One alternative might be to register preference types... and require a copy function to be defined for each type. This might be okay if I provide defaults for all the common types, but could be ornery if I require the user to do it.

Another alternative might just be to provide a "pointer" type and say that if you're going to use a more complex structure, then the module that uses it has to provide it and make sure that it says allocated.

For now I'm going to go with the last option, because it does seem reasonable, and it also seems like the least work for now. Additionally, I think I'm going to go with the union idea, as that gets rid of having to cast a ton of void pointers.

Note that in the PreferenceDefinition structure, the val is actually a pointer. This has to be because this is actually a pointer to somewhere else in memory where the actual value of the preference is stored. Because it's a union, it effectively allows it to be basically a pointer to anything, and I can interpret it as such.

== PreferenceValue ==
Based on the previous discussion, we're now going to define a union type to handle these values. (This used to be PreferenceItem and held key, value, and type triples).

<code c>
typedef union
{
  /*! integer value */
  int ival;
  /*! double value */
  double dval;
  /*! string pointer */
  char * sptr;
  /*! void pointer */
  void * ptr;
} PreferenceValue;
</code>

== Lists ==
Presently, the intent is to use object_list for all of the lists.

=== Implementation Overview ===
Preferences will be stored in a file as key/value pairs. An algorithm will read the file into a dictionary type structure, and then for every key it will look up that key in a "preferences registry". The preferences registry will be a list of structures that include things like the name of the preference, some help text, default value, etc. and a pointer to a function that can be used to interpret the value string associated with the key. The function does its thing, and sets the destination variable with its value.

To save preferences this works in just the reverse. There is also a "writer" function associated with preferences in the registry, and this is called to convert the data back into a string. We generate a series of key/value pairs that are then written to a text file.

The key/value pair structures can be returned to the calling function to be retained for future inquiry. For example, maybe a plug-in chooses to store a preference in the main pcb preferences file. When pcb is initialized, if the plug-in isn't loaded yet, the preference will still be read and retained so that when the plug-in does load, the read value will be available to it for conversion.

A python pseudo-code might look something like this:
<code python>
def load_preferences(filename, registry):
  file_data = read_pref_file(filename)
  for key, value in file_data:
    if key in registry:
      registry[key].reader(key, value, registry[key].ptr)
      
  return file_data
  
def save_preferences(filename, registry):
  file_data = []
  for key in registry:
    file_data.append([key, registry[key].writer(key, registry[key].ptr)])
    
  write_pref_file(file_data)
  return len(file_data)
</code>
(why is it always so much easier in python?)


=== Functions ===
There are a number of key functions here: load_preferences, save_preferences, readers, and writers. Note that the file IO is being deliberately kept separate so that the actual file format is independent. Also, this allows data from a single file to be scanned more than once against different preference registries. We saw some pseudo-code for the load_preferences and save_preferences above (although it should have used apply_preferences and collect_preferences instead of spelling it out). So let's think about some of the others, again in pseudo-code (python...).
<code python>
def load_preferences(filename, pref_list):
  with open(filename, r) as f:
    f.seek(-1) # seek to the end
    flen = f.tell()
    r.rewind()
    file_data = f.read(flen)
  
  # make sure to add a null at the end so file_data[flen] is a null char.

  # find all the new lines
  lines = [0]
  for i in range(flen):
    c = data[i]
    if c == "\n":
      data[i] = '\0'
      if i + 1 < flen:  # more data in file
        lines.append(i+1)
  
  keys = []
  for l in lines:
    # ignore lines that start with "#"
    if data[l] == "#": continue
    # ignore leading whitespace
    i = l
    while i < flen:
      if data[l] in [" ", "\t"]:
        i++
        
      else:
        keys.append[l]
        break
  
  if len(keys) == 0: return
  
  values = []
  for k in keys:
    i = k
    while i =< flen:
      c = data[i]
      if (c == '\0') or (i == flen-1):
        # no value for this key
        # point it at the key? At a null?
        values.append(i)
        break
        
      elif c in [" ", "\t"]:
        data[i] = '\0'
        if i + 1 < flen:
          values.append(i+1)
        break
      
      i++
      
</code>

=== File Format ===
  * The file should contain 1 preference per line.
  * First word on the line (everything up to the first white space) is the name of the preference (key).
  * Everything after the first word is the value of the preference.
  * "#" should indicate a comment and the line should be ignored.\\ Should I allow hashes in the middle of a line, or should everything after a hash be a comment? Colors are often specified with hashes in front, so, that might make it awkward. For now it will only be lines starting with hashes that are treated as comments.

Using lines seems like the natural thing to do, but this precludes multi-line strings. Perhaps that’s okay? I’m going to go with that for now.

Example:
  # gtk preferences
  gtk-layer1-color #FF0000
  # snapping preferences
  snap-line-radius 42
  # drc preferences
  drc-linewidth-min 8 mil

The above would create a list with three key value pairs:
^ Key ^ Value ^
| gtk-layer1-color  | #FF0000 |
| snap-line-radius  | 42 |
| drc-linewidth-min | 8 mil |

=== Thoughts on processing ===

I’ve also considered if there should be some type of hierarchical structure. Like for example, subsystems could register prefixes like “gtk-” with the system, and then the system passes them the preferences with that prefix. With the function calling system, I don’t think this is necessary. Although it is a good idea for subsystems to use such a prefix to make editing the files easier.

=== Thoughts on implementation ===

The pointer is probably often going to be the item that should be populated with the preference value, but doesn’t have to be. It could be the general preferences structure, for example, if there’s more than one parameter that needs to be updated.

Implement several “default” handlers: pref_float, pref_integer, pref_double, pref_coord… etc that take the preference value, convert into whatever type, and then assign. Similarly several default “writers” will be needed.

Then we’ll create an object list of these preference items. It will have to be initialized early in the startup process, before processing the preference related command line arguments.

There will be a function for reading a preferences file, and a function for writing a preferences file.
<code c>
void read_pref_file (char * fname)
{
FILE * fp;
/* open the file for reading */
}
</code>

<code c>
/* void pref_float (char * index_str, char * input_str, void *ptr) 
 * This function takes an input string, converts it to a float, and assigns it to ptr.
 * Return type is void only because I haven’t figured out what to do with it, or to remind you 
 * that you have to set the value with the function. */
void pref_float (index_str, input_str, ptr)
{
  /* this function doesn’t care about index_str */
  float fval = 0, *fptr=0;
  fptr = (float*) ptr; /* cast the pointer as a float */
  fval = atof(input_str); /* do the ascii to float conversion*/
  /* do any checking to see if it worked? */
  *fptr = fval;
  /* return 0; */
}
</code>

<code c>
/* char * float_pref(index_str, float fval) 
 * This function takes an input float and converts it to a string for storage in a preferences file.
 * The caller owns the string memory that the result is stored in.
 * Should the float be a pointer to a float, or the float value itself?
*/
char * float_pref (index_str, float fval)
{
  char tstr[128]; /* This ought to be big enough for anything we’re going to realistically throw at it. */
  char * fstr;
  int len = 0;
  len = sprintf(fstr, “%f”, fval);
  fstr = malloc(len+1); /* allocate a buffer that’s exactly the right size */
  strncpy(fstr, tstr, len); /* copy the new string into it */
  fstr[len] = ‘\0’;
  return fstr;
}
</code>

=== Questions ===
  * If a user loads a new preferences file, does it need to notify anything that this happened? \\ Presently, with preferences, values are updated immediately. This means that all preferences need to be such that changing them at any given moment doesn’t lead to disaster. However, this model also provides the flexibility that, if there isn’t such a preference, it can specify its own handler function which could take care of any of the necessary tasks to enact the change.
  * Should I try to use the glib class structure and create an actual manager object
  * When collecting preferences, do we collect everything, or only things that aren't the same as the default?
  * I've made an implicit assumption here that the preference keys are strings. Maybe I shouldn't? They could just be integers...


==== Old stuff ====
== Original Idea == 
Originally, I was going to do it this way... but this is just extra work. So, I'm ditching the intermediate step.
I'm breaking the preferences process into four steps:

  - Read the preferences file and create a list of key value pairs (preference items) \\ pilist = ppm_read_pref_file(fname); \\ This returns a list of PreferenceItem objects that contains the keys and values read out of the specified file.
  - Apply preferences to the PCB data structures \\ ppm_apply_preferences(pdlist, pilist); \\ This iterates over the PreferenceItems in pilist. For each item it looks up the key in a preference definition list, pdlist, and calls the function associated with that preference definition.
  - Collect preferences from PCB data structures \\ pilist = ppm_collect_preferences(pdlist); \\ This goes through the preferences definitions in pdlist and creates a set of key value pairs, pilist, that can be stored in the text file.
  - Write the preference data to a file. \\ ppm_write_pref_file(pilist); \\ Store the preferences in a file.

== New Idea ==

===== Development Blog =====
I'm starting this because I'm having trouble remembering where I am and what I've done between development sessions.

At this point, I've written data converters for ints, doubles, and strings. I've also written tests for them, so, I know they're working the way I think they should.

== Tasks ==
  * Read function

= 20201108 =

Today I managed to get a the function for writing preference files written, and a simple test that uses it.

One note: when I initially wrote the test, I did something like this (abbreviated):
<code c>
int intval;
char charvals[] = "Preference string";
PreferenceDefinition intpref = {.key = "integer", .val = &intval};
PreferenceDefinition strpref = {.key = "string", .val = &charvals};
</code>
However, this doesn't work. The val field of the strpref ended up equaling the address of charvals, whereas I needed it to be a double pointer. This makes me wonder what I ought to do here. If preferences are stored in a struct like
<code c>
typedef struct {
  char * charvals;
} Pref;
</code>
Then I have a pointer to point to. However, if the preferences are stored as "global" variables, then I just get the address of the string, and I don't have a container to point to. I wonder if I need to have some sort of accommodation for that?

= 202201115 =

I'm working today on the function that reads the files. I've looked at the current file format and it is pretty much "key = value". So, I think I'm going to allow that format also. That way I don't have to deal with trying to figure out how to get everyone's preferences converted to the new format. This means that I have to implement non-white-space delimiters, but I don't think that will be too hard. It also provides the developers with another option for delimiters. 

= 20201227 = 

Worked on the apply function. It works now. 

I also found a bunch more functions related to attribute handling in hid/common/hidinit.[c,h], and I'm starting to have a better sense of how the current systems work together. There's a "node" list, and each subsystem registers a node that is effectively an array of HID_Attributes. There are functions for parsing the command line arguments, reading and writing files, etc, all similar in function to the code that I've just implemented...

I need to think a little bit on how to handle these things hierarchically. How do subsystems inherit preferences from above? Can they back-propagate preferences? Can they share across-subsystems?

Thinking "out-loud":
When a subsystem wants to inherit something, it should be familiar with what it's parent's attributes are and just grab those attributes directly. It should only store locally things that are specific to the subsystem. 

But what if we passed a command-line parameter for a subsystem? The core won't know what to do with it because it's not in the core's list. We want that to be accessible to the subsystem, however. Maybe this is a good argument for the intermediate key/value pair structure. Perhaps we treat command-line arguments differently, and just save those vectors globally so that subsystems can inspect them at their leisure.
gEDA Project Wiki

User Tools

Site Tools

Page Tools
