<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to feature-requests</title><link href="https://sourceforge.net/p/vbdox/feature-requests/" rel="alternate"/><link href="https://sourceforge.net/p/vbdox/feature-requests/feed.atom" rel="self"/><id>https://sourceforge.net/p/vbdox/feature-requests/</id><updated>2007-08-22T13:14:53Z</updated><subtitle>Recent changes to feature-requests</subtitle><entry><title>Common comments</title><link href="https://sourceforge.net/p/vbdox/feature-requests/22/" rel="alternate"/><published>2007-08-22T13:14:53Z</published><updated>2007-08-22T13:14:53Z</updated><author><name>Dario</name><uri>https://sourceforge.net/u/darizotas/</uri></author><id>https://sourceforge.netb3b8501e2e8b1be747533352512248ad4089793c</id><summary type="html">&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;</summary></entry><entry><title>Simple file extension alias</title><link href="https://sourceforge.net/p/vbdox/feature-requests/21/" rel="alternate"/><published>2005-11-03T18:22:24Z</published><updated>2005-11-03T18:22:24Z</updated><author><name>Robert Adsett</name><uri>https://sourceforge.net/u/radsett/</uri></author><id>https://sourceforge.net6128fd5ccdba3eaf9c21c662bb1e926eab9cf2ab</id><summary type="html">&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;</summary></entry><entry><title>Overloaded member</title><link href="https://sourceforge.net/p/vbdox/feature-requests/20/" rel="alternate"/><published>2005-01-13T09:11:51Z</published><updated>2005-01-13T09:11:51Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.net3b555fa904c8c0e451f651e5270342b213db4aed</id><summary type="html">&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;</summary></entry><entry><title>Separate Friend from Private</title><link href="https://sourceforge.net/p/vbdox/feature-requests/19/" rel="alternate"/><published>2003-12-04T13:57:47Z</published><updated>2003-12-04T13:57:47Z</updated><author><name>Roland Schoofs</name><uri>https://sourceforge.net/u/rolandschoofs/</uri></author><id>https://sourceforge.netb5ff1320cb642ca3e6fe79585de92e3c16ea24a2</id><summary type="html">&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;</summary></entry><entry><title>Source Code</title><link href="https://sourceforge.net/p/vbdox/feature-requests/18/" rel="alternate"/><published>2003-09-09T21:18:32Z</published><updated>2003-09-09T21:18:32Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.netd643705658e1f6691e411234fa62cfedc016183a</id><summary type="html">&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;</summary></entry><entry><title>Currently, .DSR report files are not processed...</title><link href="https://sourceforge.net/p/vbdox/feature-requests/17/" rel="alternate"/><published>2003-07-31T21:56:56Z</published><updated>2003-07-31T21:56:56Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.net1a9a70a0ba7b3197a2110fb2f7983b29af06cd9d</id><summary type="html">&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;</summary></entry><entry><title>Don't include both property methods</title><link href="https://sourceforge.net/p/vbdox/feature-requests/16/" rel="alternate"/><published>2002-12-31T21:56:15Z</published><updated>2002-12-31T21:56:15Z</updated><author><name>Jeff Bramwell</name><uri>https://sourceforge.net/u/jbramwell/</uri></author><id>https://sourceforge.net9e6b572a1f3802b475de3766fd42b95fc4d0ecc4</id><summary type="html">&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;</summary></entry><entry><title>Group Methods/Properties</title><link href="https://sourceforge.net/p/vbdox/feature-requests/15/" rel="alternate"/><published>2002-12-31T21:54:34Z</published><updated>2002-12-31T21:54:34Z</updated><author><name>Jeff Bramwell</name><uri>https://sourceforge.net/u/jbramwell/</uri></author><id>https://sourceforge.net9a993afaf9857e1fab4cfffab9ede5ef1b836d42</id><summary type="html">&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;</summary></entry><entry><title>Show properties as one entry (.Net rptm)</title><link href="https://sourceforge.net/p/vbdox/feature-requests/14/" rel="alternate"/><published>2002-12-10T23:10:05Z</published><updated>2002-12-10T23:10:05Z</updated><author><name>Alexander Black</name><uri>https://sourceforge.net/u/noirs/</uri></author><id>https://sourceforge.netbe749812dd736d3d9d86b33ed79cf460248d7bab</id><summary type="html">&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;</summary></entry><entry><title>report errors in separate output file</title><link href="https://sourceforge.net/p/vbdox/feature-requests/13/" rel="alternate"/><published>2002-12-04T15:28:03Z</published><updated>2002-12-04T15:28:03Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.net40842f5c0e6b7e6d0975c4c1bd97045c1c8935ce</id><summary type="html">&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;</summary></entry></feed>