[Smtk-developers] Pie in the sky
Bob Obara
bob.obara at kitware.com
Tue Mar 20 17:19:32 EDT 2018
I’m ok either though I tend to like keeping “like” files close so having a json or pybind subdirectory in the same directory as the source file does remind you that you might need to make changes to them as well.
What about the stuff under bridge :) - should it be
smtk/extension/session/polygon,
or
smtk/extension/modeler/polygon
or maybe
smtk/modeler/polygon?
Bob
Robert M. O'Bara, MEng.
Assistant Director of Scientific Computing
Kitware Inc.
28 Corporate Drive
Suite 101
Clifton Park, NY 12065
Phone: (518) 881- 4931
> On Mar 20, 2018, at 4:33 PM, David Thompson <david.thompson at kitware.com> wrote:
>
>> I vote for putting them in the subdirectories of whatever source they wrap/serialize since each of them is associated with a specific file/class.
>
> I think TJ was hinting that we we do this:
>
>> core/json/smtk/{attribute, mesh, model}/jsonResource.{h,cxx}
>> core/pybind11/smtk/{attribute, mesh, model}/Py{Attribute, Mesh, Model}.cxx
>>
>> extension/json/smtk/{attribute, mesh, model}/jsonResource.{h,cxx}
>> extension/pybind11/smtk/{attribute, mesh, model}/Py{Attribute, Mesh, Model}.cxx
>
> then everything in core/smtk is in the smtkCore library; everything in the core/json directory could live in an smtkCoreJSON directory, etc. In general, the pattern would be that no two libraries have code in the same source directory.
>
> David
> _______________________________________________
> Smtk-developers mailing list
> Smtk-developers at smtk.org
> https://smtk.org/mailman/listinfo/smtk-developers
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://smtk.org/pipermail/smtk-developers/attachments/20180320/19b3e228/attachment.html>
More information about the Smtk-developers
mailing list