mojolicious::guides(3pm) [debian man page]
Mojolicious::Guides(3pm) User Contributed Perl Documentation Mojolicious::Guides(3pm) NAME
Mojolicious::Guides - Mojolicious guide to the galaxy DON'T PANIC! We are constantly working on new documentation, follow us on Twitter <http://twitter.com/kraih>, GitHub <http://github.com/kraih/mojo> or join the official IRC channel "#mojo" on "irc.perl.org" to get all the latest updates. LEARNING PERL
If you are new to Perl, we recommend Learn Perl in 2 hours 30 minutes <http://qntm.org/files/perl/perl.html> for a quick introduction, or the Modern Perl book <http://modernperlbooks.com/books/modern_perl/>, freely available in many formats. Both are excellent introductions to the language. For more books and documentation, check out learn.perl.org <http://learn.perl.org/>. TUTORIAL
Mojolicious::Lite A really fast and fun way to get started developing web applications with Mojolicious is the Mojolicious::Lite tutorial. Almost everything you learn there can also be applied to normal Mojolicious applications and is considered a prerequisite for the guides. You should definitely take a look! GUIDES
Mojolicious::Guides::Growing Starting a Mojolicious::Lite prototype from scratch and growing it into a well structured Mojolicious application. Mojolicious::Guides::Routing Simple and fun introduction to the Mojolicious router. Mojolicious::Guides::Rendering Generating content with the Mojolicious renderer. Mojolicious::Guides::Cookbook Cooking with Mojolicious, recipes for every taste. Mojolicious::Guides::FAQ Frequently asked questions with the right answers. Mojolicious::Guides::CodingGuidelines Coding guidelines and mission statement. A must read for developers and contributors! HIGHLIGHTS
Mojolicious and Mojolicious::Lite are the sum of many parts, small building blocks that can be used independently, these are the most prominent ones. Mojo::UserAgent Full featured non-blocking I/O HTTP 1.1 and WebSocket user agent. Mojo::DOM Very fun and minimalistic HTML5/XML DOM parser with CSS3 selector support. Mojo::JSON Minimalistic JSON implementation that just works. Mojo::Server::Daemon Highly portable non-blocking I/O HTTP 1.1 and WebSocket server with self-restart support through Mojo::Server::Morbo, perfect for development and testing. Mojo::Server::Hypnotoad Full featured UNIX optimized preforking non-blocking I/O HTTP 1.1 and WebSocket server with support for zero downtime software upgrades (hot deployment). Mojo::Server::CGI, Mojo::Server::PSGI Transparent CGI and PSGI support out of the box. Mojo::Template Very Perl-ish and minimalistic template system. Mojo::ByteStream Countless portable and very convenient bytestream manipulation methods. Mojolicious::Commands Pluggable command line system and the backbone of the mojo script. Test::Mojo Test driven development toolkit for web applications. ojo Fun oneliners using everything above. MORE
A lot more documentation and examples by many different authors can be found in the Mojolicious wiki at <http://github.com/kraih/mojo/wiki>. perl v5.14.2 2012-09-05 Mojolicious::Guides(3pm)
Check Out this Related Man Page
Mojolicious::Guides::CodingGuidelines(3pm) User Contributed Perl Documentation Mojolicious::Guides::CodingGuidelines(3pm) NAME
Mojolicious::Guides::CodingGuidelines - Coding guidelines OVERVIEW
This document describes the coding guidelines that are the foundations of Mojo and Mojolicious development. Please do not send patches unless you agree with them. MISSION STATEMENT
Mojo is a runtime environment for Perl real-time web frameworks. It provides all the basic tools and helpers needed to write simple web applications and higher level web frameworks such as Mojolicious. All components should be reusable in other projects and in a UNIXish way only loosely coupled. Especially for people new to Perl it should be as easy as possible to install Mojolicious and get started. Writing web applications can be one of the most fun ways to learn a language! For developers of other web frameworks it should be possible to reuse all the infrastructure and just consider the higher levels of the Mojolicious distribution an example application. RULES
Web development should be easy and fun, this is what we optimize for. The web is a moving target, to stay relevant we have to stay in motion too. Keep it simple, no magic unless absolutely necessary. The installation process should be as fast and painless as possible. (Less than a minute on most common hardware is a good rule of thumb) The addition and modification of features is decided by majority vote or the pumpking. Any core developer may nominate a new one, who must then be accepted by a 2/3 majority vote. The pumpking has veto rights and may select his successor. It's not a feature without a test and documentation. A feature is only needed when the majority of the userbase benefits from it. Features may only be changed in a major release or after being deprecated for at least 3 months. Refactoring and deprecations should be avoided if no important feature depends on it. New features can be marked as experimental to be excluded from deprecation policies. A major release is signaled by a new major version number and a unique code name based on a unicode character. Only add dependencies if absolutely necessary and make them optional if possible. Domain specific languages should be avoided in favor of Perl-ish solutions. No inline POD. Documentation belongs to the guides, module POD is just an API reference. The main focus of the included documentation should be on examples, no walls of text. (An example for every one or two sentences is a good rule of thumb) Everything should be ordered alphabetically if possible. The master source code repository should always be kept in a stable state, use feature branches for actual development. Code has to be run through Perl::Tidy with the included ".perltidyrc", and everything should look like it was written by a single person. Code should be organized in blocks and those blocks should be commented. No spaghetti code. Comments should be correctly capitalized, and funny if possible, punctuation is optional if it doesn't increase readability. Every file should contain at least one quote from "The Simpsons" or "Futurama". No names outside of "Mojolicious.pm". No Elitism. Peace! MORE
You can continue with Mojolicious::Guides now or take a look at the Mojolicious wiki <http://github.com/kraih/mojo/wiki>, which contains a lot more documentation and examples by many different authors. perl v5.14.2 2012-09-05 Mojolicious::Guides::CodingGuidelines(3pm)