Bigtop
view release on metacpan or search on metacpan
lib/Bigtop/Backend/SiteLook/GantryDefault.pm
lib/Bigtop/Backend/SQL.pm
lib/Bigtop/Backend/SQL/DB2.pm
lib/Bigtop/Backend/SQL/MySQL.pm
lib/Bigtop/Backend/SQL/Postgres.pm
lib/Bigtop/Backend/SQL/SQLite.pm
lib/Bigtop/bigtop.grammar
lib/Bigtop/Deparser.pm
lib/Bigtop/Docs/About.pod
lib/Bigtop/Docs/AutoBackends.pod
lib/Bigtop/Docs/Cookbook.pod
lib/Bigtop/Docs/FullKeywords.pod
lib/Bigtop/Docs/Modules.pod
lib/Bigtop/Docs/outliner
lib/Bigtop/Docs/QuickKeywords.pod
lib/Bigtop/Docs/QuickStart.pod
lib/Bigtop/Docs/Syntax.pod
lib/Bigtop/Docs/TentRef.pod
lib/Bigtop/Docs/TentTut.pod
lib/Bigtop/Docs/TOC.pod
lib/Bigtop/Docs/Tutorial.pod
docs/keyword_cookbook/controller/plugins/discussion view on Meta::CPAN
section. Use the one there to add default plugins for all controllers in the
application. Use the controller level version to affect only one
controller.
Note that if you have a global C<plugins> statement in the bigtop config
block, using a controller level C<plugins> statement replaces the
plugin list for the controller, so repeat any globals you still need.
All plugins must live in the C<Gantry::Plugins::> namespace, use only the
remainder of the module's package name in the C<plugins> statement.
For example, to use the AuthCookie plugin, say:
plugins AuthCookie;
The Control Gantry backend will prepend the Gantry plugin namespace.
C<plugins> statements only affect GEN modules, not stubs.
=head1 EXAMPLE
Build the example with:
bigtop -c example.bigtop all
Look for C<AuthCookie> in C<lib/Kids/GEN/Child.pm>. Also notice
the PluginNamespace and the namespace method.
docs/keyword_cookbook/controller/plugins/example.bigtop view on Meta::CPAN
field created {
is datetime;
}
field modified {
is datetime;
}
foreign_display `%name`;
}
controller Child is AutoCRUD {
# To use plugins:
plugins AuthCookie;
controls_table child;
rel_location child;
text_description child;
page_link_label Child;
method do_main is main_listing {
cols name, birth_day;
header_options Add;
row_options Edit, Delete;
title Child;
limit_by family;
lib/Bigtop/Docs/About.pod view on Meta::CPAN
=head1 Further Reading
With Bigtop's kickstart syntax, you can now build a complete CRUD app from
the command line alone. Similarly, if you have a postgres 8 database, you
can build a CRUD app for it from the command line. See
C<Bigtop::Docs::QuickStart> for details.
To start using Bigtop, see C<Bigtop::Docs::TentTut> or
C<Bigtop::Docs::Tutorial>.
If those go too fast, try the Bigtop section of C<Gantry::Docs::Tutorial>,
which builds a smaller app. After those, try C<Bigtop::Docs::Cookbook>.
For a complete doc list, see C<Bigtop::Docs::TOC>.
=head1 Why the Name
Why did I call it Bigtop? I see it as a central place in the sometimes
wild and always disparate world of a web application. It is where all
the perfomers come together. But it's also about as discriminating as
a circus tent, anyone and anything can easily come in and out. It's a big
tent. Oh, and it's meant to be fun (cue the circus music).
lib/Bigtop/Docs/Cookbook.pod view on Meta::CPAN
=head1 Name
Bigtop::Docs::Cookbook - Bigtop syntax by example
=head1 Intro
This document is meant to be like the Perl Cookbook with short wishes
you might long for, together with syntax to type in your bigtop file
and what that produces. In addition, many sections start
with a simple question about what gets built by the backend in question.
This document assumes you will be editing your bigtop file with a text
editor (it was written before tentmaker). You may also choose to
maintain your bigtop file with tentmaker. Generally, the advice here
governs what values you put in the boxes at the far right side of the
Backends tab in tentmaker. Some of the other advice must be applied
on the App Body tab. See L<Bigtop::Docs::TentTut> to get started with
lib/Bigtop/Docs/FullKeywords.pod view on Meta::CPAN
Bigtop::Docs::FullKeywords - Descriptions of all Bigtop keywords
=head1 Intro
This document is generated from C<Bigtop::Docs::Keywords>. It lists
each supported keyword available in the Bigtop language, just as tentmaker
would, but in POD form. See the beginning of C<Bigtop::Docs::Syntax>
for a general description of Bigtop source file structure. See
also C<Bigtop::Docs::TentTut>, which -- like this file -- draws from
C<Bigtop::Keywords>. You might also find C<Bigtop::Docs::Cookbook> useful.
=head1 Categories
Bigtop keywords come in many categories. Each subsection below describes
one category. Here is a brief description of where the keywords
from each categories appear in the Bigtop source file.
=over 4
=item config
lib/Bigtop/Docs/FullKeywords.pod view on Meta::CPAN
=item Default
No Templating
=back
=item plugins
List of Plugins i.e. AuthCookie Static
=item base_dir
DEPRECATED
parent of build dir
lib/Bigtop/Docs/QuickKeywords.pod view on Meta::CPAN
=head1 Intro
This document is generated from C<Bigtop::Docs::Keywords>. It is designed
to be compact. See C<Bigtop::Docs::FullKeywords> for more details.
See C<Bigtop::Docs::TOC> for an annotated list of all doc files.
config {}
engine - mod_perl 1.3, mod_perl 2.0, CGI, etc.
template_engine - Template Toolkit, Mason, etc.
plugins - List of Plugins i.e. AuthCookie Static
Example Backend Block:
SQL SQLite {}
See Bigtop::Docs::Backends for the backends whose blocks can go here.
app name {}
no_gen - Skip this app completely
location - Base Location of the app [defaults to /]
Do not use if you have a Base Controller.
authors - Who to blame for the app
contact_us - How to send complaints or join the project
lib/Bigtop/Docs/Syntax.pod view on Meta::CPAN
=head1 NAME
Bigtop::Docs::Syntax - An introduction to Bigtop syntax description
=head1 Intro
This document explains the basic structure of a bigtop file.
Note that you might find L<Bigtop::Docs::Cookbook> useful depending on
the complexity of your questions and how you like to use docs. For a
full list of Bigtop keywords, see L<Bigtop::Docs::FullKeywords>. A
shorter version is available in L<Bigtop::Docs::QuickKeywords>.
To know what each backend does, and how to configure them, see
L<Bigtop::Docs::AutoBackends>. All of those, except the cookbook,
are generated from the official source of Bigtop keywords (Bigtop::Keywords)
and so are up to date.
Other docs are available, including docs on tentmaker. See
L<Bigtop::Docs::TOC> for a complete list of documentation.
lib/Bigtop/Docs/TOC.pod view on Meta::CPAN
=item C<Bigtop::Docs::About>
Describes the features and motivations of Bigtop.
=item C<Bigtop::Docs::AutoBackends>
Documentation on each available backend and how to configure it. This
one is auto-generated, and is therefore more likely to be up to date.
=item C<Bigtop::Docs::Cookbook>
Modeled after the Perl Cookbook, this provides a list of things you might
want to do, the syntax needed to make Bigtop do them for you, and the
output produced by them. It focuses on hand written bigtop files, rather
than on tentmaker.
=item C<Bigtop::Docs::FullKeywords>
Documents all the valid keywords Bigtop understands by the block in
which they appear. This one is auto-generated and shows exactly the
same information as tentmaker.
lib/Bigtop/Docs/TentRef.pod view on Meta::CPAN
to your dbuser.
This concludes our exhaustive tour of tentmaker. I hope you are more
excited than exhausted.
'Consult Building and Starting' in C<Bigtop::Docs::TentTut> for instructions
on how to build your app once you have saved the above.
=head1 Further Reading
See C<Bigtop::Docs::Cookbook> for small problems and answers,
C<Bigtop::Docs::Tutorial> for a more complete example, with discussion,
C<Bigtop::Docs::AutoKeywords> for a list of valid keywords and their meanings,
and C<Bigtop::Docs::Sytnax> for more details. The above backend information
is repeated in shorter form in C<Bigtop::Docs::AutoBackends>, but that
document is more up to date. If you need to write your
own backends, see C<Bigtop::Docs::Modules>.
All of the doc modules are described briefly in C<Bigtop::Docs::TOC>.
=head1 Author
lib/Bigtop/Docs/TentTut.pod view on Meta::CPAN
You can continue to develop and regenerate as the model changes. The
only piece that is difficult to manage is the database once it is built.
=head1 Further Reading
See C<Bigtop::Docs::TentRef> for more details on what tentmaker can control.
For more command line options, including firing up tentmaker to build an
app based on an existing PostgreSQL 8 database, see
C<Bigtop::ScriptHelp::Style::Pg8Live>.
Try C<Bigtop::Docs::Cookbook> for small problems and answers,
C<Bigtop::Docs::Tutorial> for a more complete example, with discussion,
C<Bigtop::Docs::AutoKeywords> for details on all bigtop keywords
and C<Bigtop::Docs::Sytnax> for an explanation of bigtop file structure.
If you need to write your own backends, see C<Bigtop::Docs::Modules>.
All of the doc modules are described briefly in C<Bigtop::Docs::TOC>.
=head1 Author
Phil Crow
lib/Bigtop/Docs/Tutorial.pod view on Meta::CPAN
a short description of most of Bigtop syntax
=item Bigtop::Docs::QuickRef
an even shorter description of Bigtop syntax in an html table format
=item Bigtop::Docs::Syntax
a fairly complete picture of bigtop syntax
=item Bigtop::Docs::Cookbook
examples of what to type and what you get as a result
=back
=head1 Author
Phil Crow, E<lt>crow.phil@gmail.comE<gt>
=head1 Copyright and License
lib/Bigtop/Keywords.pm view on Meta::CPAN
type => 'select',
options => [
{ label => 'Template Toolkit', value => 'TT' },
{ label => 'No Templating', value => 'Default' },
],
sort_order => 20,
},
plugins => {
keyword => 'plugins',
label => 'Plugins',
descr => 'List of Plugins i.e. AuthCookie Static',
type => 'text',
sort_order => 30,
},
},
app => {
no_gen => {
keyword => 'no_gen',
label => 'No Gen',
descr => "Skip this app completely",
( run in 0.324 second using v1.01-cache-2.11-cpan-0d8aa00de5b )