before you apply strictures (use strict, use warnings, etc.)
Add calls to use strict to each Help module. This is probably
an overstrict interpretation of the rule.
of processTemplate, there is a call to $self->get which adds all the asset
properties to the list of template variables. Sometimes they duplicate
entries in the www_ method (like view). Sometimes they're not interesting,
like templateId, but they're still valid template variables.
I'm going to start a new template variable entry for each asset that
will just contain those variables. Any www_ method calling processTemplate
can then include them via ISA into their list of template variables.
Fixed a typo in the Macro_r_printable where an ending bold tag was dropped.
Add some POD to Asset.pm talking about variables that are added when
processTemplate is called.
More ISA work in the Help system.
topics to be inherited from multiple entries. Operation/Help now also gives
the help hash a default ISA array, to make downstream processing by tests and
documentation compilers easier.
Convert existing Help entries that already used ISA to have an array ref
instead of a singular hash ref. Also update the Help skeleton to show
the new syntax.
Add a feature to the Help where the user's UI Level is checked
and only fields that he can see are displayed. A URL is provided
to override the UI.
Article help is updated to work with UI level display.
