Mercurial > hg > forks > UniversalIndentGUI
changeset 657:24e1fd6d4bfa
Updated the documentation and the changelog.
git-svn-id: svn://svn.code.sf.net/p/universalindent/code/trunk@917 59b1889a-e5ac-428c-b0c7-476e01d41282
| author | thomas_-_s <thomas_-_s@59b1889a-e5ac-428c-b0c7-476e01d41282> |
|---|---|
| date | Mon, 09 Feb 2009 16:47:22 +0000 |
| parents | cd73fb26dfb0 |
| children | 6da4f30f2b96 |
| files | CHANGELOG.txt doc/iniFileFormat.html |
| diffstat | 2 files changed, 100 insertions(+), 90 deletions(-) [+] |
line wrap: on
line diff
--- a/CHANGELOG.txt Mon Feb 09 16:13:47 2009 +0000 +++ b/CHANGELOG.txt Mon Feb 09 16:47:22 2009 +0000 @@ -6,7 +6,7 @@ [change] When using a non Windows system the default editor font type is now Monospace instead of Courier. The latter was not found properly. [change] For security reason using a randomly generated temporary directory name on Unix based systems. [change] Improved the GUI updates for the Notepad++ plugin a bit. Not what I would call "good" yet. -[fix] Avoid a crash if an uigui ini file with faulty header info is read, where the indenter executable was emtpy. +[fix] Avoid a crash if an uigui ini file with faulty header info is read, where the indenter executable was empty. [fix] Some application settings were tried to be read from a wrong directory when running in multi user mode. 2008-10-14 Version 1.0.1
--- a/doc/iniFileFormat.html Mon Feb 09 16:13:47 2009 +0000 +++ b/doc/iniFileFormat.html Mon Feb 09 16:47:22 2009 +0000 @@ -1,20 +1,22 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> -<html> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en"> <head> - <meta http-equiv="content-type" content="text/html; charset=utf-8"> + <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <title>iniFileFormat</title> </head> <body> -Fileformat of the UniversalIndentGUI indent description ini files<br> -=================================================================<br> -<br> -1. General<br> -----------<br> -The ini file has equal base format as common used ini files. It contains groups, which are written in brackets []. These groups can contain keys, to which a value can be assigned by the equal sign =.<br> -<br> -2. Ini file header<br> -------------------<br> -At the beginning of the ini file the header is located. It is named [header]. In the following a ini file header is shown:<br> +<p> +Fileformat of the UniversalIndentGUI indent description ini files<br /> +=================================================================<br /> +<br /> +1. General<br /> +----------<br /> +The ini file has equal base format as common used ini files. It contains groups, which are written in brackets []. These groups can contain keys, to which a value can be assigned by the equal sign =.<br /> +<br /> +2. Ini file header<br /> +------------------<br /> +At the beginning of the ini file the header is located. It is named [header]. In the following a ini file header is shown:<br /> +</p> <pre> [header] categories=Predefined Style|Tab and Bracket|Indentation|Formatting @@ -25,81 +27,84 @@ indenterName=Artistic Style inputFileName=indentinput inputFileParameter= -manual="http://website.of.onlinemanual" +manual="http://website.of.onlinemanual" outputFileName=indentinput outputFileParameter=none parameterOrder=ipo stringparaminquotes=false -useCfgFileParameter="--options=" +useCfgFileParameter="--options=" version=1.21 </pre> - -"categories" defines the categories, where each parameter can be assigned to. It is a list of strings, with each category name divied by a "|" from the other.<br> -<br> -"cfgFileParameterEnding" defines how each parameter setting in the indenters config file is seperated from the other. Possible values are "cr" for CarriageReturn or any other string (also space signs, which are normally used if parameters are only set via commandline).<br> -<br> -"configFilename" is the filename of the indenters default config file. It is used when the indenter is being called and might be explicit handed over as argument by setting the parameter "useCfgFileParameter". If "configFilename" is left empty, all parameters are set with the commandline call of the indenter. (As needed for csstidy and phpCB for example.)<br> -<br> -"fileTypes" is a list of fileendings used for the selection in the "open source file" file dialog.<br> -<br> -"indenterFileName" is the name of the indenters executable without any extension. Under linux it is tested, whether only a file with the extension ".exe" exists. If so, wine will be used to call the indenter.<br> -<br> -"indenterName" is the name of the indenter as it will be shown in UniversalIndentGUIs indenters selection. Theoretic it can be any string.<br> -<br> -"inputFileName" defines the file used as input file for the called indenter. It is a copy of the previous opened source code file.<br> -<br> -"inputFileParameter" sets the eventually needed parameter in front of "inputFileName" to tell the indenter and the command line call that the following string is the input file. If set to "none" no special output file will be set.<br> -<br> -"manual" is a string that points to a website that hosts the indenters online manual.<br> -<br> -"outputFileName" the file name where the indenter writes its formatted source code to. Also the file UniversalIndentGUI reads after the indenter call to show it in the preview. Some times an indenter overwrites the content of the inputfile by default and creates a backup (as AStyle does). In this case "outputFileName" is equal to "inputFileName" but the parameter "outputFileParameter" has to be set to "none". No output file name will be selected for the indenter but UniversalIndentGUI knows where the output was written to.<br> -<br> -"outputFileParameter" same as for "inputFileParameter" with respect to the special case mentioned for "inputFileParameter" if the input file will be overwritten. If the indenter only writes to standard output (stdout) this value has to be set to "stdout" (see uigui_phpCB.ini). In that case "outputFileName" can be left empty. It will be ignored anyway.<br> -<br> -"parameterOrder" Some indenters need a strict order of the command line parameters for input file, output file and eventually indent settings. "parameterOrder" can be set to "iop", "ipo" and "pio" to define the order of input, ouput and paramters at the commandline call.<br> -<br> -"stringparaminquotes" tells UniversalIndentGUI that all string values should be written to the indenter config file in quotes.<br> -<br> -"useCfgFileParameter" is the parameter for the indenter used to tell the indenter where to find the config file, set in "configFilename", that it should use. If this parameter is left empty you should read the indenters manual where it searches by default for the config file.<br> -<br> -"version" is not evaluated by UiGUI, but by this it is easier to see for which version of the indenter the configuration file has been written for.<br> -<br> -3. The indenters parameters<br> ----------------------------<br> -After the header definition the paramters used by the indenter are defined. Each paramter name is written in brackets [] again, but the name is only descriptive and not functional. Each parameter consists of keys with values (same as in header). There are four types of parameters: boolean, numeric, string and multiple. All have the following keys in common:<br> -"Category" defines to which category they belong and are corresponding only shown there in the GUI.<br> -<br> -"Description" holds a text describing the parameter and it options. It is formatted as html, so source code examples can be embedded via <pre></pre> for example. This text is shown as tool tip for each parameter.<br> -<br> -"EditorType" defines whether the parameter is boolean, numeric, string or multiple.<br> -<br> -"ValueDefault" is the default value that is normally used by the indenter if this parameter is not defined. It is needed if the config file of an indenter is loaded but this parameter value is not defined there. For boolean 0 is equal to false and 1 is equal to true. In case of multiple the number defines which of the multiple choice parameters is selected, starting with 0.<br> -<br> -"Enabled" is not used for boolean but for all other parameters. Defines whether the value should be written to the indenters config file or not. If it is disabled it will not be written and the indenter uses its default value.<br> -<br> -<br> -3.1. Boolean parameters<br> -<br> -Example:<br> +<p> +"categories" defines the categories, where each parameter can be assigned to. It is a list of strings, with each category name divied by a "|" from the other.<br /> +<br /> +"cfgFileParameterEnding" defines how each parameter setting in the indenters config file is seperated from the other. Possible values are "cr" for CarriageReturn or any other string (also space signs, which are normally used if parameters are only set via commandline).<br /> +<br /> +"configFilename" is the filename of the indenters default config file. It is used when the indenter is being called and might be explicit handed over as argument by setting the parameter "useCfgFileParameter". If "configFilename" is left empty, all parameters are set with the commandline call of the indenter. (As needed for csstidy and phpCB for example.)<br /> +<br /> +"fileTypes" is a list of fileendings used for the selection in the "open source file" file dialog.<br /> +<br /> +"indenterFileName" is the name of the indenters executable without any extension. Under linux it is tested, whether only a file with the extension ".exe" exists. If so, wine will be used to call the indenter.<br /> +<br /> +"indenterName" is the name of the indenter as it will be shown in UniversalIndentGUIs indenters selection. Theoretic it can be any string.<br /> +<br /> +"inputFileName" defines the file used as input file for the called indenter. It is a copy of the previous opened source code file.<br /> +<br /> +"inputFileParameter" sets the eventually needed parameter in front of "inputFileName" to tell the indenter and the command line call that the following string is the input file. If set to "none" no special output file will be set. +If set to "<" or "stdin" the to be formatted source code will be sent to the indenter using the standard input stdin.<br /> +<br /> +"manual" is a string that points to a website that hosts the indenters online manual.<br /> +<br /> +"outputFileName" the file name where the indenter writes its formatted source code to. Also the file UniversalIndentGUI reads after the indenter call to show it in the preview. Some times an indenter overwrites the content of the inputfile by default and creates a backup (as AStyle does). In this case "outputFileName" is equal to "inputFileName" but the parameter "outputFileParameter" has to be set to "none". No output file name will be selected for the indenter but UniversalIndentGUI knows where the output was written to.<br /> +<br /> +"outputFileParameter" same as for "inputFileParameter" with respect to the special case mentioned for "inputFileParameter" if the input file will be overwritten. If the indenter only writes to standard output (stdout) this value has to be set to "stdout" (see uigui_phpCB.ini). In that case "outputFileName" can be left empty. It will be ignored anyway.<br /> +<br /> +"parameterOrder" Some indenters need a strict order of the command line parameters for input file, output file and eventually indent settings. "parameterOrder" can be set to "iop", "ipo" and "pio" to define the order of input, ouput and paramters at the commandline call.<br /> +<br /> +"stringparaminquotes" tells UniversalIndentGUI that all string values should be written to the indenter config file in quotes.<br /> +<br /> +"useCfgFileParameter" is the parameter for the indenter used to tell the indenter where to find the config file, set in "configFilename", that it should use. If this parameter is left empty you should read the indenters manual where it searches by default for the config file.<br /> +<br /> +"version" is not evaluated by UiGUI, but by this it is easier to see for which version of the indenter the configuration file has been written for.<br /> +<br /> +3. The indenters parameters<br /> +---------------------------<br /> +After the header definition the paramters used by the indenter are defined. Each paramter name is written in brackets [] again, but the name is only descriptive and not functional. Each parameter consists of keys with values (same as in header). There are four types of parameters: boolean, numeric, string and multiple. All have the following keys in common:<br /> +"Category" defines to which category they belong and are corresponding only shown there in the GUI.<br /> +<br /> +"Description" holds a text describing the parameter and it options. It is formatted as html, so source code examples can be embedded via <pre></pre> for example. This text is shown as tool tip for each parameter.<br /> +<br /> +"EditorType" defines whether the parameter is boolean, numeric, string or multiple.<br /> +<br /> +"ValueDefault" is the default value that is normally used by the indenter if this parameter is not defined. It is needed if the config file of an indenter is loaded but this parameter value is not defined there. For boolean 0 is equal to false and 1 is equal to true. In case of multiple the number defines which of the multiple choice parameters is selected, starting with 0.<br /> +<br /> +"Enabled" is not used for boolean but for all other parameters. Defines whether the value should be written to the indenters config file or not. If it is disabled it will not be written and the indenter uses its default value.<br /> +<br /> +<br /> +3.1. Boolean parameters<br /> +<br /> +Example:<br /> +</p> <pre> [ANSI style formatting] Category=0 -Description="<html>ANSI style formatting/indenting.</html>" +Description="<html>ANSI style formatting/indenting.</html>" EditorType=boolean -TrueFalse="--style=ansi|" +TrueFalse="--style=ansi|" Value=0 ValueDefault=0 </pre> - -The only special here is the key "TrueFalse". The string is a parameter list always consists of two parameters devided by a "|" sign, where the first one defines the true case and the second the false case. Some indenters like GreatCode have a parameter for true and false, some other like AStyle in this example only have a parameter for the false case, so the second parameter is empty.<br> -<br> -<br> -3.2. Numeric parameters<br> +<p> +The only special here is the key "TrueFalse". The string is a parameter list always consists of two parameters devided by a "|" sign, where the first one defines the true case and the second the false case. Some indenters like GreatCode have a parameter for true and false, some other like AStyle in this example only have a parameter for the false case, so the second parameter is empty.<br /> +<br /> +<br /> +3.2. Numeric parameters<br /> +</p> <pre> [Indent spaces] -CallName="--indent=spaces=" +CallName="--indent=spaces=" Category=1 -Description="<html>Indent using # spaces per indent</html>" +Description="<html>Indent using # spaces per indent</html>" EditorType=numeric Enabled=false MaxVal=20 @@ -107,41 +112,46 @@ Value=4 ValueDefault=4 </pre> - -Numeric parameters have defined a maximum value "MaxVal" and a minimum value "MinVal" which can/should not be exceeded. The "CallName" is the parameter as string as it will be written to the indenters config file. At its ending "Value" will be appended.<br> -<br> -<br> -3.3. String parameters<br> +<p> +Numeric parameters have defined a maximum value "MaxVal" and a minimum value "MinVal" which can/should not be exceeded. The "CallName" is the parameter as string as it will be written to the indenters config file. At its ending "Value" will be appended.<br /> +<br /> +<br /> +3.3. String parameters<br /> +</p> <pre> [Comment separation char] CallName=-cmt_sep_char_4- Category=5 -Description="<html>Set the special character to fill automatic comments.</html>" +Description="<html>Set the special character to fill automatic comments.</html>" EditorType=string Enabled=true Value=* ValueDefault=* </pre> - -The "CallName" is the parameter as string as it will be written to the indenters config file. At its ending "Value" will be appended. Value can also be a list of strings separated by the "|" sign. By this the parameter is written to the config file with each value in the list. <br> -In the upper example value could be "C|c|K". The result in the ouput file would be:<br> +<p> +The "CallName" is the parameter as string as it will be written to the indenters config file. At its ending "Value" will be appended. Value can also be a list of strings separated by the "|" sign. By this the parameter is written to the config file with each value in the list. <br /> +In the upper example value could be "C|c|K". The result in the ouput file would be:<br /> -cmt_sep_char_4-C -cmt_sep_char_4-c -cmt_sep_char_4-K -<br> -<br> -<br> -3.4. Multiple parameters<br> +<br /> +<br /> +<br /> +3.4. Multiple parameters<br /> +</p> <pre> [Bracket style] Category=1 -Choices="--brackets=break|--brackets=attach|--brackets=linux|--brackets=break-closing-headers" -ChoicesReadable="Break brackets|Attach brackets|Break brackets Linux like|Break closing headers" -Description="<html>Sets the bracket style.</html>" +Choices="--brackets=break|--brackets=attach|--brackets=linux|--brackets=break-closing-headers" +ChoicesReadable="Break brackets|Attach brackets|Break brackets Linux like|Break closing headers" +Description="<html>Sets the bracket style.</html>" EditorType=multiple Enabled=false Value=1 ValueDefault=-1 </pre> -Multiple parameters can have exactly one parameter out of a list selected. "Choices" is a parameter list consisting of parameters devided by a "|" sign. Each parameter in the list will be exactly written to the indenters config file as defined here. The list "ChoicesReadable" can be used to show more readable text in the combo box, instead of the "Choices" text. "ChoicesReadable" must have as many entries as "Choices".<br></body> +<p> +Multiple parameters can have exactly one parameter out of a list selected. "Choices" is a parameter list consisting of parameters devided by a "|" sign. Each parameter in the list will be exactly written to the indenters config file as defined here. The list "ChoicesReadable" can be used to show more readable text in the combo box, instead of the "Choices" text. "ChoicesReadable" must have as many entries as "Choices".<br /> +</p> +</body> </html>