Do we have to call them components? Given that we're touting Cactus as a component-based framework in which the components are the thorns it seems awkward to use component for a group of thorns.
Cheers, Steve
On 12/04/2010 12:16 AM, Erik Schnetter wrote:
One reason for having components is so that people who are experts in one subject are not bothered by having to look at issues in other fields. As you mention, it also doesn't make sense to have more than five or ten components, because otherwise the distinctions would be so fine that people would misfile.
This may work:
Cactus (flesh and all Cactus* arrangements) Carpet (all Carpet* arrangements) Einstein Toolkit (all Einstein* arrangements) web sites (Cactus, Carpet, Einstein Toolkit, Trac, ...) utilities (SimFactory, GetComponents, ...)
-erik