Skip Menu |

This queue is for tickets about the Tk-JFileDialog CPAN distribution.

Report information
The Basics
Id: 125555
Status: resolved
Priority: 0/
Queue: Tk-JFileDialog

People
Owner: turnerjw784 [...] yahoo.com
Requestors: tlhackque [...] yahoo.com
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: 2.0



Subject: Suggestion: Initial filename
Date: Mon, 11 Jun 2018 14:47:06 -0400
To: bug-Tk-JFileDialog [...] rt.cpan.org
From: tlhackque <tlhackque [...] yahoo.com>
Tk::JFileDialog::VERSION == 1.62 My day for trying to user your dialog... Wishlist item: It would be nice to have a mechanism for providing an initial value for the filename, as that would provide a better user experience in many cases.. For example: Application reads foo.txt, and would ordinarily write foo.pdf in the current directory. So, JFileDialog is called from Save As. Currently, I can't put "foo.pdf" into the filename box and './' into the path box. So even though the user is likely to use the suggested filename, but change the path, (s)he must select or type the name. This is annoying when the name is long. (There are use cases where the user rejects the filename, but uses the path.) One implementation might be: -initial => '/home/users/george/foo.pdf', or -initial => '~/george/foo.pdf', or -initial => './foo.pdf' ... leaving splitting the file and directory components to you. Or -initialPath => '/home/users/george', initialFilename => 'foo.pdf' Whatever fits your style... Thanks for your consideration.
I've just a/b got this and all the others working properly. Sry it's taken so long, but I decided to completely overhaul Tk::JFileDialog (which this module depends on) whilst I was at it and want to release it first. Quick question: How does "~" in a path name work on Windows and how is it converted to a proper "home" directory? Jim On Mon Jun 11 14:47:35 2018, tlhackque wrote: Show quoted text
> Tk::JFileDialog::VERSION == 1.62 > > My day for trying to user your dialog... Wishlist item: > > It would be nice to have a mechanism for providing an initial value for > the filename, as that would provide a better user experience in many cases.. > > For example: > Application reads foo.txt, and would ordinarily write foo.pdf in the > current directory. > > So, JFileDialog is called from Save As. > > Currently, I can't put "foo.pdf" into the filename box and './' into > the path box. > > So even though the user is likely to use the suggested filename, but > change the path, (s)he must select or type the name. This is annoying > when the name is long. (There are use cases where the user rejects the > filename, but uses the path.) > > One implementation might be: > -initial => '/home/users/george/foo.pdf', > or -initial => '~/george/foo.pdf', > or -initial => './foo.pdf' ... > > leaving splitting the file and directory components to you. > > Or -initialPath => '/home/users/george', initialFilename => 'foo.pdf' > > Whatever fits your style... > > Thanks for your consideration.
Fixed in v2.0, just released. You can now either specify -File => 'filename', with or without a -Path => '/path[/' -OR- -File => '/path/filename'. Jim. On Tue Jul 10 14:16:25 2018, TURNERJW wrote: Show quoted text
> I've just a/b got this and all the others working properly. Sry it's > taken so long, but I decided to completely overhaul Tk::JFileDialog > (which this module depends on) whilst I was at it and want to release > it first. Quick question: How does "~" in a path name work on > Windows and how is it converted to a proper "home" directory? > > Jim > > > On Mon Jun 11 14:47:35 2018, tlhackque wrote:
> > Tk::JFileDialog::VERSION == 1.62 > > > > My day for trying to user your dialog... Wishlist item: > > > > It would be nice to have a mechanism for providing an initial value > > for > > the filename, as that would provide a better user experience in many > > cases.. > > > > For example: > > Application reads foo.txt, and would ordinarily write foo.pdf in > > the > > current directory. > > > > So, JFileDialog is called from Save As. > > > > Currently, I can't put "foo.pdf" into the filename box and './' into > > the path box. > > > > So even though the user is likely to use the suggested filename, but > > change the path, (s)he must select or type the name. This is > > annoying > > when the name is long. (There are use cases where the user rejects > > the > > filename, but uses the path.) > > > > One implementation might be: > > -initial => '/home/users/george/foo.pdf', > > or -initial => '~/george/foo.pdf', > > or -initial => './foo.pdf' ... > > > > leaving splitting the file and directory components to you. > > > > Or -initialPath => '/home/users/george', initialFilename => 'foo.pdf' > > > > Whatever fits your style... > > > > Thanks for your consideration.