[Ves] Extending the App

[Pat Marion]

Thanks!  I will update the iOS toolchain file to find the 6.1 sdk.  As for
the ARC support... the current Kiwi app is going to be replaced by a new
app that uses GLKit instead of the old style EAGLView, and the new app is
written with ARC.  For a preview of it, there is the midas-kiwi branch.
This branch has some new dependencies though, curl and libarchive.  My
focus right now is to get the app into the app store, then get all this new
code into the ves master branch.  There's also a branch on stage named
kiwi-simple-example which has a very simple app iOS app using GLKit and ARC.

By  the way, these branches I'm mentioning are on the stage remote.  git
remote add stage git://vtk.org/stage/VES.git; git fetch stage

Pat

On Wed, Feb 13, 2013 at 3:03 PM, Eduardo Poyart <poyart at gmail.com> wrote:

> Thanks!
>
> For now, I'm patching the VES source and rebuilding it to add accessors to
> DataRepresentations and TextureShader.
>
> Another change I did to VES was I added iOS 6.1 support, and I changed the
> ObjC code to support automatic reference counting. Would you be interested
> in these changes? They are made on top of the master branch.
>
> Eduardo
>
>
>
> On Tue, Feb 12, 2013 at 8:22 PM, Aashish Chaudhary <
> aashish.chaudhary at kitware.com> wrote:
>
>> Pat,
>>
>> On Tue, Feb 12, 2013 at 10:57 PM, Pat Marion <pat.marion at kitware.com>wrote:
>>
>>> 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!
>>>
>>
>> As far as I know that branch need some clean up but other than that what
>> holding us to review that branch and get it into master? I guess I am in
>> favor of small topic branches. Please let me know. I also have few changes
>> pending but that can after you branch. We can follow up in separate email
>> if needed.
>>
>> 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
>>>>
>>>>
>>>
>>> _______________________________________________
>>> Ves mailing list
>>> Ves at public.kitware.com
>>> http://public.kitware.com/cgi-bin/mailman/listinfo/ves
>>>
>>>
>>
>>
>> --
>> | Aashish Chaudhary
>> | R&D Engineer
>> | Kitware Inc.
>> | www.kitware.com
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/ves/attachments/20130213/84340935/attachment-0002.html>