comment on

Hi!

Thank you for the answer. It's good to hear another opinion regarding the directory structure.

It look that I mixed things up. Tk::FileEntry does work. But it doesn't look good and it has a not-so-good documentation. That's what I improved: adding POD and switching to getOpenFile for file selection. And I made the bindings work that were commented in the test file.

I found Tk-ACH on github (https://github.com/gitpan/Tk-ACH), so I created a pull request. I hope it is usable, it's my first one.

Testing was tricky though. prove -l didn't work because there was no lib folder with expected directory structure. This is what I actually used instead of prove:

dmake TEST_FILES=t/fileentry.t TEST_VERBOSE=1 test
[download]

In reply to Re^2: Questions about Tk::ACH distribution by capfan
in thread Questions about Tk::ACH by capfan

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


more useful options
	PerlMonks