Add Basic Materials Functionality

[jmwright]

This is a smaller PR which wraps Graphic3d_MaterialAspect XCAFDoc_Material and XCAFDoc_VisMaterial from OCC and leaves open the possibility of adding in physical visualization properties later.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.80%. Comparing base (fea85a5) to head (f2ca776).

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1923      +/-   ##
==========================================
+ Coverage   95.77%   95.80%   +0.02%     
==========================================
  Files          29       29              
  Lines        7856     7911      +55     
  Branches     1183     1188       +5     
==========================================
+ Hits         7524     7579      +55     
  Misses        192      192              
  Partials      140      140              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[adam-urbanczyk]

If I understand the intent of this PR correctly, you actually want to use XCAFDoc_Material

[jmwright]

@adam-urbanczyk I need to better understand what you are thinking. The current Material class wraps Graphic3d_MaterialAspect and so it is more visualization based, but my thought was to add things like density as properties later. XCAFDoc_Material does not seem to gain us much in the way is physical properties. My intention is to create a more general-purpose material class that can be used for multiple purposes, including export. It could be possible to wrap multiple classes and have the properties be interfaces to each of those properties. So the "diffuse color" would get/set on Graphic3d_MaterialAspect, and "density" would be get/set on XCAFDoc_Material.

[adam-urbanczyk]

In the end this class should wrap XCAFDoc_VisMaterial and XCAFDoc_Material (thus not Graphic3d_*). I assume that the first (main) use case is not vis related, so XCAFDoc_Material should be prioritized.

NB: it can be used for now to simply store a name.

[jmwright]

@adam-urbanczyk How about this?

[adam-urbanczyk]

Ok, let me take a look.

[adam-urbanczyk]

Looks good in general, but could you implement pickling? If it is too much work you could for now get rid of the vis part.

[jmwright]

could you implement pickling?

@adam-urbanczyk I'll see what I can do.

[adam-urbanczyk]

FYI: here is how it is done for Color:

cadquery/cadquery/occ_impl/assembly.py

Line 145 in fea85a5

def __getstate__(self) -> Tuple[float, float, float, float]:

[jmwright]

@adam-urbanczyk I tried to bring this PR up to par with the Color class.

[adam-urbanczyk]

LGTM, but please check if you need all methods.

[adam-urbanczyk]

Do you actually use hash and eq? AFAICT it is not needed for pickiling

[jmwright]

They are not needed for pickling, it just seemed worthwhile to add them while I was going through that part of the code.

[adam-urbanczyk]

OK, clear. Thanks!