Bouml reference manual - Fedora Project Packages GIT repositories

More documents

Recommendations

Info

file:///C:/uml/BOUML/bouml_3.0/doc/TOUT.html112 of 378 07/10/2007 15:55enter the annotations proposing the default annotations (Deprecated ...) and the ones defined through the classes stereotyped @interface :The forms @{property}are replaced by the value of the corresponding user property if it is defined for the class or at an upper level, else it is not substituted.The edit body button is active when the definition contains ${body}, to edit it through the editor you want define the environmentvariable BOUML_EDITOR, furthermore, when you set add operation profile on body edition through the miscellaneous menu the formdefining the operation in the editor is added at the beginning of the edited file.Operation dialog, tab PhpThis tab allows to give the Php definition of the operation, it is visible only if Php is set through the Language menu
file:///C:/uml/BOUML/bouml_3.0/doc/TOUT.html113 of 378 07/10/2007 15:55In BOUML the generated code is obtained by the substitution of macros in a text, only the Definition part is editable, the other one helpyou to see what will be generated for Php (supposing you do not modify the Php code generator !).When you push the button Default definition, the form specified through the generation settings is proposed adding all the operationparameters given in the UML tab. These forms may be modified as you want, even to produce illegal source code !When you do not want to have this operation defined in Php, empties the definition <strong>manual</strong>ly or using the button not generated in Java.${visibility} produce the visibility (see the UML tab), except if the visibility is package, use this case to generate Php 4 code${final} produce an empty string when the check box final is not checked, else produce final${static} produce an empty string when the operation is not a class operation (see the UML tab), else produce static${abstract} produce abstract when the operation is abstract (see the UML tab), else an empty string.${name} is replaced by the name of the operation.${(} and ${)} produce ( and ), but there are also a mark for BOUML to find the parameters list${t} and ${p}produce the type and the name of each parameter (count from 0), this allows you to remove a parameter, add modifiers like array or & etc...${staticnl} produce a line break when the operation is static, else an empty string. Not used bu default, to add it change the generationsettings to use this macro.${body} is replaced by the body of the operation, this macro may also be replaced by the body itself (BOUML use this way for the getand set operations associated to a relation/attribute). The usage of ${body} has a great advantage : when you hit Default definition thebody is not cleared ! At least BOUML share the definition forms of the operations (and other objects) to minimize the needed memorysize, ${body} help for this ! The indentation of the keyword ${body} is added at the beginning of each line.The forms @{property}are replaced by the value of the corresponding user property if it is defined for the class or at an upper level, else it is not substituted.The edit body button is active when the definition contains ${body}, to edit it through the editor you want define the environmentvariable BOUML_EDITOR, furthermore, when you set add operation profile on body edition through the miscellaneous menu the formdefining the operation in the editor is added at the beginning of the edited file.
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: file:///C:/uml/BOUML/bouml_3.0/doc/
Page 111: file:///C:/uml/BOUML/bouml_3.0/doc/
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:
Page 305 and 306:
Page 307 and 308:
Page 309 and 310:
Page 311 and 312:
Page 313 and 314:
Page 315 and 316:
Page 317 and 318:
Page 319 and 320:
Page 321 and 322:
Page 323 and 324:
Page 325 and 326:
Page 327 and 328:
Page 329 and 330:
Page 331 and 332:
Page 333 and 334:
Page 335 and 336:
Page 337 and 338:
Page 339 and 340:
Page 341 and 342:
Page 343 and 344:
Page 345 and 346:
Page 347 and 348:
Page 349 and 350:
Page 351 and 352:
Page 353 and 354:
Page 355 and 356:
Page 357 and 358:
Page 359 and 360:
Page 361 and 362:
Page 363 and 364:
Page 365 and 366:
Page 367 and 368:
Page 369 and 370:
Page 371 and 372:
Page 373 and 374:
Page 375 and 376:
Page 377 and 378:
show all

Bouml reference manual - Fedora Project Packages GIT repositories

Create successful ePaper yourself

Delete template?

Save as template?