Update: This is now working, and you can see it in action on Padre trunk
The recent Padre 0.51 contains the second phase of "Save Intuition", a set of small tweaks designed to make saving quicker and less distracting.
In the first round I discussed earlier, Padre started to guess what it thinks the file name should be for the file based on the content.
In the second round, Padre will now also try to put the save dialog into the correct directory as well.
The logic goes like this.
"New files probably belong to the same project as the file that was open just before the user triggered a File -> New action. If this is a Perl file, in a Perl project, and we're saving 'package Foo::Bar', the user probably wants to save into $project/lib/Foo. Set dialog path to that directory, if it already exists."
My hope is that this feature is subtle enough that most people won't even notice it (or if they do, it's with momentary happy surprise and after that they take it for granted).
Of course, there's gaps in this logic. What if the directory does NOT exist? In the 0.51 release, it just bails out and so falls back to the normal choice for the save directory. Creating nested directory trees without the user asking for it is risky business.
But what if I specifically want that?
If I'm making a new class for an existing project, surely I should be able to just wave my hands at Padre and say "Save in the usual place" and have that just happen without showing a dialog at all (unless Padre gets confused and can't determine what the "usual place" is).
This third phase of Save Intuition is what I plan to be my main feature for 0.52 (assuming I can get it to work). I'm hoping to take Ctrl-Shift-S for this, so it acts just like a normal save, but adding the extra shift key adds more DWIM to the process.