Changeset bbff92 for src/UIElements

Timestamp:

Nov 3, 2011, 10:38:31 AM (13 years ago)

Author:

Frederik Heber <heber@…>

Branches:

Action_Thermostats, Add_AtomRandomPerturbation, Add_FitFragmentPartialChargesAction, Add_RotateAroundBondAction, Add_SelectAtomByNameAction, Added_ParseSaveFragmentResults, AddingActions_SaveParseParticleParameters, Adding_Graph_to_ChangeBondActions, Adding_MD_integration_tests, Adding_ParticleName_to_Atom, Adding_StructOpt_integration_tests, AtomFragments, Automaking_mpqc_open, AutomationFragmentation_failures, Candidate_v1.5.4, Candidate_v1.6.0, Candidate_v1.6.1, ChangeBugEmailaddress, ChangingTestPorts, ChemicalSpaceEvaluator, CombiningParticlePotentialParsing, Combining_Subpackages, Debian_Package_split, Debian_package_split_molecuildergui_only, Disabling_MemDebug, Docu_Python_wait, EmpiricalPotential_contain_HomologyGraph, EmpiricalPotential_contain_HomologyGraph_documentation, Enable_parallel_make_install, Enhance_userguide, Enhanced_StructuralOptimization, Enhanced_StructuralOptimization_continued, Example_ManyWaysToTranslateAtom, Exclude_Hydrogens_annealWithBondGraph, FitPartialCharges_GlobalError, Fix_BoundInBox_CenterInBox_MoleculeActions, Fix_ChargeSampling_PBC, Fix_ChronosMutex, Fix_FitPartialCharges, Fix_FitPotential_needs_atomicnumbers, Fix_ForceAnnealing, Fix_IndependentFragmentGrids, Fix_ParseParticles, Fix_ParseParticles_split_forward_backward_Actions, Fix_PopActions, Fix_QtFragmentList_sorted_selection, Fix_Restrictedkeyset_FragmentMolecule, Fix_StatusMsg, Fix_StepWorldTime_single_argument, Fix_Verbose_Codepatterns, Fix_fitting_potentials, Fixes, ForceAnnealing_goodresults, ForceAnnealing_oldresults, ForceAnnealing_tocheck, ForceAnnealing_with_BondGraph, ForceAnnealing_with_BondGraph_continued, ForceAnnealing_with_BondGraph_continued_betteresults, ForceAnnealing_with_BondGraph_contraction-expansion, FragmentAction_writes_AtomFragments, FragmentMolecule_checks_bonddegrees, GeometryObjects, Gui_Fixes, Gui_displays_atomic_force_velocity, ImplicitCharges, IndependentFragmentGrids, IndependentFragmentGrids_IndividualZeroInstances, IndependentFragmentGrids_IntegrationTest, IndependentFragmentGrids_Sole_NN_Calculation, JobMarket_RobustOnKillsSegFaults, JobMarket_StableWorkerPool, JobMarket_unresolvable_hostname_fix, MoreRobust_FragmentAutomation, ODR_violation_mpqc_open, PartialCharges_OrthogonalSummation, PdbParser_setsAtomName, PythonUI_with_named_parameters, QtGui_reactivate_TimeChanged_changes, Recreated_GuiChecks, Rewrite_FitPartialCharges, RotateToPrincipalAxisSystem_UndoRedo, SaturateAtoms_findBestMatching, SaturateAtoms_singleDegree, StoppableMakroAction, Subpackage_CodePatterns, Subpackage_JobMarket, Subpackage_LinearAlgebra, Subpackage_levmar, Subpackage_mpqc_open, Subpackage_vmg, Switchable_LogView, ThirdParty_MPQC_rebuilt_buildsystem, TrajectoryDependenant_MaxOrder, TremoloParser_IncreasedPrecision, TremoloParser_MultipleTimesteps, TremoloParser_setsAtomName, Ubuntu_1604_changes, stable

Children:

004ae7

Parents:

7ba268 (diff), f11c23 (diff)
Note: this is a merge changeset, the changes displayed below correspond to the merge itself.
Use the (diff) links above to see all the changes relative to each parent.

Message:

Merge branch 'Doxygen_Documentation_Enhancement' into mergeMaster

