11-03-2010 07:23 AM
This time, a few tweaks to design and start implementation of the base classes.
In thinking about the location format, I came to the conclusion that the hierarchical path format given last week cannot be used for a raw binary file. The only information of import is the location in the file. This can be specified in bytes or numbers of a certain data type, but a “path” is not appropriate. I could coerce it into some sort of path format, but this would be equivalent to creating a formatted binary file, such as TDMS or HDF5, and that is not the intent of this exercise. The path format is appropriate for the other file types.
Attached is the start of an implementation of the base classes. All base classes are all created and inheritance is in place. Base icons have been created. The icons file attached includes these so you can use them in your icon creation, as well (feel free to do a nicer job 😉 ). Note that the icons include an area at the bottom to enable customization for the file type. Only one or two of the methods have been created.
Next time, I will try to finish off the implementation of the base classes. If time permits, I will start on a vertical slice through the binary file type. After that, the next file type is up for discussion. INI, TDMS, ZIP, HDF5, ??? What would you like to see implemented?
11-29-2010 08:07 AM
Get the next one in this series here.