gitpan ... so there is nobody watching for your pull request

ha, and I see that I missed the username on the gitpan as wenbinye , so the notification went through

:) must be too much turkey

and switching to getOpenFile for file selection.

That seems very odd, as it seems to destroy the purpose behind the module , which is to avoid getOpenFile by implementing a different look/feel...

Uhm, I'm not sure I I'd miss something here. Where do you get the information that Tk::FileEntry uses the far ugliest file selector on purpose?

I thought it's used because at the time when the module was written, there was no getOpenFile implementation for all OS'.

So, if this is not the case and Tk::FileEntry will be stuck with this scarecrow dialog, then my patch (which did not get any attention) was absolutely obsolete and I will have to do it myself anyway.

What do you think of Tk::FilePicker?

Read more... (355 Bytes)

on second thought I think I may have confused the Tk::FileEntry author as writing Tk::FileSelect ... so I wrote all that wrong "destroying of purpose" stuff ... was reading too much into it :/

What do you think of Tk::FilePicker?

Never heard of it :)

Do you mean as your own replacement for Tk::FileSelect? Not bad name :)

You might consider allowing a user to chooose what kind of dialog to popup, Tk::FileSelect, Tk::JFileDialog, Tk::FBox, whatever :)

That seems very odd, as it seems to destroy the purpose behind the module , which is to avoid getOpenFile by implementing a different look/feel...

When reading this, I got the impression that you might have mixed up Tk::FileEntry with Tk::PathEntry.

see Re^5: Questions about Tk::ACH distribution