Because PEAR:PHP_UML can only reverse engineer PHP Class and Interface files (not "flat" Drupal7-style
.inc</<code> files) this element is a pure analysis element without any relationship to a reverse engineered class: <div class="info TIP"> There is however a little trick that can help ease the process and saves a lot of tie. Once a <code>.module
file (or another non-class PHP file) is stable enough to be worth representing in UML, you can duplicate that file temporarily, wrap all duplicated function statements temporarily in a PHP class statement and brackets, reverse engineer the dummy class with PEAR:PHP_UML, then copy the reverse-engineered operations and attributes from the dummy UML class into the analysis Component representing the module file. Then delete the temporary duplicate dummy Class file and its matching dummy UML Class.
But from then on you need to baby-sit the @Component by hand, unless you are willing to manage flat and non-flat Class-like versions of the PHP files (which might be possible through code inclusion into the Class file).
© Copyright 2001 - 2016 Webel IT Australia (ABN: 67 677 268 579). All rights reserved (except as specified below).
PHP code examples from Webel IT Australia on this site are distributed under the GNU General Public License.
Excludes text and code snippets from Drupal.org quoted for educational purposes.
Drupal’s online documentation is © 2000-2014 by the individual contributors and can be used in accordance with the Creative Commons License, Attribution-ShareAlike 2.0.
PHP code from Drupal.org is distributed under the GNU General Public License.
Drupal® is a registered trademark of Dries Buytaert.
Text quoted from Wikipedia for educational purposes is made available under the Creative Commons Attribution-ShareAlike License.
Wikipedia® is a registered trademark of the Wikimedia Foundation, Inc., a non-profit organization.
Site developed by Webel IT Australia.