<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic ABAP Doc printing in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap-doc-printing/m-p/10747804#M1875550</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi all together,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i tried to print my class documentation with ABAP Doc and find a small flaw in the output format of the result.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The following example describes the flaw:&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;
&lt;P&gt;"! Class to test ABAP Doc!!!!&lt;/P&gt;
&lt;P&gt;class lcl_abap_doc_test DEFINITION.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; PUBLIC SECTION.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; methods:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; "! Just a simple constructor.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; "!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; "! @parameter iv_text | A text to print....&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; constructor&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; IMPORTING&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; iv_text type string.&lt;/P&gt;
&lt;P&gt;endclass.&lt;/P&gt;
&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And these are the results within the element info view:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG class="migrated-image" src="https://community.sap.com/legacyfs/online/storage/attachments/storage/7/jiveimages/590003" width="450" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG class="migrated-image" src="https://community.sap.com/legacyfs/online/storage/attachments/storage/7/jiveimages/590005" width="450" /&gt;&lt;/P&gt;&lt;P&gt;The flaw from my point of view is, that in the result of the class part the signature of the methods is missing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If i print the class part now, i will not get the whole documentation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As a consequence it means,creating a single document with all information would require a big manual handling because i need to request each method seperately. For big classes with many methods this way is not realy comfortable.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there a way to get the whole documentation in one step? Maybe it is just a handling issues of me.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If not, would it be possible to have also the signature wihtin the class part?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BR&lt;/P&gt;&lt;P&gt;Eugen Soydas&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 20 Nov 2014 15:49:51 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2014-11-20T15:49:51Z</dc:date>
    <item>
      <title>ABAP Doc printing</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap-doc-printing/m-p/10747804#M1875550</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi all together,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i tried to print my class documentation with ABAP Doc and find a small flaw in the output format of the result.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The following example describes the flaw:&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;
&lt;P&gt;"! Class to test ABAP Doc!!!!&lt;/P&gt;
&lt;P&gt;class lcl_abap_doc_test DEFINITION.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; PUBLIC SECTION.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; methods:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; "! Just a simple constructor.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; "!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; "! @parameter iv_text | A text to print....&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; constructor&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; IMPORTING&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; iv_text type string.&lt;/P&gt;
&lt;P&gt;endclass.&lt;/P&gt;
&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And these are the results within the element info view:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG class="migrated-image" src="https://community.sap.com/legacyfs/online/storage/attachments/storage/7/jiveimages/590003" width="450" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG class="migrated-image" src="https://community.sap.com/legacyfs/online/storage/attachments/storage/7/jiveimages/590005" width="450" /&gt;&lt;/P&gt;&lt;P&gt;The flaw from my point of view is, that in the result of the class part the signature of the methods is missing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If i print the class part now, i will not get the whole documentation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As a consequence it means,creating a single document with all information would require a big manual handling because i need to request each method seperately. For big classes with many methods this way is not realy comfortable.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there a way to get the whole documentation in one step? Maybe it is just a handling issues of me.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If not, would it be possible to have also the signature wihtin the class part?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BR&lt;/P&gt;&lt;P&gt;Eugen Soydas&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 20 Nov 2014 15:49:51 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abap-doc-printing/m-p/10747804#M1875550</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2014-11-20T15:49:51Z</dc:date>
    </item>
    <item>
      <title>Re: ABAP Doc printing</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap-doc-printing/m-p/10747805#M1875551</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Eugen,&lt;/P&gt;&lt;P&gt;we are working on an export function of ABAP Doc into HTML pages that you can export from eclipse and print them out. Will be available with next enhancement pack. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Thomas. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 20 Nov 2014 21:04:41 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abap-doc-printing/m-p/10747805#M1875551</guid>
      <dc:creator>ThFiedler</dc:creator>
      <dc:date>2014-11-20T21:04:41Z</dc:date>
    </item>
    <item>
      <title>Re: ABAP Doc printing</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap-doc-printing/m-p/10747806#M1875552</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Thomas,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;many thanks for the quick reply.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm looking forward for the next EP and hope the problem i described above will be considered.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;&lt;P&gt;Eugen&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Nov 2014 08:13:52 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abap-doc-printing/m-p/10747806#M1875552</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2014-11-21T08:13:52Z</dc:date>
    </item>
  </channel>
</rss>

