[
https://issues.apache.org/jira/browse/CLI-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878217#action_12878217
]
gg commented on CLI-199:
------------------------
The assumption I made was not correct. Both rendering methods can stay
protected as it would colst too much effort to use them for gettig a nice
looking output.
Nevertheless my requirement having help content rendered into a StringBuffer
had to be solved. So I added kind of an indirection to the printng exposing
additional (public) rendering functions. One can now decide if to print or to
render into a SB.
Due to some strage behavior regarding the newLine usage renderHelp() is the
only method which may currently not be "generic".
I attached my version of the HelpFormatter to give you a better idea of the
whole thing.
Cheers, Ulf
> Improve HelpFormatter by making renderOptions() and renderWrappedText() public
> ------------------------------------------------------------------------------
>
> Key: CLI-199
> URL: https://issues.apache.org/jira/browse/CLI-199
> Project: Commons CLI
> Issue Type: Improvement
> Components: CLI-1.x
> Affects Versions: 1.1, 1.2, 1.3
> Reporter: gg
> Priority: Trivial
>
> Under certain circumstances it is usefull that HelpFormatter printing methods
> return a string buffer which can be used in further processing instead of
> direct printing to a PW or std.out.
> When having a closer look at the source one can easily retrieve string
> buffers with formatted text by changing the visibility of renderOptions() and
> renderWrappedText() from protected to public. This will make the "core"
> formatting methods available without adding additional functionallity to the
> HelpFormatter.
> Another option would be to add a set of print....() methods returning the SB
> instead of printing its content.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
