The HTML::FormFu module is well known enough to be mentioned in detail in both published Catalyst books. Despite a reasonable learning curve, once mastered saves enormous time in creating web-based forms.
The author/maintainer, Carl (aka fireartist), has been nice enough to allow me to get involved and I have pulled in a number of patches that kind people have submitted via github and RT. Only minor changes thus far, but it's great to have something so useful that people take time to tweak, fix and repair it - then submit their changes for inclusion. I am readying a release for the near future.
Which brings me to the point of my post.
If you or your organization are harboring some fixes or enhancements to HTML::FormFu, please send them through for inclusion via https://github.com/fireartist/HTML-FormFu
When I click on "login" from the front page and type in my username & password, I get a "Permission denied." error message. If I need to log in, I have to reset my password, and then I'm logged in.
Maybe you are already registered for this year’s MojoConf in New York City (June 4th-6th) or maybe you are still thinking about it. Either way, a great way to introduce yourself to the Mojolicious community is to give a talk! But what should you talk about? The cool stuff you do with Mojolicious!
Last years talks were on a wide range of topics. When I write a talk, I usually write really technical talks; I’m always trying to pack too much code into each slide. But when I’m in the audience, the ones that really knock my socks off are the ones I don’t expect.
Last year, Rich Elberger (this year’s host, incidentally) gave a talk that took me completely by surprise, he’s gaining traction using Mojolicious in an Enterprise system! How cool is that?!
I was reviewing some code I had written for a simple RPG dice algorithm (although there's already a good module for this, Game::Dice) and I realized again that I have a prefererence for functions that can fit on one screen. One strategy is breaking up the code into smaller routines but I sometimes like to compact it vertically as much as possible first.
This function roll, given a string of "dice language," should return the results of such a dice roll. An example of this would be "3d10+1" to roll three 10-sided dice and then add 1, or "4d6b3" which says to roll four 6-sided dice and take the best three.
Just to tell that there is another regexp engine coming out, re::engine::GNU. that will hopefully show how perl's regexp facility is well done, thanks to its perlreapi.
This library will bring into perl POSIX BRE, Gnu Emacs, AWK regexps etc...
The funny thing is that I took the liberty to exploit what perlreapi says: "Since any scalar can be passed as a pattern, it's possible to implement an engine that does something with an array etc...". The idea is have a default syntax (GNU Emacs), and to use an array or a hash at the right-hand side to specify the syntax of the regular expression string, i.e.:
There are now 6 courses:
4 1-day courses (From Zero to Perl, Introduction to Moose, Introduction to Go, and Programming the web with Dancer),
A 1/2 day course about Practical Career Development for Perl Developers,
and a 2-day course about front-end development using HTML5/CSS3/JavaScript, Twitter Bootstrap, Handlebars, and AngularJS with some Dancer back-end development.
For details and registration check out the Master classes.
So this year the YAPC::BR will be held at Taubaté - SP, of course in Brazil. I' m one of the hosts and we are moving forward to make a nice event.
The dates were decided during the last YAPC but I delayed this post and all English information until I payed the Hotel from venue and are 100% ok with the date. So in 18th to 20th of September this year we have another Perl conference.
The theme of event is CPAN and Perl Community. I mainly get inspired by guru at the end of YAPC::BR last year when everybody was induced to publish a module on CPAN. We brazilians are kind of shy to publish modules so make the event around it should be useful and fun.
This year YAPC::EU conference will be happening at the beginning of September and we don't want you to spend your summer thinking about what could you be presenting in Granada, so we set the call for proposals deadline on June 30.
There already almost 30 talks accepted that amount more than 15 hours of interesting stuff for the more than 100 people that have already registered. What are you waiting to submit your proposal?
Would you like to organize any kind of training course instead? Please, see our call for instructors.
Well I have said it in the past I!=SysAdmin and with the problems I have had of late I think I might as well share with other so they will not have the same three very bad days I just had.
To make a short story a little longer it started when the development box I usually work-with was rebuild after a fatal crash on the rather tired box it was on.
Things where fine on the new box the old code worked and we seemed to see no problems a few runs of cpanm would not fix. The problems started after we got caught up with the backed up day to day production fixes and I started to play with some new things that I am using.
The excellent Travis Perl helpers make it easy submit automated coverage reports to Coveralls whenever you commit to GitHub. All that's needed is to set the COVERAGE environment variable.
Unfortunately, this doesn't include the XS portions of a module. But since Devel::Cover already supports XS modules out of the box, only a slight change is needed to make it work. Simply make the Travis Perl helpers compile and link your XS code with the GCC --coverage option. (You often see the equivalent -fprofile-arcs -ftest-coverage used instead, but GCC supports --coveragesince version 4.1.0.)
Here's a quick fix that enables XS coverage reports for EU:MM based modules.
Coverage reports for XS code often contain unwanted header files in Perl's CORE directory that you might want to ignore. This commit passes options from the COVERAGE_OPTS environment variable to the cover tool. For example, you could set the variable like this:
This is not the official announcement, but I hope the organizers will forgive me for running ahead a bit.
As has been in previous years, there are going to be so called Master classes during the days before and after YAPC::NA. There are currently 4 courses listed. 3 1-day courses and a 2-day course (mine).
I don't know about the others, but for me, it is quite expensive to get to YAPC, and thus I can only afford to visit YAPC and run the course if it covers my expenses.
Therefore the course will only take place if there is a certain minimum number of students.
In order to make the decision easier for you, there is also an early-bird discount for the course I run and in the unlikely case that I won't be able to run the course your payment will be refunded by the organizers.
I recently took over maintenance of File::Which in order to fix some outstanding bugs. For those that are unawares, File::Which implements the unix capability of the which command as a portable Perl API. This allows you to search for commands in the system PATH, without actually needing to execute them. It takes the various idiosyncrasies of your platform into account so you don’t have to think about them. It also provides a command line interface called pwhich.
I put off my talk submission for the German Perl Workshop for some time, mostly because I was not satisfied with the ideas and code I had. But I just submitted my talk proposal, which is to show how to compile and use Perl on Android. The Perl documentation seems quite simple and using it and the documentation online led me to an almost working Perl. What really surprised me was how fast my (Snapdragon 801-powered) phone was at compiling Perl.
The talk will touch compiling a custom Perl, platform peculiarities of Android, using modules from CPAN (and patching them so they work on Android), and hopefully also a working program to tunnel DLNA from my home network to the network where my phone currently is present.
I hope that I can change the talk from being a presentation to something that has a bit of workshop to it, but I'm not yet sure how to best integrate the audience. Maybe I can convince people with a rooted phone to compile Perl on their phone before the talk starts...
When I transitioned from using Perl as a systems engineer, systems administrator ... etc. etc. to working as a full-time developer I was upset to discover the local Perl mongers group fizzled out a long time ago. The last post on the mailing list was about free training from Erols.com (remember that company??? WOW!?) Needless to say that's some old stuff ...
I was psyched to get things going again so I set out to figure out how to do things the proper way and assume the role as the group organizer. For those of you in a similar position I hope this post helps you!
The first thing I did was post to the mailing list and through the other communications channels to determine if anyone was still lurking.
After confirming there weren't any lurkers or other people with an interest in resurrecting the group that could help me, I looked at the Perl Mongers FAQ which pointed me to the #mongers IRC channel on irc.perl.org.
In response to sending out the Perl Weekly I've already received two e-mails from people asking if I got information about
DC-Baltimore Perl Worksop
that will take place on April 11. Presumably they wanted us to include it in the Perl Weekly newsletter.
The fact that people reach out to the editors of the Perl Weekly is lightyears better than people who just expect us to know about every event and to promote them, but we cannot do much with the events without some news.
I pointed both of them to the list of Perl Events where the DCBPW is already listed and I told both of them that if they would like to promote the workshop (which is a very positive thing by itself), and if they would like it to be included in the Perl Weekly, they need to generate some news item.
It does not need to be earth shattering, just something we can use as an excuse to talk about the event.
I put together a page on promoting Perl events, in case you need ideas what to write about.
Or you can just write about something else and link to the event as I just did above.
