Plugin questions (PLSQLDoc and version control)

[emrys]

PLSQLDoc - is it possible to generate documentation based on comments in a package BODY rather than SPEC? If not, could it be made so (since on the systems I'm working with the developers tend to have commented the body heavily and put none into the spec).

Also, is it, or could it be, possible to specify thigns to ignore in comments. For example quite often I do things like a line of equals or hypens in a comment in order to visually separate chunks of code, it would be nice to be able to specify e.g. three equals signs as marking a line to ignore etc.

Version Control - Just started to try this out, and although I can connect succesfuly to a SourceSafe project, I only see the files that are directly within that project, not any sub-projects (i.e. folders). Is this correct behaviour or do I have somethign set up incorrectly. The documentation appearss to suggest that viewing folders within projects is possible, but I not that the example shown is MKS not SourceSafe. If showing sub-projects in SourceSafe isn't currently possible, could it be added?

 

[Marco Kalter]

Both plsqldoc options are currently not possible, but are on our to-do list.

Unfortunately Visual SourceSafe does not know the concept of controlled sub-directories like other VCS tools such as PVCS and MKS. The screenshot from the documentation is from MKS. Visual SourceSafe uses sub-projects instead, but oddly enough this concept is not encapsulated in Microsoft's own SCC standard, which PL/SQL Developer uses as a common interface to all VCS systems.

As a result, you explicitly need to open a sub-project in order to access its files, which may be cumbersome if you have a lot of sub-projects.