Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse files

renamed Mojo::Manual to Mojolicious::Book

  • Loading branch information...
commit 8ea5ba2fafb2fc0f6afdfa539af51419f8594962 1 parent 87c27a5
Sebastian Riedel authored
View
1  Changes
@@ -23,6 +23,7 @@ This file documents the revision history for Perl extension Mojo.
- Added input streaming support to Mojo::Content.
- Added client, param, pause, redirect_to and resume to
Mojolicious::Controller.
+ - Renamed Mojo::Manual to Mojolicious::Book.
- Updated Mojolicious lite_app generator to use .ep templates.
- Fixed many bugs in the HTTP 1.1 state machine and added the ability
to pause transactions.
View
2  lib/Mojo.pm
@@ -108,7 +108,7 @@ Currently there are no requirements besides Perl 5.8.1.
| CGI | | FastCGI | | HTTP 1.1 |
'------------------' '------------------' '------------------'
-For userfriendly documentation see L<Mojo::Manual>.
+For user friendly documentation see L<Mojolicious::Book>.
=head1 ATTRIBUTES
View
119 lib/Mojo/Manual.pod
@@ -1,119 +0,0 @@
-# Copyright (C) 2008-2009, Sebastian Riedel.
-
-=head1 NAME
-
-Mojo::Manual - Manual
-
-=head1 SECTIONS
-
-=over 4
-
-=item L<Mojo::Manual::GettingStarted>
-
-Step by step instructions to get you started with L<Mojo>.
-
-=over 4
-
-=item * Installation
-
-=item * Running the development server
-
-=item * Writing your first micro application and testing it
-
-=back
-
-=item L<Mojo::Manual::Transaction>
-
-Everything in L<Mojo> was built around the idea of processing HTTP requests
-as transactions.
-
-=over 4
-
-=item * HTTP Messages
-
-=item * Request
-
-=item * Response
-
-=item * Cookies
-
-=item * Parameters
-
-=item * Content
-
-=back
-
-=item L<Mojo::Manual::Deployment>
-
-Running L<Mojo> applications in different environemnts.
-
-=over 4
-
-=item * Designed for portability
-
-=item * Built in servers
-
-=item * CGI
-
-=item * FastCGI
-
-=item * Easy to extend
-
-=back
-
-=item L<Mojo::Manual::Mojolicious>
-
-Introduction to L<Mojolicious>, the L<Mojo> example web framework.
-
-=over 4
-
-=item * The MVC design pattern
-
-=item * Application class
-
-=item * Dispatchers
-
-=item * Controllers
-
-=item * Routes
-
-=item * Renderer and templates
-
-=item * Modes
-
-=back
-
-=item L<Mojo::Manual::MojoliciousExample>
-
-Building your first real web application with L<Mojolicious>, a POD reader.
-
-=over 4
-
-=item * Directory structure
-
-=item * Model
-
-=item * Controller
-
-=item * Templates
-
-=item * Testing
-
-=back
-
-=item L<Mojo::Manual::Cookbook>
-
-Cooking with L<Mojo> and L<Mojolicious>!
-
-=item L<Mojo::Manual::FAQ>
-
-If you have a question, look here first.
-
-=item L<Mojo::Manual::CodingGuidelines>
-
-Coding guidelines and mission statement.
-A must read for developers and contributors!
-
-=back
-
-=cut
View
78 lib/Mojo/Manual/CodingGuidelines.pod
@@ -1,78 +0,0 @@
-# Copyright (C) 2008-2009, Sebastian Riedel.
-
-=head1 NAME
-
-Mojo::Manual::CodingGuidelines - Coding Guidelines
-
-=head1 OVERVIEW
-
-This document describes the coding guidelines that are the foundations
-of Mojo development.
-
-Please don't send patches unless you agree with them.
-
-=head1 MISSION STATEMENT
-
-Mojo is a Perl web framework that provides all the basic tools and helpers
-needed to write simple web applications and higher level web frameworks.
-
-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 Mojo and get started.
-Writing web applications can be one of the most fun ways to learn a language!
-
-For other framework developers it should be possible to reuse all the
-infrastructure and just consider the higher levels of Mojo an example
-application.
-
-=head1 RULES
-
-=over 4
-
-Keep it simple, no magic unless absolutely necessary.
-
-Code should be written with a Perl6 port in mind.
-
-No refactoring unless a very important feature absolutely depends on it.
-
-It's not a feature without a test.
-
-A feature is only needed when the majority of the userbase benefits from it.
-
-Features may not be changed without being deprecated for at least one major
-release.
-
-Deprecating a feature should be avoided at all costs.
-
-Only add prereqs if absolutely necessary.
-
-Domain specific languages should be avoided in favor of Perl'ish solutions.
-
-No inline POD.
-
-Documentation belongs to the manual, module POD is just an API reference.
-
-Lines should not be longer than 78 characters and we indent with 4
-whitespaces.
-
-Code should be run through L<Perl::Tidy> with the included C<.perltidyrc>.
-
-No spaghetti code.
-
-Code should be organized in blocks and those blocks should be commented.
-
-Comments should be funny if possible.
-
-Every file should contain at least one quote from The Simpsons or Futurama.
-
-No names outside of the CREDITS section of Mojo.pm.
-
-No Elitism.
-
-Peace!
-
-=back
-
-=cut
View
7 lib/Mojo/Manual/Cookbook.pod
@@ -1,7 +0,0 @@
-# Copyright (C) 2008-2009, Sebastian Riedel.
-
-=head1 NAME
-
-Mojo::Manual::Cookbook - Cookbook
-
-=cut
View
7 lib/Mojo/Manual/Deployment.pod
@@ -1,7 +0,0 @@
-# Copyright (C) 2008-2009, Sebastian Riedel.
-
-=head1 NAME
-
-Mojo::Manual::Deployment - Deployment
-
-=cut
View
37 lib/Mojo/Manual/FAQ.pod
@@ -1,37 +0,0 @@
-# Copyright (C) 2008-2009, Sebastian Riedel.
-
-=head1 NAME
-
-Mojo::Manual::FAQ - Frequently Asked Questions
-
-=head1 QUESTIONS
-
-=head2 Do i have to use L<Mojo::Base>?
-
-Absolutely not, you could just use any other accessor generator in your
-modules, L<Mojo::Base> is just a minimalistic base class and will stay out of
-your way.
-
-=head2 Do i have to use L<Mojo::Template>?
-
-Not at all, it is just a convenient default option and can be replaced with
-any other template engine out there.
-
-=head2 Why do my programs break if i use C<content> instead of C<body>?
-
-The C<content> attribute of L<Mojo::Message> has to contain a special
-L<Mojo::Content> object which offers advanced HTTP body manipulation
-functions.
-The C<body> method is a wrapper around that and what you will want to use in
-most cases.
-
- $tx->res->body('Hello World!');
-
-If you want to send a file for example, then C<content> would be the right
-choice.
-
- my $asset = Mojo::Asset::File->new;
- $asset->path('/etc/passwd');
- $tx->res->content->asset($asset);
-
-=cut
View
7 lib/Mojo/Manual/GettingStarted.pod
@@ -1,7 +0,0 @@
-# Copyright (C) 2008-2009, Sebastian Riedel.
-
-=head1 NAME
-
-Mojo::Manual::GettingStarted - Getting Started
-
-=cut
View
7 lib/Mojo/Manual/Mojolicious.pod
@@ -1,7 +0,0 @@
-# Copyright (C) 2008-2009, Sebastian Riedel.
-
-=head1 NAME
-
-Mojo::Manual::Mojolicious - Mojolicious
-
-=cut
View
7 lib/Mojo/Manual/MojoliciousExample.pod
@@ -1,7 +0,0 @@
-# Copyright (C) 2008-2009, Sebastian Riedel.
-
-=head1 NAME
-
-Mojo::Manual::MojoliciousExample - A Mojolicious Example
-
-=cut
View
7 lib/Mojo/Manual/Transaction.pod
@@ -1,7 +0,0 @@
-# Copyright (C) 2008-2009, Sebastian Riedel.
-
-=head1 NAME
-
-Mojo::Manual::Transaction - Transactions
-
-=cut
View
2  lib/Mojolicious.pm
@@ -172,7 +172,7 @@ Mojolicious - Web Framework
L<Mojolicous> is a MVC web framework built upon L<Mojo>.
-For userfriendly documentation see L<Mojo::Manual::Mojolicious>.
+For userfriendly documentation see L<Mojolicious::Book>.
=head1 ATTRIBUTES
View
13 lib/Mojolicious/Book.pod
@@ -0,0 +1,13 @@
+# Copyright (C) 2008-2009, Sebastian Riedel.
+
+=head1 NAME
+
+Mojolicious::Book - Modern Web Development With Perl And Mojolicious
+
+=head1 STATUS
+
+This book is currently being written, to get status updates and/or read
+early drafts you can visit L<http://labs.kraih.org> and
+L<http://twitter.com/kraih>.
+
+=cut
Please sign in to comment.
Something went wrong with that request. Please try again.