Docs/ExperienceUI/pages/syntax.htm
changeset 0 d5ce4c64ef88
equal deleted inserted replaced
-1:000000000000 0:d5ce4c64ef88
       
     1 <html>
       
     2   <head>
       
     3     <title>ExperienceUI Documentation Content Frame</title>
       
     4     <link rel=stylesheet href=style.css type=text/css>
       
     5     <script type="text/javascript" src=cmd.js></script>
       
     6   </head>
       
     7   
       
     8   <body bgcolor="#FFFFFF" style="background-color:#FFFFFF;margin:0px;padding:0px">
       
     9   
       
    10     <table border=0 width=100% height=100%>
       
    11     
       
    12       <tr>
       
    13       
       
    14         <td valign=top style=margin:10px;padding:10px>
       
    15     
       
    16                   <h1>Syntax: What it all means</h1>
       
    17                     <p style="margin-left: 0.20in">
       
    18                     <font style="color: #000000">
       
    19                       Commands in this documentation are presented as follows:<br>
       
    20                       <br>
       
    21                       <script type="text/javascript">
       
    22                         define("XPUI_DEFINE", "Parameters</i> or <i>\"The Params\"", "Description of the symbol", "Default value here");
       
    23                         macro("XPUI_MACRO", "Param1 \"Parameter #2\"", "Description of macro");
       
    24                       </script>
       
    25                       <p style=margin-left:0.2in>
       
    26                       <font face=Verdana style=font-size:8pt>
       
    27                       Some defines are true/false values.  These are considered true if the value is defined, and false otherwise.
       
    28                       
       
    29                       <script type="text/javascript">
       
    30                         define("XPUI_BOOLEAN", "No parameters (true/false value)", "Description of the symbol", "true/<b>false</b>");
       
    31                       </script>
       
    32                       
       
    33                       <p style=margin-left:0.2in>
       
    34                       <b>NSIS Syntax Highlighting</b><br>
       
    35                       <br>
       
    36                       The ExperienceUI SDK Documentation also uses syntax highlighting for various NSIS commands and parameters.  Here's how it works:<br>
       
    37                       <br>
       
    38                       <font face="Courier New" style=font-size:8pt>
       
    39                         <font color=#0000FF><b>NSISCommand</b></font> <font color=#FF8040>/NSIS /Parameter</font> NSIS_String_Not_Quoted <font color=#008080>"NSIS String in quotes <font color=#800000><i>$WITH_VAR</i></font>"</font><br>
       
    40                         <font color=#008040>!directive </font>XPUI_DEFINE_SYMBOL <font color=#008080>"XPUI Define Value"</font>
       
    41                       </font><br>
       
    42 		      <br>
       
    43                       
       
    44                     </font>
       
    45                   </p>
       
    46 		  
       
    47 		  <h1>Inserting Commands</h1>
       
    48 		  
       
    49 		    <p style=margin-left:0.2in>
       
    50 		    
       
    51 		      <font face=Verdana style=font-size:8pt>
       
    52 		      
       
    53 		        In the ExperienceUI, all has a set order and organization.  The method for inserting commands and setting settings has been fine-tuned for the best
       
    54 			possible performance and the easiest possible setting of settings.<br>
       
    55 			<br>
       
    56 			To insert ExperienceUI-related macros, you must include the XPUI.nsh file before the point in the script where the macro is inserted.  If you fail to do
       
    57 			this, the NSIS compiler will halt.<br>
       
    58 			<br>
       
    59 			If you want custom GUI settings, you must define them before inserting the first language into your script.<br>
       
    60 			<br>
       
    61 			To change strings for any given language, you will need to define the string in the language you want it in, and then insert the associated 
       
    62 			XPUI_LANGUAGE macro.<br>
       
    63 			<br>
       
    64                         To change the UI that is used, you must define XPUI_UI, XPUI_UI_IDDINST, XPUI_UI_BOTTOMIMAGE, or XPUI_WANSIS_UI <b>before</b> including XPUI.nsh.  This is because some of the branding image controls are referenced in every page, and MakeNSIS requires that these controls be present in the current UI file.
       
    65 		      </font>
       
    66 		    
       
    67 		    </p>
       
    68 		    
       
    69         </td>
       
    70         
       
    71       </tr>
       
    72       
       
    73       <tr>
       
    74       
       
    75         <td valign=bottom style=margin:0px;padding:0px>
       
    76     
       
    77           <p class=footer>Copyright &copy; 2004-2006 Dan Fuhry.  All rights except those explicitly given in the <a href=license_agreement.htm style=color:#A0A0D0 onmouseover="this.style.color='#A0A0A0'" onmouseout="this.style.color='#A0A0D0'">license agreement</a> reserved.</p>
       
    78   
       
    79         </td>
       
    80         
       
    81       </tr>
       
    82       
       
    83     </table>
       
    84   
       
    85   </body>
       
    86   
       
    87 </html>