File:

• src/UIElements/CommandLineUI/CommandLineParser.hpp (modified) (1 diff)

src/UIElements/CommandLineUI/CommandLineParser.hpp

@@ -31 +31 @@
 
 /** This class is a wrapper for boost::program_options.
- *
- * <h1> CommandLine Howto </h1>
- * <h2> Introduction </h2>
- *
- * The UIFactory is a base class for the User Interaction. There are three UI specializations:
- * Text, GUI and CommandLine. Accessing functionality via the CommandLine UI is explained here.
- *
- * First, an Action has to be written for the specific functionality. This Action should
- * be added in Actions/...Action in the respective subdirectory of the following types:
- *  -# Analysis: Analysis actions like evaluating pair correlation, bonds, ...
- *  -# Atom: adding, removing, manipulating atoms
- *  -# Cmd: specifying data bases, verbosity, ...
- *  -# Fragmentation: fragmenting a system, performing graph analysis, ...
- *  -# Molecule: adding, removing, manipulating molecules
- *  -# Parser: Parsing files (loading, saving)
- *  -# Tesselation: obtaining (non)convex surface of a molecule, embedding, ...
- *  -# World: Setting Box dimensions, default name of new molecules, ...
- *
- *  The CommandLineUIFactory is a specialization of the UIFactory for parsing command
- *  line parameters, generating and executing actions there from.
- *
- *  The idea of the CommandLineFactory is explained elsewhere, here we would like to give a
- *  receipe for creating new actions.
- *
- * <h3>Introducing new actions</h3>
- *
- * Let us now introduce what to do if a new action is to be implemented. Here, we use the
- * CommandLineVersionAction as an example.
- * This consists if basically three parts:
- * 1. Create the files, write the classes and make them compilable
- *   - Create new source and header files in one of the above subfolders in the Actions folder,
- *     e.g. create VersionAction.cpp and VersionAction.hpp in Actions/Cmd/
- *   - Give it a sensible class name, the convention is <type><what it does>Action,
- *     where <type> is basically the naming (written out) of the subdirectory,
- *     e.g. class CommandLineVersionAction.
- *   - Add the source and header file to the respective variables in molecuilder/src/Makefile.am,
- *     e.g. if you add a Cmd action the variables are CMDACTIONSOURCE and CMDACTIONHEADER,
- *     such that they get compiled.
- * 2. Add an instance to the CommandLineUIFactory, such that they are known to the UI.
- *   - Add the header file as an include to UIElements/CommandLineWindow.cpp, e.g.
- *     #include "Actions/Cmd/VersionAction.hpp"
- *   - Add an instance of your class to the specific populater-function in
- *     UIElements/CommandLineWindow.cpp, e.g. for the above Cmd action, add to populateCommandActions()
- *     add new CommandLineVersionAction().
- *     This will automatically register in the ActionRegistry.
- * 3. Give them an option name, short hand an description, such that they can be referenced from
- *    the command line.
- *   - think of a new key name, e.g. "version", which is the long form of the command parameter,
- *     i.e. --version).
- *   - add this key to every map of MapofActions, i.e. to
- *     - MapofActions::DescriptionMap: the description which appears as help and tooltip
- *     - MapofActions::ShortFormMap: the short form of the command parameter (e.g. -v)
- *     - MapofActions::ValueMap: the value the command parameter has (do not create if it does not need one)
- *   - If your action requires additional parameters, these need to be added in the same manner as in
- *     the list item above.
- *
- *  Don't forget to write the actual code. :)
- *
- * <h3>Writing an action</h3>
- *
- *  As you write a new action you may think in terms of the command line, i.e. you want to use this
- *  new functionality you add by calling molecuilder as: ./molecuilder --super-action foobar.txt, where
- *  the key of your new action would be "super-action". While this is fine, keep in mind, that your action
- *  should be useable for the other UI specializations as well, i.e. from the menu and the GUI. Therefore,
- *  -# Don't use cin to ask the user for input: Use Query...()!
- *  -# Rather don't use cout/cerrs, but either give Log() or eLog() or use QueryEmpty() if you want to give
- *     the user specific information what you ask of him.
  *
  */