From: Rod W. <lis...@rw...> - 2002-11-12 04:06:39
|
On Fri, 2002-11-08 at 09:04, Lutz M=FCller wrote: > You can always > set up new objects like exif-mn-[entry,content,tag] (mn =3D MakerNote) > inheriting from the exif-equivalents. > (Me looking at the source...) > I think I have already done something like that in > libexif/libexif/olympus. Could you give me your opinion on that? I've used what you've provided in libexif/libexif/olympus, and made the following changes: 1/ Added a "note" field to ExifData to store an ExifNote (looks like an ExifContent), which is a set of ExifNoteEntry (looks like an ExifEntry). = The new data structures are in exif-note.c and in the maker-specific directories. 2/ Added code to exif_data_load_data_entry and exif_data_save_data_entry = to load and save the MakerNote entry to and from the "note" field in ExifDat= a. Added code to allow dumping of the makernote (so a test-tree run will dum= p out the individual makernote entries). 3/ Added lots of new methods in ExifNote to handle accessing individual ExifNoteEntry entries. My big question going forward is to do with the exif/exif/main.c file and how these new individually named things (ExifNoteEntry, accessed via the ExifNoteTag) should be identified by the user. The options are the re-us= e the -tag switch, and just have a new -ifd option for the MakerNote (but I know that you're not keen on this option), or to add a new set of switche= s (-note, -list_notes) for handling MakerNote entries separately. Let me know if you'd like to see the code (either a tarball or diffs). -- Rod Whitby |