Data structure for SimFile complete.
Data structure for SimFile complete.

Now we begin work on setters, getters, and modifiers. We have a couple ways of
doing this:

1) Each File class can have [set|get|mod]_attribute() methods that do exactly
   as they appear to. This will allow existing access to self.data, and we can
   write a simple decorator that does the appropriate read/writes and copying for getting
   and setting. The downside to this is that it makes these low-level classes a
   bit messy.

2) Each File object has a get, set, and mod object, which themselves contain the
   appropriate function for each attribute. We can apply operators the same
   way, although each of these object will have to have a reference to its
   parent File object in order to access the data structure and use the File
   object's methods for reading/writing. This is the more complicated approach,
   but it has a prettier (and possibly more efficient) result. It can also help
   to illustrate whether our similar design plans for Aggregators will actually
   work.

I think I will go with option 2 for now, just because it's really cool if I can
get it to work. Plus, it's a preview of things to come. ^_^

andreabedini/datreant,datreant/datreant.data,dotsdl/datreant,datreant/datreant,datreant/datreant.core,datreant/datreant,datreant/datreant.core