[Ves] Extending the App

[Pat Marion]

Hi Eduardo,

You're correct that the vesKiwiViewerApp api is insufficient.  There's a
branch called kiwi-update which has a new version of the code which adds
methods to access the internal representations, and add new ones to the
list.  You could use this branch, or modify your copy of vesKiwiViewerApp.
The kiwi-update branch has a lot of changes to it though, so if don't want
the disruption then I would recommend you just modify vesKiwiViewerApp to
add accessors to the internal representations vector.

But, you might be interested in some of the changes, there are new features
to the existing image widget class vesKiwiImageWidgetRepresentation.  I'd
be interested to hear from you if you want to share what you are doing with
your ImageWidgetRepresentation class, and if you have any suggestions for
improvements to the vesKiwiWidgetRepresentation base class.  Thanks!

Pat

On Wed, Feb 13, 2013 at 9:43 AM, Eduardo Poyart <poyart at gmail.com> wrote:

> Hello,
>
> I extended vesKiwiViewerApp with my own subclass ViewerApp. I also needed
> to create a new representation, which I called ImageWidgetRepresentation,
> extending from vesKiwiWidgetRepresentation.
>
> I wrote a custom load routine in ViewerApp, and now I need to add the data
> to Internal, with something like:
>
> this->Internal->DataRepresentations.push_back(rep);
>
> However this can't be done since vesKiwiViewerApp.Internal is private.
> What is the correct design pattern in this case?
>
> Thanks
> Eduardo
>
>
>
>
> _______________________________________________
> Ves mailing list
> Ves at public.kitware.com
> http://public.kitware.com/cgi-bin/mailman/listinfo/ves
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/ves/attachments/20130213/78a9b382/attachment-0001.html>