When to publish Version 9, we are very excepting

We will have scheduled a public beta version for this quarter.

what are the new features ?

That will be revealed at that time

Will my still existing and very bothering Window List sort order problem (http://www.allroundautomations.com/...amp;Main=9485&Number=38585#Post38585)
finally be fixed then?

[quote]We will have scheduled a public beta version for this quarter.[/quote]
Tadaa, only 29 days left

Please, don't forget about promises to make version 9 multi-db and multi-schemas connection enable. To work like toad, in one copy of program with many databases and many schemas in it.
Thank You very much

Tadaa, only 14 days left

Maybe it's a bit late for this proposal, but i think the greatest weakness of PLSQLDeveloper is it's behaviour with Program code
and Debugging at the moment.

For Example:
- There is no paramter Info (popup) when you write a Function/Procedure
- Simple refactoring like rename variabels does only work on the definition
- The package navigator does nearly only work, when the code is compilable
- There is no debugging support of types and records

A agree to all requests.

I think that the name PL/SQL Developer would imply that the main focus of the program should be to faccilitate and support developing and debugging of PL/SQL code.

[quote]Simple refactoring like rename variabels does only work on the definition[/quote]
Please also refer to the topics:
Enhancement request refactoring: renaming record fields
Refactoring .... Rename Item for Type does not work.
Bug: Refactoring - Rename item does not work when prefixed with a minus
Bug?: refactoring cursor variables

[quote]The package navigator does nearly only work, when the code is compilable [/quote]
I agree, this as quite a pain in the a..
I have earlier suggested to the development team, that the line number is stored internally when a method/variable etc. is shown in the code content pane, and when the parser is unable to parse the code, the navigation should go to the stored line number. In this way, the cursor would always end somewhere near the code in question.