[Kwiver-users] Save vital type to disk

[Linus Sherrill]

I agree. File I/O is not a property of the object but an operation on the
object.

On Wed, Sep 6, 2017 at 10:51 AM, Matthew Leotta <matt.leotta at kitware.com>
wrote:

> I would not add any file I/O fu actions 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.
>
> On Sep 6, 2017, at 10:38 AM, Matt Brown <matt.brown at kitware.com> wrote:
>
> 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:
>
>
>    - Should this go in the base class or in homography_?
>    - 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.
>
> _______________________________________________
> Kwiver-users mailing list
> Kwiver-users at public.kitware.com
> http://public.kitware.com/mailman/listinfo/kwiver-users
>
>
>
> _______________________________________________
> Kwiver-users mailing list
> Kwiver-users at public.kitware.com
> http://public.kitware.com/mailman/listinfo/kwiver-users
>
>


-- 
*Linus Sherrill - *Staff R&D Engineer
Kitware, Inc.
28 Corporate Drive
Clifton Park, NY 12065-8662
E: linus.sherrill at kitware.com
P: 518.881.4400
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/kwiver-users/attachments/20170906/55653a0a/attachment.html>