Tk-JFileDialog 1.6
- Released by
- TURNERJW
- Version
- Release Date
- 2015-01-25
- Kwalitee
- 131.25
- Core Kwalitee
- 84.38
- LINKS
Tk-JFileDialog 1.6 Deleted
Kwalitee Issues
- has_changelog
-
Add a Changelog (best named 'Changes') to the distribution. It should list at least major changes implemented in newer versions.
- has_human_readable_license
-
Add a section called "LICENSE" to the documentation, or add a file named LICENSE to the distribution.
- has_license_in_source_file
-
Add =head1 LICENSE and the text of the license to the main module in your code.
- manifest_matches_dist
-
Run a proper command ("make manifest" or "./Build manifest", maybe with a force option), or use a distribution builder to generate the MANIFEST. Or update MANIFEST manually.
Error:
- MANIFEST (11) does not match dist (9):
- Missing in Dist: Tk::JFileDialog.3
- Duplicates in MANIFEST: test.pl
- no_pod_errors
-
Remove the POD errors. You can check for POD errors automatically by including Test::Pod to your test suite.
Error: Tk-JFileDialog-1.6/lib/Tk/JFileDialog.pm -- Around line 56: '=item' outside of any '=over' Around line 107: You forgot a '=back' before '=head1' Around line 125: You forgot a '=back' before '=head1'
- meta_yml_declares_perl_version
-
If you are using Build.PL define the {requires}{perl} = VERSION field. If you are using MakeMaker (Makefile.PL) you should upgrade ExtUtils::MakeMaker to 6.48 and use MIN_PERL_VERSION parameter. Perl::MinimumVersion can help you determine which version of Perl your module needs.
- has_tests_in_t_dir
-
Add tests or move tests.pl to the t/ directory!
- has_known_license_in_source_file
-
Add =head1 LICENSE and/or the proper text of the well-known license to the main module in your code.
- use_warnings
-
Add 'use warnings' (or its equivalents) to all modules, or convince us that your favorite module is well-known enough and people can easily see the modules warn when something bad happens.
Error: Tk::JFileDialog
- meta_yml_has_provides
-
Add all modules contained in this distribution to the META.yml field 'provides'. Module::Build or Dist::Zilla::Plugin::MetaProvides do this automatically for you.
- meta_yml_has_repository_resource
-
Add a 'repository' resource to the META.yml via 'meta_add' accessor (for Module::Build) or META_ADD parameter (for ExtUtils::MakeMaker).
- has_separate_license_file
-
This is not a critical issue. Currently mainly informative for the CPANTS authors. It might be removed later.
Modules
| Name | Abstract | Version | View |
|---|---|---|---|
| Tk::JFileDialog | A highly configurable File Dialog widget for Perl/Tk. | 1.6 | metacpan |