From: Dave Rolsky <autarch@urth.org>
Date: Tue, 29 Jul 2008 18:05:03 +0000 (+0000)
Subject: add the welcome to the meta-world "recipe" - more of an intro than a recipe
X-Git-Tag: 0_55~26
X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=17a65b17069faa1f01c9e7edc1c9d7c38db23a05;hp=58d129ba26b341e29238a6e6563e84d5c77c71ae;p=gitmo%2FMoose.git

add the welcome to the meta-world "recipe" - more of an intro than a recipe
---

diff --git a/MANIFEST b/MANIFEST
index d83b67f..d9feae4 100644
--- a/MANIFEST
+++ b/MANIFEST
@@ -23,6 +23,7 @@ lib/Moose/Cookbook/Basics/Recipe6.pod
 lib/Moose/Cookbook/Basics/Recipe7.pod
 lib/Moose/Cookbook/Basics/Recipe9.pod
 lib/Moose/Cookbook/FAQ.pod
+lib/Moose/Cookbook/Meta/Recipe1.pod
 lib/Moose/Cookbook/Meta/Recipe2.pod
 lib/Moose/Cookbook/Meta/Recipe3.pod
 lib/Moose/Cookbook/Roles/Recipe1.pod
diff --git a/lib/Moose/Cookbook.pod b/lib/Moose/Cookbook.pod
index 7554aa4..02adb27 100644
--- a/lib/Moose/Cookbook.pod
+++ b/lib/Moose/Cookbook.pod
@@ -100,7 +100,7 @@ I<abstract goes here>
 
 =over 4
 
-=item L<Moose::Cookbook::Meta::Recipe1> - Welcome to the meta-world (TODO)
+=item L<Moose::Cookbook::Meta::Recipe1> - Welcome to the meta-world (Why Go Meta?)
 
 I<abstract goes here>
 
diff --git a/lib/Moose/Cookbook/Meta/Recipe1.pod b/lib/Moose/Cookbook/Meta/Recipe1.pod
new file mode 100644
index 0000000..37aac8c
--- /dev/null
+++ b/lib/Moose/Cookbook/Meta/Recipe1.pod
@@ -0,0 +1,67 @@
+
+=pod
+
+=head1 NAME
+
+Moose::Cookbook::Meta::Recipe1 - Welcome to the meta world (Why Go Meta?)
+
+=head1 SUMMARY
+
+If you've ever found yourself thinking "Moose is great, but I wish it
+did X differently", then you've gone meta. The meta recipes are all
+about how to change and extend the way Moose does its thing, by
+changing how the various meta classes (C<Moose::Meta::Class>,
+C<Moose::Meta::Attribute>, etc) work.
+
+The metaclass system is a set of classes that describe classes, roles,
+attributes, etc. The metaclass API lets you ask questions about a
+class, like "what attributes does it have?", or "what roles does the
+class do?"
+
+The metaclass system also lets you actively make changes to a class,
+for example by adding new methods.
+
+The interface with which you normally use Moose (C<has>, C<with>,
+C<extends>) is just a thin layer of syntactic sugar over the
+underlying metaclass system.
+
+By extending and changing how this metaclass system works, you can in
+effect create a modified object implementation for your classes.
+
+=head2 Examples
+
+Let's say that you want to additional properties to
+attributes. Specifically, we want to add a "label" property to each
+attribute, so we can write C<<
+My::Class->meta()->get_attribute('size')->label() >>. The first two
+recipes show two different ways to do this, one with a full
+meta-attribute subclass, and the other with an attribute trait.
+
+You might also want to add additional properties to your
+metaclass. For example, if you were writing an ORM based on Moose, you
+could associate a table name with each class via the class's metaclass
+object, letting you write C<< My::Class->meta()->table_name() >>.
+
+=head1 SEE ALSO
+
+Many of the MooseX modules on CPAN implement metaclass extensions. A
+couple good examples include C<MooseX::Singleton> and
+C<MooseX::AttributeHelpers>. For a more complex example see
+C<Fey::ORM>.
+
+=head1 AUTHOR
+
+Dave Rolsky E<lt>autarch@urth.org<gt>
+
+=head1 COPYRIGHT AND LICENSE
+
+Copyright 2008 by Infinity Interactive, Inc.
+
+L<http://www.iinteractive.com>
+
+This library is free software; you can redistribute it and/or modify
+it under the same terms as Perl itself.
+
+=cut
+
+