Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Simplify application help messages #273

Closed
prudhomm opened this issue Feb 16, 2014 · 7 comments
Closed

Simplify application help messages #273

prudhomm opened this issue Feb 16, 2014 · 7 comments

Comments

@prudhomm
Copy link
Member

We should simplify the help message obtained using --help: at the moment it prints all options from the application and from the library. It is probably quite hard for the user to understand what is going on and see his/her options. We should separate the application option from the library option. This would require a second _desc parameter e.g. _desc_lib to specify the library option. This should be compatible with the previous setting.

@prudhomm prudhomm self-assigned this Feb 16, 2014
@prudhomm prudhomm added this to the Feel++ v0.97.0 milestone Feb 16, 2014
@prudhomm
Copy link
Member Author

@aancel this should actually allow to simplify the onelab interface : we can separate the menu for the application and the library and have the library menu closed by default

@prudhomm
Copy link
Member Author

@StephaneVeys @aancel have i broken anything in onefeel ? for example the reduced basis app

@aancel
Copy link
Contributor

aancel commented Feb 17, 2014

@prudhomm @StephaneVeys After a quick test, it seems to still be working on my side (also tested with crb_heatshield1app)

@prudhomm
Copy link
Member Author

good!
There should be a way to close the menu Feelpp. Why do we have DefinedParameters et GeneralParameters ? is it just to distinguish parameters changed from config-file or command line ?

@aancel
Copy link
Contributor

aancel commented Feb 17, 2014

Regarding to closing the Feelpp menu, I have looked into Onelab scripting syntax and didn't find anything to do that. I think it will require modifying code in Gmsh.

The DefinedParameters and GeneralParametersis just a trick for Gmsh alphabetical ordering, so we have the parameters that have been user-defined in first position (either through a config-file or command line).

@Doyeux
Copy link
Contributor

Doyeux commented Feb 17, 2014

Since this commit I have the following error: (compiling with gcc-4.7 and
4.8)

/home/vinch/feelpp/feel/feelcore/environment.hpp:164:103: error: no match
for 'operator[]' (operand types are 'const
boost::parameter::aux::arg_list<const
boost::parameter::aux::tagged_argument<Feel::tag::argv, char
_>,
boost::parameter::aux::arg_list<const
boost::parameter::aux::tagged_argument<Feel::tag::argc, int>,
boost::parameter::aux::empty_arg_list> >' and 'const
boost::parameter::keywordFeel::tag::desc')_

  • = boost::shared_ptrpo::options_description( new
    po::options_description( args[_desc] ) )*

Vincent Doyeux
Homepage : http://www-lsp.ujf-grenoble.fr/equipe/dyfcom/doyeux
Dynamique des Fluides Complexes (DyFCoM)
Interdisciplinary Laboratory of
Physicshttp://www-liphy.ujf-grenoble.fr/?lang=en(LIPhy).
UJF - University of Grenoble
140, rue de la physique, 38402 St Martin d'Hères Cedex
Bureau 330
Tel : +334 76 51 43 33

On Mon, Feb 17, 2014 at 12:15 PM, Alexandre Ancel
[email protected]:

Regarding to closing the Feelpp menu, I have looked into Onelab scripting
syntax and didn't find anything to do that. I think it will require
modifying code in Gmsh.

The DefinedParameters and GeneralParametersis just a trick for Gmsh
alphabetical ordering, so we have the parameters that have been
user-defined in first position (either through a config-file or command
line).

Reply to this email directly or view it on GitHubhttps://github.com//issues/273#issuecomment-35247978
.

prudhomm added a commit that referenced this issue Feb 17, 2014

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
@Doyeux this should be fine now
@prudhomm
Copy link
Member Author

this is fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants