Specify whether all generated anonymous CSS rules
must be stored in the external CSS file
(global style sheet).
Anonymous CSS rules are CSS rules generated from the formatting settings
specified on template components. They are called "anonymous" because these are basically sets
of inline CSS properties initially generated for particular HTML tags and, then, moved to a style sheet
to eliminate their repeating across the HTML file(s).
Now, only class selectors assigned to those CSS rules are specified in the HTML tags
(instead of the original CSS properties).
But the class selectors are generated automatically, which depends on how early a particular
CSS property set was registered in the style sheet. That makes them completely
unpredictable and dependent on the data being documented, which prohibits substituting
the anonymous rules with any custom ones.
When this option is selected (true
), all
anonymous rules
generated across all generated HTML files will be collected in the
global style sheet
(which is printed further as the external CSS file).
That produces the most compact documentation files, because many anonymous rules repeat themselves
across different HTML document. So, it is the default setting.
When this option is unselected (false
), the
anonymous rules
will be generated and stored
locally
by each HTML document where they are used.
The global style sheet
won't include anonymous rules.
You may want this in the following situations:
-
Since anonymous CSS rules
(i.e. their class selectors) are generated completely unpredictably, even a little change
in the input data, which would affect just a single HTML file, may cause a great disturbance
in the naming of all anonymous rules stored in the
style sheet
used by that HTML file.
When it is the global style sheet,
all HTML files, where any anonymous rules are used, will change too.
This won't be good, for instance, when you store your generated documentation in a repository system
that updates only changes of files relative to the previous version. Then, a massive disturbance in
the generated HTML (caused by just a few changes in the input data) will lead to a massive update of
your repository (particularly in the case of very large documentation).
So, keeping all anonymous rules locally would help!
-
If you substitute all generated default
and
named CSS rules
with your custom CSS rules
and exclude all anonymous rules
from the
global style sheet,
its content effectively becomes static.
Then, you can simply use a
CSS pattern file
as a complete your CSS file.
${include css_usage_link.htm}