yorik wrote: ↑Fri Feb 15, 2019 12:16 pm
For me a "price" field is useful, because something we do quite often in the building industry is price estimation for a project. You basically make a spreadsheet where you count how much brick wall, how much concrete beams, etc... there is in a project, and give a price to each.
I wonder that this doesn't cause serious problems for you. In my experience the material "brick" can cost 10 Cents per brick part or 2 $, depending on the shape quality, pore density, color, supplier and so on. I just had a look in my lunch break in the neighboring garden center.
The more I think about it the less I see why a cost for a material would be sensible. Take for example wood, it makes a huge difference how the wood is shaped, what kind of wood, how much you buy at one, if you can buy it directly from a state forest or from a company etc.. The differences are several 100%.
I thought the material editor is in FC because of
- necessary to perform FEM analysis
- to apply a default surface shade and color for display and ray tracing
- to be able to specify the material in a technical drawing
- what do I miss?
I am pretty sure that every company has its own price handling system and I think this is for good reason.
If you see reliable applications, then of course keep the price. It would then be useful that the use cases are documented in the Wiki.
Btw. I see that most FEM Wiki pages are empty. I almost finished the description for a2plus and when I find time I will document FEM. But be warned - writing documentation leads to many bug reports