Bouml reference manual - Fedora Project Packages GIT repositories

More documents

Recommendations

Info

file:///C:/uml/BOUML/bouml_3.0/doc/TOUT.html354 of 378 07/10/2007 15:55Plug-outsTheplug-outsare the external programs written in C++ or Java interacting with BOUML, these programs may be written using BOUML itself. Tprevious chapter describe some plug-out including the code generators and code reverse.A plug-out is a very practical way to automatize treatment on the model, do not hesitate to write plug-out. I just recommend you to saveyour model before executing your plug-outs when you debug them :-) !Declaring a plug-outTo be executed, a plug-out must be declared through the tool dialog called when you select the tools settings entry of the tools menu :The first column specify how the plug-outis executed, for a C++ program you just have to give its name and may be the path depending on your environment, in Java the -cp optionallows to specify the path and the starting class is Main (except if you change the definition of the executable artifact !).The content of the second column will be displayed in the menu when your plug-out is applicable on the target item.The other columns allows to specify the kind of the items on whose the plug-out is applicable. For instance below, gpro may only beapplied on a artifact.Note that the declaration of the plug-out is saved in the file named tools, this allows you to quickly set the tools list after creating a newproject copying the tools file of an old project (this file is read when you load the project).Creating a new plug-outThe distribution of BOUML contains a project named empty, this one is a plug-out doing nothing for you point of view, in fact itimplements in C++ and Java the API allowing to interact with BOUML. To develop a new plug-out open the empty project, BOUML willask you to save it in an other project to keep empty unmodified. You may also develop a plug-out from one of the others availableplug-outs, you just have to know that these ones was developed at different step of the BOUML definition, then they do not contain allthe BOUML API and some operations may not be defined. By definition, empty contains all the API.The empty plug-out contains several already defined classes with their associated artifact, half of them are placed under the package APIBASE and implement the API with BOUML, you cannot modify them, they define the system part of a plus-out. The other half is yours,each of these user classes inherits to a system class, and sometimes a system class inherits of a user class, for instance the classesassociated to ... the classes are:
file:///C:/uml/BOUML/bouml_3.0/doc/TOUT.html355 of 378 07/10/2007 15:55In this diagram the blue classes are the system classes, the other classes are yours. UmlItem is the user class inherited by almost all theother classes.The disadvantage of this choice in C++ is to recompile many files when a base class is modified, but this allows to define (virtual)operations managing several classes.I do not describe in this documentation all the predefined classes and their operations, the better is to look at the model of a newly createdplug-out or to generate the html pages describing it (this is done under the empty_html directory, the html entry page isindex-withframe.html). I also recommend you to look at the plug-outs given with the BOUML distribution. Nevertheless you have toknow :the entry point of a plug-out in C++ and Java is placed in the artifact named Main under USER API, refer to itin C++ :if the C++ pre-processor variables WITHCPP, WITHJAVA, WITHPHP and WITHIDL are defined (using #define or -Doption of the G++ compiler, etc ...) you will get all the informations from BOUML.if the C++ pre-processor variables WITHCPP, WITHJAVA, WITHPHP and WITHIDL are not defined you will accessonly to UML data, this means for instance that the operations cppDecl javaDecl phpDecl and idlDecl will not be definedfor UmlBaseClassItem, this limits the amount of data managed by a plug-out and reduce the execution time and usedmemory spaceif only WITHCPP is defined you will access only to UML and C++ data, this means for instance that the operationsjavaDecl phpDecl and idlDecl will not be defined for UmlBaseClassItem, this limits the amount of data managed by aplug-out and reduce the execution time and used memory spaceif only WITHJAVA is defined you will access only to UML and Java data, this means for instance that the operationscppDecl phpDecl and idlDecl will not be defined for UmlBaseClassItem, this limits the amount of data managed by aplug-out and reduce the execution time and used memory spaceif only WITHPHP is defined you will access only to UML and Php data, this means for instance that the operationscppDecl javaDecl and idlDecl will not be defined for UmlBaseClassItem, this limits the amount of data managed by aplug-out and reduce the execution time and used memory spaceif only WITHIDL is defined you will access only to UML and IDL data, this means for instance that the operationscppDecl javaDecl and phpDecl will not be defined for UmlBaseClassItem, this limits the amount of data managed by aplug-out and reduce the execution time and used memory spacethe other combinations where only two of these three pre-processor variables are defined are illegal.
Page 1 and 2:
file:///C:/uml/BOUML/bouml_3.0/doc/
Page 3 and 4:
Page 5 and 6:
Page 7 and 8:
Page 9 and 10:
Page 11 and 12:
Page 13 and 14:
Page 15 and 16:
Page 17 and 18:
Page 19 and 20:
Page 21 and 22:
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
Page 193 and 194:
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Page 241 and 242:
Page 243 and 244:
Page 245 and 246:
Page 247 and 248:
Page 249 and 250:
Page 251 and 252:
Page 253 and 254:
Page 255 and 256:
Page 257 and 258:
Page 259 and 260:
Page 261 and 262:
Page 263 and 264:
Page 265 and 266:
Page 267 and 268:
Page 269 and 270:
Page 271 and 272:
Page 273 and 274:
Page 275 and 276:
Page 277 and 278:
Page 279 and 280:
Page 281 and 282:
Page 283 and 284:
Page 285 and 286:
Page 287 and 288:
Page 289 and 290:
Page 291 and 292:
Page 293 and 294:
Page 295 and 296:
Page 297 and 298:
Page 299 and 300:
Page 301 and 302:
Page 303 and 304: file:///C:/uml/BOUML/bouml_3.0/doc/
Page 353: file:///C:/uml/BOUML/bouml_3.0/doc/
show all

Bouml reference manual - Fedora Project Packages GIT repositories

Create successful ePaper yourself

Delete template?

Save as template?