Sounds good to me,<br><br><div class="gmail_quote">On Tue, Apr 10, 2012 at 10:24 AM, Marcus D. Hanwell <span dir="ltr"><<a href="mailto:marcus.hanwell@kitware.com">marcus.hanwell@kitware.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I think Domains would be better, and I prefer it to Science. We set<br>
out very early on that library names would be camel case, and that top<br>
level groups could only have one word to avoid any confusion.<br>
<br>
Unless anyone says anything soon, I would like to proceed with<br>
Domains. I remember brainstorming some of these with George a few<br>
weeks ago as we were unhappy with the current layout.<br>
<span class="HOEnZb"><font color="#888888"><br>
Marcus<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
On Tue, Apr 10, 2012 at 8:18 AM, David Gobbi <<a href="mailto:david.gobbi@gmail.com">david.gobbi@gmail.com</a>> wrote:<br>
> Hi Will,<br>
><br>
> "DomainSpecific" captures exactly the right idea. But maybe shortened<br>
> to "Domains". So just like there is a "FiltersGeometry" module, there<br>
> could be a "DomainsChemistry" module.<br>
><br>
> - David<br>
><br>
> On Tue, Apr 10, 2012 at 4:04 AM, Will Schroeder<br>
> <<a href="mailto:will.schroeder@kitware.com">will.schroeder@kitware.com</a>> wrote:<br>
>> George-<br>
>><br>
>> You said it in your email, how about "DomainSpecific" instead of "Science" ?<br>
>> Science is too narrow a term, I can see all sorts of domains that are not<br>
>> really science, more engineering or data-related.<br>
>><br>
>> W<br>
>><br>
>><br>
>> On Mon, Apr 9, 2012 at 9:50 PM, George Zagaris <<a href="mailto:george.zagaris@kitware.com">george.zagaris@kitware.com</a>><br>
>> wrote:<br>
>>><br>
>>> Moving AMR under Filters seems reasonable. We may need to have AMR and<br>
>>> ParallelAMR under Filters for serial and parallel implementations<br>
>>> respectively (right now everything depends on parallel).<br>
>>><br>
>>> I think a top-level "Science" or similar directory would be useful.<br>
>>> Right now, it is not clear where domain-specific code should go. I can<br>
>>> see it grow with, Chemistry, Cosmology, CFD, etc.<br>
>>><br>
>>> Best,<br>
>>> George<br>
>>><br>
>>> On Mon, Apr 9, 2012 at 9:28 PM, Marcus D. Hanwell<br>
>>> <<a href="mailto:marcus.hanwell@kitware.com">marcus.hanwell@kitware.com</a>> wrote:<br>
>>> > On Mon, Apr 9, 2012 at 6:42 PM, David Gobbi <<a href="mailto:david.gobbi@gmail.com">david.gobbi@gmail.com</a>><br>
>>> > wrote:<br>
>>> >> Hi All,<br>
>>> >><br>
>>> >> In Modular, I've noticed that Chemistry, Charts, Geovis, AMR only have<br>
>>> >> Core. I'm wondering if people have opinions about where they could<br>
>>> >> go, to reduce the number of directories at the root.<br>
>>> >><br>
>>> >> My thoughts are:<br>
>>> >><br>
>>> >> Science/Chemistry<br>
>>> >> Filters/AMR<br>
>>> >> Rendering/Charts<br>
>>> >> Rendering/Geovis<br>
>>> >><br>
>>> >> It seems that Views also belongs in Rendering, but it already has<br>
>>> >> subdirectories other than Core.<br>
>>> ><br>
>>> > I was trying to think of a good top level container for some of these<br>
>>> > modules. I agree that Chemistry, Charts, Geovis and AMR all seem like<br>
>>> > candidates for being moved. If we had Science that could be good for<br>
>>> > future growth, although right now swaps one top level for another.<br>
>>> ><br>
>>> > If anyone can think of anything appropriate for three or four of them<br>
>>> > that would be great. There are a lot of modules in Rendering, and I<br>
>>> > would love to use a different top level for more specialized rendering<br>
>>> > types/implementations.<br>
>>> ><br>
>>> > Marcus<br>
>>> > _______________________________________________<br>
>>> > Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
>>> ><br>
>>> > Visit other Kitware open-source projects at<br>
>>> > <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
>>> ><br>
>>> > Follow this link to subscribe/unsubscribe:<br>
>>> > <a href="http://www.vtk.org/mailman/listinfo/vtk-developers" target="_blank">http://www.vtk.org/mailman/listinfo/vtk-developers</a><br>
>>> ><br>
>>> _______________________________________________<br>
>>> Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
>>><br>
>>> Visit other Kitware open-source projects at<br>
>>> <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
>>><br>
>>> Follow this link to subscribe/unsubscribe:<br>
>>> <a href="http://www.vtk.org/mailman/listinfo/vtk-developers" target="_blank">http://www.vtk.org/mailman/listinfo/vtk-developers</a><br>
>>><br>
>><br>
>><br>
>><br>
>> --<br>
>> William J. Schroeder, PhD<br>
>> Kitware, Inc.<br>
>> 28 Corporate Drive<br>
>> Clifton Park, NY 12065<br>
>> <a href="mailto:will.schroeder@kitware.com">will.schroeder@kitware.com</a><br>
>> <a href="http://www.kitware.com" target="_blank">http://www.kitware.com</a><br>
>> <a href="tel:%28518%29%20881-4902" value="+15188814902">(518) 881-4902</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>William J. Schroeder, PhD<br>Kitware, Inc.<br>28 Corporate Drive<br>Clifton Park, NY 12065<br><a href="mailto:will.schroeder@kitware.com">will.schroeder@kitware.com</a><br>
<a href="http://www.kitware.com">http://www.kitware.com</a><br>(518) 881-4902<br>