<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">I would not add any file I/O fuactions directly to the Vital type classes. You can add stream operators (that is, >> and <<) along side the type classes. I believe homography already has those. Currently we are putting file I/O functions in separate files in "kwiver/vital/io”. Look at camera_io.h as an example. These I/O functions should mostly just validate file object and then call the stream operators. <div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Sep 6, 2017, at 10:38 AM, Matt Brown <<a href="mailto:matt.brown@kitware.com" class="">matt.brown@kitware.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">My current interest is in reading/writing a vital/homography from/to disk. Note, this is the simpler homography without other metadata in it (i.e., not homography_f2f). I would like to create a base class methods save_to_file and read_from_file, but I have a few questions:<br class=""><br class=""><ul class=""><li class="">Should this go in the base class or in homography_?</li><li class="">It seems to me that this might be a useful generic facility across all vital types, so maybe we should take a moment and consider what the member function names should be and their scope.<br class=""></li></ul></div>
_______________________________________________<br class="">Kwiver-users mailing list<br class=""><a href="mailto:Kwiver-users@public.kitware.com" class="">Kwiver-users@public.kitware.com</a><br class="">http://public.kitware.com/mailman/listinfo/kwiver-users<br class=""></div></blockquote></div><br class=""></div></body></html>