Recent content by Bergeroy

  1. B

    MAILTO tag with plsqldoc

    Hi Marco, How long will we wait for the next version with the corrected bug ? Thank you
  2. B

    MAILTO tag with plsqldoc

    I forgot to mention that I use the 1.1.16 version of plsqldoc. I did'nt have this problem with 1.1.15.
  3. B

    MAILTO tag with plsqldoc

    To be more precise, this is what I get in my generated HTML source: <A HREF="MAILTO:</code>#form@option.value#</code>"></code>#form@option.value#</code></A> and this is what I see in my browser for the same generated HTML documentation: <A HREF="MAILTO:#form@radio.value#">#form@radio.value#
  4. B

    MAILTO tag with plsqldoc

    Hi, In my source code documentation, I got something like: <code>#form@radio.value#</code> . After plsqldoc processing, I got this in my HTML documentation: <A HREF="MAILTO:#form@radio.value#">#form@radio.value# I don't know why plsqldoc is adding this anchor tag with MAILTO. In my...
  5. B

    Next release schedule

    Hi Marco, With your previous post, do you mean that you took my documentation directory as it is, that you ran plsqldoc over every objects and that you got all those objects cross-referenced ? If it's so, I must ask you again which version of plsqldoc your are using and also what are your...
  6. B

    Next release schedule

    Hi Marco, I'm always waiting for your feedback concerning the various PLSQLDoc Enhancements. Thank you
  7. B

    Next release schedule

    repost
  8. B

    Next release schedule

    Hi Marco, I just resent you the zip file at support@allroundautomations.com with the subject FW: Cross-reference bug with plsqldoc 1.1.4 I hope you received it this time. Thank you
  9. B

    Next release schedule

    Hi Marco, I sent you the zip file containing my documentation directory. Did you see anything concerning the missing cross-references ? Thank you
  10. B

    Next release schedule

    Hi again, Just to be sure we are testing the same plug-in, mine is about 1119k and was last modified on 2003/11/03 18:24
  11. B

    Next release schedule

    Hi, On what base does plsqldoc generates the link ? Does it scan all the previous generated HTML files or does it keep in memory a table of some kind ? Does the directory names that keep the generated files have some importance ? In fact, what could cause the problem ? Thank you
  12. B

    Next release schedule

    Hi, Here is a simple test case for the cross-reference bug with 1.1.4 version of plsqldoc. First, create that type: create or replace type /** Comment for TEST_TYPE_ABC */ TEST_TYPE_ABC as table of varchar2(10); Then, this one: create or replace type TEST_TYPE_DEF as object /**...
  13. B

    Next release schedule

    Hi, We just installed the last plsqldoc version (1.1.4) and some problems noticed before seem to be always there: - tag (see http://www.allroundautomations.com/ubb/Forum3/HTML/000396.html ). There is always a generated on the line before the one that contains a tag. It seems to me that...
  14. B

    Documenting Types for Plsqldoc

    Hi, The problem about type commenting seems to be also present in version 1.1.4 of plsqldoc. Is that problem scheduled to be corrected in a soon to be release version of plsqldoc? Thank you
  15. B

    Using the code tag with plsqldoc

    Hi, I'm trying again the CODE tag with the 1.1.4 version of plsqldoc. There seem to be some improvements but there is always an annoying BR on the line before the one that got a CODE tag. So create or replace package test2 is /** Sentence without a CODE tag that continues on the next...
Back
Top