From a.fetzer at dkfz-heidelberg.de Wed Jun 3 04:04:41 2015 From: a.fetzer at dkfz-heidelberg.de (Fetzer, Andreas) Date: Wed, 3 Jun 2015 10:04:41 +0200 Subject: [Ctk-developers] Extend CTK CLI XML schema for meshes and grids Message-ID: Hi all. We are using the CTK CLI module a lot for exchanging and connecting functionalities between different projects. Now, some of our users raised the requirement to also specify meshes and grids within a cli. Since the CTK cli xml schema (https://github.com/commontk/CTK/blob/master/Libs/CommandLineModules/Core/Resources/ctkCmdLineModule.xsd) currently only defines images we would have to extend the schema. That is why I wanted to ask, if you see any obstacles regarding the enhancement of the schema for meshes and grids, or if there was a specific reason, why only images are currently defined by the xml schema. Thanks, Andreas From julien.finet at kitware.com Wed Jun 3 05:39:43 2015 From: julien.finet at kitware.com (Julien Finet) Date: Wed, 3 Jun 2015 11:39:43 +0200 Subject: [Ctk-developers] Extend CTK CLI XML schema for meshes and grids In-Reply-To: References: Message-ID: Hi Andreas, Isn't "model" good enough for you guys? A model is a poly-data. Julien. On Wed, Jun 3, 2015 at 10:04 AM, Fetzer, Andreas < a.fetzer at dkfz-heidelberg.de> wrote: > Hi all. > > We are using the CTK CLI module a lot for exchanging and connecting > functionalities between different projects. > Now, some of our users raised the requirement to also specify meshes and > grids within a cli. > > Since the CTK cli xml schema ( > https://github.com/commontk/CTK/blob/master/Libs/CommandLineModules/Core/Resources/ctkCmdLineModule.xsd > ) > currently only defines images we would have to extend the schema. > > That is why I wanted to ask, if you see any obstacles regarding the > enhancement of the schema for meshes and grids, or if there was a specific > reason, > why only images are currently defined by the xml schema. > > Thanks, > > Andreas > _______________________________________________ > Ctk-developers mailing list > Ctk-developers at public.kitware.com > http://public.kitware.com/mailman/listinfo/ctk-developers > -------------- next part -------------- An HTML attachment was scrubbed... URL: From m.clarkson at ucl.ac.uk Wed Jun 3 14:41:51 2015 From: m.clarkson at ucl.ac.uk (Clarkson, Matt) Date: Wed, 3 Jun 2015 18:41:51 +0000 Subject: [Ctk-developers] Extend CTK CLI XML schema for meshes and grids In-Reply-To: References: Message-ID: <9528AAC9-2486-4508-9396-9DB375968A76@live.ucl.ac.uk> Hi Andreas, Sounds good to me in principal. However, I have to admit to not knowing all the history. I also can see that there is a geometryType, which has enumeration of fibrebundle and model. Both of these could I imagine (but don?t know for sure) be represented by vtkPolyData. So, are meshes and grids similar? Matt On 3 Jun 2015, at 09:04, Fetzer, Andreas wrote: > Hi all. > > We are using the CTK CLI module a lot for exchanging and connecting functionalities between different projects. > Now, some of our users raised the requirement to also specify meshes and grids within a cli. > > Since the CTK cli xml schema (https://github.com/commontk/CTK/blob/master/Libs/CommandLineModules/Core/Resources/ctkCmdLineModule.xsd) > currently only defines images we would have to extend the schema. > > That is why I wanted to ask, if you see any obstacles regarding the enhancement of the schema for meshes and grids, or if there was a specific reason, > why only images are currently defined by the xml schema. > > Thanks, > > Andreas > _______________________________________________ > Ctk-developers mailing list > Ctk-developers at public.kitware.com > http://public.kitware.com/mailman/listinfo/ctk-developers From pieper at isomics.com Wed Jun 3 14:46:17 2015 From: pieper at isomics.com (Steve Pieper) Date: Wed, 3 Jun 2015 14:46:17 -0400 Subject: [Ctk-developers] Extend CTK CLI XML schema for meshes and grids In-Reply-To: <9528AAC9-2486-4508-9396-9DB375968A76@live.ucl.ac.uk> References: <9528AAC9-2486-4508-9396-9DB375968A76@live.ucl.ac.uk> Message-ID: Hi - In our (slicer) terminology Model is basically a vtkPolyData for the purposes of a CLI. A fiber bundle is a specialized type of Model that includes tensors at the vertices of polylines. -Steve On Wed, Jun 3, 2015 at 2:41 PM, Clarkson, Matt wrote: > Hi Andreas, > > Sounds good to me in principal. However, I have to admit to not knowing > all the history. > I also can see that there is a geometryType, which has enumeration of > fibrebundle and model. > Both of these could I imagine (but don?t know for sure) be represented by > vtkPolyData. > So, are meshes and grids similar? > > Matt > > > On 3 Jun 2015, at 09:04, Fetzer, Andreas > wrote: > > > Hi all. > > > > We are using the CTK CLI module a lot for exchanging and connecting > functionalities between different projects. > > Now, some of our users raised the requirement to also specify meshes and > grids within a cli. > > > > Since the CTK cli xml schema ( > https://github.com/commontk/CTK/blob/master/Libs/CommandLineModules/Core/Resources/ctkCmdLineModule.xsd > ) > > currently only defines images we would have to extend the schema. > > > > That is why I wanted to ask, if you see any obstacles regarding the > enhancement of the schema for meshes and grids, or if there was a specific > reason, > > why only images are currently defined by the xml schema. > > > > Thanks, > > > > Andreas > > _______________________________________________ > > Ctk-developers mailing list > > Ctk-developers at public.kitware.com > > http://public.kitware.com/mailman/listinfo/ctk-developers > > _______________________________________________ > Ctk-developers mailing list > Ctk-developers at public.kitware.com > http://public.kitware.com/mailman/listinfo/ctk-developers > -------------- next part -------------- An HTML attachment was scrubbed... URL: From a.fetzer at Dkfz-Heidelberg.de Mon Jun 15 02:37:08 2015 From: a.fetzer at Dkfz-Heidelberg.de (Fetzer, Andreas) Date: Mon, 15 Jun 2015 08:37:08 +0200 Subject: [Ctk-developers] Extend CTK CLI XML schema for meshes and grids In-Reply-To: References: <9528AAC9-2486-4508-9396-9DB375968A76@live.ucl.ac.uk> Message-ID: Hi all! thank you for your feedback and sorry for my late response, I was on a business trip last week. We are using the image tag to create a image specific selection combobox in MITK, so that only images can be selected as input parameters. Now some of our users want to have the same selection combobox for vtkPolyData and vtkUnstructuredGrid. I will have to check whether the geometry type is sufficient for that. I think if we could differentiate between polydata and unstructuredGrid, it would be great and the "model" type might be to generic for that. Thanks again! Andreas Von: Steve Pieper > Datum: Wednesday 3 June 2015 20:46 An: Matt Clarkson > Cc: Andreas Fetzer >, "ctk-developers at commontk.org" > Betreff: Re: [Ctk-developers] Extend CTK CLI XML schema for meshes and grids Hi - In our (slicer) terminology Model is basically a vtkPolyData for the purposes of a CLI. A fiber bundle is a specialized type of Model that includes tensors at the vertices of polylines. -Steve On Wed, Jun 3, 2015 at 2:41 PM, Clarkson, Matt > wrote: Hi Andreas, Sounds good to me in principal. However, I have to admit to not knowing all the history. I also can see that there is a geometryType, which has enumeration of fibrebundle and model. Both of these could I imagine (but don?t know for sure) be represented by vtkPolyData. So, are meshes and grids similar? Matt On 3 Jun 2015, at 09:04, Fetzer, Andreas > wrote: > Hi all. > > We are using the CTK CLI module a lot for exchanging and connecting functionalities between different projects. > Now, some of our users raised the requirement to also specify meshes and grids within a cli. > > Since the CTK cli xml schema (https://github.com/commontk/CTK/blob/master/Libs/CommandLineModules/Core/Resources/ctkCmdLineModule.xsd) > currently only defines images we would have to extend the schema. > > That is why I wanted to ask, if you see any obstacles regarding the enhancement of the schema for meshes and grids, or if there was a specific reason, > why only images are currently defined by the xml schema. > > Thanks, > > Andreas > _______________________________________________ > Ctk-developers mailing list > Ctk-developers at public.kitware.com > http://public.kitware.com/mailman/listinfo/ctk-developers _______________________________________________ Ctk-developers mailing list Ctk-developers at public.kitware.com http://public.kitware.com/mailman/listinfo/ctk-developers From lasso at queensu.ca Tue Jun 16 17:11:20 2015 From: lasso at queensu.ca (Andras Lasso) Date: Tue, 16 Jun 2015 21:11:20 +0000 Subject: [Ctk-developers] Extend CTK CLI XML schema for meshes and grids In-Reply-To: References: <9528AAC9-2486-4508-9396-9DB375968A76@live.ucl.ac.uk> Message-ID: type="model" means vtkPolyData. Probably it's better not to overload this meaning but instead define a new type for vtkUnstructuredGrid. Maybe something like type="unstructured-model", type="unstructured", type="unstructured-grid". Andras -----Original Message----- From: Ctk-developers [mailto:ctk-developers-bounces at public.kitware.com] On Behalf Of Fetzer, Andreas Sent: Monday, June 15, 2015 2:37 AM To: ctk-developers at commontk.org Subject: Re: [Ctk-developers] Extend CTK CLI XML schema for meshes and grids Hi all! thank you for your feedback and sorry for my late response, I was on a business trip last week. We are using the image tag to create a image specific selection combobox in MITK, so that only images can be selected as input parameters. Now some of our users want to have the same selection combobox for vtkPolyData and vtkUnstructuredGrid. I will have to check whether the geometry type is sufficient for that. I think if we could differentiate between polydata and unstructuredGrid, it would be great and the "model" type might be to generic for that. Thanks again! Andreas Von: Steve Pieper > Datum: Wednesday 3 June 2015 20:46 An: Matt Clarkson > Cc: Andreas Fetzer >, "ctk-developers at commontk.org" > Betreff: Re: [Ctk-developers] Extend CTK CLI XML schema for meshes and grids Hi - In our (slicer) terminology Model is basically a vtkPolyData for the purposes of a CLI. A fiber bundle is a specialized type of Model that includes tensors at the vertices of polylines. -Steve On Wed, Jun 3, 2015 at 2:41 PM, Clarkson, Matt > wrote: Hi Andreas, Sounds good to me in principal. However, I have to admit to not knowing all the history. I also can see that there is a geometryType, which has enumeration of fibrebundle and model. Both of these could I imagine (but don't know for sure) be represented by vtkPolyData. So, are meshes and grids similar? Matt On 3 Jun 2015, at 09:04, Fetzer, Andreas > wrote: > Hi all. > > We are using the CTK CLI module a lot for exchanging and connecting functionalities between different projects. > Now, some of our users raised the requirement to also specify meshes and grids within a cli. > > Since the CTK cli xml schema > (https://github.com/commontk/CTK/blob/master/Libs/CommandLineModules/C > ore/Resources/ctkCmdLineModule.xsd) > currently only defines images we would have to extend the schema. > > That is why I wanted to ask, if you see any obstacles regarding the > enhancement of the schema for meshes and grids, or if there was a specific reason, why only images are currently defined by the xml schema. > > Thanks, > > Andreas > _______________________________________________ > Ctk-developers mailing list > Ctk-developers at public.kitware.com .com> http://public.kitware.com/mailman/listinfo/ctk-developers _______________________________________________ Ctk-developers mailing list Ctk-developers at public.kitware.com http://public.kitware.com/mailman/listinfo/ctk-developers _______________________________________________ Ctk-developers mailing list Ctk-developers at public.kitware.com http://public.kitware.com/mailman/listinfo/ctk-developers From a.fetzer at Dkfz-Heidelberg.de Thu Jun 18 05:54:03 2015 From: a.fetzer at Dkfz-Heidelberg.de (Fetzer, Andreas) Date: Thu, 18 Jun 2015 11:54:03 +0200 Subject: [Ctk-developers] Extend CTK CLI XML schema for meshes and grids In-Reply-To: References: <9528AAC9-2486-4508-9396-9DB375968A76@live.ucl.ac.uk> Message-ID: For our case this would be very helpful. We need to distinguish these different types. If there are no objections, we would gladly contribute this. Am 16/06/15 23:11 schrieb "Andras Lasso" unter : >type="model" means vtkPolyData. Probably it's better not to overload this >meaning but instead define a new type for vtkUnstructuredGrid. Maybe >something like type="unstructured-model", type="unstructured", >type="unstructured-grid". > >Andras > >-----Original Message----- >From: Ctk-developers [mailto:ctk-developers-bounces at public.kitware.com] >On Behalf Of Fetzer, Andreas >Sent: Monday, June 15, 2015 2:37 AM >To: ctk-developers at commontk.org >Subject: Re: [Ctk-developers] Extend CTK CLI XML schema for meshes and >grids > >Hi all! > >thank you for your feedback and sorry for my late response, I was on a >business trip last week. >We are using the image tag to create a image specific selection combobox >in MITK, so that only images can be selected as input parameters. > >Now some of our users want to have the same selection combobox for >vtkPolyData and vtkUnstructuredGrid. I will have to check whether the >geometry type is sufficient for that. I think if we could differentiate >between polydata and unstructuredGrid, it would be great and the "model" >type might be to generic for that. > >Thanks again! > >Andreas > >Von: Steve Pieper > >Datum: Wednesday 3 June 2015 20:46 >An: Matt Clarkson > >Cc: Andreas Fetzer >>, >"ctk-developers at commontk.org" >> >Betreff: Re: [Ctk-developers] Extend CTK CLI XML schema for meshes and >grids > >Hi - > >In our (slicer) terminology Model is basically a vtkPolyData for the >purposes of a CLI. A fiber bundle is a specialized type of Model that >includes tensors at the vertices of polylines. > >-Steve > >On Wed, Jun 3, 2015 at 2:41 PM, Clarkson, Matt >> wrote: >Hi Andreas, > >Sounds good to me in principal. However, I have to admit to not knowing >all the history. >I also can see that there is a geometryType, which has enumeration of >fibrebundle and model. >Both of these could I imagine (but don't know for sure) be represented by >vtkPolyData. >So, are meshes and grids similar? > >Matt > > >On 3 Jun 2015, at 09:04, Fetzer, Andreas >> wrote: > >> Hi all. >> >> We are using the CTK CLI module a lot for exchanging and connecting >>functionalities between different projects. >> Now, some of our users raised the requirement to also specify meshes >>and grids within a cli. >> >> Since the CTK cli xml schema >> (https://github.com/commontk/CTK/blob/master/Libs/CommandLineModules/C >> ore/Resources/ctkCmdLineModule.xsd) >> currently only defines images we would have to extend the schema. >> >> That is why I wanted to ask, if you see any obstacles regarding the >> enhancement of the schema for meshes and grids, or if there was a >>specific reason, why only images are currently defined by the xml schema. >> >> Thanks, >> >> Andreas >> _______________________________________________ >> Ctk-developers mailing list >> Ctk-developers at public.kitware.com> .com> http://public.kitware.com/mailman/listinfo/ctk-developers > >_______________________________________________ >Ctk-developers mailing list >Ctk-developers at public.kitware.com> >http://public.kitware.com/mailman/listinfo/ctk-developers > >_______________________________________________ >Ctk-developers mailing list >Ctk-developers at public.kitware.com >http://public.kitware.com/mailman/listinfo/ctk-developers From pieper at isomics.com Thu Jun 18 07:23:08 2015 From: pieper at isomics.com (Steve Pieper) Date: Thu, 18 Jun 2015 07:23:08 -0400 Subject: [Ctk-developers] Extend CTK CLI XML schema for meshes and grids In-Reply-To: References: <9528AAC9-2486-4508-9396-9DB375968A76@live.ucl.ac.uk> Message-ID: +1 On Thu, Jun 18, 2015 at 5:54 AM, Fetzer, Andreas < a.fetzer at dkfz-heidelberg.de> wrote: > For our case this would be very helpful. We need to distinguish these > different types. > If there are no objections, we would gladly contribute this. > > > Am 16/06/15 23:11 schrieb "Andras Lasso" unter : > > >type="model" means vtkPolyData. Probably it's better not to overload this > >meaning but instead define a new type for vtkUnstructuredGrid. Maybe > >something like type="unstructured-model", type="unstructured", > >type="unstructured-grid". > > > >Andras > > > >-----Original Message----- > >From: Ctk-developers [mailto:ctk-developers-bounces at public.kitware.com] > >On Behalf Of Fetzer, Andreas > >Sent: Monday, June 15, 2015 2:37 AM > >To: ctk-developers at commontk.org > >Subject: Re: [Ctk-developers] Extend CTK CLI XML schema for meshes and > >grids > > > >Hi all! > > > >thank you for your feedback and sorry for my late response, I was on a > >business trip last week. > >We are using the image tag to create a image specific selection combobox > >in MITK, so that only images can be selected as input parameters. > > > >Now some of our users want to have the same selection combobox for > >vtkPolyData and vtkUnstructuredGrid. I will have to check whether the > >geometry type is sufficient for that. I think if we could differentiate > >between polydata and unstructuredGrid, it would be great and the "model" > >type might be to generic for that. > > > >Thanks again! > > > >Andreas > > > >Von: Steve Pieper > > >Datum: Wednesday 3 June 2015 20:46 > >An: Matt Clarkson > > >Cc: Andreas Fetzer > >>, > >"ctk-developers at commontk.org" > >> > >Betreff: Re: [Ctk-developers] Extend CTK CLI XML schema for meshes and > >grids > > > >Hi - > > > >In our (slicer) terminology Model is basically a vtkPolyData for the > >purposes of a CLI. A fiber bundle is a specialized type of Model that > >includes tensors at the vertices of polylines. > > > >-Steve > > > >On Wed, Jun 3, 2015 at 2:41 PM, Clarkson, Matt > >> wrote: > >Hi Andreas, > > > >Sounds good to me in principal. However, I have to admit to not knowing > >all the history. > >I also can see that there is a geometryType, which has enumeration of > >fibrebundle and model. > >Both of these could I imagine (but don't know for sure) be represented by > >vtkPolyData. > >So, are meshes and grids similar? > > > >Matt > > > > > >On 3 Jun 2015, at 09:04, Fetzer, Andreas > >> wrote: > > > >> Hi all. > >> > >> We are using the CTK CLI module a lot for exchanging and connecting > >>functionalities between different projects. > >> Now, some of our users raised the requirement to also specify meshes > >>and grids within a cli. > >> > >> Since the CTK cli xml schema > >> (https://github.com/commontk/CTK/blob/master/Libs/CommandLineModules/C > >> ore/Resources/ctkCmdLineModule.xsd) > >> currently only defines images we would have to extend the schema. > >> > >> That is why I wanted to ask, if you see any obstacles regarding the > >> enhancement of the schema for meshes and grids, or if there was a > >>specific reason, why only images are currently defined by the xml schema. > >> > >> Thanks, > >> > >> Andreas > >> _______________________________________________ > >> Ctk-developers mailing list > >> Ctk-developers at public.kitware.com >> .com> http://public.kitware.com/mailman/listinfo/ctk-developers > > > >_______________________________________________ > >Ctk-developers mailing list > >Ctk-developers at public.kitware.com Ctk-developers at public.kitware.com > >> > >http://public.kitware.com/mailman/listinfo/ctk-developers > > > >_______________________________________________ > >Ctk-developers mailing list > >Ctk-developers at public.kitware.com > >http://public.kitware.com/mailman/listinfo/ctk-developers > > _______________________________________________ > Ctk-developers mailing list > Ctk-developers at public.kitware.com > http://public.kitware.com/mailman/listinfo/ctk-developers > -------------- next part -------------- An HTML attachment was scrubbed... URL: From M.Nolden at Dkfz-Heidelberg.de Wed Jun 24 08:15:01 2015 From: M.Nolden at Dkfz-Heidelberg.de (Nolden, Marco) Date: Wed, 24 Jun 2015 14:15:01 +0200 Subject: [Ctk-developers] Permanent branch / tag policy Message-ID: <558A9F45.8080005@dkfz-heidelberg.de> Hi CTK'ers, for our recent MITK 2015.05 release we used a specific CTK hash which includes some branches that were at that time not yet ready for merging into master. The integration branch we used is currently living outside of the github commontk organization, but to keep things together and make them easier accessible for external users I would like to add it to commontk and also create some permanent reference to it. I thinking about two options: 1. create a tag, like ctk-for-mitk-2015.05 2. create an integration branch on commontk, and after everything has been included through the outstanding pull requests, merge that branch with the "ours" merge policy just to keep the reference What do you think, any other ideas? Marco From pieper at isomics.com Fri Jun 26 12:48:38 2015 From: pieper at isomics.com (Steve Pieper) Date: Fri, 26 Jun 2015 12:48:38 -0400 Subject: [Ctk-developers] Permanent branch / tag policy In-Reply-To: <558A9F45.8080005@dkfz-heidelberg.de> References: <558A9F45.8080005@dkfz-heidelberg.de> Message-ID: Hi Marco - Either option sounds fair to me. Probably a tag for the exact version that corresponds to the MITK release is a good idea even if you also keep a branch. -Steve On Wed, Jun 24, 2015 at 8:15 AM, Nolden, Marco wrote: > Hi CTK'ers, > > for our recent MITK 2015.05 release we used a specific CTK hash which > includes some branches that were at that time not yet ready for merging > into master. The integration branch we used is currently living outside > of the github commontk organization, but to keep things together and > make them easier accessible for external users I would like to add it to > commontk and also create some permanent reference to it. I thinking > about two options: > > 1. create a tag, like ctk-for-mitk-2015.05 > 2. create an integration branch on commontk, and after everything has > been included through the outstanding pull requests, merge that branch > with the "ours" merge policy just to keep the reference > > What do you think, any other ideas? > > Marco > > _______________________________________________ > Ctk-developers mailing list > Ctk-developers at public.kitware.com > http://public.kitware.com/mailman/listinfo/ctk-developers > -------------- next part -------------- An HTML attachment was scrubbed... URL: From pieper at isomics.com Tue Jun 30 10:45:56 2015 From: pieper at isomics.com (Steve Pieper) Date: Tue, 30 Jun 2015 10:45:56 -0400 Subject: [Ctk-developers] CommonGL idea Message-ID: Hi VTKers and CTKers - Nicolas and the XTK team [1,2] have been working on some upgrades to XTK's WebGL and volume rendering and I've been helping a bit while also playing with GLSL shaders in VTK. It seems to us that there's an opportunity to write the GLSL code in a way that would be usable in both the traditional desktop and the web/embedded use cases. Granted OpenGL != WebGL but the shaders are close enough that we think it's feasible to create a resource we're calling CommonGL. Anyway I wrote up some notes and ideas [2] and would appreciate any feedback or help. Best, Steve [1] https://github.com/xtk/X [2] http://slicedrop.com/ [3] https://docs.google.com/document/d/1-4Up_Shq6oFTGhwXIF5DuiXUYsdIMlAC1oK7eNHWP_o/edit?usp=sharing -------------- next part -------------- An HTML attachment was scrubbed... URL: From pieper at isomics.com Tue Jun 30 15:37:38 2015 From: pieper at isomics.com (Steve Pieper) Date: Tue, 30 Jun 2015 15:37:38 -0400 Subject: [Ctk-developers] [vtk-developers] CommonGL idea In-Reply-To: References: Message-ID: Hi Cory - I know there is more OpenGL2 work for VTK coming down the pipeline but I've looked through the what is in VTK 6.2 and clearly there is a lot of logic in the C++ code for generating and manipulating the GLSL shader code. I think it would be hard to meaningfully re-use the current VTK shader code in WebGL, but I think we can write new code that works either place, or at least that's the hypothesis. For people wanting a concrete example, this script works with some minor modifications to VTK (in the same wrap-shaders branch -- basically just some extra classes wrapped for python). https://github.com/pieper/VTK/blob/wrap-shaders/Rendering/OpenGL/Testing/Python/DynamicShader.py The shader itself came from this source with only minor modifications: http://glslsandbox.com/e#25816.0 -Steve On Tue, Jun 30, 2015 at 12:51 PM, Cory Quammen wrote: > Hi Steve, > > How much does the OpenGL2 backend in VTK help in getting you to CommonGL? > > Thanks, > Cory > > On Tue, Jun 30, 2015 at 10:45 AM, Steve Pieper wrote: > >> Hi VTKers and CTKers - >> >> Nicolas and the XTK team [1,2] have been working on some upgrades to >> XTK's WebGL and volume rendering and I've been helping a bit while also >> playing with GLSL shaders in VTK. >> >> It seems to us that there's an opportunity to write the GLSL code in a >> way that would be usable in both the traditional desktop and the >> web/embedded use cases. >> >> Granted OpenGL != WebGL but the shaders are close enough that we think >> it's feasible to create a resource we're calling CommonGL. >> >> Anyway I wrote up some notes and ideas [2] and would appreciate any >> feedback or help. >> >> Best, >> Steve >> >> [1] https://github.com/xtk/X >> >> [2] http://slicedrop.com/ >> >> [3] >> https://docs.google.com/document/d/1-4Up_Shq6oFTGhwXIF5DuiXUYsdIMlAC1oK7eNHWP_o/edit?usp=sharing >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Search the list archives at: http://markmail.org/search/?q=vtk-developers >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/vtk-developers >> >> >> > > > -- > Cory Quammen > R&D Engineer > Kitware, Inc. > -------------- next part -------------- An HTML attachment was scrubbed... URL: