You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was thinking that maybe a more maintainable strategy (i.e. it'll actually get done...) for user documentation is actually do it in the code and then the user can do something like grins --info or maybe a separate grins-info program and we just dump out all the things. Or grins --info physics to get descriptions of all the Physics classes and their required options, etc.
I was leaning towards a separate program to keep the main program clean and not having to check if --info is on the command line and do different things (which then the user may be required to do if they did some module extension since if there's a --info, we probably don't want to do grins.run()).
At any rate, was thinking we can have a static void Physics::all_info( std::ostream & ) method (and similar for other classes) where the implementation just loops through all the registered Physics objects and calls virtual void Physics::info( std::ostream & ) const =0 implementations. Pure virtual so it has to be implemented. And then each implementation is just documentation about what the Physics is, it's options, etc.
Hmm, this would give us all the Physics the user asked for in input, but it would be more useful to get info about all Physics registered with the PhysicsFactory. Need to think a bit about how to do that.
The text was updated successfully, but these errors were encountered:
I was thinking that maybe a more maintainable strategy (i.e. it'll actually get done...) for user documentation is actually do it in the code and then the user can do something like
grins --info
or maybe a separategrins-info
program and we just dump out all the things. Orgrins --info physics
to get descriptions of all thePhysics
classes and their required options, etc.I was leaning towards a separate program to keep the main program clean and not having to check if
--info
is on the command line and do different things (which then the user may be required to do if they did some module extension since if there's a--info
, we probably don't want to dogrins.run()
).At any rate, was thinking we can have a
static void Physics::all_info( std::ostream & )
method (and similar for other classes) where the implementation just loops through all the registeredPhysics
objects and callsvirtual void Physics::info( std::ostream & ) const =0
implementations. Pure virtual so it has to be implemented. And then each implementation is just documentation about what thePhysics
is, it's options, etc.Hmm, this would give us all the
Physics
the user asked for in input, but it would be more useful to get info about allPhysics
registered with thePhysicsFactory
. Need to think a bit about how to do that.The text was updated successfully, but these errors were encountered: