A couple of weeks ago I asked for a show of hands to gather interest in restarting the Thames Valley Perl Mongers. The positive response we received is an encouraging sign that TVPMs are still out there (at least 30 of you) and interested in meeting up!
The meeting will be held on Wednesday 20th March at 7pm, and for this first occasion we hope to have two talks with a short break.
The venue is Reading Enterprise Centre on the University of Reading main campus. Refreshments and light snacks will kindly be provided on the evening by our hosts, …
After being dormant for longer than I can remember, the Thames Valley Perl Mongers mail list woke up recently when someone[1] offered to host a meeting.
I've put together a very short survey to work out how many might be interested. If you live in this corner of the UK and/or fancy coming along, please let us know:
http://www.surveymonkey.com/s/QNPF2V8
[1] the offer comes from ="_bl…
For App::fooapp type distributions then you might want the README etc generated from a specific file. Add this to dist.ini:
main_module = bin/fooapp
; btw, semicolon leads a comment, in case you forgot how to do that
Any Module::Install converts reading this should note the bin directory, not script.
In bin/fooapp itself you also provide an additional metadata hint (next to ABSTRACT):
# PODNAME: fooapp
Which results in nifty Metacpan links such as:
Finally this hint to the POD munger will allow a section to be pinned in place above the SYNOPSIS:
=begin :prelude
# POD here...
=end :prelude
I hope these tips are helpful to some…
For a couple of years I’ve been planning to rip apart and put back together the guts of Catalyst::Plugin::AutoCRUD, to address limitations in the initial implementation. After changing job and moving house I’m pleased this finally came to the top of my hacking stack.
Nothing was going to happen however before I could work out how to do one thing: achieve independence from DBIx::Class as a “storage engine”. I love DBIx::Class, but it would be much more cool to support any data storage system able to represent a table+column paradigm (even things like CSV, as a test case).
So SQL::Translator hit me like a thunderbolt. Of course, that’s exactly what it does - introspect some data storage and provide a neutral, class-based representation of the tables and columns (fields). It’s a little rough around the edges, but certainly good enough. The Translator provides a metadata structure which AutoCRUD’s web front-end can use, independent of any particular storage engine such as DBIx::Class. This also paves the way for development of display engines other than the bundled ExtJS and simple HTML offerings.
Right now there’s a developer release of AutoCRUD on CPAN, and I hope shortly to have a production release. Whilst the web side might not look much different, the fact is that it can now support significant features such as tables with composite/compound primary keys, or no primary keys for that matter, database views, relations to self, multiple relations to the same table, and so on.
Alongside that, I’ve taken the opportunity to fix a few quirks of the web interface, and chomp my way through the outstanding wishlist. The updated code is now running on a DotCloud instance, so please go and have a play!
p.s. a cron job will restore the demo’s databases at the top of every hour
You might have stumbled across Dist::Zilla's --trial command line option in the past, and maybe even used it for a developer CPAN release. Its effect is (as I understand it) two-fold:
- adds
-TRIAL to the name of the distribution archive being produced
- sets
release: testing in the META.json file which is parsed by CPAN services
It came to my attention that using -TRIAL is actually pretty bad for…
Computer Networks is my business, so Perl is my glue.