view release on metacpan or search on metacpan
[@Author::PERLANCAR]
:version=0.53
[PruneFiles / PruneFiles additional]
filename = devscripts
filename = devdata
[Prereqs]
[Prereqs / DevelopRecommends]
;!lint_prereqs assume-used "spec"
view all matches for this distribution
view release on metacpan or search on metacpan
[@Author::PERLANCAR]
:version=0.53
[PruneFiles / PruneFiles additional]
filename = devscripts
filename = devdata
[Prereqs]
[Prereqs / DevelopRecommends]
;!lint_prereqs assume-used "spec"
view all matches for this distribution
view release on metacpan or search on metacpan
[@Author::PERLANCAR]
:version=0.53
[PruneFiles / PruneFiles additional]
filename = devscripts
filename = devdata
[Prereqs]
[Prereqs / DevelopRecommends]
;!lint_prereqs assume-used "spec"
view all matches for this distribution
view release on metacpan or search on metacpan
[@Author::PERLANCAR]
:version=0.53
[PruneFiles / PruneFiles additional]
filename = devscripts
filename = devdata
[Prereqs]
[Prereqs / DevelopRecommends]
;!lint_prereqs assume-used "spec"
view all matches for this distribution
view release on metacpan or search on metacpan
[@Author::PERLANCAR]
:version=0.53
[PruneFiles / PruneFiles additional]
filename = devscripts
filename = devdata
[Prereqs]
[Prereqs / DevelopRecommends]
;!lint_prereqs assume-used "spec"
view all matches for this distribution
view release on metacpan or search on metacpan
[@Author::PERLANCAR]
:version=0.53
[PruneFiles / PruneFiles additional]
filename = devscripts
filename = devdata
[Prereqs]
[Prereqs / DevelopRecommends]
;!lint_prereqs assume-used "spec"
view all matches for this distribution
view release on metacpan or search on metacpan
[@Author::PERLANCAR]
:version=0.53
[PruneFiles / PruneFiles additional]
filename = devscripts
filename = devdata
[Prereqs]
[Prereqs / DevelopRecommends]
;!lint_prereqs assume-used "spec"
view all matches for this distribution
view release on metacpan or search on metacpan
[@Author::PERLANCAR]
:version=0.53
[PruneFiles / PruneFiles additional]
filename = devscripts
filename = devdata
[Prereqs]
[Prereqs / DevelopRecommends]
;!lint_prereqs assume-used "spec"
view all matches for this distribution
view release on metacpan or search on metacpan
[@Author::PERLANCAR]
:version=0.53
[PruneFiles / PruneFiles additional]
filename = devscripts
filename = devdata
[Prereqs]
[Prereqs / DevelopRecommends]
;!lint_prereqs assume-used "spec"
view all matches for this distribution
view release on metacpan or search on metacpan
[@Author::PERLANCAR]
:version=0.54
[PruneFiles / PruneFiles additional]
filename = devscripts
filename = devdata
[Prereqs]
[Prereqs / DevelopX_spec]
-phase=develop
view all matches for this distribution
view release on metacpan or search on metacpan
[@Author::PERLANCAR]
:version=0.59
[PruneFiles / PruneFiles additional]
filename = devscripts
filename = devdata
[Prereqs]
[Prereqs / DevelopX_spec]
-phase=develop
view all matches for this distribution
view release on metacpan or search on metacpan
[@Author::PERLANCAR]
:version=0.53
[PruneFiles / PruneFiles additional]
filename = devscripts
filename = devdata
[Prereqs]
[Prereqs / DevelopRecommends]
;!lint_prereqs assume-used "spec"
view all matches for this distribution
view release on metacpan or search on metacpan
[@Author::PERLANCAR]
:version=0.53
[PruneFiles / PruneFiles additional]
filename = devscripts
filename = devdata
[Prereqs]
[Prereqs / DevelopRecommends]
;!lint_prereqs assume-used "spec"
view all matches for this distribution
view release on metacpan or search on metacpan
[@Author::PERLANCAR]
:version=0.53
[PruneFiles / PruneFiles additional]
filename = devscripts
filename = devdata
[Prereqs]
[Prereqs / DevelopRecommends]
;!lint_prereqs assume-used "spec"
view all matches for this distribution
view release on metacpan or search on metacpan
[@Author::PERLANCAR]
:version=0.53
[PruneFiles / PruneFiles additional]
filename = devscripts
filename = devdata
[Prereqs]
[Prereqs / DevelopRecommends]
;!lint_prereqs assume-used "spec"
view all matches for this distribution
view release on metacpan or search on metacpan
[@Author::PERLANCAR]
:version=0.54
[PruneFiles / PruneFiles additional]
filename = devscripts
filename = devdata
[Prereqs]
[Prereqs / DevelopX_spec]
-phase=develop
view all matches for this distribution
view release on metacpan or search on metacpan
[@Author::PERLANCAR]
:version=0.54
[PruneFiles / PruneFiles additional]
filename = devscripts
filename = devdata
[Prereqs]
[Prereqs / DevelopX_spec]
-phase=develop
view all matches for this distribution
view release on metacpan or search on metacpan
[@Author::PERLANCAR]
:version=0.46
[PruneFiles / PruneFiles additional]
filename = devscripts
filename = devdata
[Prereqs]
[Prereqs / DevelopRecommends]
;!lint_prereqs assume-used "spec"
view all matches for this distribution
view release on metacpan or search on metacpan
[@Author::PERLANCAR]
:version=0.46
[PruneFiles / PruneFiles additional]
filename = devscripts
filename = devdata
[Prereqs]
[Prereqs / DevelopRecommends]
;!lint_prereqs assume-used "spec"
view all matches for this distribution
view release on metacpan or search on metacpan
lib/Acme/CPANLists/PERLANCAR/ArrayClassBuilder.pm view on Meta::CPAN
This list catalogs class builders for classes that use array (instead of the
popular hash) as their backend storage.
Hash is the vastly popular backend for object due to its flexibility and
convenient mapping of hash keys to object attributes, but actually Perl objects
can be references to any kind of data (array, scalar, glob). Storing objects as
other kinds of references can be useful in terms of attribute access speed,
memory size, or other aspects. But they are not as versatile and generic as
hash.
_
lib/Acme/CPANLists/PERLANCAR/ArrayClassBuilder.pm view on Meta::CPAN
This list catalogs class builders for classes that use array (instead of the
popular hash) as their backend storage.
Hash is the vastly popular backend for object due to its flexibility and
convenient mapping of hash keys to object attributes, but actually Perl objects
can be references to any kind of data (array, scalar, glob). Storing objects as
other kinds of references can be useful in terms of attribute access speed,
memory size, or other aspects. But they are not as versatile and generic as
hash.
view all matches for this distribution
view release on metacpan or search on metacpan
"version" : "0.02"
},
{
"class" : "Dist::Zilla::Plugin::PERLANCAR::EnsurePrereqToSpec",
"config" : {
"Dist::Zilla::Role::ModuleMetadata" : {
"Module::Metadata" : "1.000037",
"version" : "0.006"
}
},
"name" : "@Author::PERLANCAR/PERLANCAR::EnsurePrereqToSpec",
"version" : "0.064"
"Dist::Zilla::Plugin::CheckSelfDependency" : {
"finder" : [
":InstallModules"
]
},
"Dist::Zilla::Role::ModuleMetadata" : {
"Module::Metadata" : "1.000037",
"version" : "0.006"
}
},
"name" : "@Author::PERLANCAR/CheckSelfDependency",
"version" : "0.011"
"$Dist::Zilla::Role::MetaProvider::Provider::VERSION" : "2.002004",
"inherit_missing" : 1,
"inherit_version" : 1,
"meta_noindex" : 1
},
"Dist::Zilla::Role::ModuleMetadata" : {
"Module::Metadata" : "1.000037",
"version" : "0.006"
}
},
"name" : "@Author::PERLANCAR/MetaProvides::Package",
"version" : "2.004003"
view all matches for this distribution
view release on metacpan or search on metacpan
"version" : "0.02"
},
{
"class" : "Dist::Zilla::Plugin::PERLANCAR::EnsurePrereqToSpec",
"config" : {
"Dist::Zilla::Role::ModuleMetadata" : {
"Module::Metadata" : "1.000037",
"version" : "0.006"
}
},
"name" : "@Author::PERLANCAR/PERLANCAR::EnsurePrereqToSpec",
"version" : "0.064"
"Dist::Zilla::Plugin::CheckSelfDependency" : {
"finder" : [
":InstallModules"
]
},
"Dist::Zilla::Role::ModuleMetadata" : {
"Module::Metadata" : "1.000037",
"version" : "0.006"
}
},
"name" : "@Author::PERLANCAR/CheckSelfDependency",
"version" : "0.011"
"$Dist::Zilla::Role::MetaProvider::Provider::VERSION" : "2.002004",
"inherit_missing" : 1,
"inherit_version" : 1,
"meta_noindex" : 1
},
"Dist::Zilla::Role::ModuleMetadata" : {
"Module::Metadata" : "1.000037",
"version" : "0.006"
}
},
"name" : "@Author::PERLANCAR/MetaProvides::Package",
"version" : "2.004003"
view all matches for this distribution
view release on metacpan or search on metacpan
"version" : "0.02"
},
{
"class" : "Dist::Zilla::Plugin::PERLANCAR::EnsurePrereqToSpec",
"config" : {
"Dist::Zilla::Role::ModuleMetadata" : {
"Module::Metadata" : "1.000037",
"version" : "0.006"
}
},
"name" : "@Author::PERLANCAR/PERLANCAR::EnsurePrereqToSpec",
"version" : "0.064"
"Dist::Zilla::Plugin::CheckSelfDependency" : {
"finder" : [
":InstallModules"
]
},
"Dist::Zilla::Role::ModuleMetadata" : {
"Module::Metadata" : "1.000037",
"version" : "0.006"
}
},
"name" : "@Author::PERLANCAR/CheckSelfDependency",
"version" : "0.011"
"$Dist::Zilla::Role::MetaProvider::Provider::VERSION" : "2.002004",
"inherit_missing" : 1,
"inherit_version" : 1,
"meta_noindex" : 1
},
"Dist::Zilla::Role::ModuleMetadata" : {
"Module::Metadata" : "1.000037",
"version" : "0.006"
}
},
"name" : "@Author::PERLANCAR/MetaProvides::Package",
"version" : "2.004003"
view all matches for this distribution
view release on metacpan or search on metacpan
lib/Acme/CPANModules/ArrayClassBuilder.pm view on Meta::CPAN
This list catalogs class builders for classes that use array (instead of the
popular hash) as their backend storage.
Hash is the vastly popular backend for object due to its flexibility and
convenient mapping of hash keys to object attributes, but actually Perl objects
can be references to any kind of data (array, scalar, glob). Storing objects as
other kinds of references can be useful in terms of attribute access speed,
memory size, or other aspects. But they are not as versatile and generic as
hash.
_
lib/Acme/CPANModules/ArrayClassBuilder.pm view on Meta::CPAN
This list catalogs class builders for classes that use array (instead of the
popular hash) as their backend storage.
Hash is the vastly popular backend for object due to its flexibility and
convenient mapping of hash keys to object attributes, but actually Perl objects
can be references to any kind of data (array, scalar, glob). Storing objects as
other kinds of references can be useful in terms of attribute access speed,
memory size, or other aspects. But they are not as versatile and generic as
hash.
=head1 ACME::CPANMODULES ENTRIES
view all matches for this distribution
view release on metacpan or search on metacpan
lib/Acme/CPANModules/ArrayData.pm view on Meta::CPAN
our $DIST = 'Acme-CPANModules-ArrayData'; # DIST
our $VERSION = '0.001'; # VERSION
my $text = <<'MARKDOWN';
<pm:ArrayData> is a way to package 1-dimensional array data as a Perl/CPAN
module. It also provides a standard interface to access the data, including
iterating the data rows, getting the column names, and so on.
**The data**
All Perl modules under `ArrayData::*` namespace are modules that contain array
data data. Examples include: `ArrayData::Sample::DeNiro`,
`ArrayData::Lingua::Word::EN::Enable`.
**CLIs**
<prog:arraydata> (from <pm:App::arraydata>) is the official CLI for `ArrayData`.
**Sah schemas**
<pm:Sah::Schemas::ArrayData>
lib/Acme/CPANModules/ArrayData.pm view on Meta::CPAN
This document describes version 0.001 of Acme::CPANModules::ArrayData (from Perl distribution Acme-CPANModules-ArrayData), released on 2024-01-22.
=head1 DESCRIPTION
L<ArrayData> is a way to package 1-dimensional array data as a Perl/CPAN
module. It also provides a standard interface to access the data, including
iterating the data rows, getting the column names, and so on.
B<The data>
All Perl modules under C<ArrayData::*> namespace are modules that contain array
data data. Examples include: C<ArrayData::Sample::DeNiro>,
C<ArrayData::Lingua::Word::EN::Enable>.
B<CLIs>
L<arraydata> (from L<App::arraydata>) is the official CLI for C<ArrayData>.
B<Sah schemas>
L<Sah::Schemas::ArrayData>
lib/Acme/CPANModules/ArrayData.pm view on Meta::CPAN
=item L<ArrayData>
Author: L<PERLANCAR|https://metacpan.org/author/PERLANCAR>
=item L<App::arraydata>
Author: L<PERLANCAR|https://metacpan.org/author/PERLANCAR>
=item L<Sah::Schemas::ArrayData>
view all matches for this distribution
view release on metacpan or search on metacpan
"version" : "0.02"
},
{
"class" : "Dist::Zilla::Plugin::PERLANCAR::EnsurePrereqToSpec",
"config" : {
"Dist::Zilla::Role::ModuleMetadata" : {
"Module::Metadata" : "1.000037",
"version" : "0.006"
}
},
"name" : "@Author::PERLANCAR/PERLANCAR::EnsurePrereqToSpec",
"version" : "0.064"
"Dist::Zilla::Plugin::CheckSelfDependency" : {
"finder" : [
":InstallModules"
]
},
"Dist::Zilla::Role::ModuleMetadata" : {
"Module::Metadata" : "1.000037",
"version" : "0.006"
}
},
"name" : "@Author::PERLANCAR/CheckSelfDependency",
"version" : "0.011"
"$Dist::Zilla::Role::MetaProvider::Provider::VERSION" : "2.002004",
"inherit_missing" : 1,
"inherit_version" : 1,
"meta_noindex" : 1
},
"Dist::Zilla::Role::ModuleMetadata" : {
"Module::Metadata" : "1.000037",
"version" : "0.006"
}
},
"name" : "@Author::PERLANCAR/MetaProvides::Package",
"version" : "2.004003"
view all matches for this distribution
view release on metacpan or search on metacpan
lib/Acme/CPANModules/BPOM/FoodRegistration.pm view on Meta::CPAN
**List of food additives**
<prog:bpom-list-food-additives> (from <pm:App::BPOMUtils::Table::FoodAdditive>)
is a CLI tool to search the database, which is scraped from BPOM website
(<https://ereg-rba.pom.go.id>).
**List of food ingredients**
<prog:bpom-list-food-ingredients-rba> (from
<pm:App::BPOMUtils::Table::FoodIngredient>) is a CLI tool to search the "daftar
bahan pangan" database, which is scraped from BPOM website
(<https://ereg-rba.pom.go.id>).
**List of food categories**
<prog:bpom-list-food-categories-rba> (from
<pm:App::BPOMUtils::Table::FoodCategory>) is a CLI tool to query the "kategori
pangan" database, which is scraped from BPOM website
(<https://ereg-rba.pom.go.id>).
**List of food types**
<prog:bpom-list-food-types-rba-importer> and
<prog:bpom-list-food-types-rba-producer> (from
<pm:App::BPOMUtils::Table::FoodType>) is a CLI tool to query the "jenis pangan"
database, which is scraped from BPOM website (<https://ereg-rba.pom.go.id>).
**List of registration code prefixes**
<prog:bpom-list-reg-code-prefixes> (from
lib/Acme/CPANModules/BPOM/FoodRegistration.pm view on Meta::CPAN
version of the website).
B<List of food additives>
L<bpom-list-food-additives> (from L<App::BPOMUtils::Table::FoodAdditive>)
is a CLI tool to search the database, which is scraped from BPOM website
(L<https://ereg-rba.pom.go.id>).
B<List of food ingredients>
L<bpom-list-food-ingredients-rba> (from
L<App::BPOMUtils::Table::FoodIngredient>) is a CLI tool to search the "daftar
bahan pangan" database, which is scraped from BPOM website
(L<https://ereg-rba.pom.go.id>).
B<List of food categories>
L<bpom-list-food-categories-rba> (from
L<App::BPOMUtils::Table::FoodCategory>) is a CLI tool to query the "kategori
pangan" database, which is scraped from BPOM website
(L<https://ereg-rba.pom.go.id>).
B<List of food types>
L<bpom-list-food-types-rba-importer> and
L<bpom-list-food-types-rba-producer> (from
L<App::BPOMUtils::Table::FoodType>) is a CLI tool to query the "jenis pangan"
database, which is scraped from BPOM website (L<https://ereg-rba.pom.go.id>).
B<List of registration code prefixes>
L<bpom-list-reg-code-prefixes> (from
L<App::BPOMUtils::Table::RegCodePrefix>) is a CLI tool to query the list of
view all matches for this distribution
view release on metacpan or search on metacpan
lib/Acme/CPANModules/BloomFilters.pm view on Meta::CPAN
our $LIST = {
summary => "List of bloom filter modules on CPAN",
description => <<'_',
Bloom filter is a data structure that allows you to quickly check whether an
element is in a set. Compared to a regular hash, it is much more
memory-efficient. The downside is that bloom filter can give you false
positives, although false negatives are not possible. So in essence you can ask
a bloom filter which item is "possibly in set" or "definitely not in set". You
can configure the rate of false positives. The larger the filter, the smaller
the rate. Some examples for application of bloom filter include: 1) checking
whether a password is in a dictionary of millions of common/compromised
passwords; 2) checking an email address against leak database; 3) virus pattern
checking; 4) IP/domain blacklisting/whitelisting. Due to its properties, it is
sometimes combined with other data structures. For example, a small bloom filter
can be distributed with a software to check against a database. When the answer
from bloom filter is "possibly in set", the software can further consult on
online database to make sure if it is indeed in set. Thus, bloom filter can be
used to reduce the number of direct queries to database.
In Perl, my default go-to choice is <pm:Algorithm::BloomFilter>, unless there's
a specific feature I need from other implementations.
_
lib/Acme/CPANModules/BloomFilters.pm view on Meta::CPAN
This document describes version 0.004 of Acme::CPANModules::BloomFilters (from Perl distribution Acme-CPANModules-BloomFilters), released on 2022-03-18.
=head1 DESCRIPTION
Bloom filter is a data structure that allows you to quickly check whether an
element is in a set. Compared to a regular hash, it is much more
memory-efficient. The downside is that bloom filter can give you false
positives, although false negatives are not possible. So in essence you can ask
a bloom filter which item is "possibly in set" or "definitely not in set". You
can configure the rate of false positives. The larger the filter, the smaller
the rate. Some examples for application of bloom filter include: 1) checking
whether a password is in a dictionary of millions of common/compromised
passwords; 2) checking an email address against leak database; 3) virus pattern
checking; 4) IP/domain blacklisting/whitelisting. Due to its properties, it is
sometimes combined with other data structures. For example, a small bloom filter
can be distributed with a software to check against a database. When the answer
from bloom filter is "possibly in set", the software can further consult on
online database to make sure if it is indeed in set. Thus, bloom filter can be
used to reduce the number of direct queries to database.
In Perl, my default go-to choice is L<Algorithm::BloomFilter>, unless there's
a specific feature I need from other implementations.
=head1 ACME::CPANMODULES ENTRIES
lib/Acme/CPANModules/BloomFilters.pm view on Meta::CPAN
An Inline::C module. Barely documented. Also does not provide filter
saving/loading methods.
=item * L<Algorithm::BloomFilter> - A simple bloom filter data structure
Author: L<SMUELLER|https://metacpan.org/author/SMUELLER>
XS, made by SMUELLER. Can merge other bloom filters. Provides serialize and
deserialize methods.
=item * L<Bloom::Scalable> - Implementation of the probalistic datastructure - ScalableBloomFilter
Author: L<SUBBU|https://metacpan.org/author/SUBBU>
Pure-perl module. A little weird, IMO, e.g. with hardcoded filenames. The
distribution also provides L<Bloom::Simple>.
view all matches for this distribution
view release on metacpan or search on metacpan
"version" : "0.02"
},
{
"class" : "Dist::Zilla::Plugin::PERLANCAR::EnsurePrereqToSpec",
"config" : {
"Dist::Zilla::Role::ModuleMetadata" : {
"Module::Metadata" : "1.000037",
"version" : "0.006"
}
},
"name" : "@Author::PERLANCAR/PERLANCAR::EnsurePrereqToSpec",
"version" : "0.064"
"Dist::Zilla::Plugin::CheckSelfDependency" : {
"finder" : [
":InstallModules"
]
},
"Dist::Zilla::Role::ModuleMetadata" : {
"Module::Metadata" : "1.000037",
"version" : "0.006"
}
},
"name" : "@Author::PERLANCAR/CheckSelfDependency",
"version" : "0.011"
"$Dist::Zilla::Role::MetaProvider::Provider::VERSION" : "2.002004",
"inherit_missing" : 1,
"inherit_version" : 1,
"meta_noindex" : 1
},
"Dist::Zilla::Role::ModuleMetadata" : {
"Module::Metadata" : "1.000037",
"version" : "0.006"
}
},
"name" : "@Author::PERLANCAR/MetaProvides::Package",
"version" : "2.004003"
view all matches for this distribution
view release on metacpan or search on metacpan
lib/Acme/CPANModules/BrowsingTableInteractively.pm view on Meta::CPAN
our $DATE = '2023-06-15'; # DATE
our $DIST = 'Acme-CPANModules-BrowsingTableInteractively'; # DIST
our $VERSION = '0.009'; # VERSION
our $LIST = {
summary => 'List of modules/tools for browsing table data interactively',
description => <<'_',
This list reviews what tools are available on CPAN and in general to browse
table data interactively.
Let me say first that the best tools are not Perl-based since sadly Perl is not
a favorite choice for writing tools these days. That said, Perl is still a great
glue to help make those tools work together better for you.
1) **Visidata**, <https://www.visidata.org>
This is currently my favorite. It's terminal-based, written in Python, and has
more features than any other tools currently written in Perl, by far. vd has
support for many formats, including CSV, TSV, Excel, JSON, and SQLite. It makes
it particularly easy to create summary for your table like histogram or
sum/average/max/min/etc, or add new columns, or edit some cells. It also has
visualization features like XY-plots.
It has the concept of "sheets" like sheets in a spreadsheet workbook so anytime
you filter rows/columns or create summary or do some other derivation from your
data, you create a new sheet which you can edit, save, and destroy later as
needed and go back to your original table. It even presents settings and
metadata as sheets so you can edit them as a normal sheet.
It has plugins, and I guess it should be simple enough to create a plugin so you
can filter rows or add columns using Perl expression instead of the default
Python, if needed.
My CLI framework <pm:Perinci::CmdLine> (<pm:Perinci::CmdLine::Lite>, v1.918+)
has support for Visidata. You can specify command-line option `--format=vd` to
browse the output of your CLI program in Visidata.
2) **DataTables**, <https://datatables.net>
DataTables is a JavaScript (jQuery-based) library to add controls to your HTML
table so you can filter rows incrementally, sort rows, reorder columns, and so
on. It also has plugins to do more customized stuffs. I still prefer Visidata
most of the time because I am comfortable living in the terminal, but I
particularly love the incremental searching feature that comes built-in with
DataTables.
My CLI framework <pm:Perinci::CmdLine> (<pm:Perinci::CmdLine::Lite>, v1.918+)
also has support for DataTables. You can specify command-line option
`--format=html+datatables` to output your CLI program's result as HTML table
(using <pm:Text::Table::HTML::DataTables>) when possible and then browse the
output in browser.
3) **Tickit::Widget::Table**, <pm:Tickit::Widget::Table>
lib/Acme/CPANModules/BrowsingTableInteractively.pm view on Meta::CPAN
reordering, etc.
5) **less**
Don't forget the good ol' Unix pager. You can render your table data as an ASCII
table (using modules like <pm:Text::Table::More>, <pm:Text::ANSITable>, or
<pm:Text::Table::Any> for more formats to choose from) then pipe the output to
it. At least with *less* you can scroll horizontally or perform incremental
searching (though not interactive filtering of rows).
6) **SQLite browser**, **SQLiteStudio**, or other SQLite-based front-ends
Another way to browse your table data interactively is to export it to SQLite
database then use one of the many front-ends (desktop GUI, web-based, TUI, as
well as CLI) to browse it. If you have your table data as a CSV, you can use the
<prog:csv2sqlite> script from <pm:App::SQLiteUtils> to convert it to SQLite
database.
<https://sqlitebrowser.org>
<http://sqlitestudio.pl>
6) **Microsoft Excel**, **LibreOffice**, or other spreadsheet programs
Yet another way to browse your table data interactively is to use a spreadsheet,
which offers a rich way to view and manipulate data. You can generate a CSV from
your table data; all spreadsheets support opening CSV files.
_
entries => [
{
module => 'Tickit::Widget::Table',
lib/Acme/CPANModules/BrowsingTableInteractively.pm view on Meta::CPAN
},
],
};
1;
# ABSTRACT: List of modules/tools for browsing table data interactively
__END__
=pod
=encoding UTF-8
=head1 NAME
Acme::CPANModules::BrowsingTableInteractively - List of modules/tools for browsing table data interactively
=head1 VERSION
This document describes version 0.009 of Acme::CPANModules::BrowsingTableInteractively (from Perl distribution Acme-CPANModules-BrowsingTableInteractively), released on 2023-06-15.
=head1 DESCRIPTION
This list reviews what tools are available on CPAN and in general to browse
table data interactively.
Let me say first that the best tools are not Perl-based since sadly Perl is not
a favorite choice for writing tools these days. That said, Perl is still a great
glue to help make those tools work together better for you.
1) B<Visidata>, L<https://www.visidata.org>
This is currently my favorite. It's terminal-based, written in Python, and has
more features than any other tools currently written in Perl, by far. vd has
support for many formats, including CSV, TSV, Excel, JSON, and SQLite. It makes
it particularly easy to create summary for your table like histogram or
sum/average/max/min/etc, or add new columns, or edit some cells. It also has
visualization features like XY-plots.
It has the concept of "sheets" like sheets in a spreadsheet workbook so anytime
you filter rows/columns or create summary or do some other derivation from your
data, you create a new sheet which you can edit, save, and destroy later as
needed and go back to your original table. It even presents settings and
metadata as sheets so you can edit them as a normal sheet.
It has plugins, and I guess it should be simple enough to create a plugin so you
can filter rows or add columns using Perl expression instead of the default
Python, if needed.
My CLI framework L<Perinci::CmdLine> (L<Perinci::CmdLine::Lite>, v1.918+)
has support for Visidata. You can specify command-line option C<--format=vd> to
browse the output of your CLI program in Visidata.
2) B<DataTables>, L<https://datatables.net>
DataTables is a JavaScript (jQuery-based) library to add controls to your HTML
table so you can filter rows incrementally, sort rows, reorder columns, and so
on. It also has plugins to do more customized stuffs. I still prefer Visidata
most of the time because I am comfortable living in the terminal, but I
particularly love the incremental searching feature that comes built-in with
DataTables.
My CLI framework L<Perinci::CmdLine> (L<Perinci::CmdLine::Lite>, v1.918+)
also has support for DataTables. You can specify command-line option
C<--format=html+datatables> to output your CLI program's result as HTML table
(using L<Text::Table::HTML::DataTables>) when possible and then browse the
output in browser.
3) B<Tickit::Widget::Table>, L<Tickit::Widget::Table>
lib/Acme/CPANModules/BrowsingTableInteractively.pm view on Meta::CPAN
There is currently no support beyond the most basic stuffs, so no column hiding,
reordering, etc.
5) B<less>
Don't forget the good ol' Unix pager. You can render your table data as an ASCII
table (using modules like L<Text::Table::More>, L<Text::ANSITable>, or
L<Text::Table::Any> for more formats to choose from) then pipe the output to
it. At least with I<less> you can scroll horizontally or perform incremental
searching (though not interactive filtering of rows).
6) B<SQLite browser>, B<SQLiteStudio>, or other SQLite-based front-ends
Another way to browse your table data interactively is to export it to SQLite
database then use one of the many front-ends (desktop GUI, web-based, TUI, as
well as CLI) to browse it. If you have your table data as a CSV, you can use the
L<csv2sqlite> script from L<App::SQLiteUtils> to convert it to SQLite
database.
L<https://sqlitebrowser.org>
L<http://sqlitestudio.pl>
6) B<Microsoft Excel>, B<LibreOffice>, or other spreadsheet programs
Yet another way to browse your table data interactively is to use a spreadsheet,
which offers a rich way to view and manipulate data. You can generate a CSV from
your table data; all spreadsheets support opening CSV files.
=head1 ACME::CPANMODULES ENTRIES
=over
view all matches for this distribution