Well not really but it did save me a good deal of time. I have been slowly putting together a small stand alone web app with Mojolicious to trunly demonstate what I have been doing with all these Moose posts.
Well I was just setting up a controller (using Mojolicious::Lite here to save space) and was creating my first form and like I many I have created before I started with a validator; something like this
Sadly Perl Hardware has been off to an incredibly slow start but his YAPC::NA I want to really give it a big kick to get going. In those efforts I need help. I am offering a free Bus Pirate v4 to anyone that will write a CPAN module and blog post about it. This would need ready by June 1 for YAPC::NA. Binary scripting mode examples that may help you get started.
If you are already doing something cool with perl and a Bus Pirate please share.
Ideally, if a syntax is useful and clear,
and a programmer can easily read it at a glance,
you should be able to add it to an existing language.
In this post, I will describe
a modest incremental change to the Perl syntax.
It's one I like, because that's beside the point, for two
reasons.
First, it's simply intended as an example of language evolution.
Second, regardless of its merits, it is unlikely to happen,
because of the way that Perl 5 is parsed.
In this post I will demonstrate a way of writing a parser,
so that this change,
or others, can be made in a straightforward way,
and without designing your language into a corner.
Although YAPC::Europe::2014 preparations are well underway in Sofia,
it is time for the venue committee of the YAPC::Europe Foundation (YEF)
to think about the location of the 2015 conference. YAPC::Europe wouldn’t
exist without dedicated teams of volunteers, and we are always excited
to see the enthusiasm and learn about the new ideas the community has to
offer.
Further information about preparing a complete application can be found
on http://www.yapceurope.org/organizers/index.html . Proposals
submitted to the venue committee will be added to this public repository
(you may provide private information separately) to benefit future
organizers.
The deadlines which apply to this portion of the procedure are:
Friday, 25 April: Deadline for sending a letter of intent.
This letter simply expresses interest in hosting the conference and
provides contact information (both email and telephone) for at least two
organizers. This is an optional step but it can be to your advantage to
alert the venue committee of your proposal.
Monday, 7 July: Deadline for sending proposals to host YAPC::Europe 2015.
If you do not receive a confirmation for your letter of intent or
proposal within a couple of days, please personally contact a member of
the venue committee.
Please send your questions, letters of intent, and proposals to
venue@yapceurope.org.
As most of the readers on this blog know that my sys-admin skills are not on the high side. Well also one thing that I am very poor at is regexes. I know I hold my head in shame in this, I just never used them very much and most of my programming hasn't been in the area of text processing so I have never use them very much.
Most of the time when I run into a regex I can figure out what is going on but when the complex ones come into play I am just flustered.
As I was spending some time updating the list of MetaCPAN sponsors, it occurred to me that we had not listed the QA Hackathon as one of our sponsors. I came to realize that this was a fairly significant omission since, if you run the numbers, the QA Hackathon is one of our biggest sponsors. The hackathon has sponsored a MetaCPAN hacker for 3 years now. 2011 (Amsterdam), 2012 (Paris) and 2014 (Lyon). The 2012 and 2014 sponsorships involve me flying across the Atlantic and all 3 years involved hotels, meals, etc. If you take all that together, it really adds up.
Announcing the first Czech Perl Workshop, which will be held on 20th-21st of May 2014 in Prague, hotel Jurys Inn. Call for papers closed on 25th of March for english presentations (1st of April for czech ones).
Still exploring the MooseX name-space these days and today I was going to have a look at 'MooseX::YAML' as that was the format I was saving my AD&D data in it (for the time being) I thought it might be a good fit to load things up faster or at least save me some code in writing a YAML parse role.
Hi All! It's still in alpha stage, but anybody is welcome to try it out. Pjam provides standard continues integration server api with additional features:
checks out source code from subversion VCS
creates builds
keeps artefacts
notifies users on successful / failed builds
shows differences between builds
shows users activity log - who, what and when changed
shows build's detailed logs
and more ...
Pjam uses pinto to handle cpan dependencies, Pjam is a rails application. Sqlite or mysql database engine may be used as data storage. Check out more on
https://github.com/melezhik/pjam-on-rails
I've created a first proof-of-concept for a 'CPAN Dashboard'. I want a summary of all my dists, with all sorts of information per dist, and with dists presented in the order of 'needing something done'. I'm hoping something like this could be added to MetaCPAN.
More details, and a list of ideas for inclusion, can be found on my blog. Any and all suggestions very welcome - I'm going to bounce ideas around with Olaf later this week.
Putting this down here both for the public and for myself as a reminder.
I still run ActivePerl v12, both because our production servers are at that version and because i see a lot of windows users at that version and lower. I use CPAN a lot and do tend to find obscure issues that break modules on v12 or cause incompatibilities.
However there's a fairly big stone in the way when going that path, since ActiveState has followed their rolling lockdown policy and with the release of Pumpkin Perl v18 locked the PPM servers for v12 (and below) to the public, leaving them only accessible to paying business customers. So i ended up having to compile it manually and this time managed to navigate the maze and figure out the right incantations.
One part of AD&D that I allays loved and why I played it for so long was its story telling nature. I can't tell you how many reams of paper myself and the rest of us players and DMs produced in our epic mutil-year game, Still have a few stuffed upstairs in the attice where they where shoved after life caught up with me and my cohorts and the joys or, wives, husband, jobs, houses and kids overtook our game.
It was the 'in-character' and 'NPC' conversions that where always best as some of my fellow players where very good at it. One player what an expert at imitating a ranting nut bar that may or may not have some good info for the party a.k.a. 'the old man from scene 24'.
Well I was wondering if there as a way to add this sort of thing into my game rather than the rather stale, tablets or very expensive 'cut out' videos many of todays games.
Well it is time to make a choice! I started with three and took another good look at was available in the MooseX space on CPAN today and didn't see anything else that I think would do what I want. Though I was quite interested in Moose::Templated until I figured out it was a template system for rendering content utilizing roles rather that what I was looking for a template system to create roles and classes.
Anyway back to my choice.
At least it was easy to eliminate MooseX::ClassCompositor as it did not do what I wanted though I could see it use some-where else. To use it I would have to trash a good deal of code and have no 'Base' class just roles. Well AD&D is just a little too static for that but if I had a very large number of characters and classes like in the 5thEd. I might start out that way.
This is part 13 (and the final installment) of an ongoing series where I explore my relationship with Perl. You may wish to begin at the beginning.
This week we look at what comes next.
I suppose at the end of any long rumination on the past, it’s only natural to think about the future. I’ve tended to avoid pontificating on Perl’s prospects for a number of reasons, not the least of which is that I don’t have any special knowledge to share. I’m not an author of Perl books, a contributor to the Perl core, or even a particularly prolific creator or maintainer of CPAN modules.1 I don’t have any inside knowledge of Perl from hanging out with Larry, or the folks that run the Perl Foundation, or the current Pumpking (nor any past ones, for that matter). I’m just a regular Joe JAPH—admittedly one who has made his living off Perl for 17 years, well enough to support a nice house in southern California and a complement of five humans, three cats, one guinea pig, and a tank full of tropical fish, snails, and shrimp—but just a working schmoe nonetheless, whose opinion isn’t any better or smarter or wiser or more likely to be true than yours. So, you should definitely not listen to me.
Depending on the application, a person may have no name at all -- think about hospitals and automobile accidents, for example.
Thinking carefully about what name or names you need. Is this name for display to the user? Does it have to be used for email or postal mail? Should the name be sortable? There are lots of issues to consider.