Such minor changes are easy to do by modifying the XSL templates, I will
add a "deprecated" label.
An external "component.tapdoc.xml" file may be used per component to
provide additional information about the component, like:
- see also section
- visual sample
- others will come later, like inline examples...
I will add a <use-instead> (or similar) tag to implement the feature you
proposed until a better solution is available. In case of pure
java-based components (so without a .jwc specification) the @deprecated
javadoc tag and the @Deprecated annotation can be used as well to
express deprecation. (The framework should handle @Deprecated as well
when loading component classes...)
Regards,
Norbi
Brian K. Wallace wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Norbi -
This looks great. I'm always in favor of more/better documentation. :-)
Would it be possible on the deprecated components to have "Deprecated"
text (either above the description or somewhere around the see also)?
Not that it isn't spelled out that it's deprecated, but the boldness
lets it stand out (as there's no "legend" marking strikeout as
deprecated and past that you have to read the description) It'd be great
to have the "use instead", too (Deprecated: Use X instead) - but I'm
thinking that's just not possible if it's not put in the component in a
uniform fashion. :-/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
