Marco -
First, great idea on the plsqldoc plug in. This will definitely play into our long-term processes.
Second, after using for 1/2 day or so, here are a few comments/suggestions.
1. Working on multiple databases I can see index.html becoming large and unruly. It would be nice to have a "master index" which simply provided a list of databases which then takes you to a database-specific index.html.
2. From within PL/SQL Developer, if I simply log off/on to a different database, plsqldoc doesn't recognize this change and will create a new 'owner' directory under the old 'database' directory.
That's all for now, back to changing the way we work around here.
- Tim
First, great idea on the plsqldoc plug in. This will definitely play into our long-term processes.
Second, after using for 1/2 day or so, here are a few comments/suggestions.
1. Working on multiple databases I can see index.html becoming large and unruly. It would be nice to have a "master index" which simply provided a list of databases which then takes you to a database-specific index.html.
2. From within PL/SQL Developer, if I simply log off/on to a different database, plsqldoc doesn't recognize this change and will create a new 'owner' directory under the old 'database' directory.
That's all for now, back to changing the way we work around here.
- Tim