Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).
This package collects everything to do with generation of Flag Plus banners for Flags. The default implementation is a rectangular strip banner with a text color, background color, border color and some style settings that apply across all banners (independent of flag state to type). But one could easily provide another implementation that uses a different geometry.
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).
Package/Model overview diagrams not do usually have to show the external client elements that depend on the elements of the Package or Model, it is done here only for illustration.
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).
Default simple factory for common products for this module.
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).
Simple factory for common products for this module.
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).
Implements management of data specific to a Flag banner state.
This version is suitable for use for a simple rectangular strip with a text color, background color, and border color. The same data could however be used for other banner designs.
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).
Default implementation of a banner specific to a Flag. This version uses a simple rectangular strip.
Note how it stores the data (text color, background color, border color, and style options) for the 2 separate states 'flagged' and 'not flagged' in dedicated state data holders !
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).
Helper class for aspects of banners specific to a Flag. Includes some simple database interaction helper methods.
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).
Manages information on flag applicability by entity type and bundle.
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).
If you look at the earliest code commits you'll see that the 2nd order $entity2flag map array was originally used directly; the module was refactored so that this helper class encapsulates it and only exposes value-added access methods.
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).
Constants common to the database schema of the banner aspects of the module.
So far just enough as an interim step to capture the column names of the DB table used for per-Flag banner settings.
Promotes robust Don't Repeat Yourself (DRY) code rather than error-prone Write Everything Twice (WET) code.
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).
Builder and handlers for bundle-to-flag sub forms.
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).
EXPERIMENTAL: AJAX version of a form for applicability of flags by bundle.
The form it builds has one or more embedded sub-forms for choosing applicability of flags by entity type and bundle (shown according to the entity-type filter choice).
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).
For building readonly pages of flag applicability by bundle.
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).
For building editable pages of flag applicability by bundle.
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).
In MagicDraw UML, a Component does not "steal ownership" of a graphically contained child element if the child's SYMBOL is moved/dragged from WITHIN A DIAGRAM into the Component's SYMBOL; it only steals ownerhips if the child model element is moved into (under) the Component WITHIN THE MODEL BROWSER.
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).
This "logical" analysis wrapper Component is for graphical organisation only. It does not (in this case) change the logical grouped elements' ownerships, but it does indicate a possible future packaging.
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).
The "unwrapped" diagram for the logical grouping component, showing Component Realization relationships to the logically (and otherwise graphically/visually) grouped participants.
The @Component is still (in this case) in fact contained (owned by) the Package 'flagplus', because how it was moved (dragged) as a graphical symbol into another graphical Component symbol, in MagicDraw UML ! By contrast, in MagicDraw UML, if you drag a Packageable model element in the project browser instead of in a diagraminto a Component it will change ownership ! Both of these modes yield fully compliant UML diagrams.
Collects constants and helper methods common to all bybundle flag forms.
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).
This educational site is brought to you by Webel IT Australia, experts in database-driven web technology for industry, engineering, education and science. Webel is one of Australia's most experienced Drupal CMS web site specialists.