From: eap Date: Tue, 16 Oct 2018 10:47:56 +0000 (+0300) Subject: Typo and whitespace fixes by Kunda X-Git-Tag: V9_2_0a2~1 X-Git-Url: http://git.salome-platform.org/gitweb/?a=commitdiff_plain;h=33ccfdef3af44823c04b5e243e719a936df39eb1;p=plugins%2Fgmshplugin.git Typo and whitespace fixes by Kunda http://www.salome-platform.org/forum/forum_9/454200149#834683007 --- diff --git a/CMakeLists.txt b/CMakeLists.txt index 1f6128f..9e5cf02 100644 --- a/CMakeLists.txt +++ b/CMakeLists.txt @@ -55,7 +55,7 @@ IF(EXISTS ${KERNEL_ROOT_DIR}) LIST(APPEND CMAKE_MODULE_PATH "${KERNEL_ROOT_DIR}/salome_adm/cmake_files") INCLUDE(SalomeMacros) FIND_PACKAGE(SalomeKERNEL REQUIRED) - KERNEL_WITH_CORBA() # check whether KERNEL builded with CORBA + KERNEL_WITH_CORBA() # check whether KERNEL built with CORBA ELSE(EXISTS ${KERNEL_ROOT_DIR}) MESSAGE(FATAL_ERROR "We absolutely need a Salome KERNEL, please define KERNEL_ROOT_DIR") ENDIF(EXISTS ${KERNEL_ROOT_DIR}) @@ -107,7 +107,7 @@ IF(SALOME_BUILD_GUI) IF(EXISTS ${GUI_ROOT_DIR}) LIST(APPEND CMAKE_MODULE_PATH "${GUI_ROOT_DIR}/adm_local/cmake_files") FIND_PACKAGE(SalomeGUI) - SALOME_GUI_WITH_CORBA() # check whether GUI builded with CORBA + SALOME_GUI_WITH_CORBA() # check whether GUI built with CORBA ADD_DEFINITIONS(${GUI_DEFINITIONS}) INCLUDE_DIRECTORIES(${GUI_INCLUDE_DIRS}) ELSE(EXISTS ${GUI_ROOT_DIR}) diff --git a/README b/README index 80c1ff0..548995c 100644 --- a/README +++ b/README @@ -2,12 +2,12 @@ About SALOME GMSH plug-in ************************* -\b GMSHPLUGIN plugin provides an integration of certain functionnalities of the +\b GMSHPLUGIN plugin provides an integration of certain functionalities of the well known Gmsh three-dimensional finite element mesh generator. -It is capable to to mesh 2D and 3D geometric entities. The plugin was especialy -developped to integrate the Gmsh compound functionnality. +It is capable of meshing 2D and 3D geometric entities. The plugin was especially +developed to integrate the Gmsh compound functionality. For more information please visit the SALOME platform web site: @@ -32,8 +32,8 @@ Installation Pre-requisites -------------- -SALOME platform relies on a set of third-party softwares; some of them are needed -at build time only, while other ones are needed in runtime also. +SALOME platform relies on a set of third-party software; some of them are needed +at build time only, while other ones are needed at runtime as well. For more information about the pre-requisites please visit SALOME platform web site: @@ -54,7 +54,7 @@ Basic Installation ------------------ The build procedure of the SALOME platform is implemented with CMake. -In order to build the plug-in you have to do the following actions: +In order to build the plug-in you have to do the following actions: 1. Set up environment for pre-requisites (see "Pre-requisites" section above). @@ -70,7 +70,7 @@ In order to build the plug-in you have to do the following actions: where - is either Release or Debug (default: Release); - is a destination folder to install SALOME GMSH - plug-in (default: /usr); + plug-in (default: /usr); - is a path to the SALOME GMSH plug-in sources directory. Note: by default (if CMAKE_INSTALL_PREFIX option is not given), SALOME GMSH diff --git a/SalomeGMSHPLUGINConfig.cmake.in b/SalomeGMSHPLUGINConfig.cmake.in index 8a1e67e..7eba890 100644 --- a/SalomeGMSHPLUGINConfig.cmake.in +++ b/SalomeGMSHPLUGINConfig.cmake.in @@ -20,7 +20,7 @@ # - Config file for the @PROJECT_NAME@ package # It defines the following variables. -# Specific to the pacakge @PROJECT_NAME@ itself: +# Specific to the package @PROJECT_NAME@ itself: # @PROJECT_NAME_UC@_ROOT_DIR_EXP - the root path of the installation providing this CMake file # diff --git a/doc/salome/gui/GMSHPLUGIN/input/gmsh_2d_3d_hypo.doc b/doc/salome/gui/GMSHPLUGIN/input/gmsh_2d_3d_hypo.doc index b0e4120..237594e 100644 --- a/doc/salome/gui/GMSHPLUGIN/input/gmsh_2d_3d_hypo.doc +++ b/doc/salome/gui/GMSHPLUGIN/input/gmsh_2d_3d_hypo.doc @@ -13,9 +13,9 @@ hypotheses and algorithms (2D and 1D for meshing 3D objects and 1D for meshing 2 The Arguments tab of the dialog boxes is very similar to the original Gmsh GUI general mesh option tab. One familiar with the original interface can refer to the - Gmsh documentation for more informations. + Gmsh documentation for more information. We briefly describe each argument of the Arguments tab and give the original corresponding Gmsh keyword -(refering to Gmsh Mesh options list): +(referring to Gmsh Mesh options list): - Name - allows to define the name for the algorithm ("Gmsh Parameters" by default). - 2D algorithm - allows to choose the Gmsh 2D algorithm for both 2D and 3D meshes. Original corresponding Gmsh keyword is "Mesh.Algorithm". @@ -41,14 +41,14 @@ Original corresponding Gmsh keyword is "Mesh.CharacteristicLengthMin". which actually will become quadratic. Original corresponding Gmsh keyword is "Mesh.ElementOrder" (set to 2 if the box is checked in, else 1). - Use incomplete elements - if this box is checked in (default), quadratic elements will be incomplete. -For example a quadrangle will have 8 nodes if incomplete, 9 nodes if complete. See - Node ordering for more informations. -Be carefull with the case of pyramides. Complete pyramides will have 14 nodes but there is no pyra14 available in smesh. +For example a quadrangle will have 8 nodes if incomplete, 9 nodes if complete. See + Node ordering for more information. +Be careful with the case of pyramids. Complete pyramids will have 14 nodes but there is no pyra14 available in smesh. The last node created by Gmsh will then be ignored and using complete element can lead to orphelin nodes. Original corresponding Gmsh keyword is "Mesh.SecondOrderIncomplete" (set to 1 if the box is checked in, else 0).
-\image html Compounds.png Coumpounds tab of the dialog boxe. +\image html Compounds.png Compounds tab of the dialog boxes. In the Compounds tab of the dialog boxes, it is possible to choose the following arguments: - Add - allows to add geometrical defined groups of edges or groups of faces as compounds. @@ -57,5 +57,3 @@ When meshed, the single entity will be reparametrized as a single surface, whose - Remove - deletes selected rows from the table. */ - - diff --git a/doc/salome/gui/GMSHPLUGIN/input/index.doc b/doc/salome/gui/GMSHPLUGIN/input/index.doc index 5a69e32..b020186 100644 --- a/doc/salome/gui/GMSHPLUGIN/input/index.doc +++ b/doc/salome/gui/GMSHPLUGIN/input/index.doc @@ -2,10 +2,10 @@ \mainpage Introduction to GMSHPLUGIN -\b GMSHPLUGIN plugin provide an integration of certain functionnalities of the well known +\b GMSHPLUGIN plugin provides an integration of certain functionalities of the well known Gmsh three-dimensional finite element mesh generator. -It is possible to mesh 2D and 3D geometric entities. The plugin was especialy developped to -integrate the Gmsh coumpound functionnality. +It is possible to mesh 2D and 3D geometric entities. The plugin was especially developed to +integrate the Gmsh compound functionality. To manage parameters of the GMSHPLUGIN use \subpage gmsh_2d_3d_hypo_page. diff --git a/src/GMSHPlugin/GMSHPlugin_Mesher.cxx b/src/GMSHPlugin/GMSHPlugin_Mesher.cxx index da965f6..0875a33 100644 --- a/src/GMSHPlugin/GMSHPlugin_Mesher.cxx +++ b/src/GMSHPlugin/GMSHPlugin_Mesher.cxx @@ -296,7 +296,7 @@ void GMSHPlugin_Mesher::FillSMesh() e->getVertices(verts); ASSERT(verts.size()==1); //SMDS_Mesh0DElement* zeroDElement = 0; - // WE DONT ADD 0D ELEMENTS because it does not follow the salome meshers philosophy + // WE DON'T ADD 0D ELEMENTS because it does not follow the salome meshers philosophy //zeroDElement = meshDS->Add0DElementWithID(verts[0]->getNum(),e->getNum()); //meshDS->SetMeshElementOnShape(zeroDElement, topoVertex); }