<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to feature-requests</title><link>https://sourceforge.net/p/vbdox/feature-requests/</link><description>Recent changes to feature-requests</description><atom:link href="https://sourceforge.net/p/vbdox/feature-requests/feed.rss" rel="self"/><language>en</language><lastBuildDate>Wed, 22 Aug 2007 13:14:53 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/vbdox/feature-requests/feed.rss" rel="self" type="application/rss+xml"/><item><title>Common comments</title><link>https://sourceforge.net/p/vbdox/feature-requests/22/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Is there anyway at all possible to create common comments?&lt;/p&gt;
&lt;p&gt;So far I know currently have to be done in the following way:&lt;br /&gt;
''Common comment.&lt;br /&gt;
Public Const CONST_1 As Integer = 0&lt;br /&gt;
''Common comment.&lt;br /&gt;
Public Const CONST_2 As Integer = 1&lt;/p&gt;
&lt;p&gt;May be a new tag could be defined like PhpDocumentor does, for example:&lt;/p&gt;
&lt;p&gt;''@cc+&lt;br /&gt;
'Common comment.&lt;br /&gt;
Public Const CONST_1 As Integer = 0&lt;br /&gt;
Public Const CONST_2 As Integer = 1&lt;br /&gt;
''@cc-&lt;/p&gt;
&lt;p&gt;Where:&lt;br /&gt;
@cc+ Common comment begins.&lt;br /&gt;
@cc- Common comment ends.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dario</dc:creator><pubDate>Wed, 22 Aug 2007 13:14:53 -0000</pubDate><guid>https://sourceforge.netb3b8501e2e8b1be747533352512248ad4089793c</guid></item><item><title>Simple file extension alias</title><link>https://sourceforge.net/p/vbdox/feature-requests/21/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;I ran into this when using VBDOX with RAPID.&lt;br /&gt;
&lt;/p&gt;
&lt;p&gt;RAPID uses the extension .prg as well as .mod and .sys &lt;/p&gt;
&lt;p&gt;Since the extension for many languages is not fixed it&lt;br /&gt;
would be nice to be able to tell the program to use a&lt;br /&gt;
particular language parser with the file being loaded&lt;br /&gt;
regardless of its extension.&lt;/p&gt;
&lt;p&gt;As it is now it just fails.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Robert Adsett</dc:creator><pubDate>Thu, 03 Nov 2005 18:22:24 -0000</pubDate><guid>https://sourceforge.net6128fd5ccdba3eaf9c21c662bb1e926eab9cf2ab</guid></item><item><title>Overloaded member</title><link>https://sourceforge.net/p/vbdox/feature-requests/20/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;VB.NET supports overloaded member.&lt;br /&gt;
In version 2.0.40, overloaded subroutine, function etc,&lt;br /&gt;
are same.&lt;br /&gt;
I would like to see they are different.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Thu, 13 Jan 2005 09:11:51 -0000</pubDate><guid>https://sourceforge.net3b555fa904c8c0e451f651e5270342b213db4aed</guid></item><item><title>Separate Friend from Private</title><link>https://sourceforge.net/p/vbdox/feature-requests/19/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;In version 2.0.30 Friend and Private members are &lt;br /&gt;
grouped together. Public members are listed first, then &lt;br /&gt;
Private members. I would like to see Public first, then &lt;br /&gt;
Friend, then Public.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Roland Schoofs</dc:creator><pubDate>Thu, 04 Dec 2003 13:57:47 -0000</pubDate><guid>https://sourceforge.netb5ff1320cb642ca3e6fe79585de92e3c16ea24a2</guid></item><item><title>Source Code</title><link>https://sourceforge.net/p/vbdox/feature-requests/18/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;When are documenting internal projects could be very &lt;br /&gt;
usefull be able to view the soource code of an module, &lt;br /&gt;
function, or sub...&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Tue, 09 Sep 2003 21:18:32 -0000</pubDate><guid>https://sourceforge.netd643705658e1f6691e411234fa62cfedc016183a</guid></item><item><title>Currently, .DSR report files are not processed...</title><link>https://sourceforge.net/p/vbdox/feature-requests/17/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Since they're essentially the same as any other module, &lt;br /&gt;
it should be easy to include them also...&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Thu, 31 Jul 2003 21:56:56 -0000</pubDate><guid>https://sourceforge.net1a9a70a0ba7b3197a2110fb2f7983b29af06cd9d</guid></item><item><title>Don't include both property methods</title><link>https://sourceforge.net/p/vbdox/feature-requests/16/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;It would be nice to have an option that would allow only &lt;br /&gt;
one entry for each property declaration.  For example, if &lt;br /&gt;
I have a GET and a LET for a property I will end up with &lt;br /&gt;
two entries in my documentation.  It would be nice to &lt;br /&gt;
end up with a single entry that's marked as Read, &lt;br /&gt;
Write, or Read/Write.&lt;/p&gt;
&lt;p&gt;--- Thanks, Jeff&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jeff Bramwell</dc:creator><pubDate>Tue, 31 Dec 2002 21:56:15 -0000</pubDate><guid>https://sourceforge.net9e6b572a1f3802b475de3766fd42b95fc4d0ecc4</guid></item><item><title>Group Methods/Properties</title><link>https://sourceforge.net/p/vbdox/feature-requests/15/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;It would be very nice if the methods and properties could &lt;br /&gt;
be grouped separately (e.g. under a Methods and &lt;br /&gt;
Properties headings).&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jeff Bramwell</dc:creator><pubDate>Tue, 31 Dec 2002 21:54:34 -0000</pubDate><guid>https://sourceforge.net9a993afaf9857e1fab4cfffab9ede5ef1b836d42</guid></item><item><title>Show properties as one entry (.Net rptm)</title><link>https://sourceforge.net/p/vbdox/feature-requests/14/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;I think it would be better (and more consistent with &lt;br /&gt;
Microsoft) if Properties (Let/Get/Set) were rendered in &lt;br /&gt;
the report manager as one method.&lt;/p&gt;
&lt;p&gt;For example, instead of seeing:&lt;/p&gt;
&lt;p&gt;Title (get) The Title that will appear in the body of the &lt;br /&gt;
browser. E.g. &amp;amp;quot;Add Employee&amp;amp;quot; &lt;br /&gt;
Title (let) The Title that will appear in the body of the &lt;br /&gt;
browser. E.g. &amp;amp;quot;Add Employee&amp;amp;quot; &lt;/p&gt;
&lt;p&gt;I'd like to see:&lt;/p&gt;
&lt;p&gt;Title (get, let) The Title that will appear in the body of &lt;br /&gt;
the browser. E.g. &amp;amp;quot;Add Employee&amp;amp;quot; &lt;br /&gt;
&lt;/p&gt;
&lt;p&gt;Then when you click on this, it will give more info. &lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexander Black</dc:creator><pubDate>Tue, 10 Dec 2002 23:10:05 -0000</pubDate><guid>https://sourceforge.netbe749812dd736d3d9d86b33ed79cf460248d7bab</guid></item><item><title>report errors in separate output file</title><link>https://sourceforge.net/p/vbdox/feature-requests/13/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;VBDox supports in the actual version a batch mode or &lt;br /&gt;
quiet mode (command-line), which is very handy for &lt;br /&gt;
automated reporting generation via a scheduled task.&lt;/p&gt;
&lt;p&gt;but there is one thing, which is really missing:&lt;/p&gt;
&lt;p&gt;- a separate file, which contains all actual &lt;br /&gt;
documentation errors (These errors were normally &lt;br /&gt;
displayed with a message-box in the non-quit-mode)&lt;/p&gt;
&lt;p&gt;the error of course can be found in the documention file &lt;br /&gt;
itself, but there is no error-summary, where i can easyly &lt;br /&gt;
look, if there were any errors in the documentation.&lt;/p&gt;
&lt;p&gt;Axel&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Wed, 04 Dec 2002 15:28:03 -0000</pubDate><guid>https://sourceforge.net40842f5c0e6b7e6d0975c4c1bd97045c1c8935ce</guid></item></channel></rss>